CyberSorted Lite — Security Advisory
A role-aware advisory skill that provides security and architecture guidance
tailored to your perspective. Covers threat modelling, risk assessment, compliance mapping,
and document generation.
This is the free, open-source edition. For the full skill with 8 roles, 8 frameworks,
8 templates, and 5 checklists, see CyberSorted Skills Pro.
Supported Roles
| Role |
Focus |
Output Style |
| CISO |
Strategic risk, board reporting, programme governance, budget justification |
Executive summaries, risk heatmaps, business impact |
| CTO |
Technology strategy, platform security, build-vs-buy, technical debt |
Architecture decisions, technical depth with business context |
| Security Architect |
Threat modelling, security patterns, controls design, reference architectures |
Technical diagrams, control specifications, design patterns |
Workflow
Step 1: Identify the User's Role
Determine the user's role from context. Look for explicit statements ("As a CISO...") or
infer from the nature of their request:
- Asking about board reporting, programme strategy, risk appetite → CISO
- Asking about technology choices, platform architecture, scaling → CTO
- Asking about threat models, security controls, reference architectures → Security Architect
If unclear, ask: "What's your role or perspective? This helps me tailor the depth and format."
Load the corresponding playbook from roles/<role>.md to guide tone, depth, and output format.
Step 2: Identify the Capability Needed
Determine which mode to operate in:
Advisory Analysis
Provide expert analysis on security or architecture topics. Use role playbook to set depth and perspective.
Includes: Threat modelling, risk assessment, architecture review, security posture analysis, technology evaluation, attack surface analysis.
Document Generation
Generate a structured deliverable using a template from templates/.
Available templates:
templates/threat-model.md — STRIDE/PASTA threat model
templates/security-policy.md — Security policy document
templates/risk-assessment.md — Risk register / assessment
Read the template file, then fill each section with context from the user's request.
Interactive Assessment
Walk through a framework-based assessment interactively.
Available frameworks:
frameworks/nist-800-53.md — NIST SP 800-53 control families
frameworks/iso-27001.md — ISO 27001:2022 Annex A controls
Process:
- Load the framework reference
- Walk through each domain/control family
- Ask the user about their current state for each area
- Score maturity (1-5 scale: Initial, Developing, Defined, Managed, Optimising)
- Generate a maturity scorecard with gap analysis and prioritised recommendations
Compliance Mapping
Map existing infrastructure, policies, or controls to specific framework requirements.
Process:
- Understand the user's current environment (cloud provider, services, policies)
- Load the target framework from
frameworks/
- Map each control requirement to existing implementations
- Identify gaps — controls with no coverage or partial coverage
- Generate a compliance matrix with status: Compliant, Partial, Gap, N/A
- Prioritise gaps by risk level
Step 3: Execute
Follow the role playbook for tone, depth, and output format:
- CISO: Lead with business impact and strategic recommendations. Use executive summaries. Quantify risk where possible (likelihood x impact). Reference industry benchmarks.
- CTO: Lead with technical architecture. Include specific commands, configurations, and code examples. Connect technical decisions to business outcomes.
- Security Architect: Lead with technical architecture. Use diagrams (reference the cloud-diagram skill for visual outputs). Specify controls at the design level.
Step 4: Present Output
Format output appropriate to the audience:
Executive audience (CISO, CTO):
- Start with a 2-3 sentence executive summary
- Use risk ratings: Critical / High / Medium / Low
- Include business impact statements
- End with prioritised recommendations (Quick wins, Short-term, Long-term)
Technical audience (Security Architect):
- Start with scope and assumptions
- Include technical details, configurations, and code examples
- Reference specific framework controls (e.g., "NIST AC-2", "ISO A.5.1")
- End with implementation steps and dependencies
Step 5: Cross-Skill Integration
For architecture visualisation, reference the cloud-diagram skill:
- "Would you like me to generate an architecture diagram showing the security controls?"
- The cloud-diagram skill supports Azure, AWS, GCP, K8s, and on-prem nodes
- Security-relevant nodes: WAF, Firewall, IAM, KMS, Security Groups, Network Policies
Quick Reference: Common Requests by Role
CISO
- "Assess our security posture" → Advisory Analysis
- "Prepare a board briefing" → Advisory Analysis (use board-briefing format)
- "What's our ISO 27001 readiness?" → Interactive Assessment (ISO 27001 framework)
CTO
- "Review our platform security architecture" → Advisory Analysis
- "Should we build or buy a SIEM?" → Advisory Analysis
- "Evaluate our DevSecOps maturity" → Interactive Assessment
- "Review our cloud architecture for security" → Advisory Analysis
Security Architect
- "Create a threat model for our payment system" → Document Generation (threat-model template)
- "Design a zero-trust architecture" → Advisory Analysis + Framework Reference
- "Review our network segmentation" → Advisory Analysis
- "Create a security reference architecture" → Advisory Analysis + cloud-diagram
Troubleshooting
| Problem |
Fix |
| Role not detected |
Ask the user directly: "What's your role or perspective?" |
| Framework not available |
Use the closest available framework and note limitations |
| User wants visual output |
Reference the cloud-diagram skill for architecture diagrams |
| Assessment too broad |
Narrow scope to a specific domain or control family first |
| Need more roles/frameworks |
Upgrade to CyberSorted Skills Pro |
1---2name: cybersorted-lite3description: Security advisory skill (free edition). Use this skill when the user needs help with cybersecurity strategy, threat modelling, risk assessment, compliance, or security architecture. Trigger when the user mentions: security posture, threat model, STRIDE, PASTA, risk assessment, risk register, compliance mapping, ISO 27001, NIST 800-53, incident response, IR plan, security policy, architecture decision, vendor risk, board briefing, security maturity, gap analysis, security review, security architecture, network segmentation, defence in depth, least privilege, data classification, encryption strategy, key management, identity and access management, IAM, vulnerability management, business continuity, disaster recovery, zero trust, platform security, DevSecOps, or any security and architecture advisory request. Supports roles: CISO, CTO, Security Architect. For additional roles (CPO, Security Engineer, Enterprise Architect, Secure Developer, Penetration Tester), frameworks (SOC2, CIS, MITRE ATT&CK, CSTM, OSCP), te4license: MIT5---6
7# CyberSorted Lite — Security Advisory
8
9A role-aware advisory skill that provides security and architecture guidance
10tailored to your perspective. Covers threat modelling, risk assessment, compliance mapping,
11and document generation.
12
13This is the free, open-source edition. For the full skill with 8 roles, 8 frameworks,
148 templates, and 5 checklists, see [CyberSorted Skills Pro](https://github.com/cyber-sorted/skills-pro).
15
16## Supported Roles
17
18| Role | Focus | Output Style |
19|------|-------|-------------|
20| **CISO** | Strategic risk, board reporting, programme governance, budget justification | Executive summaries, risk heatmaps, business impact |
21| **CTO** | Technology strategy, platform security, build-vs-buy, technical debt | Architecture decisions, technical depth with business context |
22| **Security Architect** | Threat modelling, security patterns, controls design, reference architectures | Technical diagrams, control specifications, design patterns |
23
24## Workflow
25
26### Step 1: Identify the User's Role
27
28Determine the user's role from context. Look for explicit statements ("As a CISO...") or
29infer from the nature of their request:
30
31- Asking about board reporting, programme strategy, risk appetite → **CISO**
32- Asking about technology choices, platform architecture, scaling → **CTO**
33- Asking about threat models, security controls, reference architectures → **Security Architect**
34
35If unclear, ask: "What's your role or perspective? This helps me tailor the depth and format."
36
37Load the corresponding playbook from `roles/<role>.md` to guide tone, depth, and output format.
38
39### Step 2: Identify the Capability Needed
40
41Determine which mode to operate in:
42
43#### Advisory Analysis
44Provide expert analysis on security or architecture topics. Use role playbook to set depth and perspective.
45
46**Includes:** Threat modelling, risk assessment, architecture review, security posture analysis, technology evaluation, attack surface analysis.
47
48#### Document Generation
49Generate a structured deliverable using a template from `templates/`.
50
51**Available templates:**
52- `templates/threat-model.md` — STRIDE/PASTA threat model
53- `templates/security-policy.md` — Security policy document
54- `templates/risk-assessment.md` — Risk register / assessment
55
56Read the template file, then fill each section with context from the user's request.
57
58#### Interactive Assessment
59Walk through a framework-based assessment interactively.
60
61**Available frameworks:**
62- `frameworks/nist-800-53.md` — NIST SP 800-53 control families
63- `frameworks/iso-27001.md` — ISO 27001:2022 Annex A controls
64
65**Process:**
661. Load the framework reference
672. Walk through each domain/control family
683. Ask the user about their current state for each area
694. Score maturity (1-5 scale: Initial, Developing, Defined, Managed, Optimising)
705. Generate a maturity scorecard with gap analysis and prioritised recommendations
71
72#### Compliance Mapping
73Map existing infrastructure, policies, or controls to specific framework requirements.
74
75**Process:**
761. Understand the user's current environment (cloud provider, services, policies)
772. Load the target framework from `frameworks/`
783. Map each control requirement to existing implementations
794. Identify gaps — controls with no coverage or partial coverage
805. Generate a compliance matrix with status: Compliant, Partial, Gap, N/A
816. Prioritise gaps by risk level
82
83### Step 3: Execute
84
85Follow the role playbook for tone, depth, and output format:
86
87- **CISO**: Lead with business impact and strategic recommendations. Use executive summaries. Quantify risk where possible (likelihood x impact). Reference industry benchmarks.
88- **CTO**: Lead with technical architecture. Include specific commands, configurations, and code examples. Connect technical decisions to business outcomes.
89- **Security Architect**: Lead with technical architecture. Use diagrams (reference the cloud-diagram skill for visual outputs). Specify controls at the design level.
90
91### Step 4: Present Output
92
93Format output appropriate to the audience:
94
95**Executive audience (CISO, CTO):**
96- Start with a 2-3 sentence executive summary
97- Use risk ratings: Critical / High / Medium / Low
98- Include business impact statements
99- End with prioritised recommendations (Quick wins, Short-term, Long-term)
100
101**Technical audience (Security Architect):**
102- Start with scope and assumptions
103- Include technical details, configurations, and code examples
104- Reference specific framework controls (e.g., "NIST AC-2", "ISO A.5.1")
105- End with implementation steps and dependencies
106
107### Step 5: Cross-Skill Integration
108
109For architecture visualisation, reference the **cloud-diagram** skill:
110- "Would you like me to generate an architecture diagram showing the security controls?"
111- The cloud-diagram skill supports Azure, AWS, GCP, K8s, and on-prem nodes
112- Security-relevant nodes: WAF, Firewall, IAM, KMS, Security Groups, Network Policies
113
114## Quick Reference: Common Requests by Role
115
116### CISO
117- "Assess our security posture" → Advisory Analysis
118- "Prepare a board briefing" → Advisory Analysis (use board-briefing format)
119- "What's our ISO 27001 readiness?" → Interactive Assessment (ISO 27001 framework)
120
121### CTO
122- "Review our platform security architecture" → Advisory Analysis
123- "Should we build or buy a SIEM?" → Advisory Analysis
124- "Evaluate our DevSecOps maturity" → Interactive Assessment
125- "Review our cloud architecture for security" → Advisory Analysis
126
127### Security Architect
128- "Create a threat model for our payment system" → Document Generation (threat-model template)
129- "Design a zero-trust architecture" → Advisory Analysis + Framework Reference
130- "Review our network segmentation" → Advisory Analysis
131- "Create a security reference architecture" → Advisory Analysis + cloud-diagram
132
133## Troubleshooting
134
135| Problem | Fix |
136|---------|-----|
137| Role not detected | Ask the user directly: "What's your role or perspective?" |
138| Framework not available | Use the closest available framework and note limitations |
139| User wants visual output | Reference the cloud-diagram skill for architecture diagrams |
140| Assessment too broad | Narrow scope to a specific domain or control family first |
141| Need more roles/frameworks | Upgrade to [CyberSorted Skills Pro](https://github.com/cyber-sorted/skills-pro) |