IAM Audit Preparation Guide: SOX, SOC 2, and HIPAA Readiness

IAM audit findings are among the most common and most consequential compliance issues organizations face. "Excessive access," "inadequate access reviews," "untimely deprovisioning," and "insufficient segregation of duties" appear on audit reports with predictable regularity. These findings carry real consequences: SOX material weaknesses can affect stock price, SOC 2 qualifications can lose you customers, and HIPAA violations carry financial penalties.

The irony is that most IAM audit failures are not caused by bad technology or malicious intent. They result from poor preparation, organizations that manage access reasonably well day-to-day but cannot produce the evidence to prove it. This guide helps you bridge that gap.

Prerequisites

• Understanding of your regulatory scope, Which frameworks apply? SOX (public companies), SOC 2 (service organizations), HIPAA (healthcare data), PCI DSS (payment data), or others.
• An IAM platform with logging enabled, You cannot produce evidence from systems that do not log.
• Access to audit reports from previous years, Understanding prior findings accelerates preparation.
• Collaboration with Internal Audit, They are your partners in preparation, not your adversaries.

Architecture: The Audit Evidence Framework

What Auditors Are Looking For

Across all frameworks, auditors evaluate IAM against a consistent set of control objectives:

1. Access Provisioning Controls

• Is access granted based on documented approval?
• Are access rights appropriate for the user's role?
• Is there a formal access request and approval workflow?

2. Access Review Controls

• Is existing access reviewed periodically?
• Are reviews performed by appropriate reviewers (managers, data owners)?
• Are review decisions documented and acted upon?

3. Access Termination Controls

• Is access revoked timely when employment ends?
• Are there orphan or dormant accounts?
• Is there a process to detect and remediate stale access?

4. Privileged Access Controls

• Is privileged access limited to those who need it?
• Is privileged access monitored and reviewed more frequently?
• Are privileged sessions logged and auditable?

5. Segregation of Duties

• Are conflicting duties identified and separated?
• Are SoD violations detected and remediated?
• Are exceptions documented with compensating controls?

6. Authentication Controls

• Is multi-factor authentication enforced?
• Are password policies appropriate?
• Are authentication events logged?

Framework-Specific Requirements

SOX (Sarbanes-Oxley): SOX focuses on the integrity of financial reporting. IAM controls are relevant because unauthorized access to financial systems could lead to fraudulent reporting.

Key SOX IAM requirements:

• Access to financial applications must be approved by management.
• Segregation of duties must prevent any individual from controlling all aspects of a financial transaction.
• Access reviews must be performed for systems that affect financial reporting.
• Terminated employees must lose access to financial systems immediately.
• Privileged access to financial databases and applications must be tightly controlled.

Audit scope: Applications that feed into, process, or report financial data. This typically includes ERP systems, general ledger, accounts payable/receivable, payroll, and financial reporting tools.

SOC 2 (Service Organization Control): SOC 2 evaluates controls relevant to security, availability, processing integrity, confidentiality, and privacy. The Trust Services Criteria (TSC) define the control objectives.

Key SOC 2 IAM requirements (Common Criteria):

• CC6.1: Logical and physical access controls, the entity implements controls to restrict logical access based on authorization.
• CC6.2: Prior to issuing system credentials, the entity registers and authorizes new users with appropriate approval.
• CC6.3: The entity authorizes, modifies, or removes access to data, software, functions, and other protected information assets based on roles.
• CC6.5: The entity discontinues logical and physical protections over assets only after the ability to protect them is transferred.

HIPAA (Health Insurance Portability and Accountability Act): HIPAA's Security Rule requires covered entities and business associates to implement administrative, physical, and technical safeguards for electronic Protected Health Information (ePHI).

Key HIPAA IAM requirements:

• Unique user identification (164.312(a)(2)(i)), assign a unique identifier for each workforce member.
• Emergency access procedure (164.312(a)(2)(ii)), establish procedures for obtaining ePHI during emergencies.
• Automatic logoff (164.312(a)(2)(iii)), implement electronic procedures to terminate sessions after inactivity.
• Access control (164.312(a)(1)), implement technical policies and procedures that allow access to ePHI systems only to persons or software programs granted access rights.
• Access authorization (164.308(a)(4)(ii)(B), an addressable administrative safeguard), implement policies and procedures for granting access to ePHI, for example through access to a workstation, transaction, program, or process. The companion specification 164.308(a)(4)(ii)(C) covers establishing, documenting, reviewing, and modifying a user's access.
• Audit controls (164.312(b)), implement mechanisms to record and examine activity in systems containing ePHI.

Step-by-Step: Audit Preparation

Step 1: Determine Scope and Timeline

Identify in-scope systems:

For each regulatory framework, identify which applications, databases, and infrastructure components are in scope:

