SOC 2 Confidentiality: when to add it, and when Privacy or Processing Integrity instead
Updated
Confidentiality is optional. Add it when a contract makes you promise to restrict information a customer gives you and to destroy it later, not simply because the data is sensitive. It adds two criteria: identifying and protecting that information, and disposing of it. Disposal is where most of the evidence work sits. This guide shows what triggers it, how it differs from Privacy, what disposal evidence looks like, and when Processing Integrity is the category you actually need. The sources are consultancies that sell SOC 2 services, so confirm the scope with your CPA firm.
Security is required; Confidentiality adds C1.1 and C1.2
Every SOC 2 report covers Security; the other four categories are chosen (see which Trust Services Criteria to include). TCSA, a compliance consultancy, says Confidentiality adds two criteria: C1.1, identifying and maintaining confidential information, and C1.2, disposing of it (TCSA, reviewed Aug 2026). The criterion pages show what the Policyseed policies say for each: C1.1 and C1.2.
The trigger is a commitment, not how sensitive the data feels
TCSA tells readers to choose Confidentiality when a contract, agreement or regulation obliges them to restrict and eventually destroy information (TCSA). It names three places that obligation shows up:
- a designation clause that defines what the agreement treats as confidential;
- a return-or-destroy clause that sets the disposal obligation;
- a buyer's security exhibit that names the category, such as "SOC 2 Type 2 covering Security and Confidentiality".
Fractional CISO, a vCISO firm writing in January 2023, takes a broader view: "Most modern businesses will benefit from including Confidentiality in their SOC 2 audit, since most do collect some amount of confidential information from their customers" (Fractional CISO, 19 Jan 2023). The article is almost four years old. Cybersecify points to startups that handle sensitive business data for customers and whose contracts carry confidentiality obligations beyond ordinary security (Cybersecify, updated 9 Sep 2026). The sources disagree on how common the add is, so start from what your own contracts say.
Confidentiality or Privacy: who the promise is to
| Confidentiality | Privacy | |
|---|---|---|
| Promise runs to | The counterparty that gave you the information | The individual the information is about |
| Criteria added | Two: C1.1 and C1.2 | Eighteen, from P1.1 (notice) to P8.1 (complaints) |
Both rows are from TCSA (TCSA). A company can need both: a customer contract restricts the customer's business data, and a privacy notice makes promises to that customer's users.
What disposal evidence looks like
For C1.2, TCSA lists what an auditor works from (TCSA):
- the population: every record, dataset, contract or asset that reached the end of its retention period during the observation period;
- deletion job output with record counts and timestamps;
- offboarding tickets showing deletion against the contractual deadline;
- certificates of destruction for physical media;
- an exception list for anything not deleted, with reasons.
And what it says gets rejected:
- a deletion policy with no execution;
- deletion in the primary store with nothing said about backups, log archives, the warehouse or downstream SaaS;
- a destruction certificate dated after the contractual deadline.
The generated Data Retention and Disposal Policy sets the customer deadline (item 4.3):
Customer data in Northwind is retained for the term of the customer agreement and deleted within 30 days after termination or after a verified written deletion request, unless a legal hold applies. Northwind Cloud Inc confirms deletion in writing on request.
and the record (item 4.12):
Disposal of Confidential or Restricted data and of hardware that has held company data is recorded in the disposal log with date, method, performer and verifier.
When you answer the generator's scope question with Confidentiality, item 4.12 also keeps disposal records for the whole examination period, and three other policies change their wording (listed in the scope guide). The data retention schedule has a disposal log for these records, and SOC 2 data retention covers backups and legal holds.
Processing Integrity, briefly
Cybersecify says Processing Integrity applies to "payments platforms, billing engines, data-transformation products" and to "anything where a wrong output is a direct harm to the customer", and that "most general SaaS does not need it" (Cybersecify). Policyseed's generator does not add Processing Integrity wording; if you need it, the controls come from your own product, and your CPA firm sets what it tests.
How to decide
- Read your customer agreements and the security exhibits buyers send: look for designation and return-or-destroy clauses.
- If they exist, Confidentiality is likely in scope; check that you can show deletion past the primary store.
- If your promises are to individuals (a privacy notice, consent, access requests), look at Privacy instead or as well.
- If customers pay you for correct processing, ask your CPA firm about Processing Integrity.
Frequently asked questions
- Is Confidentiality required for SOC 2?
- No. Security is the one category every SOC 2 report covers; Confidentiality, Availability, Processing Integrity and Privacy are added when you choose them. The sources read for this guide tie the choice to what your contracts promise, so read your customer agreements before you decide.
- What is the difference between SOC 2 Confidentiality and Privacy?
- Who the promise is made to. TCSA puts it this way: Confidentiality promises run to the counterparty that gave you the information, Privacy promises run to the individual the information is about. Confidentiality adds two criteria (C1.1 and C1.2); Privacy adds eighteen, from notice (P1.1) to complaint handling (P8.1), according to the same source.
- Does keeping customer data mean I need Confidentiality?
- Not on its own, according to TCSA, which says the trigger is an obligation in a contract, agreement or regulation to restrict and eventually destroy information. Fractional CISO takes a broader view (2023): most businesses collect some confidential information and will benefit from including it. Sources differ, so ask your customers what their contracts expect and your CPA firm what it would test.
- Do I need Processing Integrity?
- Cybersecify (updated September 2026) says it applies to payments platforms, billing engines and data-transformation products, anything where a wrong output directly harms the customer, and that most general SaaS does not need it.
Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.