secure-saas
Skill2 starsChanged 33 days agoApache-2.0View on GitHub
Audit SaaS and identity-provider security posture — scan GitHub, GitLab, Okta, Google Workspace, Microsoft 365, Slack, Atlassian, and Snowflake with cnspec for access, MFA, sharing, and configuration risks, mapped to compliance. Use to check a SaaS tenant, org, or identity provider's settings.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- author-detectionsSkill
- fix-findingsSkill
- secure-ai-servicesSkill
- secure-cloudSkill
- secure-codingSkill
- secure-osSkill
- secure-pipelineSkill
- triage-findingsSkill
- understand-codeSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Check whether a SaaS tenant or identity provider is configured securely, by running cnspec against its API.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Secure SaaS
Check whether a SaaS tenant or identity provider is configured securely, by running cnspec against its API. You ask "is our GitHub org / Okta tenant / Google Workspace hardened?" and this skill picks the right scan; cnspec carries the policies.
When to use
- Auditing a source-control org (GitHub / GitLab): branch protection, 2FA enforcement, repo visibility, token/app policies.
- Auditing an identity provider (Okta, Microsoft 365, Google Workspace): MFA, admin roles, session and sharing settings.
- Auditing collaboration / data SaaS (Slack, Atlassian, Snowflake) for access and config risks.
What cnspec checks
- Source control —
mondoo-github-security,mondoo-github-best-practices,mondoo-gitlab-security - Identity / productivity —
mondoo-okta-security,mondoo-m365-security,mondoo-google-workspace-security - Collaboration / data —
mondoo-slack-security,mondoo-atlassian-security,mondoo-snowflake-security
Run a scan
cnspec scan github --organization <org> -o sarif # requires a GitHub token
cnspec scan okta -o sarif # requires Okta org + API token
cnspec scan ms365 -o sarif # requires an Entra ID app registration
cnspec scan google-workspace -o sarif # requires a service account
cnspec scan slack -o sarif # requires a Slack token- Each provider authenticates with that SaaS's API credentials — the exact flags/env for token, org, and app registration are in the cnspec docs per provider.
- Logged in to Mondoo Platform, assigned policies run automatically; otherwise
--incognito -f <bundle>. -o sariffor a CI gate; cnspec exits non-zero on failures.
Reference, don't duplicate
cnspec owns the policies and authoring (see the cnspec repo). This skill invokes cnspec and interprets results — it does not reimplement policy.
Compliance
SaaS policies map to CIS benchmarks (where published), SOC 2, ISO 27001, and vendor best practices — a scan doubles as a compliance check.
Part of the secure-your-stack toolkit
secure-saas is the SaaS & identity pillar of posture, alongside secure-os (hosts),
secure-cloud (cloud accounts), and secure-ai-services (AI). Needs cnspec
(install) plus API credentials for the target SaaS.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

