GRC compliance operating model diagram
Use this skill to structure the GRC content and visual pattern for high-level GRC program architecture, continuous compliance operating models, three lines of defense, and executive program maps. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- continuous compliance model
- three lines of defense
- GRC platform ecosystem
- policy-control-evidence-risk-audit lifecycle
Recommended Elements
Include these when relevant:
- program capabilities
- systems of record
- governance bodies
- owners
- feedback loops
- maturity phases
- automation coverage
Recommended Output Pattern
Produce a Executive capability map, lifecycle, or GRC ecosystem diagram. 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-compliance-operating-model-diagram3description: Use when creating a draw.io diagram for high-level GRC program architecture, continuous compliance operating models, three lines of defense, and executive program maps in a GRC, security, audit, compliance, privacy, cloud, or risk context.4---56# GRC compliance operating model diagram78Use this skill to structure the GRC content and visual pattern for high-level GRC program architecture, continuous compliance operating models, three lines of defense, and executive program maps. Then use the `drawio` skill to generate the native editable `.drawio` file and optional PNG/SVG/PDF export.910## Common Requests1112- continuous compliance model13- three lines of defense14- GRC platform ecosystem15- policy-control-evidence-risk-audit lifecycle1617## Recommended Elements1819Include these when relevant:2021- program capabilities22- systems of record23- governance bodies24- owners25- feedback loops26- maturity phases27- automation coverage2829## Recommended Output Pattern3031Produce a Executive capability map, lifecycle, or GRC ecosystem diagram. Choose a layout that matches the audience:3233- Executive: compact lifecycle/capability view with business impact labels.34- Auditor/assessor: explicit evidence, owner, control, cadence, and scope labels.35- Practitioner/engineering: operational systems, data paths, automation, failure/exception paths, and implementation detail.3637## draw.io Instructions38391. Load and follow the `drawio` skill.402. Generate native mxGraphModel XML directly. Do not generate Mermaid as the final artifact.413. Use descriptive lowercase hyphenated filenames.424. Include a legend when colors, edge styles, or containers have compliance meaning.435. Validate XML well-formedness before finalizing.446. If PNG/SVG/PDF is requested, export with embedded diagram XML when the draw.io CLI is available.4546## Visual Conventions4748- Blue: systems, platforms, services, and automated collectors.49- Green: implemented controls, approvals, validated evidence, and compliant outcomes.50- Orange/red: risks, findings, exceptions, overdue items, gaps, and failed controls.51- Gray: manual tasks, external parties, optional steps, and out-of-scope areas.52- Dashed containers: audit scope, trust boundaries, authorization boundary, or responsibility boundary.53- Solid edges: primary process or system flow.54- Dashed edges: evidence or attestation flow.55- Dotted edges: optional, manual, exception, or escalation flow.5657## Quality Bar5859- Make ownership explicit.60- Label regulated data, control IDs, frameworks, and evidence repositories when known.61- Show decision criteria where the process branches.62- Avoid generic boxes like "Compliance" without a role, system, artifact, or action.63- Prefer editable source of truth over screenshots.
grcengclub