AI Skill Report Card

Auditing Compliance

A-87·Sep 27, 2026·Source: Web

Compliance Auditor

14 / 15

Given a target framework (ISO 27001, SOC2, GDPR, etc.) and information about current practices, produce four deliverables in order: Compliance Matrix → Gap Analysis → Audit Checklist → Remediation Plan.

Input: "Assess our SaaS platform against SOC2 Type II Trust Services Criteria"
Output:
1. Compliance Matrix mapping each TSC (Security, Availability, Processing
   Integrity, Confidentiality, Privacy) to current controls and evidence
2. Gap Analysis identifying missing/weak controls per criterion
3. Audit Checklist of items to verify before external audit
4. Remediation Plan with owners, priority, and timeline for each gap
Recommendation▾
Add a third example covering a non-compliant/failing scenario with lower readiness score to show range of outcomes
15 / 15

Progress:

  • Step 1: Identify applicable framework(s) and scope (systems, data, business units)
  • Step 2: Gather evidence of current controls (policies, configs, logs, interviews)
  • Step 3: Build Compliance Matrix (requirement → control → evidence → status)
  • Step 4: Perform Gap Analysis (status = Compliant / Partial / Non-Compliant / N/A)
  • Step 5: Draft Audit Checklist for pre-audit verification
  • Step 6: Create Remediation Plan (gap → action → owner → priority → deadline)
  • Step 7: Summarize overall risk posture and readiness score

Step details

1. Scope framework Clarify which standard(s) apply and any overlap (e.g., ISO 27001 + SOC2 share many controls — map once, reuse). Note applicable GDPR articles if personal data is processed (Art. 5, 6, 25, 30, 32, 33).

2. Gather evidence Ask for or infer: security policies, access control lists, encryption standards, incident response plans, vendor contracts, data flow diagrams, training records. Flag anything unverifiable as "evidence pending."

3. Compliance Matrix Table format:

Requirement IDFramework ClauseControl DescriptionImplementation StatusEvidence

4. Gap Analysis For every "Partial" or "Non-Compliant" item, state: root cause, risk level (Critical/High/Medium/Low), and business impact if unaddressed.

5. Audit Checklist Actionable yes/no items an auditor would check, grouped by domain (Access Control, Data Protection, Incident Management, Vendor Management, Change Management, Logging & Monitoring).

6. Remediation Plan Table format:

GapRecommended ActionOwnerPriorityTarget DateStatus

Prioritize Critical/High risk items first; group quick wins separately from long-term structural fixes.

Recommendation▾
Include a brief template for the overall 'readiness score' summary mentioned in Step 7, since it's referenced but never demonstrated
16 / 20

Example 1: Input: "GDPR readiness check for a marketing platform storing EU customer emails" Output:

  • Compliance Matrix: Art. 5 (data minimization) → Partial, only collecting necessary fields but no retention policy; Art. 32 (security) → Compliant, TLS + encryption at rest; Art. 30 (records of processing) → Non-Compliant, no ROPA maintained
  • Gap Analysis: Missing ROPA = High risk (regulatory fine exposure); no retention policy = Medium risk
  • Audit Checklist: "Is a Record of Processing Activities maintained and updated quarterly?" "Is there a documented data retention/deletion schedule?"
  • Remediation Plan: Create ROPA (Owner: DPO, Priority: High, 30 days); Draft retention policy (Owner: Legal, Priority: Medium, 60 days)

Example 2: Input: "ISO 27001 gap assessment for access control domain (A.9)" Output:

  • Compliance Matrix: A.9.2.1 (user registration) → Compliant; A.9.2.5 (access review) → Partial, reviews done annually instead of quarterly
  • Gap Analysis: Infrequent access reviews = Medium risk of privilege creep
  • Audit Checklist: "Are access rights reviewed at defined intervals?" "Is there evidence of deprovisioning within 24h of termination?"
  • Remediation Plan: Implement quarterly access review process (Owner: IT Security, Priority: Medium, 45 days)
Recommendation▾
Clarify how to handle conflicting requirements when multiple frameworks overlap but differ in specifics
  • Always cite the specific clause/article number, not just the framework name.
  • Distinguish between "control exists" and "control is evidenced" — auditors need proof, not intent.
  • Use consistent risk rating scale (Critical/High/Medium/Low) across all sections.
  • Cross-reference overlapping requirements across frameworks to avoid duplicate remediation work.
  • Keep remediation actions SMART (specific, measurable, assigned, time-bound).
  • Flag any finding requiring legal/DPO review separately — don't give legal conclusions yourself.
  • Don't mark something "Compliant" without evidence — default to "Partial" or "Evidence Pending" if unverified.
  • Don't merge Gap Analysis into the matrix — keep them as distinct deliverables for clarity.
  • Don't give vague remediation actions like "improve security" — specify the exact control to implement.
  • Don't ignore scope boundaries — a control outside the assessed scope should be marked N/A, not skipped silently.
  • Don't treat all gaps as equal priority — always rank by risk and business impact.
0
Grade A-AI Skill Framework
Scorecard
Criteria Breakdown
Quick Start
14/15
Workflow
15/15
Examples
16/20
Completeness
18/20
Format
15/15
Conciseness
13/15