GRC evidence flow diagram
Use this skill to structure the GRC content and visual pattern for evidence collection, evidence lifecycle, audit evidence pipelines, and systems of record. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- AWS Config to evidence repository to auditor review
- GitHub branch protection evidence
- quarterly access review lifecycle
Control-to-evidence example
For an auditor-facing map, request the control, responsible owner, evidence artifact, review cadence and reviewer. Do not include actual evidence, credentials, sensitive paths or identifying details without authorization. If an input is unknown, label it unknown rather than inventing it. Create editable nodes and labeled relationships, not a screenshot. The fictional control-to-evidence example shows an access review; it is not a claim that a real control operates effectively.
For a simple, single control-to-evidence flow with supplied labels, the optional local generator described in the plugin README creates the editable model deterministically. Use it only when this fixed four-node pattern fits; the general workflow below remains available for other diagrams. Ask for missing fields rather than guessing, and review inputs for sensitive information. It does not scan for secrets or validate the truth of the relationships.
Validate the example from the repository root:
python3 plugins/grc-diagrams/examples/validate-control-evidence.py
The parser checks escaping, cell IDs, edge references and geometry for this specific uncompressed example; it is not a general draw.io validator or a secret scanner. Open the file in draw.io to inspect layout and editability. The example does not model exceptions, retention, or evidence access controls; adapt it to the actual engagement and review for sensitive content before sharing.
Recommended Elements
Include these when relevant:
- evidence sources
- collectors
- repositories
- reviewers
- approvers
- auditors
- retention
- freshness
- cadence
Recommended Output Pattern
Produce a Swimlane evidence lifecycle or evidence data-flow 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-evidence-flow-diagram3description: Use when creating a draw.io diagram for evidence collection, evidence lifecycle, audit evidence pipelines, and systems of record in a GRC, security, audit, compliance, privacy, cloud, or risk context.4allowed-tools: Write, Bash, Read, WebFetch5metadata:6 source: https://skillmd.com/skills/grcengclub/grc-evidence-flow-diagram7---89# GRC evidence flow diagram1011Use this skill to structure the GRC content and visual pattern for evidence collection, evidence lifecycle, audit evidence pipelines, and systems of record. Then use the `drawio` skill to generate the native editable `.drawio` file and optional PNG/SVG/PDF export.1213## Common Requests1415- AWS Config to evidence repository to auditor review16- GitHub branch protection evidence17- quarterly access review lifecycle1819## Control-to-evidence example2021For an auditor-facing map, request the control, responsible owner, evidence artifact, review cadence and reviewer. Do not include actual evidence, credentials, sensitive paths or identifying details without authorization. If an input is unknown, label it unknown rather than inventing it. Create editable nodes and labeled relationships, not a screenshot. The fictional [control-to-evidence example](../../examples/control-evidence-flow.drawio) shows an access review; it is not a claim that a real control operates effectively.2223For a simple, single control-to-evidence flow with supplied labels, the optional local generator described in the [plugin README](../../README.md#generate-a-control-to-evidence-flow) creates the editable model deterministically. Use it only when this fixed four-node pattern fits; the general workflow below remains available for other diagrams. Ask for missing fields rather than guessing, and review inputs for sensitive information. It does not scan for secrets or validate the truth of the relationships.2425Validate the example from the repository root:2627```bash28python3 plugins/grc-diagrams/examples/validate-control-evidence.py29```3031The parser checks escaping, cell IDs, edge references and geometry for this specific uncompressed example; it is not a general draw.io validator or a secret scanner. Open the file in draw.io to inspect layout and editability. The example does not model exceptions, retention, or evidence access controls; adapt it to the actual engagement and review for sensitive content before sharing.3233## Recommended Elements3435Include these when relevant:3637- evidence sources38- collectors39- repositories40- reviewers41- approvers42- auditors43- retention44- freshness45- cadence4647## Recommended Output Pattern4849Produce a Swimlane evidence lifecycle or evidence data-flow diagram. Choose a layout that matches the audience:5051- Executive: compact lifecycle/capability view with business impact labels.52- Auditor/assessor: explicit evidence, owner, control, cadence, and scope labels.53- Practitioner/engineering: operational systems, data paths, automation, failure/exception paths, and implementation detail.5455## draw.io Instructions56571. Load and follow the `drawio` skill.582. Generate native mxGraphModel XML directly. Do not generate Mermaid as the final artifact.593. Use descriptive lowercase hyphenated filenames.604. Include a legend when colors, edge styles, or containers have compliance meaning.615. Validate XML well-formedness before finalizing.626. If PNG/SVG/PDF is requested, export with embedded diagram XML when the draw.io CLI is available.6364## Visual Conventions6566- Blue: systems, platforms, services, and automated collectors.67- Green: implemented controls, approvals, validated evidence, and compliant outcomes.68- Orange/red: risks, findings, exceptions, overdue items, gaps, and failed controls.69- Gray: manual tasks, external parties, optional steps, and out-of-scope areas.70- Dashed containers: audit scope, trust boundaries, authorization boundary, or responsibility boundary.71- Solid edges: primary process or system flow.72- Dashed edges: evidence or attestation flow.73- Dotted edges: optional, manual, exception, or escalation flow.7475## Quality Bar7677- Make ownership explicit.78- Label regulated data, control IDs, frameworks, and evidence repositories when known.79- Show decision criteria where the process branches.80- Avoid generic boxes like "Compliance" without a role, system, artifact, or action.81- Prefer editable source of truth over screenshots.