Compliance Checker
When to activate
Use this skill when you need to:
- Map existing security controls to regulatory frameworks (GDPR, SOC 2 Type II, PCI-DSS, HIPAA)
- Audit your current security posture against compliance requirements
- Identify compliance gaps in your infrastructure or processes
- Generate a remediation roadmap with implementation priorities
- Prepare evidence for a compliance assessment or audit
- Evaluate whether a new tool, process, or change maintains compliance
Trigger scenarios:
- Expanding into a regulated market (healthcare, finance, EU)
- Preparing for an external audit or certification
- After a security incident, to verify compliance didn't break
- Before deploying a new feature that touches sensitive data
When NOT to use
- Legal interpretation required: If you need to understand ambiguous regulatory language or interpret case law, consult legal counsel — this skill maps known controls to known requirements, not edge cases
- One-off compliance question: If you just need "does GDPR require encryption?", ask directly instead of invoking the full skill
- Post-breach investigation: This skill maps controls to requirements; forensics and root-cause analysis are separate concerns
- Real-time threat response: During an active incident, focus on containment — compliance mapping comes after stabilization
- Vendor procurement decisions: Use this skill to define vendor compliance requirements, not to evaluate salespeople
Instructions
Step 1: Define Scope and Applicability
Before mapping controls, clarify:
Regulatory jurisdiction: Which frameworks apply?
- GDPR: EU/UK data processing
- HIPAA: US healthcare data (stricter than general data protection)
- PCI-DSS: Payment card data handling (any industry)
- SOC 2 Type II: Service organizations (auditor-driven)
- Others: Industry-specific (FedRAMP, FISMA, CCPA, etc.)
Data types and locations: What data does your system touch?
- Personal data (GDPR, CCPA)
- Health data (HIPAA)
- Payment card data (PCI-DSS)
- Regulated industry data (finance, government, etc.)
Scope boundaries: Which systems, teams, and processes are in scope?
- Cloud infrastructure vs. on-premises
- Third-party vendors and processors
- Development, staging, and production
Step 2: Inventory Existing Security Controls
Document what you already have:
| Control |
Current Implementation |
Evidence Location |
Owner |
| Encryption at rest |
(e.g., AES-256 in RDS) |
AWS console, IaC repo |
Platform team |
| Access control |
(e.g., IAM roles, MFA) |
Okta config |
Security team |
| Audit logging |
(e.g., CloudTrail) |
AWS account |
Ops team |
| ... |
... |
... |
... |
Use /security-audit or manual review to populate this table.
Step 3: Map Controls to Requirements
For each framework, cross-reference your controls against published requirements.
GDPR (Article-based):
- Article 5: Data subject rights and processor transparency
- Article 32: Technical and organizational measures (encryption, access, testing, monitoring)
- Article 33-35: Breach notification and DPIA
HIPAA (Rule-based):
- Administrative Safeguards: Workforce security, information access management
- Physical Safeguards: Facility access, workstation use and security
- Technical Safeguards: Access controls, encryption, audit controls, integrity controls
PCI-DSS (Requirement-based):
- 1-6: Infrastructure security
- 7-8: Access control and user identification
- 9-12: Monitoring, testing, and policies
SOC 2 Type II (Trust Service Criteria):
- CC (Common Criteria): Security, availability, processing integrity, confidentiality, privacy
- Each criterion has multiple sub-controls; attestation requires time-series evidence
Step 4: Identify Gaps
For each requirement, assess coverage:
| Requirement |
Required |
Current |
Gap |
Severity |
Evidence Gap |
| GDPR Art. 32: Encryption |
Required for PII |
AES-256 at rest; no TLS for internal comms |
TLS between services |
Medium |
No inventory of internal TLS |
| PCI-DSS 6.2: Security patches |
Monthly minimum |
Ad hoc patching every 2-3 months |
Automated patching SLA |
High |
No patch management policy |
| HIPAA Technical Safeguards: Audit logs |
All system activity |
CloudTrail + RDS logs only; no app logs |
App audit trail (who, what, when) |
Medium |
No centralized log collection |
| SOC 2 CC7.3: Prevent unauthorized data access |
Required |
IAM roles and MFA |
Attribute-based access control (ABAC) |
Low |
Meets current requirement |
Severity tiers:
- Critical: Failure exposes regulated data or violates legal requirement
- High: Creates material risk or audit finding; likely to fail certification
- Medium: Best practice gap or incomplete implementation; audit question likely
- Low: Recommended for mature programs; typically doesn't block certification
Step 5: Generate Remediation Roadmap
Prioritize by:
- Severity: Critical first, then High, Medium, Low
- Implementation cost: Quick wins first; defer expensive rewrites
- Dependencies: Some controls require others to be in place first
- Timeline: Audit dates, certification deadlines, regulatory deadlines
Roadmap template:
| # |
Control |
Gap |
Owner |
Timeline |
Effort |
Blockers |
Evidence Required |
| 1 |
Encrypt internal traffic (TLS) |
TLS between services |
Platform |
Q3 2026 |
2 weeks |
Cert management infra |
TLS cert audit, network capture |
| 2 |
Centralized audit logging |
App audit trail |
Eng + Ops |
Q3 2026 |
3 weeks |
Blocked by #1 |
Log ingestion setup, 6-month sample |
| 3 |
Automated patch management |
Patch SLA enforcement |
Ops |
Q4 2026 |
4 weeks |
Blocked by #2 |
Patch policy document, 12-month history |
Step 6: Build Evidence Inventory for Audit
Create a control-evidence mapping:
| Control |
Document Type |
Owner |
Refresh Cadence |
Location |
| IAM access control |
Policy doc + audit report |
Security |
Quarterly |
Security drive > IAM Policy.pdf + access-audit-Q2-2026.csv |
| Encryption at rest |
Architecture doc + test report |
Platform |
Annually |
Security drive > Encryption Standards.md |
| Incident response |
Playbook + post-mortems |
Security |
Ad hoc updates |
GitHub > security/incident-response.md |
Auditors ask for:
- Policies: Formal written requirements
- Evidence: Logs, screenshots, reports proving compliance
- Timelines: Dates showing sustained compliance (not one-off checks)
Example
Scenario: A US health tech startup preparing for SOC 2 Type II and HIPAA certification
Step 1: Scope
- Frameworks: HIPAA (health data) + SOC 2 Type II (service organization)
- Data: Patient records, genomic data, audit logs
- Scope: AWS cloud, three regions, third-party data processor
Step 2: Inventory
- Encryption: RDS encryption at rest (AES-256), but no TLS in transit
- Access: IAM roles + Okta SSO, but no MFA enforcement
- Logging: CloudTrail + RDS logs, but no application audit trail
- Backup: Daily snapshots, no tested restore procedure
Step 3: Map to Requirements
HIPAA Technical Safeguards § 164.312(a)(2):
- (i) Encryption and decryption → Partial: At rest ✓, in transit ✗
- (ii) Access controls → Partial: IAM ✓, MFA ✗, role audits ✗
SOC 2 CC6.1 (Logical access controls):
- "System is protected against unauthorized logical access" → Partial: MFA missing, no attribute-based access
Step 4: Gaps
| Requirement |
Current |
Gap |
Severity |
| HIPAA § 164.312(a)(2)(i): Encryption in transit |
TLS optional |
Enforce TLS for all data flows |
Critical |
| HIPAA § 164.312(a)(2)(ii): MFA |
Optional |
Enforce MFA for healthcare staff |
High |
| HIPAA § 164.312(b): Audit controls |
CloudTrail + DB logs |
Application audit trail (who accessed which records, when) |
High |
| SOC 2 CC6.2: User access provisioning |
Ad hoc Okta grants |
Formal approval workflow + quarterly access reviews |
Medium |
Step 5: Remediation Roadmap
| Priority |
Control |
Effort |
Timeline |
Evidence |
| 1 |
TLS everywhere |
2 weeks |
Q3 immediate |
TLS audit, network scan |
| 2 |
Enforce MFA |
1 week |
Q3 immediate |
Okta config, user enrollment report |
| 3 |
Application audit trail |
4 weeks |
Q3 |
Centralized logging setup, 6-month sample logs |
| 4 |
Access review workflow |
3 weeks |
Q4 |
Approval forms, quarterly review records |
Step 6: Evidence Collected for Auditors
- HIPAA Compliance Checklist: Filled in, signed by Security Officer
- Encryption Audit Report: Network capture showing TLS on all data flows
- IAM Access Report: Q2 2026 access review with manager sign-offs
- Audit Log Sample: 6 months of application + system logs proving "who did what when"
- Policies: Written HIPAA Security Rule implementation policy, MFA policy, incident response plan
Related Skills
/security-audit — Inventory and assess current security controls
/threat-modeling — Identify new threats; cross-reference against compliance gaps
/incident-response — When gaps are exploited; collect evidence for post-incident compliance
1---2name: compliance-checker3description: Compliance Checker4metadata:5 source: https://skillmd.com/skills/uitbreidenos/compliance-checker6---7# Compliance Checker89## When to activate1011Use this skill when you need to:12- Map existing security controls to regulatory frameworks (GDPR, SOC 2 Type II, PCI-DSS, HIPAA)13- Audit your current security posture against compliance requirements14- Identify compliance gaps in your infrastructure or processes15- Generate a remediation roadmap with implementation priorities16- Prepare evidence for a compliance assessment or audit17- Evaluate whether a new tool, process, or change maintains compliance1819Trigger scenarios:20- Expanding into a regulated market (healthcare, finance, EU)21- Preparing for an external audit or certification22- After a security incident, to verify compliance didn't break23- Before deploying a new feature that touches sensitive data2425## When NOT to use2627- **Legal interpretation required**: If you need to understand ambiguous regulatory language or interpret case law, consult legal counsel — this skill maps known controls to known requirements, not edge cases28- **One-off compliance question**: If you just need "does GDPR require encryption?", ask directly instead of invoking the full skill29- **Post-breach investigation**: This skill maps controls to requirements; forensics and root-cause analysis are separate concerns30- **Real-time threat response**: During an active incident, focus on containment — compliance mapping comes after stabilization31- **Vendor procurement decisions**: Use this skill to define vendor compliance requirements, not to evaluate salespeople3233## Instructions3435### Step 1: Define Scope and Applicability3637Before mapping controls, clarify:38391. **Regulatory jurisdiction**: Which frameworks apply?40 - GDPR: EU/UK data processing41 - HIPAA: US healthcare data (stricter than general data protection)42 - PCI-DSS: Payment card data handling (any industry)43 - SOC 2 Type II: Service organizations (auditor-driven)44 - Others: Industry-specific (FedRAMP, FISMA, CCPA, etc.)45462. **Data types and locations**: What data does your system touch?47 - Personal data (GDPR, CCPA)48 - Health data (HIPAA)49 - Payment card data (PCI-DSS)50 - Regulated industry data (finance, government, etc.)51523. **Scope boundaries**: Which systems, teams, and processes are in scope?53 - Cloud infrastructure vs. on-premises54 - Third-party vendors and processors55 - Development, staging, and production5657### Step 2: Inventory Existing Security Controls5859Document what you already have:6061| Control | Current Implementation | Evidence Location | Owner |62|---|---|---|---|63| Encryption at rest | (e.g., AES-256 in RDS) | AWS console, IaC repo | Platform team |64| Access control | (e.g., IAM roles, MFA) | Okta config | Security team |65| Audit logging | (e.g., CloudTrail) | AWS account | Ops team |66| ... | ... | ... | ... |6768Use `/security-audit` or manual review to populate this table.6970### Step 3: Map Controls to Requirements7172For each framework, cross-reference your controls against published requirements.7374**GDPR (Article-based)**:75- Article 5: Data subject rights and processor transparency76- Article 32: Technical and organizational measures (encryption, access, testing, monitoring)77- Article 33-35: Breach notification and DPIA7879**HIPAA (Rule-based)**:80- Administrative Safeguards: Workforce security, information access management81- Physical Safeguards: Facility access, workstation use and security82- Technical Safeguards: Access controls, encryption, audit controls, integrity controls8384**PCI-DSS (Requirement-based)**:85- 1-6: Infrastructure security86- 7-8: Access control and user identification87- 9-12: Monitoring, testing, and policies8889**SOC 2 Type II (Trust Service Criteria)**:90- CC (Common Criteria): Security, availability, processing integrity, confidentiality, privacy91- Each criterion has multiple sub-controls; attestation requires time-series evidence9293### Step 4: Identify Gaps9495For each requirement, assess coverage:9697| Requirement | Required | Current | Gap | Severity | Evidence Gap |98|---|---|---|---|---|---|99| GDPR Art. 32: Encryption | Required for PII | AES-256 at rest; no TLS for internal comms | TLS between services | Medium | No inventory of internal TLS |100| PCI-DSS 6.2: Security patches | Monthly minimum | Ad hoc patching every 2-3 months | Automated patching SLA | High | No patch management policy |101| HIPAA Technical Safeguards: Audit logs | All system activity | CloudTrail + RDS logs only; no app logs | App audit trail (who, what, when) | Medium | No centralized log collection |102| SOC 2 CC7.3: Prevent unauthorized data access | Required | IAM roles and MFA | Attribute-based access control (ABAC) | Low | Meets current requirement |103104Severity tiers:105- **Critical**: Failure exposes regulated data or violates legal requirement106- **High**: Creates material risk or audit finding; likely to fail certification107- **Medium**: Best practice gap or incomplete implementation; audit question likely108- **Low**: Recommended for mature programs; typically doesn't block certification109110### Step 5: Generate Remediation Roadmap111112Prioritize by:1131. **Severity**: Critical first, then High, Medium, Low1142. **Implementation cost**: Quick wins first; defer expensive rewrites1153. **Dependencies**: Some controls require others to be in place first1164. **Timeline**: Audit dates, certification deadlines, regulatory deadlines117118**Roadmap template**:119120| # | Control | Gap | Owner | Timeline | Effort | Blockers | Evidence Required |121|---|---|---|---|---|---|---|---|122| 1 | Encrypt internal traffic (TLS) | TLS between services | Platform | Q3 2026 | 2 weeks | Cert management infra | TLS cert audit, network capture |123| 2 | Centralized audit logging | App audit trail | Eng + Ops | Q3 2026 | 3 weeks | Blocked by #1 | Log ingestion setup, 6-month sample |124| 3 | Automated patch management | Patch SLA enforcement | Ops | Q4 2026 | 4 weeks | Blocked by #2 | Patch policy document, 12-month history |125126### Step 6: Build Evidence Inventory for Audit127128Create a control-evidence mapping:129130| Control | Document Type | Owner | Refresh Cadence | Location |131|---|---|---|---|---|132| IAM access control | Policy doc + audit report | Security | Quarterly | Security drive > IAM Policy.pdf + access-audit-Q2-2026.csv |133| Encryption at rest | Architecture doc + test report | Platform | Annually | Security drive > Encryption Standards.md |134| Incident response | Playbook + post-mortems | Security | Ad hoc updates | GitHub > security/incident-response.md |135136Auditors ask for:137- **Policies**: Formal written requirements138- **Evidence**: Logs, screenshots, reports proving compliance139- **Timelines**: Dates showing sustained compliance (not one-off checks)140141---142143## Example144145### Scenario: A US health tech startup preparing for SOC 2 Type II and HIPAA certification146147**Step 1: Scope**148- Frameworks: HIPAA (health data) + SOC 2 Type II (service organization)149- Data: Patient records, genomic data, audit logs150- Scope: AWS cloud, three regions, third-party data processor151152**Step 2: Inventory**153- Encryption: RDS encryption at rest (AES-256), but no TLS in transit154- Access: IAM roles + Okta SSO, but no MFA enforcement155- Logging: CloudTrail + RDS logs, but no application audit trail156- Backup: Daily snapshots, no tested restore procedure157158**Step 3: Map to Requirements**159160HIPAA Technical Safeguards § 164.312(a)(2):161- (i) Encryption and decryption → **Partial**: At rest ✓, in transit ✗162- (ii) Access controls → **Partial**: IAM ✓, MFA ✗, role audits ✗163164SOC 2 CC6.1 (Logical access controls):165- "System is protected against unauthorized logical access" → **Partial**: MFA missing, no attribute-based access166167**Step 4: Gaps**168169| Requirement | Current | Gap | Severity |170|---|---|---|---|171| HIPAA § 164.312(a)(2)(i): Encryption in transit | TLS optional | Enforce TLS for all data flows | Critical |172| HIPAA § 164.312(a)(2)(ii): MFA | Optional | Enforce MFA for healthcare staff | High |173| HIPAA § 164.312(b): Audit controls | CloudTrail + DB logs | Application audit trail (who accessed which records, when) | High |174| SOC 2 CC6.2: User access provisioning | Ad hoc Okta grants | Formal approval workflow + quarterly access reviews | Medium |175176**Step 5: Remediation Roadmap**177178| Priority | Control | Effort | Timeline | Evidence |179|---|---|---|---|---|180| 1 | TLS everywhere | 2 weeks | Q3 immediate | TLS audit, network scan |181| 2 | Enforce MFA | 1 week | Q3 immediate | Okta config, user enrollment report |182| 3 | Application audit trail | 4 weeks | Q3 | Centralized logging setup, 6-month sample logs |183| 4 | Access review workflow | 3 weeks | Q4 | Approval forms, quarterly review records |184185**Step 6: Evidence Collected for Auditors**186187- **HIPAA Compliance Checklist**: Filled in, signed by Security Officer188- **Encryption Audit Report**: Network capture showing TLS on all data flows189- **IAM Access Report**: Q2 2026 access review with manager sign-offs190- **Audit Log Sample**: 6 months of application + system logs proving "who did what when"191- **Policies**: Written HIPAA Security Rule implementation policy, MFA policy, incident response plan192193---194195## Related Skills196197- `/security-audit` — Inventory and assess current security controls198- `/threat-modeling` — Identify new threats; cross-reference against compliance gaps199- `/incident-response` — When gaps are exploited; collect evidence for post-incident compliance