GRC third-party risk diagram
Use this skill to structure the GRC content and visual pattern for vendor intake, tiering, questionnaires, security/privacy/legal review, contracting, and ongoing monitoring. Then use the drawio skill to generate the native editable .drawio file and optional PNG/SVG/PDF export.
Common Requests
- new vendor intake
- security questionnaire workflow
- vendor tiering
- DPIA handoff
- continuous vendor monitoring
Recommended Elements
Include these when relevant:
- business owner
- procurement
- legal
- privacy
- security
- vendor
- approver
- artifacts
- tiering decisions
Recommended Output Pattern
Produce a Vendor lifecycle, swimlane workflow, or tiering decision tree. 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-third-party-risk-diagram3description: Use when creating a draw.io diagram for vendor intake, tiering, questionnaires, security/privacy/legal review, contracting, and ongoing monitoring in a GRC, security, audit, compliance, privacy, cloud, or risk context.4---56# GRC third-party risk diagram78Use this skill to structure the GRC content and visual pattern for vendor intake, tiering, questionnaires, security/privacy/legal review, contracting, and ongoing monitoring. Then use the `drawio` skill to generate the native editable `.drawio` file and optional PNG/SVG/PDF export.910## Common Requests1112- new vendor intake13- security questionnaire workflow14- vendor tiering15- DPIA handoff16- continuous vendor monitoring1718## Recommended Elements1920Include these when relevant:2122- business owner23- procurement24- legal25- privacy26- security27- vendor28- approver29- artifacts30- tiering decisions3132## Recommended Output Pattern3334Produce a Vendor lifecycle, swimlane workflow, or tiering decision tree. Choose a layout that matches the audience:3536- Executive: compact lifecycle/capability view with business impact labels.37- Auditor/assessor: explicit evidence, owner, control, cadence, and scope labels.38- Practitioner/engineering: operational systems, data paths, automation, failure/exception paths, and implementation detail.3940## draw.io Instructions41421. Load and follow the `drawio` skill.432. Generate native mxGraphModel XML directly. Do not generate Mermaid as the final artifact.443. Use descriptive lowercase hyphenated filenames.454. Include a legend when colors, edge styles, or containers have compliance meaning.465. Validate XML well-formedness before finalizing.476. If PNG/SVG/PDF is requested, export with embedded diagram XML when the draw.io CLI is available.4849## Visual Conventions5051- Blue: systems, platforms, services, and automated collectors.52- Green: implemented controls, approvals, validated evidence, and compliant outcomes.53- Orange/red: risks, findings, exceptions, overdue items, gaps, and failed controls.54- Gray: manual tasks, external parties, optional steps, and out-of-scope areas.55- Dashed containers: audit scope, trust boundaries, authorization boundary, or responsibility boundary.56- Solid edges: primary process or system flow.57- Dashed edges: evidence or attestation flow.58- Dotted edges: optional, manual, exception, or escalation flow.5960## Quality Bar6162- Make ownership explicit.63- Label regulated data, control IDs, frameworks, and evidence repositories when known.64- Show decision criteria where the process branches.65- Avoid generic boxes like "Compliance" without a role, system, artifact, or action.66- Prefer editable source of truth over screenshots.
grcengclub