Skip to content
Skills Library
Law & compliance · Analysis

control-mapping

/control-mapping

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.

Repository
Claude-Blue ↗
Licence
MIT
Last repository change
01.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
5
Deprecation

No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Original author description

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.

How it works

  1. Structure
  2. Method
  3. Gap analysis output
  4. Related skills
  5. References
Original SKILL.md headings · 38 lines, 251 words
SKILL.md preview
---
name: control-mapping
description: 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.
license: MIT
metadata:
  category: compliance-audit
  version: "2.0.0"
  verification: documented
---

# 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

1. Start from the framework with the most granular requirements you must meet (often 800-53 or PCI) or from your existing control set.
2. 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.
3. Write controls as **testable statements** (who/what/how often/evidence).
4. Identify gaps: framework requirements with no mapped internal control.
5. Assign owners and evidence sources; automate evidence where possible (`continuous-control-monitoring`).
6. 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

Versions

The database has no other skills named control-mapping.

Database snapshot: 13.11.2026 · package version 4babf6921049 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90framework-mapper
    Map security controls, policies, evidence or requirements across frameworks (ISO 27001:2022, NIST CSF 2.0, CIS Controls v8, SOC 2, NIS2, DORA, EU AI Act) and run gap analyses. Use when the user asks "which ISO control covers X", wants a control crosswalk, needs to reuse evidence…
  • 90Compliance Mapping
    This skill should be used when the user asks about "compliance mapping", "PCI-DSS", "HIPAA", "SOC 2", "NIST CSF", "regulatory requirements", "compliance report", or needs to map security findings to compliance framework requirements.
  • 100compliance-and-audit
    Use when a project requires a compliance framework mapping, when risks need formal documentation, when audit evidence must be collected, or when producing a compliance attestation before release. Applies to SOC 2, ISO 27001, GDPR, PCI DSS, NIST CSF, and DORA.
  • 100security-compliance-mapping-soc2-iso-pci-nist
    Guides mapping technical controls an engineering team has already implemented — secrets management, IAM/least-privilege, logging and audit trails, encryption at rest/in transit, SAST/DAST/SCA scanning, backup and DR — to SOC 2 Trust Services Criteria, ISO/IEC 27001 Annex A…
  • 90compliance-assessment
    Gap-assess an organization or system against a compliance framework (SOC 2, ISO 27001, PCI DSS, HIPAA, GDPR, NIST CSF/800-53), mapping controls to evidence, identifying gaps, and producing a prioritized remediation and audit-readiness plan. Use for compliance gap analysis,…
  • 90framework-mapper
    Answer any question about what a security or privacy framework requires, from fixed mapping files and never from memory, even when you think you know the answer, since only the files are traceable. Use for any question that names or needs an article, clause or control of ISO…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.