On this page
SOC 2 security controls are the controls you design to meet the AICPA's Common Criteria, which apply to every SOC 2 report, even one that leaves out the Security category. CC6 has eight criteria on access and CC7 has five on detecting and responding to security events. The table below gives each criterion's example controls from [our library](/insights/soc-2-controls-list/), the evidence an auditor may ask to see, and a readiness gap to check. One control can support two criteria, and in our mapping CC6.5 and CC7.3 each rest on a single control. CC7.2 and its points of focus name no SIEM or other product class, so a SIEM is not required.
Which library controls and evidence map to each CC6 and CC7 criterion?
Our controls library maps every criterion from CC6.1 to CC6.8 and CC7.1 to CC7.5 to named example controls, each with the evidence an auditor may ask to see. Several controls carry two criteria, so a team can operate each one once and cite it under every criterion it supports.
The criteria are not a prescribed control catalog: you design controls for your risks, and the auditor tests them against the criteria. The SOC 2 controls library holds 82 example controls across all criteria, and the table lists the ones mapped to CC6 and CC7. Control IDs do not change once issued. Reports today use the 2017 Trust Services Criteria with the 2022 points of focus, and the IDs here follow them. The AICPA’s proposed 2027 criteria are not in force: see what they change.
Jump to a criterion: CC6.1 · CC6.2 · CC6.3 · CC6.4 · CC6.5 · CC6.6 · CC6.7 · CC6.8 · CC7.1 · CC7.2 · CC7.3 · CC7.4 · CC7.5
| Criterion | Library controls | Evidence an auditor may ask to see | Readiness gap to check |
|---|---|---|---|
| CC6.1 Logical access securityProtect information assets with logical access software, infrastructure and architecture. | AC-01 MFA and unique user IDs; AC-02 secrets and service-account credentials; AC-07 privileged and break-glass access; AC-08 customer login and tenant isolation; AC-09 connected-app review; AM-01 system and data inventory; DP-01 encryption at rest; NS-02 authenticated production access; EP-01 managed laptops; EP-03 device baseline | Identity-provider MFA policy export and SSO application list; secrets-manager access policy and a service-account inventory with owners; admin account list with a reason for each; application login settings and tenant-isolation tests; export of connected apps and OAuth grants; inventory checked against a cloud resource export; encryption settings for each data store; device compliance reports | MFA not enforced; unmanaged credentials |
| CC6.2 User registration and removalRegister and authorize users before issuing credentials, and remove credentials when access ends. | AC-03 approval before access; AC-04 removal at departure; AC-06 quarterly access review | Request tickets with requester, approver and approval time set against account-creation timestamps; HR termination list set against deactivation timestamps, including systems outside SSO; review sign-offs and removal records | Access provisioned before approval is documented; contractors with indefinite access |
| CC6.3 Roles and least privilegeAuthorize, change and remove access by role, with least privilege and segregation of duties in mind. | AC-04 removal at departure; AC-05 role-based access; AC-06 quarterly access review; AC-07 privileged and break-glass access | Role matrix against the current user-to-role export; approval tickets for permissions beyond a role; dated account exports with reviewer decisions; leaver deactivation records, as under CC6.2 | Access review run once and not repeated at the cadence your policy sets (the points of focus set none); records confirm the user list but not the permissions themselves |
| CC6.4 Physical accessRestrict physical access to facilities and protected assets to authorized personnel. | PE-01 office and equipment-room entry; PE-02 hosting provider report review | Badge user list against current staff, visitor log and badge removals for leavers; each provider's current SOC 2 report with a review note on exceptions and the customer controls you rely on | No visitor log; no evidence the cloud provider's SOC 2 report was reviewed |
| CC6.5 Asset disposalKeep protections on physical assets until the ability to read or recover their data and software has been diminished and is no longer needed to meet objectives. | AM-02 wipe or destroy before reuse or disposal | Disposal log linked to the asset inventory with method, date and person; remote-wipe confirmations; destruction certificate listing serial numbers | Retired equipment lacks sanitization evidence |
| CC6.6 Outside threatsProtect the system with logical access measures against threats from outside its boundaries. | NS-01 internet exposure and segmentation; NS-02 authenticated production access; AC-09 connected-app review | Firewall or security-group settings showing allowed inbound traffic; public endpoint inventory with owners; dated quarterly rule review; SSH and RDP closed to the internet; remote-access settings requiring SSO and MFA, with session logs; export of connected apps and OAuth grants | Broad firewall rules or unreviewed public endpoints |
| CC6.7 Transmission and removal of dataRestrict the movement and removal of information to authorized users and protect it while it moves. | NS-03 TLS and approved transfer methods; AIM-02 AI provider data settings | TLS scan results for public endpoints; data-handling rule naming approved transfer methods; log or tickets for bulk exports of customer data; AI provider settings for training opt-out, retention and data region | TLS 1.0/1.1 still enabled on legacy endpoints; no data transfer policy |
| CC6.8 Malicious softwarePrevent or detect, and act on, unauthorized or malicious software. | EP-01 managed laptops; EP-02 malware protection; EP-03 device baseline | Device enrollment report against the device inventory; protection coverage report with agent status and last check-in; malware alert log with an outcome for each alert | Malware protection missing on some in-scope endpoints or servers |
| CC7.1 Configuration and vulnerability detectionDetect configuration changes that introduce vulnerabilities, and susceptibility to newly discovered ones. | VM-01 baselines and scheduled scans; VM-02 fixes within deadlines; VM-03 annual penetration test | Hardening standard and dated scan reports covering the inventory; dependency scan results from CI; remediation tickets with open and close dates, plus signed risk acceptances; penetration test report with retest | Scans miss in-scope systems; findings or patches miss the deadlines in your policy |
| CC7.2 Anomaly monitoringMonitor system components for anomalies and analyze them to decide whether they are security events. | LG-01 central logging; LG-02 alerting and triage; BC-06 uptime monitoring; AIM-03 AI request logging | Audit logging enabled in every cloud account and region in use; log sources compared with the inventory; retention settings; alert rules, on-call routing and alert records with triage notes; uptime monitor setup and outage tickets | Missing log sources or retention short of the period; alerts with no on-call or tuning evidence |
| CC7.3 Evaluation of security eventsDecide whether a security event is an incident, and act to prevent or address the failure. | LG-02 alerting and triage | Alert records with acknowledgment time, triage notes and outcome; written severity criteria for deciding when an event is an incident | No incident classification criteria; incidents tracked informally in Slack |
| CC7.4 Incident responseRespond to identified incidents through a defined incident-response program. | IR-01 response plan; IR-02 annual exercise; IR-03 incident records; IR-04 customer notification | Plan with owner, version and last review date; exercise record with date, scenario, participants and findings; incident tickets from detection to closure; copies of notices set against contractual deadlines | Response procedure untested, or the plan is stale |
| CC7.5 RecoveryRecover from identified incidents; the points of focus add root cause and preventing recurrence. | IR-02 annual exercise; IR-03 incident records | Exercise record showing recovery steps were tested; incident tickets with recovery and closure times; post-incident reviews and corrective-action tickets tracked to completion | No demonstrated recovery or completed corrective actions |
The library column shows where one control does double duty. AC-04 and AC-06 each support CC6.2 and CC6.3, and AC-07 supports CC6.1 and CC6.3. NS-02 and AC-09 each support CC6.1 and CC6.6, EP-01 and EP-03 support CC6.1 and CC6.8, LG-02 supports CC7.2 and CC7.3, and IR-02 and IR-03 support CC7.4 and CC7.5. A missed AC-06 review therefore leaves the evidence for two criteria incomplete.
The mapping is also uneven. CC6.1 draws on controls for authentication, secrets, privileged access, inventory and encryption, while in our mapping CC6.5 rests on AM-02 alone and CC7.3 on LG-02 alone. If alerts reach a channel nobody owns, there is no triage record and no second control behind that criterion.
To size the population and sample for any row, see how SOC 2 Type 2 controls are tested and how auditors decide sample size. Policy wording for CC6.1 to CC6.3 is in the access control policy template, encryption evidence for CC6.1 and CC6.7 is in SOC 2 encryption requirements, and CC8 sits on the change management controls page.
Where CC6 and CC7 get misread
A SIEM is not required. CC7.2 asks the entity to monitor for anomalies and analyze them. Its points of focus name detection policies, procedures and tools, and no product class. A central log store with alerting is one design an auditor could find suitable; the auditor judges the design against your risks and objectives. When the auditor uses your logs or alerts as evidence, the auditor evaluates whether that information is complete and accurate, and for a Type 2 report, across the whole period (SOC 2 Guide, paragraphs 3.138 and 3.143). Log sources that miss in-scope systems, or retention that does not reach back to the start of the period, leave less to test.
Vulnerability scanning, and fixing what the scans find, belong to CC7.1, not CC6.8. Applying patches is a CC8.1 change-management point of focus. CC7.1’s points of focus include periodic vulnerability scans, scans after significant changes and timely remediation, and they set no frequency or deadline. Your policy sets those, and the auditor tests against it. CC6.8 covers unauthorized or malicious software.
A period with no incident is not an exception. If no incident occurred, the auditor confirms that and states in the report that the response control did not need to operate, with no change to the opinion (SOC 2 Guide, paragraph 3.175). If the annual exercise (IR-02) is a control in your description, the auditor tests it whether or not an incident occurred.
Breach response procedures are a privacy point of focus. If Privacy is in scope, the CC7.4 privacy points of focus include defining and applying breach response procedures for confirmed privacy incidents. Points of focus guide the auditor and are not requirements.
What Changes When You Use a SOC 2 Software Tool?
A compliance platform can collect evidence, show failed tests, and coordinate access reviews. It does not decide whether a control is suitable or whether the evidence is sufficient. In its FAQ on the effect of software tools on SOC 2 examinations, first issued in 2021, the AICPA describes these tools as designed to improve the efficiency of preparing for and undergoing an examination, and says a tool does not change the service auditor’s responsibilities.
For CC6 and CC7, that means:
- Confirm that each integration covers the full in-scope population, not just the systems that were easy to connect. An SSO-only integration, for example, misses the systems outside SSO that the CC6.2 row sets against the HR termination list.
- Validate that imported data is complete and accurate before treating a green test as audit evidence.
- Expect the auditor to test whether the tool’s information is accurate and complete before relying on it, and to run their own risk assessment and procedures rather than rely on the tool’s output alone.
- Ask how any commercial relationship between the tool provider and CPA firm is disclosed and how the firm protects its independence.
The SOC 2 evidence request list covers the artifacts to prepare, and readiness firms can close gaps before the observation period starts. To compare auditors, use the SOC 2 auditor directory or ask for quotes. What a SOC 2 audit costs covers the budget.
More in Audit Preparation