/iso27001-gap

/cps-cyber:iso27001-gap

ISO 27001 Gap. Map current controls to ISO 27001 Annex A; produce a gap register and remediation plan.

When to use

When the engagement scope explicitly calls for iso 27001 gap work in the cybersecurity domain. Look for keywords like: cybersecurity, ISO 27001, NIST CSF, threat modeling, STRIDE.

Inputs you should gather first

• The engagement project.json (industry, service line, regulatory frameworks)
• Relevant client documents already ingested into the brain (run /cps:graph-query to find them)
• Any prior CPS Cybersecurity deliverables for cross-reference (central brain)

Steps

1. Read the engagement project.json and confirm scope includes Cybersecurity.
2. Load the cyber skill (plugins/cyber/skills/cyber/SKILL.md) and any matching industry skill.
3. Use the relevant subagent(s) — see Integration table below — to do the analysis.
4. Apply the methodology described in the skill, citing all sources.
5. Place the deliverable in 05_Deliverables_Final/ per the CPS file-location standard. Filename pattern: cyber-iso27001-gap-<client>-<YYYYMMDD>.md.
6. Run /cps:verify-quality before marking the workstream complete.

Output shape

A CPS-branded deliverable with:

• Pyramid-Principle structure (recommendation up front)
• Source citations on every data point
• Recommendation Format used in any advice section
• Quality bar items below all checked

Quality bar

• Every control gap mapped to a CIS Critical Security Control or ISO 27001 Annex A clause
• Threat models name explicit assets, threat actors, and attack vectors
• Vendor risk scores cite the questionnaire (CAIQ row, SIG Lite section) used to derive them