Skip to content

SOC2 Audit — Provided By Client (PBC) Guide

Purpose

When the SOC2 auditor arrives they send a PBC list — a specific set of evidence requests. This guide maps each common request to exactly where the evidence lives so audit response time is hours, not days.

Audit window: September 2026 (Type II — evidence covers the preceding 12 months) Auditor contact: TBD — see Adriana for current engagement details Internal coordinator: Rory (technical evidence), Adriana (administrative docs)


How SOC2 Type II Evidence Works

Type II means the auditor is checking that controls operated consistently over the audit period — not just that they exist today. For every control, they want to see:

  1. A policy or procedure describing the control
  2. Evidence the control actually ran during the period (logs, screenshots, reports)
  3. Exception handling if it ever failed

If a control was implemented mid-period, document the implementation date. Partial coverage is better than pretending it was always there.


PBC Evidence Map

CC1 — Control Environment (Policies and Organization)

Auditor RequestLocationWho Provides
Information security policycompliance/hipaa-policy-set.mdRory
Acceptable use policycompliance/hipaa-policy-set.mdRory
Org chart / key personnelREADME.md → Key People tableRory
Risk assessmentcompliance/hipaa-risk-assessment.mdRory
Evidence of risk assessment reviewGit commit history on hipaa-risk-assessment.mdRory
Vendor management policycompliance/vendor-risk-inventory.mdAdriana
BAA registercompliance/vendor-phi-inventory.mdAdriana

CC2 — Communication and Information

Auditor RequestLocationWho Provides
Security awareness training policycompliance/hipaa-policy-set.mdRory
Training completion records for audit periodcompliance/training-completion-log.mdRory
Phishing simulation resultscompliance/phishing-simulation-schedule.md + SecOps evidenceRory
Evidence employees acknowledged policiesOnboarding checklist completion recordsAdriana

CC3 — Risk Assessment

Auditor RequestLocationWho Provides
Formal risk assessment documentcompliance/hipaa-risk-assessment.mdRory
Threat modelsecurity/threat-model.mdRory
Risk acceptance registercompliance/risk-acceptance-register.mdRory
Evidence of risk assessment updatesGit history on threat model and risk assessmentRory

CC4 — Monitoring Activities

Auditor RequestLocationWho Provides
Evidence of continuous monitoringcompliance/logging-architecture.md — log sources and archiveRory
Security monitoring tool evidencearchitecture/security-monitoring-architecture.mdRory
Sample HIPAA audit email reportsops-automation email archive (IT admin mailbox)Rory
Arctic Wolf MDR reports (sample)Arctic Wolf portal → ReportsRory
Vulnerability scan resultscompliance/pentest-results-log.md → GitHub Actions artifactsRory
Evidence of alert reviewSecOps incident history for audit periodRory

CC5 — Control Activities (Policies and Procedures)

Auditor RequestLocationWho Provides
Change management policy/procedurecicd/pipeline-overview.md + security/firewall-change-procedure.mdRory
Evidence of change management during periodGitHub PR history (all infra repos) — every merge = documented CMRory
Change management ticketsSecOps → Changes table (auto-created per merged PR)Rory
Incident response procedurerunbooks/incident-response.mdRory
Evidence of IR procedure useSecOps incident history for audit periodRory

CC6 — Logical and Physical Access Controls

Auditor RequestLocationWho Provides
Access control policycompliance/three-layer-access-architecture.mdRory
User access provisioning/de-provisioning procedurecompliance/onboarding-security-checklist.mdRory
MFA evidenceEntra ID → Conditional Access policy screenshotsRory
Privileged access controlscompliance/pam-scope.md + PIM audit reportsRory
Access review evidencecompliance/access-control-review.md + periodic review recordsRory
Terminated user offboarding evidenceHR records + Entra account disable timestampsAdriana + Rory
Remote access controlscompliance/vpnlyr-audit-evidence.mdRory
Encryption in transit/at restcompliance/hipaa-controls.md §164.312(a)(2)(iii)Rory
Break-glass account controlsrunbooks/break-glass-procedure.mdRory

CC7 — System Operations

Auditor RequestLocationWho Provides
Vulnerability management proceduresecurity/vulnerability-management.md + security/penetration-testing.mdRory
Penetration test results for audit periodcompliance/pentest-results-log.md → GitHub Actions artifactsRory
Patch management evidencesecurity/patch-management.md + Intune patch reportsRory
EDR coverage evidencesecurity/edr-cortex-xdr.md + Cortex XDR console screenshotsRory
MDR evidenceArctic Wolf portal — MDR scope + coverage reportsRory
Incident log for audit periodSecOps incident exportRory
Evidence of log reviewMonthly security review recordsRory

CC8 — Change Management

