continuous-control-monitoring
Skill0 starsChanged 15 days agoMITView on GitHub
Implement continuous control monitoring (CCM) — automated, scheduled checks of security controls via APIs and policy engines (AWS Config/Security Hub, Azure Policy, GCP Org Policy, IdP and EDR reports, Steampipe/Powerpipe, OPA), thresholds, alerting, evidence retention and dashboards. Use when automating compliance evidence, replacing point-in-time audits with ongoing assurance, or building control health dashboards.
In this repository273 other files it gives its agents.
- ad-attack-path-analysisSkill
- adcs-security-reviewSkill
- ad-privileged-access-reviewSkill
- dcsync-detectionSkill
- gpo-security-reviewSkill
- kerberos-attack-detectionSkill
- agent-tool-permission-reviewSkill
- ai-incident-responseSkill
- llm-gateway-controlsSkill
- llm-security-evaluationSkill
- mcp-server-security-reviewSkill
- model-artifact-securitySkill
- prompt-injection-reviewSkill
- rag-security-reviewSkill
- api-abuse-detectionSkill
- api-authorization-testingSkill
- api-inventorySkill
- api-schema-securitySkill
- dast-baselineSkill
- sast-triageSkill
- sca-dependency-riskSkill
- secure-code-reviewSkill
- security-requirementsSkill
- threat-modelingSkill
- asset-criticality-tieringSkill
- asset-inventory-reconciliationSkill
- external-attack-surface-reviewSkill
- shadow-it-discoverySkill
- aws-credential-compromiseSkill
- aws-iam-reviewSkill
- aws-org-guardrailsSkill
- cloudtrail-investigationSkill
- guardduty-triageSkill
- s3-exposure-reviewSkill
- azure-activity-investigationSkill
- azure-rbac-reviewSkill
- conditional-access-reviewSkill
- entra-audit-investigationSkill
- entra-signin-investigationSkill
- backup-assuranceSkill
- critical-service-mappingSkill
- ransomware-recoverySkill
- recovery-exerciseSkill
- cloud-exposure-reviewSkill
- cloud-incident-responseSkill
- cloud-logging-baselineSkill
- cloud-posture-assessmentSkill
- audit-evidence-packageSkill
- control-mappingSkill
- control-testing-samplingSkill
- container-incidentSkill
- dockerfile-hardeningSkill
- image-scanningSkill
- runtime-detection-falcoSkill
- db-audit-loggingSkill
- db-exfiltration-investigationSkill
- db-hardeningSkill
- db-privilege-reviewSkill
- data-classificationSkill
- data-discoverySkill
- The first 60 shown.
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 30
Use native policy engines where possible:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Continuous Control Monitoring
Good CCM candidates
| Control | Automated test | Source |
| MFA for all users / admins | % users with MFA registered; % admin sign-ins with phishing-resistant MFA | IdP API / sign-in logs |
| EDR coverage | Healthy agents ÷ inventory | EDR API + CMDB (edr-coverage-health) |
| Patch SLA | % critical vulns past SLA | Vuln scanner API |
| Encryption at rest | Non-encrypted volumes/buckets/databases | AWS Config rules, Azure Policy, GCP Org Policy, Prowler |
| Logging enabled | CloudTrail/diagnostic settings present | Config/Policy |
| Public exposure | Public buckets, 0.0.0.0/0 admin ports | CSPM |
| Access reviews | Campaign completion % by due date | IGA |
| Backup | Successful backups and last restore test date | Backup platform API |
| Leavers | Accounts enabled after termination | HR ↔ IdP reconciliation (joiner-mover-leaver) |
Implementation
- Define each check as code with: control ID, query/API call, pass threshold, frequency, owner, evidence output.
- Use native policy engines where possible:
aws configservice describe-compliance-by-config-rule --compliance-types NON_COMPLIANT az policy state summarize --management-group MG steampipe query "select name, region from aws_s3_bucket where bucket_policy_is_public" - Store results immutably with timestamps (evidence for auditors).
- Alert owners on threshold breach; track remediation tickets.
- Dashboard trend per control; report exceptions to governance.
Pitfalls
Checks that test configuration presence but not effectiveness (policy exists but excludes most users), stale inventories making coverage look good, alert fatigue without owners.
Related skills
audit-evidence-package, control-mapping, security-metric-definition, cloud-posture-assessment
References
- AWS Config managed rules: https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html
- Azure Policy: https://learn.microsoft.com/en-us/azure/governance/policy/overview
- NIST SP 800-137 Information Security Continuous Monitoring: https://csrc.nist.gov/pubs/sp/800/137/final
- Steampipe: https://steampipe.io/docs
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

