Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    crg compliance mapper

    1

    Maps risk scenarios to NIST CSF 2.0, SP 800-53, and ISO 27002 controls with candidate legal obligations.

    $10

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    crg compliance mapper

    crg compliance mapper

    Example session with this skill installed

    Private clinic in Québec. Scenarios LIB-F1448 and LIB-F1129. Evidence: E1 backup policy; E2 failed restore test. Provide a crosswalk and legal pointers.

    • Read your context and instructions
    • Compiled the crg compliance mapper

    The risk scenarios have been mapped to NIST and ISO frameworks, with candidate legal obligations identified for the Québec jurisdiction.

    1. Scope and inputs

    ItemContentBasis
    ScenariosLIB-F1448, LIB-F1129User input
    FrameworksNIST CSF 2.0, SP 800-53 R5, ISO 27002:2022Request
    EvidenceE1 (Backup Policy), E2 (Restore Test)User Assertion

    2. Scenario-to-control crosswalk

    ScenarioNIST CSF 2.0NIST SP 800-53 Rev. 5ISO/IEC 27002:2022Link confidence
    LIB-F1129 Data LossPR.DS-11 Backups of dataCP-9 System Backup8.13H
    LIB-F1448 System FailurePR.DS-01 Service availabilityCP-2 Contingency Plan5.30M

    3. Control-to-scenario reverse lookup

    ControlFrameworkTitleScenarios in this setLibrary scenarios linked
    CP-9NIST SP 800-53System BackupLIB-F112912
    8.13ISO 27002:2022(identifier only)LIB-F11298

    4. Candidate legal obligations (to confirm by legal counsel)

    InstrumentPointerTitle in catalogueScenariosQuestion for counselStatus
    Law 25 (P-39.1)s. 10Security measuresLIB-F1129Are backups sufficient for s.10?To confirm by legal counsel

    5. Statement of applicability (draft, evidence-based)

    ControlFrameworkScenarios addressedApplicabilityStatus from evidenceEvidenceGap or note
    PR.DS-11CSF 2.0LIB-F1129ProposedPartly in placeE1, E2Restore failed (E2)

    7. Limits and decisions

    Management decision required: Final approval of the applicability of PR.DS-11.
    To confirm by legal counsel: All candidate obligations in Section 4.
    Mapping is never evidence of compliance.

    Next steps

    1. Review the "Analytical estimate" markers in the full report.
    2. Submit Section 4 to legal counsel for jurisdictional validation.
    3. Update evidence list with the successful re-test of the imaging restore.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Managing cybersecurity compliance across fragmented frameworks often leads to inconsistent mapping and unverifiable claims. This skill automates the crosswalk between risk scenarios and major standards like NIST CSF 2.0, NIST SP 800-53 Rev. 5, and ISO/IEC 27002:2022.

    What it does

    • Multi-framework mapping connects cybersecurity risk scenarios to specific control identifiers and titles from NIST and ISO libraries.
    • Legal pointers identifies candidate obligations from Québec, Canadian, and EU jurisdictions based on organization type and sector.
    • Reverse lookup determines which specific risk scenarios are addressed by a given control.
    • Statement of applicability drafts evidence-based tables linking user-provided audit findings or policies to control status.
    • Gap analysis flags missing controls and information voids without inventing data or scoring coverage.

    How it works

    1. Intake gathers risk scenarios, control lists, and registered evidence (labeled E1, E2, etc.).
    2. Analysis queries the local ontology to find library matches for scenarios and legal instruments.
    3. Drafting generates a structured crosswalk, reverse lookup, and applicability statement using specific markers for analytical estimates.
    4. Validation lists required management decisions and legal counsel checkpoints to ensure human oversight.

    Frameworks & tools

    NIST CSF 2.0, NIST SP 800-53 Rev. 5, ISO/IEC 27002:2022, and the CyberRiskGuardian risk method.

    Why this beats prompting it yourself

    Generic prompts often hallucinate control numbers or mix versions like CSF 1.1 and 2.0. This skill uses a strict local ontology of over 1,800 scenarios to ensure every link is grounded in established cybersecurity references.

    Use cases

    • Map specific risk scenarios to required technical controls for an audit.
    • Identify which laws (like Québec Law 25 or GDPR) potentially apply to a set of risks.
    • Build a statement of applicability based on existing internal evidence.
    • Identify control gaps where specific risks have no mapped mitigation.

    Known limitations

    Does not provide audit opinions, legal advice, or ISO certification. Titles for ISO controls are excluded for licensing reasons. Only supports English and French.

    Does not provide legal advice or audit opinions. ISO titles are excluded. Supports English and French only. Requires user-supplied evidence for status updates.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 7 days ago

    Permissions

    Read Files
    Write Files
    Network Access
    Listed7 days ago

    What's inside

    Frequently Asked Questions

    This skill automates the mapping between your specific risk scenarios and major frameworks like NIST CSF 2.0, SP 800-53, and ISO 27002, ensuring your compliance documentation is consistent and grounded in established standards.

    Unlike generic prompts, this skill uses a strict local ontology of over 1,800 scenarios to prevent 'hallucinated' control numbers and ensures all mappings align with the latest versions, such as CSF 2.0 instead of legacy versions.

    The skill identifies candidate legal obligations for Québec, Canadian, and EU jurisdictions (such as Law 25 or GDPR) based on your organization type and the specific risks you input.

    Yes, the 'Reverse Lookup' feature allows you to input a specific control identifier to see which risk scenarios that control is intended to mitigate within your environment.

    The skill requires your risk scenarios, existing control lists, and any labeled evidence (e.g., E1, E2) to generate its structured crosswalks and statements of applicability.

    For licensing compliance, the tool provides specific ISO control identifiers and mappings but does not display the full proprietary text of ISO 27002 control titles.

    New in LLM Ops