SOC 2 Trust Services Criteria โ SP 800-53 Coverage
How well do NIST SP 800-53 Rev 5 controls address each SOC 2 TSC requirement? This analysis maps from framework clauses back to SP 800-53, with expert coverage weightings and gap identification.
Clause-by-Clause Analysis
Sorted by clauseCC1.1 Integrity and ethical values
Rationale
PL-04 sets rules of behaviour for everyone who uses the system and collects each user's signed acknowledgement. PS-06 has staff and contractors sign access agreements, such as nondisclosure and acceptable use, before they get access. PS-07 holds external providers' staff to the same personnel security requirements and monitors their compliance. PS-08 applies a formal sanctions process to people who break security and privacy policies.
Gaps
The criterion asks for a code of conduct on integrity and ethics across the whole organisation, with the board and senior management setting the tone. It also asks you to evaluate how people and teams keep to it. SP 800-53's rules of behaviour cover system use, so write the wider code yourself.
CC1.2 Board independence and oversight of internal control
Rationale
PM-01 has the security programme plan approved by a senior official who is accountable for the risk, and reviews it on a schedule. PM-29 appoints a senior accountable official for risk and a risk executive function that looks at security and privacy risk across the organisation. CA-06 has a senior authorising official accept the remaining risk and approve each system before it operates, then renew that approval.
Gaps
The criterion asks the board to oversee internal control independently of management, with members who have the skills and expertise the role needs. It also covers the board's use of subcommittees and outside advisers. SP 800-53 gives oversight to senior officials, so set up the board's part yourself.
CC1.3 Organisation structure and lines of authority
Rationale
PM-01 assigns security roles and responsibilities and sets out how parts of the organisation coordinate. PM-18 describes the structure of the privacy programme and the roles of privacy officials and staff. PM-02 appoints a senior information security officer with the mission and resources to run an organisation-wide security programme. PM-19 appoints a senior privacy official with authority and accountability for privacy requirements and risk. PM-29 names a senior accountable official for risk, backed by a risk executive function, to align security and privacy with strategic, operational and budget planning. PS-09 writes security and privacy responsibilities into position descriptions. AC-05 identifies duties that need separating and sets access rights to keep them apart. SA-09 defines oversight and user roles for services that outside providers run, covering how the organisation works with them.
Gaps
The criterion asks you to design reporting lines across the whole organisation, spanning its legal entities, operating units and regions. It also gives the board a part in setting structures and lines of authority. SP 800-53 sets roles for security and privacy, so set out the wider structure and the board's part yourself.
CC1.4 Building and keeping a competent workforce
Rationale
AT-02 gives all users, including managers, executives and contractors, security and privacy literacy training at the start and on a schedule after. AT-03 adds role-based training before people take on their duties and periodically after, which keeps technical skills current. AT-04 documents and monitors training and keeps individual records, which shows who has the training their role needs. PM-13 sets up a programme to develop and improve the security and privacy workforce. PS-02 gives each position a risk designation with screening criteria. PS-03 screens people before they get access and rescreens them when set conditions arise. PS-07 holds contractor and vendor staff to the organisation's personnel security requirements and monitors their compliance.
Gaps
The criterion asks you to evaluate the competence of staff and outsourced providers when you decide to hire or keep them. It also asks for succession and contingency plans for key internal control roles, and for mentoring and other ways to attract and keep staff. SP 800-53 covers training and screening, so set up these wider workforce practices yourself.
CC1.5 Holding people accountable for internal control
Rationale
PS-09 writes security and privacy responsibilities into position descriptions, which gives a basis for judging how each person carries them out. PL-04 and PS-06 have each person acknowledge their responsibilities in writing before access, and again when the rules or agreements change. PS-08 applies formal sanctions when people break security and privacy policies, as when negligence causes a privacy incident. PM-06 develops, monitors and reports measures of performance for the security and privacy programmes.
Gaps
The criterion asks you to evaluate how each person performs their internal control duties and to link incentives and rewards to the results. It also asks you to watch for excessive pressure on staff and manage it. PM-06 measures the programmes as a whole, so set up the reviews of individuals yourself.
CC2.1 Quality information for internal control
Rationale
CM-08 keeps an accurate inventory of system components, detailed enough for tracking and accountability. PM-05 keeps an inventory of the organisation's systems, and PM-05(01) adds one for the systems that process personal data. CM-12 records where defined information is processed and stored, on which components, and who has access to it. CM-13 maps how personal data moves through the system's processing. PL-02 documents each system's components, information types, connections and dependencies, which records its boundaries and data flows. RA-02 categorises each system and its information by impact, so the controls can fit the information.
Gaps
The criterion asks you to identify the information internal control needs. It asks for timely, accurate, complete and verifiable data and reports behind each control. It also covers the organisation's data on vendors' devices and staff's own phones. CM-12 records where information sits, so extend that tracking to those devices.
CC2.2 Internal communication about internal control
Rationale
AT-02 gives all users, including managers and executives, security and privacy awareness training and updates it with lessons from incidents. AT-03 tells people with control duties what they are responsible for and refreshes that training when systems change. PL-04 gives each user written rules on their security and privacy responsibilities and has them acknowledge the rules again after each update. SA-05 gives administrators and users documentation on secure operation and on their responsibilities. PM-01 shares the security programme plan, with its roles and requirements, across the organisation. PL-02 sends the system plans to named people and tells them about later changes. PM-31 reports the security and privacy status of systems to designated leaders on a set schedule. IR-06 has staff report suspected incidents within a set time, and IR-07 gives users a support resource for handling and reporting them.
Gaps
The criterion asks for a separate channel, such as a whistle-blower line, where people can raise concerns anonymously or in confidence. It asks management and the board to keep each other informed on internal control. It also asks you to tell staff the organisation's objectives and any changes to them. SP 800-53 covers security and privacy communication, so set these up yourself.
CC2.3 Communication with external parties
Rationale
CA-03 uses agreements to set the security and privacy requirements, controls and responsibilities for each exchange of information with outside parties. SA-09 tells outside service providers the security and privacy requirements they must meet. SR-08 sets up agreements with supply chain partners to notify each other of compromises and share assessment results. IR-06 reports incident information to designated outside authorities, and IR-06(03) shares it with supply chain partners. PM-20 publishes privacy practices on a public web page with ways to reach the privacy office. PT-05 gives people a clear notice of how and why their personal data is processed. PM-26 receives, tracks and answers complaints and questions from the public about security and privacy practices. PM-27 sends privacy reports to oversight bodies, such as regulators.
Gaps
The criterion asks you to describe the system, its boundaries and its objectives to customers and other outside users. It asks for a whistle-blower channel open to outside parties, and for the board to receive the results of outside assessments. It also covers communication with shareholders and analysts about internal control. Add these to your external communication.
CC3.1 Objectives clear enough to assess risks against
Rationale
PM-09 sets the organisation-wide strategy for managing security and privacy risk. PM-28 documents the assumptions, constraints, priorities and risk tolerance that frame risk assessment. PM-11 defines mission and business processes with security and privacy in mind and works out the protection needs that follow. RA-02 sets impact levels for confidentiality, integrity and availability, which act as each system's security objectives. PM-18 states the privacy programme's strategic goals and objectives. SA-02 sets high-level security and privacy requirements during business planning and allocates the resources to meet them.
Gaps
The criterion asks for objectives across the organisation's operations, its financial and non-financial reporting and its compliance with laws. It asks you to weigh materiality and the precision users need when you set reporting objectives. SP 800-53 frames objectives for security and privacy, so set the wider business objectives yourself.
CC3.2 Identifying and analysing risks
Rationale
RA-03 identifies threats and vulnerabilities and judges the likelihood and impact of harm, joining system, business process and organisation views. RA-03(01) adds supply chain risk. PM-09 applies one strategy for managing security and privacy risk across the organisation. PM-28 records the risk tolerance, assumptions and priorities that guide analysis and response. PM-29 brings the right levels of management into an organisation-wide view of risk through a risk executive function. PM-16 shares threat intelligence to identify threats. RA-05 scans systems and applications for vulnerabilities and analyses the results. RA-09 identifies the most critical system components and functions. SR-06 assesses and reviews the risks from suppliers and contractors and from what they supply. RA-07 responds to each risk in line with risk tolerance, by accepting, avoiding, reducing or sharing it.
Gaps
The criterion asks you to identify and assess risk in each subsidiary, division and operating unit. It also covers threats from customers and business partners, through the access you give them. Add both to the assessment under RA-03, which works at organisation, business process and system level.
CC3.3 Fraud risk
Rationale
RA-03 assesses the risk from insiders and from unauthorised access, use, disclosure or change of information, which takes in fraud carried out through IT. PM-12 runs an insider threat programme with a cross-discipline team that deals with people who misuse their access. AC-05 identifies duties that would let one person both commit and conceal fraud, and separates them.
Gaps
The criterion asks for a fraud risk assessment in its own right, covering fraud in reporting, the loss or misuse of assets and corruption. It also asks you to weigh the incentives and pressures that push people towards fraud, and how they justify it. Run that assessment yourself, drawing on what RA-03 and PM-12 find about insider misuse.
CC3.4 Changes that could affect internal control
Rationale
RA-03 updates the risk assessment when the system, its environment or other conditions change significantly. RA-03(01) does the same when supply chain relationships change. PM-09 reviews and updates the risk management strategy as the organisation changes. CM-04 analyses the security and privacy impact of system changes before they are made. CA-07 monitors controls on an ongoing basis, and CA-07(04) builds change monitoring into risk monitoring. PM-16 shares threat intelligence to track how threats change. SI-05 receives security alerts and advisories from outside sources on an ongoing basis, which flags new threats and vulnerabilities.
Gaps
The criterion asks you to assess changes in regulation, the economy and the physical environment. It also covers changes to the business, such as new business lines, acquisitions, rapid growth and expansion into new countries, and changes in leadership. PM-09 reviews the strategy as the organisation changes, so build these changes into that review and into the risk assessment.
CC4.1 Ongoing and separate evaluations of controls
Rationale
CA-02 runs control assessments on a schedule, with suitable assessors, to see whether controls are in place and working. CA-02(01) adds independent assessors, and CA-02(03) uses assessment results from outside organisations. CA-07 assesses and monitors controls on an ongoing basis at set frequencies. PM-31 sets the organisation-wide monitoring strategy, with its metrics and its monitoring and assessment frequencies. PM-14 makes sure testing and monitoring plans exist, are carried out and are reviewed against risk priorities. CA-08 runs penetration tests and RA-05 scans for vulnerabilities. CP-04 tests the contingency plan for effectiveness and readiness to recover.
Gaps
The criterion asks for an internal audit function and for ongoing evaluations built into business processes outside IT. It also asks you to evaluate every part of internal control, the control environment among them. SP 800-53's assessments cover security and privacy controls, so set up internal audit and widen the scope yourself.
CC4.2 Reporting control deficiencies in time
Rationale
CA-02 writes up each control assessment in a report and gives the results to designated people. CA-07 reports each system's security and privacy status to designated roles and sets response actions on the results. PM-31 does the same across the organisation. CA-05 keeps a plan of action and milestones for fixing weaknesses and updates it with each assessment, audit and monitoring result. PM-04 runs that process across the organisation and reports the plans as required. RA-07 responds to those findings in line with risk tolerance.
Gaps
The criterion asks you to report deficiencies to the board and to judge how serious each one is. SP 800-53 directs reports to the roles the organisation designates, so name the board among them and set criteria for rating severity.
CC5.1 Choosing control activities that reduce risk
Rationale
PL-10 selects a control baseline for each system as the starting set of controls. PL-11 tailors that baseline to the system's environment, mission and risks. PL-02 records the controls in place or planned and the reasons for each tailoring decision. PM-11 works out protection needs from defined business processes, which shows where controls are needed. RA-07 turns risk findings into responses within risk tolerance, which links the controls to the risk assessment. AC-05 identifies incompatible duties and separates them through access rights.
Gaps
The criterion asks for a deliberate mix of manual and automated controls, and of preventive and detective ones. Where separating duties is impractical, it asks you to choose other controls that cover the same risk. Plan both as you tailor the baseline under PL-11.
CC5.2 General controls over technology
Rationale
AC-02 approves and reviews accounts, grants access by role and removes it when the need ends. AC-06 limits each user and process to the access their tasks require. CM-02 keeps a current baseline configuration of the technology under configuration control. CM-03 reviews, approves and records changes to systems. SA-03 acquires, develops and manages systems through a life cycle that builds in security and privacy. SA-04 puts security and privacy requirements into acquisition contracts. SC-07 monitors and controls communications at external and key internal boundaries to protect against outside threats. PL-02 links each system to the business processes it supports and the controls that protect it.
Gaps
The criterion asks you to work out how business processes and their automated controls depend on general technology controls. It also asks for controls that keep technology processing complete and accurate. PL-02 links each system to its business processes, so start the dependency map there and add the processing controls yourself.
CC5.3 Policies and the procedures that carry them out
Rationale
AC-01, AT-01, AU-01, CA-01, CM-01, CP-01, IA-01, IR-01, MA-01, MP-01, PE-01, PL-01, PS-01, PT-01, RA-01, SA-01, SC-01, SI-01 and SR-01 set the policy and procedures for each family. Each policy states roles and responsibilities and has a named official as its owner. The organisation shares each policy with the people who need it and reviews it on a schedule and after set events. PM-01 brings the policies together in the security programme plan and assigns responsibility for them. A senior official approves the plan, and the organisation keeps it up to date.
Gaps
The criterion asks that competent people with enough authority perform each control activity on time. It also asks them to look into anything the work turns up and act on it. Write these duties into the procedures under each family's policy.
CC6.1 Logical access security over information assets
Rationale
CM-08 inventories the system components to protect. RA-02 categorises information and systems by impact, which sets how tightly to restrict access. AC-03 enforces approved authorisations, and AC-06 limits users and processes to the access they need. AC-04 enforces approved information flows, which supports segmentation. PT-03 limits use of personal data to its documented purposes. IA-02 authenticates the organisation's own users, and IA-02(01) and (02) add multi-factor authentication. IA-08 authenticates customers and other users from outside. IA-03 and IA-09 authenticate devices, services and applications before they connect. IA-04 authorises each identifier and stops its reuse. IA-05 manages authenticators from issue to revocation, and IA-05(02) adds certificate-based authentication. AC-17 authorises each type of remote access. SC-07 segments networks, and SC-07(04) manages each external connection. CM-06 hardens components with the most restrictive settings, and CM-07 turns off unneeded functions, ports and services. PL-08 develops the security and privacy architecture and assesses planned changes before use. SC-12 manages cryptographic keys, and SC-13 sets the cryptography for each use. SC-08 and SC-28 protect data in transit and at rest, with encryption under SC-08(01) and SC-28(01).
Gaps
The criterion's points of focus name zero trust architecture as one way to separate networks, and SC-07, AC-03 and IA-02 supply parts of one. The points of focus also cover encrypting data during processing where the risk calls for it. Keep an inventory of each point of access from outside, with the data that passes through it and the people and systems that use it.
CC6.2 Registering and authorising users before access
Rationale
IA-12 proves each user's identity and validates the evidence before an account is created, which registers the user. AC-02 requires approval to create each account and grants access on authorisation. It reviews accounts on a schedule and disables or removes them when the need ends, promptly under AC-02(03). IA-04 assigns an identifier only after a designated role authorises it. IA-05 verifies identity before issuing an authenticator and revokes lost or compromised ones. PS-04 disables access and revokes credentials when someone leaves. PS-07 has external providers report when their staff who hold credentials leave or move, so the organisation can remove that access.
Gaps
The criterion asks the owner of each asset to authorise the credentials that give access to it. AC-02 lets the organisation choose who approves account requests, so make each asset's owner the approver for that asset.
CC6.3 Managing access by role, with least privilege and separation of duties
Rationale
AC-02 sets the conditions for role and group membership, approves each change to access and reviews accounts on a schedule. AC-03 enforces approved authorisations, and AC-03(07) adds role-based access control. AC-05 identifies incompatible duties and sets access rights that keep them apart. AC-06 grants each task only the access it needs, and AC-06(07) reviews privileges and removes any that are unneeded. PS-05 reviews and adjusts access when people change roles, and PS-04 removes it when they leave.
Gaps
The criterion asks the asset owner to approve each change to access. Write that approval into your access procedures, naming the owner of each asset.
CC6.4 Restricting physical access to sites and assets
Rationale
PE-02 keeps an approved list of people with facility access and issues their credentials. It reviews the list and removes people whose need has ended. PE-03 enforces those authorisations at entry and exit points, controls visitors and secures keys and other access devices. MP-02 restricts access to digital and paper media to authorised roles. MP-04 stores media, backup media included, securely in controlled areas. PS-05 reviews and changes physical access when people transfer. PS-04 recovers badges, devices and other property when employment ends.
Gaps
The criterion also asks you to recover badges and devices from contractors, vendors and business partners when their need for access ends. PS-04 covers your own staff when they leave. Set up the same recovery for those outside parties.
CC6.5 Removing data and software before disposing of assets
Rationale
MP-06 sanitises media before disposal, reuse or release from the organisation's control, with a strength that matches the information, and MP-06(08) adds remote wiping. MA-02 sanitises equipment before it leaves the site for maintenance, repair or replacement. SR-12 disposes of data, documentation and components by defined techniques.
Gaps
The criterion also covers the organisation's data on devices that vendors and employees own, such as personal phones used for work. SP 800-53 deals with the organisation's own media, so set out how you remove your data from those devices.
CC6.6 Protection from threats outside the system boundary
Rationale
SC-07 monitors and controls traffic at the external boundary through managed interfaces such as firewalls. It puts public-facing components in separate subnetworks. SI-04 watches the boundary for attacks and unauthorised connections, as intrusion detection and prevention systems do, and SI-04(23) monitors hosts. AC-17 authorises each type of remote access and sets its usage restrictions. CM-07 turns off unneeded ports, protocols and services, which limits what each channel can carry. IA-02 authenticates the organisation's own users, and IA-02(01) and (02) add multi-factor authentication for access from outside. IA-08 authenticates customers and other outside users who connect from beyond the boundary. IA-05 protects credentials from disclosure, and IA-05(01) sends passwords only over protected channels. SC-08 protects data in transit, credentials included.
Gaps
The criterion includes endpoint detection and response. SI-04 covers part of it, with host-based monitoring under SI-04(23). Choose and run endpoint detection and response tools on your devices for the rest.
CC6.7 Controlling the movement and removal of information
Rationale
AC-04 enforces approved information flows within and between systems, the basis of data loss prevention rules. SC-07 controls traffic at managed interfaces, and SC-07(10) prevents exfiltration. SC-08 and SC-28 protect data in transit and at rest, laptops and removable media included, with encryption under SC-08(01) and SC-28(01). AC-19 sets configuration and connection requirements for mobile devices and authorises their connection. AC-19(05) adds full-device or container encryption. MP-07 restricts or bans removable media on defined systems. MP-05 protects media in transport, keeps track of it and limits who may carry it. PE-16 authorises and records the components that enter and leave the facility.
Gaps
The criterion treats laptops, desktops and sensors as one group of endpoints to protect. AC-19 covers mobile devices. Set out how you protect desktops, sensors and other fixed endpoints as well.
CC6.8 Preventing and detecting malicious software
Rationale
SI-03 runs anti-malware at entry and exit points and on endpoints. It scans files from outside sources and blocks or quarantines the malware it finds. CM-07 restricts software and functions to what the system needs, and CM-07(02), (04) and (05) stop unauthorised software from running. CM-14 blocks installation of software and firmware that lacks an approved digital signature. CM-11 sets and enforces rules for software that users install, and monitors compliance. CM-03 puts software changes through approved change control. CM-05 limits who can change systems and install software. SI-07 uses integrity checks to detect unauthorised changes to software, firmware and information.
Gaps
The criterion asks you to scan devices for malware when they return to the organisation's custody, before they reconnect. SI-03 scans files from outside sources, so add a scan for returned devices. It also asks you to limit and monitor utility software that can get around security controls.
CC7.1 Detecting configuration changes and new vulnerabilities
Rationale
CM-02 keeps a documented baseline configuration and updates it as components change. CM-06 sets secure configuration settings and monitors them for deviations. CM-08 maintains the component inventory, and CM-08(03) detects unknown or unauthorised components. SI-07 alerts on unauthorised changes to critical files, as file integrity monitoring does. RA-05 scans for vulnerabilities on a schedule and when new ones are reported, and has findings fixed within set times. SI-05 receives security alerts and advisories about newly found vulnerabilities and acts on them. SI-02 corrects flaws and installs security updates within set times.
Gaps
The criterion asks for a vulnerability scan after each significant change to the environment. RA-05 scans on a schedule and when new vulnerabilities are reported. Add a scan to your change process for each significant change.
CC7.2 Monitoring components for anomalies
Rationale
SI-04 monitors systems for attacks, unauthorised connections and unauthorised use, and analyses the anomalies it detects. SI-04(09) tests the monitoring tools. AU-02 sets which events are logged to support detection and investigation, and AU-12 has system components generate those records. AU-06 reviews and analyses audit records for unusual activity and reports findings. AU-07 filters and summarises events for analysis. AU-05 alerts staff when logging fails, which keeps detection working. PE-06 monitors physical access to detect physical security incidents. PE-14 monitors environmental conditions, and PE-14(02) raises alarms on harmful changes. PM-16 shares threat intelligence, which helps detect newly found threats.
Gaps
The criterion asks you to detect when an authorised outside party has been compromised. Extend your monitoring to the access those parties hold.
CC7.3 Evaluating security events to find incidents
Rationale
IR-04 handles incidents, and its detection and analysis step judges whether an event is an incident and what it affects. AU-06 analyses audit records for unusual activity and reports findings to the people responsible. IR-06 has staff report suspected incidents to the incident response capability, and IR-05 tracks and documents each one. IR-08 sets a plan that defines reportable incidents, and IR-08(01) assesses breaches of personal data for harm. IR-09 identifies the information involved in a spill and the other components it affects. IR-03 tests how well the incident response capability works.
Gaps
The criterion asks you to judge whether an event involving personal data broke laws or regulations. IR-08(01) assesses breaches of personal data for harm, so add a check against the laws and regulations that apply.
CC7.4 Incident response program
Rationale
IR-08 sets the incident response plan, its structure and who is responsible, and IR-08(01) adds a process for breaches of personal data. IR-04 contains, eradicates and recovers from incidents and builds lessons learned into procedures. IR-07 provides incident response support, and IR-07(02) works with outside providers. IR-06 reports incident information to designated authorities. IR-05 tracks and documents incidents, which gives the record for reviewing patterns. IR-03 tests the response capability for effectiveness. SI-02 corrects the flaws an incident exposes. PS-08 sanctions people who break security and privacy policies, such as through misuse of personal data.
Gaps
The criterion asks management to review incident patterns regularly and decide which system changes they call for. It also asks you to notify affected individuals and customers. IR-08(01) decides whether notice is needed, so set out how you give it.
CC7.5 Recovering from security incidents
Rationale
CP-02 sets recovery objectives and priorities and plans full restoration with the original controls intact. It updates the plan with lessons from incidents and tests. CP-10 recovers and rebuilds the system to a known state within set times. CP-04 tests the contingency plan and acts on the results. IR-03 tests incident response, recovery steps included. IR-04 covers recovery within incident handling and builds lessons learned into procedures, training and testing. IR-08 updates the response plan for problems found in use or testing. IR-06 reports incident information to designated authorities. SI-02 installs patches and corrects the flaws found during recovery, and SI-02(07) looks for their root cause.
Gaps
The criterion asks you to find the root cause of each incident. SI-02(07) does this for flaws, so add the same analysis to incident handling. It also asks you to test recovery against scenarios chosen by each threat's likelihood and severity, such as the loss of key staff.
CC8.1 Change management
Rationale
CM-02 keeps a baseline configuration up to date, and CM-06 sets and controls the configuration settings for software. CM-03 reviews, approves, documents and records changes, and CM-03(02) tests them before release. CM-04 analyses each change's security and privacy impact before it's made, in a separate test environment under CM-04(01). CM-05 restricts who can make changes, and CM-05(04) and (05) separate duties in deployment. SA-03 builds security and privacy into the development life cycle, and SA-03(02) controls live data in test environments. SA-08 applies security and privacy engineering principles to design and change, including secure failure under SA-08(24) and data minimisation under SA-08(33). SA-24 designs systems for cyber resiliency. SA-10 has developers make only approved changes and track flaws, and SA-11 has them run unit, integration and regression tests. SA-11(01) and (08) add static and dynamic code analysis. SI-02 tests patches and installs them within set times through configuration management. RA-08 assesses privacy impact before the organisation builds or buys technology that handles personal data. PM-25 limits and authorises personal data used in testing, training and research.
Gaps
The criterion asks for a process to handle emergency changes. CM-03 sets up change control in general, so write the emergency process yourself and record those changes with the rest.
CC9.1 Reducing the risk of business disruption
Rationale
CP-02 plans how to keep essential functions running through a disruption and restore them afterwards. It sets roles and recovery objectives, and shares contingency information. CP-06 holds backup information at an alternate storage site with equivalent controls. CP-07 sets up an alternate processing site where essential operations resume within set times. CP-08 provides alternate telecommunications services for when primary services fail.
Gaps
The criterion asks you to consider insurance against the financial cost of loss events. It also covers disruption to business operations as a whole. SP 800-53's contingency planning centres on information systems, so extend it to the rest of the business yourself.
CC9.2 Vendor and business partner risk
Rationale
SA-04 writes security and privacy requirements, responsibilities and acceptance criteria into contracts. SA-04(12) covers returning and removing data when a contract ends. SA-09 requires external service providers to meet security and privacy requirements, defines oversight roles and monitors their compliance. PS-07 sets security requirements for vendors' staff and monitors their compliance too. CA-03 sets requirements and responsibilities, nondisclosure among them, in agreements for exchanging information with outside systems. PM-30 sets an organisation-wide supply chain risk management strategy, and PM-30(01) identifies and ranks critical suppliers for assessment. SR-02 plans supply chain risk management across the life cycle. SR-03 finds and fixes weaknesses in the supply chain, and SR-03(03) flows controls down to subcontractors. SR-06 assesses and reviews suppliers on a schedule. SR-08 agrees with suppliers how they report compromises and assessment results.
Gaps
The criterion asks you to assess the risk that a vendor fails financially. It also asks how you handle exceptions and resolve issues with vendors, and how you end a relationship. When one ends, confirm the vendor returns or deletes your data. The criterion covers business partners other than suppliers as well. CA-03 reaches them through exchange agreements, so extend your risk assessments to them too.
A1.1 Managing processing capacity against demand
Rationale
CP-02 sets up the contingency plan, and CP-02(02) plans the processing, telecommunications and environmental capacity that contingency operations need. SC-05 limits the effects of denial-of-service events. SC-05(02) manages capacity, bandwidth and redundancy to withstand flooding attacks, and SC-05(03) monitors whether resources are sufficient. SC-06 allocates resources by priority or quota to protect their availability.
Gaps
The criterion asks for ongoing capacity management. Measure current use to set a baseline, then forecast average and peak demand against capacity and your tolerances. Start a change when a forecast passes a tolerance. SP 800-53 plans capacity for contingency operations and denial-of-service attacks, so set up the ongoing process yourself.
A1.2 Environmental protection and recovery infrastructure
Rationale
PE-11 provides an uninterruptible power supply, and PE-11(01) adds an alternate source such as a generator. PE-09 protects power equipment and cabling from damage. PE-13 runs fire detection and suppression systems on an independent power source, and PE-13(01) notifies responders automatically. PE-14 keeps temperature and humidity within limits and monitors them, with alarms under PE-14(02). PE-15 protects against water damage with accessible, working shutoff valves. CP-09 backs up user and system data and protects the backups, and CP-09(08) encrypts them. CP-06 keeps backups at an alternate storage site, and CP-07 provides an alternate processing site. CP-06(01) and CP-07(01) separate both from the primary site. CP-10 recovers and rebuilds the system to a known state within set times.
Gaps
The criterion asks you to choose which data to back up. It also asks you to monitor backups for failures and correct them. Plan for threats to recovery such as ransomware, building on the protection CP-09 gives the backups.
A1.3 Testing recovery plans
Rationale
CP-04 tests the contingency plan and starts corrective action from the results. CP-04(01) coordinates testing with related plans, and CP-04(04) tests a full recovery. CP-02 updates the plan with what testing finds, and CP-02(07) coordinates it with external service providers. CP-09 backs up the system, and CP-09(01) tests the backups for reliability and integrity. CP-09(02) restores a sample of them as part of testing.
Gaps
The criterion asks you to base test scenarios on how likely each threat is and how much harm it could do. Include scenarios where key people or vendors are unavailable. Add both to the tests you define under CP-04.
C1.1 Identifying and keeping confidential information
Rationale
RA-02 categorises information by impact, which identifies what needs confidentiality protection. AC-16 attaches security attributes that mark information as confidential, and keeps them with it in storage, processing and transmission. MP-03 marks media with distribution limits and handling caveats. CM-12 records where defined information is stored and processed, and who has access to it. SI-12 manages and retains information to meet legal and operational requirements. CP-09 backs up information against loss during its retention period, and CP-09(07) needs two people to approve deleting a backup.
Gaps
The criterion asks you to mark information as confidential at the point you receive or create it. It also asks you to match each retention period to the purpose the information serves. Build both into the categorisation and retention that RA-02 and SI-12 set up.
C1.2 Disposing of confidential information
Rationale
SI-12 manages information through its retention period, and SI-12(03) disposes of it by defined techniques once that period ends. MP-06 sanitises media before disposal or reuse, with a strength that matches the information's sensitivity. MP-06(01) tracks and verifies the disposal. SR-12 disposes of data, documentation and components by defined techniques.
Gaps
The criterion asks you to identify confidential information once its retention period ends, so it reaches disposal on time. Review your holdings regularly against the retention periods you set under SI-12.
PI1.1 Information about processing objectives and specifications 15%
Rationale
SA-05 provides user and administrator documentation on how to use the system and its functions. It centres on security functions and user responsibilities.
Gaps
The criterion asks you to define the data you supply with a service and share the definitions with users. Cover points such as the data's sources, units, precision and time periods. It also asks you to set processing requirements, both functional and non-functional, and to share the product and service specifications users need. SA-05 documents security functions, so write this processing documentation yourself.
Mapped Controls
PI1.2 Controls over system inputs
Rationale
SI-10 checks the validity of defined inputs against set rules. SI-10(05) limits inputs to trusted sources and approved formats, and SI-10(02) reviews and resolves input errors. AU-12 generates records of defined events, which can include input activity. AU-03 makes each record show what happened, when and where, the source and outcome, and who was involved.
Gaps
The criterion asks you to define the input characteristics that your product or service requirements call for. It also asks you to check that inputs are complete, for example with control totals and reconciliations. Run these checks alongside the validity checks in SI-10.
PI1.3 Controls over processing
Rationale
SI-07 detects unauthorised changes to software and data that could corrupt processing, whether they come from error or malice. SI-11 gives staff error messages with the information they need to correct a problem. AU-12 generates records of defined events, which can include processing activity.
Gaps
The criterion asks you to define processing specifications and the activities that meet them. It also asks you to process inputs completely, accurately, on time and as authorised. Check this with reconciliations or control totals, for example. Detect and correct processing errors promptly, building on SI-11's error messages.
PI1.4 Controls over outputs
Rationale
SI-15 checks output from defined software against its expected content. AC-03 enforces access authorisations, so output goes to the users it's meant for. PE-05 controls physical access to output devices, so only authorised people collect the output. SC-08 protects the confidentiality and integrity of output sent over networks, and SC-28 protects stored output at rest. SI-12 manages and retains output in line with requirements. AU-12 generates records of defined events, which can include output activity.
Gaps
The criterion asks you to deliver output completely and on time, in line with its specifications. SP 800-53 guards output and validates its content, so check each delivery against the specification yourself.
PI1.5 Controls over stored data
Rationale
SC-28 protects the confidentiality and integrity of stored information, and SI-07 detects unauthorised changes to it. CP-09 backs up stored data and protects the backups against loss and corruption. MP-04 stores media securely in controlled areas until it's destroyed or sanitised. SI-12 manages and retains stored information and outputs in line with requirements. AU-12 generates records of defined events, which can include storage activity. AU-09 protects those records from unauthorised access, change and deletion. AU-11 keeps them for set periods, and AU-11(01) keeps long-term records retrievable.
Gaps
The criterion asks you to store data completely, accurately and on time, as the system specifications set out. SP 800-53 protects data at rest, so add checks that what you store matches those specifications.
P1.1 Privacy notice and its updates
Rationale
PM-20 publishes the organisation's privacy practices on a central public web page that is easy to find. PM-20(01) writes the website's privacy policies in plain language and updates them after substantive changes. PT-03 documents the purposes of processing and describes them in public privacy notices. PT-05 gives individuals a clear notice of the purposes of processing and the authority for it, at first contact and periodically after. PT-05(01) adds notice at the point of collection.
Gaps
The criterion asks the notice to cover topics such as access, disclosure, data quality, enforcement and sources other than the individual. It also asks you to tell data subjects when the notice changes and to keep earlier versions. PT-05's notice covers purposes and authority, so add the other topics and the change process yourself.
P2.1 Choice and consent
Rationale
PT-04 gives individuals tools to consent before collection, so they can make an informed decision. PT-04(01) and (02) add tailored and just-in-time consent, and PT-04(03) lets individuals revoke it. PT-05 tells individuals about the processing, which informs their choice. PT-02 documents the authority for processing and records the basis the organisation relies on where consent is implied. PT-03 puts any new purpose for processing through the required steps. PT-07 sets conditions, such as explicit consent, for sensitive categories of personal data.
Gaps
The criterion asks you to tell individuals what happens if they refuse consent or later withdraw it. It also asks for consent before personal data moves to or from an individual's device. Add both to your consent process.
P3.1 Collecting personal information
Rationale
PT-02 documents the legal authority for processing and restricts collection to what that authority permits. PT-03 keeps collection and use within the documented purposes. RA-08 requires a privacy impact assessment before any new collection of personal data or new technology to process it. The assessment reviews the planned collection methods. SI-12 manages information in the system, and SI-12(01) limits the personal data processed to the elements the organisation has defined.
Gaps
The criterion asks you to confirm that third parties who supply personal data collected it fairly and lawfully. It also asks you to tell individuals when you develop or acquire more information about them. PT-02 and PT-03 govern your own collection, so add both steps yourself.
P3.2 Explicit consent before collection
Rationale
PT-04 obtains individuals' consent before collection, through tools that support an informed decision. PT-05 tells individuals which processing needs their consent, and PT-05(01) gives that notice at the point of collection. PT-07 sets conditions, such as explicit consent, for processing sensitive categories of personal data.
Gaps
PT-04 obtains consent before collection. The criterion also asks you to keep a record of each explicit consent, and to tell individuals what happens if they refuse. Store those records where you can retrieve them, and state the consequences of refusing in your notice.
P4.1 Using personal information only for its purposes
Rationale
PT-03 restricts processing to uses compatible with the identified purposes and monitors changes to them. PT-02 holds processing to what the documented authority permits. PT-04 obtains individuals' consent before processing that needs it. PM-25 minimises the personal data used in testing, training and research, and authorises each such use.
Gaps
SP 800-53 states this more generally than the criterion. Check the controls against AICPA's wording.
P4.2 Retaining personal information
Rationale
SI-12 keeps information for as long as laws, regulations, policies and operational needs require. CP-09 backs up information and protects the backups, so personal data survives loss or destruction during its retention period.
Gaps
The criterion asks you to keep personal data while its stated purposes need it, and then dispose of it. SI-12 retains data for the periods that laws and policies set. Set the retention period for each kind of personal data from its purpose as well.
P4.3 Disposing of personal information securely
Rationale
SI-12(03) destroys or erases information at the end of its retention period, using defined techniques. MP-06 sanitises media holding personal data before disposal or reuse. SR-12 disposes of data and components by defined techniques. SI-18(04) deletes personal data when individuals ask. SI-19 removes identifying elements from datasets and checks that the de-identification works.
Gaps
The criterion asks you to capture each request to delete personal data and flag the data in every system that holds it. SI-18(04) deletes data on request, so add the step that carries each request to all those systems.
P5.1 Access for data subjects to their personal information
Rationale
AC-03 enforces access rules, and AC-03(14) gives individuals a way to access defined elements of their own personal data. IA-08 identifies and authenticates data subjects, as users from outside the organisation, before they get that access.
Gaps
The criterion asks you to give individuals an understandable copy of their data, in reasonable time and at reasonable cost. It also asks you to explain any refusal to the individual. Where the organisation acts as a processor, answer the access requests that data controllers pass on.
P5.2 Correcting personal information
Rationale
PM-22 sets policies for correcting personal data and telling recipients about corrections. It also sets out how the organisation handles appeals when it refuses a correction. SI-18 corrects or deletes inaccurate or outdated personal data. SI-18(04) acts on individuals' requests, and SI-18(05) tells recipients and the individual about the change.
Gaps
The criterion asks for a written reason whenever you refuse a request, giving the legal basis and how the individual can challenge it. Where the organisation acts as a processor, carry out the update requests that data controllers pass on.
P6.1 Disclosing personal information to third parties
Rationale
PT-03 treats disclosure as a form of processing and limits it to purposes compatible with those identified. PT-04 obtains consent before processing, disclosure included. AC-21 helps users check that a sharing partner's authorisations match the information's use restrictions before they share it. CA-03 sets privacy requirements and responsibilities in agreements with the parties that receive the information.
Gaps
The criterion asks for consent before you disclose personal data for a new purpose. It also asks you to pass your privacy instructions to each third party you share the data with. Add both steps to your disclosure process.
P6.2 Record of authorised disclosures 90%
Rationale
PM-21 keeps an accurate accounting of disclosures, with the date, nature, purpose and recipient of each. It also retains that accounting for a set period.
Gaps
SP 800-53 states this more generally than the criterion. Check the controls against AICPA's wording.
Mapped Controls
P6.3 Record of unauthorised disclosures and breaches
Rationale
IR-05 tracks and documents incidents, unauthorised disclosures and breaches of personal data among them. IR-06 has staff report suspected incidents within a set time, so each one is recorded.
Gaps
The criterion asks for a complete, current record of unauthorised disclosures of personal data, separate from the general incident log. Keep that record yourself, drawing on what IR-05 tracks.
P6.4 Privacy commitments from vendors and third parties
Rationale
SA-04 writes privacy requirements and responsibilities into contracts. CA-03 records privacy requirements in agreements with the parties that receive personal data. SA-09 requires external providers to meet the organisation's privacy requirements and monitors their compliance. SR-06 reviews suppliers and their risks on a schedule, including whether their controls work. SR-08 sets agreements under which suppliers report compromises to the organisation.
Gaps
SA-09 monitors whether providers comply with your privacy requirements. The criterion also asks you to take corrective action if a third party misuses the personal data you shared with it. Set out the steps you take when that happens.
P6.5 Vendors reporting unauthorised disclosures
Rationale
SR-08 sets agreements under which suppliers notify the organisation of compromises. SA-04 puts requirements into contracts, which can include a duty to report breaches. SA-09 holds external providers to the organisation's requirements, such as reporting incidents. IR-06 brings those reports to the incident response capability, and IR-04 handles them. IR-04(10) and IR-06(03) coordinate that work with the other parties in the supply chain.
Gaps
The criterion asks you to take corrective action against any third party that misuses the personal data you shared. Add those steps to how you handle a vendor's report.
P6.6 Notifying breaches and incidents
Rationale
IR-06 reports incident information to designated authorities, such as regulators. IR-08 sets the incident response plan, and IR-08(01) adds a process to decide whether individuals and other organisations need notice of a breach. That process assesses the harm and takes account of the privacy requirements that apply.
Gaps
IR-08(01) decides whether to notify. The criterion also asks you to set the method and timing of each notice and who receives it. Add these to your incident response plan.
P6.7 Telling data subjects what is held and disclosed
Rationale
PM-21 gives individuals the accounting of disclosures of their personal data when they ask for it. CM-13 maps each action on personal data, with the components involved and who operates them. PM-05 keeps an inventory of systems, and PM-05(01) lists the systems and projects that process personal data. CM-13 and PM-05(01) show the organisation where it processes personal data.
Gaps
PM-21 accounts for disclosures. The criterion also asks you to tell individuals, on request, what personal data you hold about them. Where the organisation acts as a processor, answer the requests that data controllers pass on.
P7.1 Accurate and relevant personal information
Rationale
PM-22 sets policies for reviewing the quality of personal data and for correcting or deleting it. SI-18 checks personal data for accuracy, relevance, timeliness and completeness, and corrects or deletes what is wrong.
Gaps
SP 800-53 states this more generally than the criterion. Check the controls against AICPA's wording.
P8.1 Handling privacy complaints and monitoring compliance
Rationale
PM-20 publishes the channels individuals use to reach the privacy office with questions and complaints. PM-26 tracks each complaint and question and answers it within set times. CA-02 assesses privacy controls and reports the results. CA-07 monitors their effectiveness on an ongoing basis and acts on what it finds. CA-05 plans and tracks the fixes for any deficiencies. PM-27 reports on privacy compliance to oversight bodies and the officials who monitor it. PS-08 sanctions staff who break privacy policies.
Gaps
The criterion asks you to record how you resolved each complaint and to tell the individual the outcome. It also asks for a way to settle disputes that gives individuals recourse. PM-26 tracks and answers complaints, so add these steps to that process.
Methodology and Disclaimer
This coverage analysis maps from SOC 2 TSC clauses/requirements back to NIST SP 800-53 Rev 5 controls, assessing how well the SP 800-53 control set addresses each framework requirement.
Coverage weighting represents an informed estimate based on control-objective alignment, not a definitive compliance determination. Weightings consider whether SP 800-53 controls address the intent of each framework requirement, even where terminology and structure differ.
This analysis should be validated by qualified assessors for use in compliance or audit activities. The authoritative source for any compliance determination is always the framework itself.