Readiness Assessment

A practical guide to readiness assessment for AI audit and assurance practitioners.

What This Lesson Covers

Readiness Assessment is a key topic within SOC 2 for AI Services. In this lesson you will learn the underlying audit and assurance discipline, the controlling standards and frameworks, how to apply the procedures to real AI systems, and the open questions practitioners are actively working through. By the end you will be able to engage with readiness assessment in real AI audit and assurance work with confidence.

This lesson belongs to the Audit Frameworks & Standards category of the AI Audit & Assurance track. AI audit sits at the intersection of internal audit, IT audit, model risk management, AI governance, and emerging conformity-assessment regimes. Understanding the underlying discipline is what lets you build audit programs that survive board scrutiny, regulator inquiry, and certification audits.

Why It Matters

Apply SOC 2 to AI services. Learn how Trust Services Criteria (Security, Availability, Confidentiality, Processing Integrity, Privacy) extend to AI systems and emerging AI-specific criteria.

The reason readiness assessment deserves dedicated attention is that AI audit and assurance is a young discipline whose standards are landing every quarter (ISO/IEC 42001 audits going live, EU AI Act conformity assessment, AICPA AI assurance, ISACA AI audit toolkit, NYC AEDT bias audits, CO AI Act assessments). Auditors and management who can reason from first principles will navigate the next standard or attestation requirement far more effectively than those who only know current rules.

How It Works in Practice

Below is a practical AI audit framework for readiness assessment. Read through it once, then think about how you would apply it to a real engagement on an AI system in your portfolio.

# SOC 2 Trust Services Criteria mapping for AI services
SOC2_TSC_AI_MAPPING = {
    "Security (CC)": [
        "CC6 logical/physical access -> model registry RBAC, training data perimeter, GPU cluster",
        "CC7 system operations -> production model monitoring, alerting, incident response",
        "CC8 change management -> CI/CD for models, registry approval, rollback testing",
    ],
    "Availability (A)": [
        "Inference uptime SLA, fallback design, multi-region",
        "Capacity planning for GPU/inference",
    ],
    "Processing Integrity (PI)": [
        "Model output correctness vs spec",
        "Data lineage, reproducibility, end-to-end test cases",
        "Hallucination detection + handling for LLM features",
    ],
    "Confidentiality (C)": [
        "Training data + model artifact confidentiality",
        "Customer data isolation in inference",
    ],
    "Privacy (P)": [
        "Notice + consent for AI use of personal data",
        "Subject rights handling on AI-derived data",
        "Cross-border transfer mechanism",
    ],
}

# Type I = design at point in time. Type II = operating effectiveness over period (typically 6-12 months).
# Most AI services pursue Type II for credibility; some do Type I bridging until enough operating evidence.

Step-by-Step Analytical Approach

1. Establish the criteria — What standard, framework, or policy will this audit measure against (NIST RMF, ISO 42001, EU AI Act Article 9, internal policy, contractual commitment)? Document the criteria up front; auditing without explicit criteria is opinion, not assurance.
2. Plan the procedures — Map criteria to procedures (inquire, observe, inspect, recalculate, reperform, analytics). For AI specifically, prefer reperformance (rerun the eval) over inquiry (“trust the team”).
3. Sample appropriately — Statistical for control-pass-fail tests, judgmental for corner cases, stratified for fairness, adversarial-seed for robustness. Document the sampling rationale.
4. Collect sufficient appropriate evidence — Multiple sources, time-stamped, hash-pinned, secured. The bar is what a sophisticated reviewer would expect to support the conclusion.
5. Form the conclusion — Compare evidence to criteria; identify exceptions; quantify if possible; classify by severity.
6. Communicate and track — Findings + recommendations + management response; tracker through validated closure; periodic aging report to audit committee.

When This Topic Applies (and When It Does Not)

Readiness Assessment applies when:

• You are providing assurance over AI systems (internal audit, external audit, certification, regulator)
• You are subject to a standard that requires AI audit (EU AI Act conformity, ISO 42001 certification, sector regulator audit)
• You need to demonstrate AI controls operate effectively to the board, customers, regulators, or in litigation
• You are consuming third-party AI assurance reports (SOC 2, ISO 42001 certificate, AICPA attestation)

It does not apply (or applies lightly) when:

• The activity is design-stage advisory rather than independent assurance
• The AI system is genuinely low-stakes with no audit obligation
• The work is consulting / co-sourcing rather than independent audit (independence rules differ)

Practitioner Checklist

• Are the criteria for this engagement explicit, written, and agreed with management?
• Are procedures designed to give sufficient appropriate evidence (not just inquiry)?
• Is the sample defensible (rationale documented, stratified where relevant)?
• Is evidence preserved with integrity (timestamp, hash, immutable storage)?
• Are findings traceable from evidence to criteria to conclusion?
• Do you have a written management response with owner and due date?
• Is closure validation tested, not self-attested?

Disclaimer

This educational content is provided for general informational purposes only. It does not constitute audit, legal, regulatory, or professional advice; it does not create a professional engagement; and it should not be relied on for any specific audit, certification, or compliance matter. AI audit standards and regulations vary by jurisdiction and change rapidly. Consult qualified professional auditors and counsel for advice on your specific situation.

Next Steps

The other lessons in SOC 2 for AI Services build directly on this one. Once you are comfortable with readiness assessment, the natural next step is to combine it with the patterns in the surrounding lessons — that is where doctrinal mastery turns into a working audit program. AI audit is most useful as an integrated discipline covering planning, fieldwork, evidence, conclusion, reporting, and remediation.