Auditor RequestLocationWho Provides
Change management procedurecicd/pipeline-overview.md + security/firewall-change-procedure.mdRory
Evidence of CI/CD pipeline enforcing controlsGitHub Actions run history + Checkov scan results on PRsRory
OIDC authentication evidence (no stored secrets)cicd/oidc-authentication.md + GitHub Actions workflow filesRory
Sample change ticketsSecOps → Changes for audit periodRory
Evidence changes were tested before productionterraform plan output in PR comments (GitHub PR history)Rory

CC9 — Risk Mitigation

Auditor RequestLocationWho Provides
Vendor due diligencecompliance/vendor-risk-inventory.mdAdriana
BAA statuscompliance/vendor-phi-inventory.mdAdriana
Cyber insurancecompliance/cyber-insurance-review-checklist.md + policy on fileAdriana
IR retainercompliance/ir-retainer-evaluation.mdAdriana

A1 — Availability (if in scope)

Auditor RequestLocationWho Provides
Business continuity / DR planaws/dr-overview.md + aws/dr-failover-procedure.mdRory
Emergency mode operation plancompliance/emergency-mode-operation-plan.mdRory
Backup architecturerunbooks/backup-architecture.mdRory
Evidence of backup testingVeeam validation report (March 4, 2026) in runbooks/backup-architecture.mdRory
DR test resultsQ2 2026 DR test results (post June test)Rory
RTO/RPO definitionsrunbooks/backup-architecture.md — RPO ~24h, RTO 1–4h/4–8hRory

C1 — Confidentiality (if in scope)

Auditor RequestLocationWho Provides
Data classification policycompliance/hipaa-policy-set.mdRory
PHI handling procedurescompliance/hipaa-administrative-procedures.mdRory
DLP controls evidencecompliance/purview-dlp-enforce-mode-criteria.md + Purview audit logsRory
Encryption documentationcompliance/hipaa-controls.md §164.312(a)(2)(iii)Rory

Evidence Collection — How To Pull It

GitHub evidence (CI/CD, change management)

Pull all merged PRs for a given repo and date range:

gh pr list --repo Cirius-Group-Inc/azure-infra --state merged --limit 200 \
  --json number,title,mergedAt,author | jq '.[] | select(.mergedAt > "2025-09-01")'

For each PR, the auditor can see: what changed, who approved, what Checkov/terraform plan said, when it merged.

Entra / Azure evidence

Export from Azure Portal → Entra ID → Sign-in logs (CSV export, max 30 days per pull). For longer periods, use Log Analytics — SignInLogs table in cirius-logging-law-central.

SecOps incident evidence

Export from secops.bedrockcybersecurity.org — admin panel → Incidents → Export CSV for date range. Provides incident timeline, severity, resolution for the audit period.

Arctic Wolf evidence

Log in to Arctic Wolf portal → Reports → generate coverage and activity report for the audit period. Arctic Wolf also provides an annual summary letter for auditors on request.

Cortex XDR evidence

Log in to Cortex XDR console → Reports → Endpoint inventory report (shows all protected endpoints) + activity summary. Export as PDF for auditor.


What Auditors Always Ask That You Might Forget

These come up every audit and are easy to miss:

  1. Terminated user list — show that departed employees' access was revoked within X days. Pull from HR (Adriana) + Entra account disable timestamps. Match the dates.

  2. Evidence that someone actually looked at the security reports — not just that they were generated. Monthly security review records with a date and Rory's sign-off.

  3. Exception register — any deviation from policy (a privileged account without MFA, a resource without tagging) must be formally accepted. See compliance/risk-acceptance-register.md. An auditor who finds an undocumented exception is more concerned than one who finds a documented one.

  4. Evidence of training for everyone, not just new hires — annual refresher completion, not just onboarding completion.

  5. Business continuity test evidence — not just the plan, but proof it was tested. The June 2026 DR test with written results is critical for the September audit.


Pre-Audit Checklist (Run 4–6 Weeks Before Audit)

  • [ ] compliance/hipaa-risk-assessment.md — reviewed and dated within 12 months
  • [ ] compliance/training-completion-log.md — all employees have current-year entries
  • [ ] compliance/pentest-results-log.md — last 12 months of monthly results documented
  • [ ] compliance/vendor-phi-inventory.md — all BAAs current (check expiry dates)
  • [ ] compliance/risk-acceptance-register.md — all open exceptions reviewed
  • [ ] compliance/access-control-review.md — access review completed within 6 months
  • [ ] June 2026 DR test completed and results documented
  • [ ] SecOps incident export for audit period — verify all P1/P2 incidents have resolution notes
  • [ ] Arctic Wolf annual summary letter requested
  • [ ] Cortex XDR endpoint coverage report exported


Document History

DateChangeAuthor
May 2026Initial draft — maps all common SOC2 PBC requests to evidence locations. Covers CC1–CC9, A1, C1.Rory

Internal use only — Cirius Group