control-mapping
Skill0 starsChanged 12 days agoMITView on GitHub
Build and maintain a unified control framework that maps one set of internal controls to multiple frameworks — ISO/IEC 27001:2022 Annex A, SOC 2 TSC, NIST CSF 2.0, NIST SP 800-53, PCI DSS v4.0.1, CIS Controls, HIPAA, NIS2/DORA — using official crosswalks (NIST OLIR, CSF informative references) to test once, comply many. Use when preparing for multiple audits, onboarding a new framework, or performing gap analysis.
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
- continuous-control-monitoringSkill
- 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
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Start from the framework with the most granular requirements you must meet (often 800-53 or PCI) or from your existing control set.
- Distinctive: line 26
Use authoritative crosswalks: NIST CSF 2.0 informative references and OLIR mappings, CIS Controls mappings, ISO 27001 ↔ 27002 guidance, …
- Very specific: line 27
Write controls as testable statements (who/what/how often/evidence).
≈ “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
Control Mapping (Unified Control Framework)
Structure
Internal control ID | Control statement (testable) | Owner | Frequency | Evidence | Mapped requirements (ISO A.x, SOC2 CCx.x, CSF xx.xx-xx, 800-53 xx-n, PCI x.x.x, CIS x.x)
Example internal control:
- IAM-03: "Administrative access to production systems requires phishing-resistant MFA; compliance is reported monthly from the IdP."
- Maps to: ISO/IEC 27001:2022 A.8.5 (Secure authentication); SOC 2 CC6.1; NIST CSF 2.0 PR.AA-03; NIST SP 800-53 IA-2(1), IA-2(2); PCI DSS v4.0.1 8.4.2; CIS Controls 6.5.
(Verify each mapping against the current framework text — numbering changes between versions.)
Method
- Start from the framework with the most granular requirements you must meet (often 800-53 or PCI) or from your existing control set.
- Use authoritative crosswalks: NIST CSF 2.0 informative references and OLIR mappings, CIS Controls mappings, ISO 27001 ↔ 27002 guidance, AICPA SOC 2 to CSF mapping.
- Write controls as testable statements (who/what/how often/evidence).
- Identify gaps: framework requirements with no mapped internal control.
- Assign owners and evidence sources; automate evidence where possible (
continuous-control-monitoring). - Version the mapping; update on framework revisions (e.g., PCI DSS v4.0 future-dated requirements effective 31 March 2025).
Gap analysis output
Framework requirement | Mapped control(s) | Coverage (full/partial/none) | Gap | Action | Owner
Related skills
audit-evidence-package, continuous-control-monitoring, maturity-assessment, policy-review
References
- NIST CSF 2.0 informative references: https://www.nist.gov/informative-references
- NIST OLIR program: https://csrc.nist.gov/projects/olir
- CIS Controls mappings: https://www.cisecurity.org/controls/cis-controls-navigator
- PCI DSS v4.0.1 document library: https://www.pcisecuritystandards.org/document_library/
- AICPA Trust Services Criteria: https://www.aicpa-cima.com/resources/download/2017-trust-services-criteria-with-revised-points-of-focus-2022
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.