C1.1: Identifying and protecting confidential information
The company defines what counts as confidential, labels or classifies it, and applies handling and retention rules so it stays protected for as long as it is kept.
Category: Confidentiality (optional category) · Series: C1 (Confidentiality) · TSC 2017 (2022 points of focus)
That summary is Policyseed’s own paraphrase, written to be read next to the policy sections below. The authoritative wording is the AICPA’s Trust Services Criteria, which the CPA firm tests your controls against during the examination.
How auditors usually test C1.1
For confidentiality the auditor checks that you define what counts as confidential, know where that data lives and handle it accordingly. Expect a look at the classification scheme, the data inventory and the retention rules, with spot checks that a few stores holding confidential data follow the stated handling. A typical exception is a store, such as an analytics warehouse or support tool, holding customer data the inventory omits.
Example control for C1.1
- Confidential data is classified and handled according to written rules. Documented in P06 Data Classification and Handling. Evidence: Classification matrix with handling rules, and a data inventory showing where each class is stored.
One way to meet the criterion, not the only one. The SOC 2 controls list has the other examples side by side.
Policies that address C1.1
The Policyseed crosswalk points C1.1 at 3 policies. Each link opens the full sample text at the section an auditor would read. Section 4 holds the statements management commits to; section 5 holds the procedures that produce evidence.
- P06 Data Classification and Handling Policy, section 4 (Policy Statements). Owner: Security Owner.
- P07 Data Retention and Disposal Policy, section 4 (Policy Statements). Owner: Security Owner. Working template: Data retention schedule template (.xlsx), a working schedule for the periods this policy sets, with sixteen common record types and a disposal log.
- P22 Privacy and Data Protection Policy, section 4 (Policy Statements). Owner: Security Owner.
Preparing for ISO 27001 as well? The same policies are mapped to Annex A controls on the ISO 27001 policy templates page, so one document set can serve both. The Annex A controls that share a policy with C1.1 are listed in the SOC 2 to ISO 27001 mapping.
Evidence examples for C1.1
Artifacts a company of 5 to 200 people can realistically produce. The Audit Kit’s evidence checklist lists them per policy with an owner column so each one has a name against it before the examination.
- Data classification matrix listing the classification levels and handling rules for each
- Data inventory or data map showing where confidential and personal data is stored
- Retention schedule listing each data category and its retention period
- Sample customer contract confidentiality clause
Readiness check question for C1.1
- Is customer data classified, encrypted in transit and at rest, and deleted on a defined schedule?
It is one of the 20 questions in the free SOC 2 readiness check, which scores your answers in the browser and lists what to fix first.
Related criteria in C1 (Confidentiality)
Previous: A1.3 Recovery testing. Next: C1.2 Disposing of confidential information. All 38 criteria are listed on the template index.
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.