Application	SOX In-Scope	SOC 2 In-Scope	HIPAA In-Scope	IAM Integrated
SAP ERP	Yes	No	No	Yes
AWS Production	Yes	Yes	Yes	Yes (SSO)
Salesforce	No	Yes	No	Yes (SSO)
Epic EHR	No	No	Yes	Partial
Jira	No	Yes	No	Yes (SSO)

Establish the audit period:

• SOX: Fiscal year (Jan 1 - Dec 31 for calendar year companies)
• SOC 2 Type II: Typically 6 or 12 months
• HIPAA: Point-in-time assessment or review period as defined by the auditor

Create a preparation timeline:

• T-90 days: Begin evidence collection and gap analysis
• T-60 days: Remediate identified gaps
• T-30 days: Complete evidence packages and conduct dry run
• T-14 days: Final review with Internal Audit
• T-0: External audit fieldwork begins

Step 2: Collect Access Evidence

User access listings:

For each in-scope application, generate a complete user access listing showing:

• User identifier (employee ID or username)
• Full name
• Job title and department
• Access level or role within the application
• Date access was granted
• Approver of the access
• Date of last access review
• Active/disabled status

Automate this extraction. Manual screenshots are error-prone and auditors will question them.

-- Example: Extract user access listing from your IAM platform
SELECT
  u.employee_id,
  u.display_name,
  u.department,
  u.job_title,
  ua.application_name,
  ua.role_name,
  ua.granted_date,
  ua.approved_by,
  ua.last_review_date,
  u.status
FROM users u
JOIN user_access ua ON u.id = ua.user_id
WHERE ua.application_name IN ('SAP', 'AWS-Production', 'Salesforce')
ORDER BY ua.application_name, u.display_name;

Privileged access listings:

Separately enumerate all privileged/admin access:

• System administrators
• Database administrators
• Application administrators
• Users with elevated roles (finance approvers, HR administrators)
• Service accounts with privileged access

Terminated user access evidence:

For each employee terminated during the audit period, provide:

• Termination date (from HR)
• Date account was disabled in the IdP
• Date access was revoked in each in-scope application
• Time delta between termination and access revocation

This is where many organizations fail. Auditors compare each time delta against your documented termination policy, so a multi-day lag on a policy that promises same-day removal is a finding.

Step 3: Document Access Review Evidence

Certification campaign records:

For each access review campaign during the audit period, provide:

• Campaign scope (which applications, which users)
• Campaign dates (start, deadline, completion)
• Reviewer list (who reviewed which users)
• Decision records (for each entitlement: certified, revoked, or escalated)
• Completion rate (percentage of reviews completed)
• Revocation evidence (for items that were revoked, evidence that access was actually removed)

Format evidence clearly:

Auditors review hundreds of controls across many organizations. Make their job easy:

Access Review Campaign: Q1 2026 - Financial Applications
Period: January 15 - February 15, 2026
Applications: SAP ERP, Oracle Financials, Concur
Total entitlements reviewed: 2,847
Completion rate: 97.3%
Entitlements certified: 2,712 (95.3%)
Entitlements revoked: 108 (3.8%)
Entitlements pending (escalated): 27 (0.9%)
Revocations completed: 108/108 (100%), Evidence attached as Appendix C

Step 4: Prepare Segregation of Duties Evidence

SoD rule documentation:

For each SoD rule, provide:

• Rule definition (which entitlements conflict and why)
• Business risk if the rule is violated
• Current violation count
• Remediation status for each violation
• Exception documentation for approved violations

SoD exception documentation:

For each approved SoD exception:

• The specific violation (user, conflicting entitlements)
• Business justification for the exception
• Compensating control description
• Approval from appropriate authority (typically CISO or CFO for financial SoD)
• Exception expiration date
• Evidence that the compensating control is operating effectively

Step 5: Prepare Authentication and Policy Evidence

MFA coverage evidence:

• Total user population
• Users enrolled in MFA
• MFA enforcement policy (screenshot or export of conditional access policy)
• Exceptions to MFA policy with justification
• MFA method distribution (authenticator app, FIDO2, SMS)

Password policy evidence:

• Configured password policy (length, complexity, expiration, history)
• Policy enforcement mechanism (IdP configuration screenshot or export)
• Evidence that the policy applies to all in-scope applications

Conditional access / login policy evidence:

• All conditional access policies with descriptions
• Policy assignments (who is affected)
• Policy controls (what is enforced)
• Policy exceptions with justification

Step 6: Conduct a Gap Analysis and Remediate

Before the audit, conduct an honest self-assessment:

Common gaps and remediation:

Gap	Risk Level	Remediation	Timeline (rough estimate)
Terminated users with active access	Critical	Run reconciliation, disable accounts, implement automated deprovisioning	2 weeks
No access reviews for some applications	High	Conduct retroactive review, implement ongoing schedule	4 weeks
Undocumented SoD exceptions	High	Document existing exceptions with compensating controls	2 weeks
Shared/generic accounts in use	Medium	Assign individual accounts, disable shared accounts	6 weeks
Missing approval records for access grants	Medium	Implement request/approval workflow, retroactively document existing access	4 weeks
MFA not enforced for all users	Medium	Enable MFA for remaining users, document exceptions	3 weeks

