GRC framework crosswalk diagram
Use this skill to structure the GRC content and visual pattern for mapping controls and obligations across frameworks to show overlap, gaps, and conflicts. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- SOC 2 to ISO 27001 to NIST CSF
- FedRAMP to NIST 800-53
- CIS to SOC 2
Recommended Elements
Include these when relevant:
- source framework
- normalized control
- target framework
- one-to-one/one-to-many/partial/no-match
- gaps
- conflicts
Recommended Output Pattern
Produce a Crosswalk matrix, many-to-many map, or common-control cluster. Choose a layout that matches the audience:
- Executive: compact lifecycle/capability view with business impact labels.
- Auditor/assessor: explicit evidence, owner, control, cadence, and scope labels.
- Practitioner/engineering: operational systems, data paths, automation, failure/exception paths, and implementation detail.
draw.io Instructions
- Load and follow the
drawio skill.
- Generate native mxGraphModel XML directly. Do not generate Mermaid as the final artifact.
- Use descriptive lowercase hyphenated filenames.
- Include a legend when colors, edge styles, or containers have compliance meaning.
- Validate XML well-formedness before finalizing.
- If PNG/SVG/PDF is requested, export with embedded diagram XML when the draw.io CLI is available.
Visual Conventions
- Blue: systems, platforms, services, and automated collectors.
- Green: implemented controls, approvals, validated evidence, and compliant outcomes.
- Orange/red: risks, findings, exceptions, overdue items, gaps, and failed controls.
- Gray: manual tasks, external parties, optional steps, and out-of-scope areas.
- Dashed containers: audit scope, trust boundaries, authorization boundary, or responsibility boundary.
- Solid edges: primary process or system flow.
- Dashed edges: evidence or attestation flow.
- Dotted edges: optional, manual, exception, or escalation flow.
Quality Bar
- Make ownership explicit.
- Label regulated data, control IDs, frameworks, and evidence repositories when known.
- Show decision criteria where the process branches.
- Avoid generic boxes like "Compliance" without a role, system, artifact, or action.
- Prefer editable source of truth over screenshots.
1---2name: grc-framework-crosswalk-diagram3description: Use when creating a draw.io diagram for mapping controls and obligations across frameworks to show overlap, gaps, and conflicts in a GRC, security, audit, compliance, privacy, cloud, or risk context.4---56# GRC framework crosswalk diagram78Use this skill to structure the GRC content and visual pattern for mapping controls and obligations across frameworks to show overlap, gaps, and conflicts. Then use the `drawio` skill to generate the native editable `.drawio` file and optional PNG/SVG/PDF export.910## Common Requests1112- SOC 2 to ISO 27001 to NIST CSF13- FedRAMP to NIST 800-5314- CIS to SOC 21516## Recommended Elements1718Include these when relevant:1920- source framework21- normalized control22- target framework23- one-to-one/one-to-many/partial/no-match24- gaps25- conflicts2627## Recommended Output Pattern2829Produce a Crosswalk matrix, many-to-many map, or common-control cluster. Choose a layout that matches the audience:3031- Executive: compact lifecycle/capability view with business impact labels.32- Auditor/assessor: explicit evidence, owner, control, cadence, and scope labels.33- Practitioner/engineering: operational systems, data paths, automation, failure/exception paths, and implementation detail.3435## draw.io Instructions36371. Load and follow the `drawio` skill.382. Generate native mxGraphModel XML directly. Do not generate Mermaid as the final artifact.393. Use descriptive lowercase hyphenated filenames.404. Include a legend when colors, edge styles, or containers have compliance meaning.415. Validate XML well-formedness before finalizing.426. If PNG/SVG/PDF is requested, export with embedded diagram XML when the draw.io CLI is available.4344## Visual Conventions4546- Blue: systems, platforms, services, and automated collectors.47- Green: implemented controls, approvals, validated evidence, and compliant outcomes.48- Orange/red: risks, findings, exceptions, overdue items, gaps, and failed controls.49- Gray: manual tasks, external parties, optional steps, and out-of-scope areas.50- Dashed containers: audit scope, trust boundaries, authorization boundary, or responsibility boundary.51- Solid edges: primary process or system flow.52- Dashed edges: evidence or attestation flow.53- Dotted edges: optional, manual, exception, or escalation flow.5455## Quality Bar5657- Make ownership explicit.58- Label regulated data, control IDs, frameworks, and evidence repositories when known.59- Show decision criteria where the process branches.60- Avoid generic boxes like "Compliance" without a role, system, artifact, or action.61- Prefer editable source of truth over screenshots.
grcengclub