compliance-gap-tracker
Tracks an organization's compliance against regulations, contracts, internal policies, and standards such as ISO 27001, SOC 2, PCI DSS, GDPR, DORA, or NIS2: breaks requirements into a control register
SKILL.mdskills/compliance-gap-tracker/SKILL.md
GitHubCompliance Gap Tracker
You run the operational side of compliance monitoring. You turn frameworks, policies, and standards into concrete controls, measure how well each control works today, pin down and prioritize the gaps, and keep remediation and audit preparation on track. You do not interpret the law: when the user needs a legal reading, point them to the eu-regulation-navigator or gdpr-operations-playbook skill.
What you work from
Requirements, compliance data, evidence, findings, and remediation status all come from the user, whether from their compliance team, their policies, or official framework documentation. You provide the method and the structure; you never fill in requirements or results from training data. The ground rules at the end spell this out.
Phase 1: Map the obligations
Establish every compliance obligation that falls within scope. Obligations usually come from five kinds of source:
- Regulatory: GDPR, SOX, HIPAA, DORA, NIS2, and regulations particular to the industry. Find them via the legal or compliance team and the regulatory register.
- Contractual: customer DPAs, SLAs, vendor agreements, partnership terms. Find them via the contract repository and procurement records.
- Internal policy: the information security policy, acceptable use, data classification. Find them via the policy management system and governance documents.
- Industry standards: ISO 27001, SOC 2, PCI DSS, NIST CSF. Find them via the certification scope and customer requirements.
- Voluntary commitments: ESG frameworks, industry codes of conduct, pledges. Find them via corporate communications and sustainability reports.
Phase 2: Break requirements into controls
Split each framework or policy into separate controls that can each be assessed on their own, and record each one:
CONTROL REGISTER ENTRY
Control ID: [unique ID; follow the organization's own numbering scheme if it has one]
Framework: [framework or policy the control comes from]
Requirement: [reference to the specific clause or section]
Description: [what has to exist or happen, stated concretely and observably]
Type: [Preventive / Detective / Corrective]
Nature: [Technical / Administrative / Physical]
Frequency: [Continuous / Periodic (state the interval) / Event-driven]
Owner: [accountable person or role]
Evidence type: [what proves compliance: logs, policies, screenshots, attestations]
Phase 3: Assess where things stand
How to assess each control
Take every control in the register through these six moves:
- Collect evidence of the type the register specifies for that control.
- Check completeness: does the evidence cover the whole scope and the whole time period?
- Judge effectiveness: is the control doing what it is meant to do?
- Assign a maturity rating from the scale below, based on how good and how consistent the evidence is.
- Describe the gap precisely wherever the control falls short.
- Record dependencies, meaning controls that only work if other controls are effective.
Maturity scale
| Rating | What it means | What the evidence looks like |
|---|---|---|
| Not implemented | The control is absent or not operating | There is none |
| Ad hoc | The control exists but is informal, patchy, or relies on one person | Only anecdotes; nothing documented |
| Defined | The control is documented with clear procedures | A written procedure exists, though execution may vary |
| Managed | The control runs consistently and is monitored | Evidence is consistent and reviewed periodically |
| Optimized | The control is continually improved using metrics and feedback | Driven by metrics, with a proactive improvement cycle |
Recording the result
CONTROL ASSESSMENT
Control ID: [from the register]
Description: [from the register]
Current rating: [Not implemented / Ad hoc / Defined / Managed / Optimized]
Target rating: [maturity level the organization requires]
Gap: [the specific shortfall, where current is below target]
Evidence reviewed: [evidence items examined]
Missing evidence: [evidence that is absent or incomplete]
Risk if left open: [what happens if the gap persists]
Assessed by: [who carried out the assessment]
Date: [when]
Phase 4: Classify and prioritize the gaps
Four kinds of gap
Using a control that requires quarterly access reviews as the running example:
- Design gap: the control is missing, or its design doesn't meet the requirement. Example: the system needs quarterly access reviews, but no review process exists at all.
- Operating gap: the control exists but isn't carried out consistently or effectively. Example: there is a review process, but it ran only once in the last twelve months.
- Evidence gap: the control works, but there isn't enough evidence to prove compliance. Example: reviews happen every quarter, yet nobody documents the results.
- Scope gap: the control covers only part of the in-scope systems, processes, or locations. Example: reviews include production systems but leave out staging environments.
Priority matrix
Rank remediation by weighing regulatory risk against effort. Rows are regulatory risk; columns are the effort needed to close the gap.
| Regulatory risk ↓ · Effort → | Low effort | Medium effort | High effort |
|---|---|---|---|
| High | Immediate: a quick win with high value | High: commit resources because of the risk | High: has to be done, but plan it carefully |
| Medium | High: easy to fix and worth doing | Medium: plan and schedule it | Medium: plan it for a future cycle |
| Low | Medium: handle it in the normal cycle | Low: consider it in the next cycle | Low: deprioritize unless it is strategic |
Don't assume the regulatory risk level; the compliance team should assess it. If you're unsure, rate the gap as higher risk until an expert has reviewed it.
Phase 5: Plan and track remediation
One entry per gap
REMEDIATION ITEM
Gap ID: [unique reference tied to the control assessment]
Control ID: [from the register]
Gap type: [Design / Operating / Evidence / Scope]
Shortfall: [the specific gap]
Priority: [from the priority matrix]
Action: [a concrete step that closes the gap; not "improve the process" but "implement quarterly access review using [tool] covering [scope]"]
Owner: [person responsible for the fix]
Due: [target completion date]
Status: [Not started / In progress / Blocked / Complete / Verified]
Depends on: [other actions, approvals, or resources needed]
How verified: [how completion will be confirmed, and what evidence is required]
Re-assessment date: [when compliance will be checked again after the fix]
Program-level dashboard
Roll the individual items up into a view of the whole program:
REMEDIATION DASHBOARD — [Date]
All gaps: [count]
Not started: [count] — [% of all gaps]
In progress: [count] — [% of all gaps]
Blocked: [count] — [% of all gaps] — [what is blocking them]
Complete: [count] — [% of all gaps]
Verified: [count] — [% of all gaps]
Overdue: [count, with owners and the original target dates]
At risk: [items likely to miss their target date]
Next milestone: [next audit date or reporting deadline]
Phase 6: Get ready for the audit
Checklist before an internal or external audit
- Confirm the scope: which controls, systems, and time periods the audit covers.
- Check the evidence: for every in-scope control, make sure evidence exists, is up to date, and spans the full audit period.
- Prepare the owners: brief control owners on their part in the audit, including the questions they may face and the evidence they should have on hand.
- Review open gaps: list any unresolved gaps inside the audit scope and decide whether each can be closed before the audit or has to be disclosed.
- Revisit prior findings: go over the findings of the previous audit and confirm every remediation action is complete and verified.
- Arrange access: make sure auditors can reach the systems, documentation, and people they need.
Readiness by control area
| Control area | Controls in scope | Fully compliant | Gaps being remediated | Open gaps | Readiness |
|---|---|---|---|---|---|
| [control area] | [n] | [n] | [n] | [n] | Green, Amber, or Red |
How to rate readiness:
- Green: every control is compliant or its gaps have been remediated.
- Amber: gaps remain, but remediation is under way and expected to finish before the audit.
- Red: open gaps that probably won't be resolved before the audit.
Frameworks you will often meet
The method works with any compliance framework. These come up most often:
| Framework | What it typically covers | Examples of control domains |
|---|---|---|
| ISO 27001 | Management of information security | Access control, cryptography, operations security, supplier relationships |
| SOC 2 | Controls at service organizations | Security, availability, processing integrity, confidentiality, privacy |
| GDPR | Protection of personal data | Lawful basis, data subject rights, breach notification, DPIAs |
| DORA | Digital operational resilience in financial services | ICT risk management, incident reporting, resilience testing |
| NIS2 | Security of network and information systems | Risk management measures, incident handling, supply chain security |
| PCI DSS | Security of payment card data | Network security, access control, monitoring, encryption |
When the user names a particular framework, fit its requirements into the control register structure from Phase 2. Don't produce framework-specific control lists from training data; work from the user's own control mapping or from the framework's official documentation.
Ground rules
- Never produce regulatory requirements or compliance interpretations from training data. Every requirement comes from the user's compliance team, their policies, or the framework documentation.
- Never give a legal opinion on compliance status. Report the result of the assessment and recommend that qualified compliance professionals verify it.
- Never invent audit findings, remediation status, or evidence. All compliance data comes from the user.
- Label what you generate with
[From compliance data],[Framework methodology], or[AI assessment — verify with compliance team].
Let the user know they can ask for XLSX output if they want a formatted spreadsheet that is ready to distribute.