Step 7: Package Evidence for Auditors

Evidence package structure:

IAM Audit Evidence Package
├── 1. Access Provisioning
│   ├── Access request and approval policy
│   ├── Sample access request approvals (the sample your auditor selects)
│   └── Access provisioning procedure documentation
├── 2. Access Reviews
│   ├── Access review policy
│   ├── Campaign records (Q1, Q2, Q3, Q4)
│   ├── Revocation evidence
│   └── Review completion reports
├── 3. Access Termination
│   ├── Termination procedure documentation
│   ├── Terminated user list with deprovisioning dates
│   └── Reconciliation evidence (no orphan accounts)
├── 4. Privileged Access
│   ├── Privileged access listing
│   ├── Privileged access review records
│   └── PAM session logs (sample)
├── 5. Segregation of Duties
│   ├── SoD rule matrix
│   ├── Current violation report
│   ├── Exception documentation
│   └── Compensating control evidence
├── 6. Authentication
│   ├── MFA policy and coverage report
│   ├── Password policy configuration
│   └── Conditional access policies
└── 7. Supporting Documentation
    ├── IAM architecture diagram
    ├── In-scope application inventory
    └── IAM policy and standards documents

Best Practices

Automate Evidence Collection

If evidence collection requires manual effort each audit cycle, it will be incomplete and error-prone. Automate:

• User access listing generation (scheduled exports from your IAM platform)
• Terminated user reconciliation (daily automated comparison of HR data and active accounts)
• Access review completion tracking (real-time dashboards from your IGA platform)
• Privileged access monitoring (continuous logging from your PAM solution)

Maintain Continuous Audit Readiness

Do not prepare for audits. Maintain continuous compliance:

• Run access reviews on schedule throughout the year, not in a rush before the audit.
• Process terminations within hours, not days.
• Document SoD exceptions when they are approved, not when auditors ask.
• Generate evidence reports monthly, not annually.

Organizations that maintain continuous readiness spend a fraction of the time on audit preparation compared to those that scramble.

Build Relationships with Auditors

External auditors are evaluating your controls, not trying to catch you. Early communication about your IAM program, proactive disclosure of known issues and remediation plans, and well-organized evidence packages build credibility. Auditors are far more understanding of issues you have identified and are actively remediating than issues they discover that you were unaware of.

Track Remediation Formally

When auditors identify findings, track remediation with formal project management:

• Assign an owner to each finding
• Set a remediation deadline
• Define success criteria
• Report progress to the governance committee monthly
• Verify remediation before the next audit cycle

Testing

Dry Run Audit

Two months before the external audit:

1. Have Internal Audit or a trusted team member role-play as the external auditor.
2. Request the same evidence the external auditor will request.
3. Evaluate the completeness, accuracy, and organization of the evidence.
4. Identify gaps and remediate them before the real audit.

Sample Testing

Auditors will sample your evidence. Pre-test your samples:

• Pull a random sample of terminated employees and verify all access was revoked within your policy.
• Pull a random sample of access grants and verify approval documentation exists.
• Pull a random sample of SoD exceptions and verify compensating controls are documented and operating.

If you find issues in your pre-test samples, investigate and remediate the underlying cause before the audit.

Common Pitfalls

Reactive Audit Preparation

Scrambling to produce evidence in the weeks before an audit is the most common failure mode. Evidence gathered under time pressure is incomplete, inconsistent, and raises auditor skepticism. Start preparation at least 90 days before fieldwork.

Inconsistent Evidence Across Applications

If your user access listing for Application A is a database export and for Application B is a series of screenshots, auditors will question the reliability. Standardize evidence formats across all in-scope applications.

Ignoring Service and System Accounts

Auditors increasingly scrutinize non-human accounts. If your privileged access listing only includes human administrators but your financial database has 15 service accounts with admin access, expect a finding.

Providing Too Much or Too Little Evidence

Overwhelming auditors with raw data dumps is as problematic as providing insufficient evidence. Provide concise, well-organized evidence that directly addresses the control objective. Include summary reports with supporting detail available upon request.

Not Addressing Prior Year Findings

Repeat findings are worse than first-time findings. They indicate that the organization is not taking compliance seriously. Prioritize remediating prior year findings above all else.

Conclusion

IAM audit preparation is fundamentally about maintaining disciplined identity governance practices and being able to demonstrate them with evidence. The organizations that pass audits cleanly are not those with perfect IAM, they are those that have documented processes, execute them consistently, identify and remediate gaps proactively, and present evidence clearly.

Invest in automation for evidence collection, maintain continuous audit readiness rather than annual preparation sprints, and treat each audit cycle as an opportunity to improve your IAM program. Over time, audit preparation becomes a routine reporting exercise rather than a fire drill.