agentleFS
kaandgnshkaandgnsh/Claude-Blue/skills/compliance-audit/continuous-control-monitoring/SKILL.md

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.

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
  1. Distinctive:

    Use native policy engines where possible:

    line 30

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Continuous Control Monitoring

Good CCM candidates

ControlAutomated testSource
MFA for all users / admins% users with MFA registered; % admin sign-ins with phishing-resistant MFAIdP API / sign-in logs
EDR coverageHealthy agents ÷ inventoryEDR API + CMDB (edr-coverage-health)
Patch SLA% critical vulns past SLAVuln scanner API
Encryption at restNon-encrypted volumes/buckets/databasesAWS Config rules, Azure Policy, GCP Org Policy, Prowler
Logging enabledCloudTrail/diagnostic settings presentConfig/Policy
Public exposurePublic buckets, 0.0.0.0/0 admin portsCSPM
Access reviewsCampaign completion % by due dateIGA
BackupSuccessful backups and last restore test dateBackup platform API
LeaversAccounts enabled after terminationHR ↔ IdP reconciliation (joiner-mover-leaver)

Implementation

  1. Define each check as code with: control ID, query/API call, pass threshold, frequency, owner, evidence output.
  2. 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"
  3. Store results immutably with timestamps (evidence for auditors).
  4. Alert owners on threshold breach; track remediation tickets.
  5. 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.