Framework · Assurance report · Attestation
SOC 2 compliance: criteria, Type I vs Type II and audit steps
SOC 2 is an attestation report in which a licensed CPA firm examines a service organisation's controls against the AICPA Trust Services Criteria. Security is always in scope; availability, processing integrity, confidentiality and privacy are optional. A Type I report covers control design at a date; Type II tests operation over a period.
What you need to know about SOC 2
Who needs SOC 2?
No law requires it, but these situations usually make it a requirement in practice.
QULDEX helps here first: the readiness check shows where you stand before you commit budget.
What does SOC 2 require?
SOC 2 requires controls that meet the Trust Services Criteria for the categories you put in scope, a written system description, and evidence that the controls were designed (Type I) or operated (Type II). Security, the common criteria, is mandatory.
Security
Common criteria covering governance, risk, monitoring, access, operations, change and vendors.
In QULDEX: One control set reused for ISO 27001 and NIST CSFAvailability
Capacity, backup, recovery and recovery testing.
In QULDEX: Backup and DR tests scheduled with results attachedProcessing integrity
Complete, accurate and timely processing.
In QULDEX: Reconciliation evidence collected per cycleConfidentiality
Identify, protect and dispose of confidential information.
In QULDEX: Classification evidence shared with ISO 27001Privacy
Notice, consent, use, access, disclosure, quality and complaints.
In QULDEX: Privacy evidence reused for ISO 27701 and GDPRSystem description
Describe services, boundaries, infrastructure, people, data and controls.
In QULDEX: System description drafted from your scoped assetsExamination
The CPA firm tests controls and issues its opinion.
In QULDEX: Auditors sample evidence in a controlled viewWhat are the SOC 2 Trust Services Criteria?
The 2017 Trust Services Criteria have 33 common criteria for security (CC1–CC9) and 28 more for availability, processing integrity, confidentiality and privacy. Select any criterion to see what it asks for, typical evidence and the matching ISO 27001 controls.
Showing up to 6 per group. Search, filter, or open a group to see all 61.
Security (common criteria) 33
CC1.1Commitment to integrity and ethical valuesShow that the organisation commits to integrity and ethical values, for example through a code of conduct people acknowledge.
In QULDEXGovernance evidence (board minutes, org charts, policy sign-offs) is requested on schedule and kept for the auditor to sample.
- Typical evidence
- Code of conduct, signed acknowledgements
CC1.2Board independence and oversightThe board is independent of management and oversees internal control.
In QULDEXGovernance evidence (board minutes, org charts, policy sign-offs) is requested on schedule and kept for the auditor to sample.
- Typical evidence
- Board or audit committee minutes
CC1.3Structures, reporting lines and authoritiesManagement sets structures, reporting lines and authorities for meeting objectives.
In QULDEXGovernance evidence (board minutes, org charts, policy sign-offs) is requested on schedule and kept for the auditor to sample.
- Typical evidence
- Org chart, role descriptions
CC1.4Commitment to competenceAttract, develop and retain competent people in line with objectives.
In QULDEXTraining completion is imported as evidence and checked against headcount.
- Typical evidence
- Training records, hiring checks
- Maps to
- ISO 27001 A.6.3NIST PR.AT-01
CC1.5Accountability for internal controlHold people accountable for their internal control responsibilities.
In QULDEXGovernance evidence (board minutes, org charts, policy sign-offs) is requested on schedule and kept for the auditor to sample.
- Typical evidence
- Performance reviews, disciplinary policy
CC2.1Quality information to support internal controlObtain or generate relevant, quality information to support internal control.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
CC2.2Internal communication of objectives and responsibilitiesCommunicate control objectives and responsibilities internally.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Policy portal, security awareness content
- Maps to
- ISO 27001 A.6.3
CC2.3Communication with external partiesCommunicate with external parties about matters affecting internal control.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Customer-facing security page, contracts
CC3.1Objectives specified clearly enough to identify risksSet objectives clearly enough to identify and assess related risks.
In QULDEXObjectives live in the risk register next to the risks they drive.
CC3.2Risk identification and analysisIdentify and analyse risks to objectives across the entity.
In QULDEXThe risk register holds the assessment; treatment decisions link to criteria.
- Typical evidence
- Risk assessment, risk register
- Maps to
- ISO 27001 6.1.2NIST ID.RA-05
CC3.3Fraud risk assessmentConsider the potential for fraud when assessing risks.
In QULDEXFraud scenarios sit in the same risk register with owners and reviews.
CC3.4Changes that could impact internal controlIdentify and assess changes that could significantly affect internal control.
In QULDEXSignificant changes trigger a risk review task in QULDEX.
CC4.1Ongoing and separate evaluationsRun ongoing and separate evaluations to check controls are present and working.
In QULDEXInternal audits and control tests run in the audit workspace with sampling.
- Typical evidence
- Internal audit reports, control test results
CC4.2Communicating internal control deficienciesCommunicate deficiencies to those responsible for corrective action in time.
In QULDEXDeficiencies become CAPA items with owners and due dates.
CC5.1Control activities that mitigate riskSelect and develop control activities that reduce risks to acceptable levels.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
CC5.2General controls over technologySelect and develop general control activities over technology.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
CC5.3Policies and procedures that put controls in placeDeploy controls through policies and the procedures that put them into action.
In QULDEXPolicies are versioned with approvals and linked to the criteria they support.
- Typical evidence
- Approved policy set with review dates
CC6.1Logical access securityImplement logical access security software, infrastructure and architectures over protected information.
In QULDEXAccess controls are tested once and reused for ISO 27001 A.5.15 and A.8.5.
- Typical evidence
- Access policy, IdP and MFA settings
- Maps to
- ISO 27001 A.5.15A.8.5NIST PR.AA-05
CC6.2User registration and authorisationRegister and authorise new users before issuing credentials, and remove access when no longer needed.
In QULDEXJoiner and leaver tickets attach as evidence and are sampled in the same workspace.
- Typical evidence
- Provisioning and deprovisioning tickets
- Maps to
- ISO 27001 A.5.16A.5.18
CC6.3Role-based access and least privilegeAuthorise, change or remove access based on roles, least privilege and segregation of duties.
In QULDEXAccess reviews run as recurring tasks; revocations become tracked actions.
- Typical evidence
- Quarterly access review sign-off
- Maps to
- ISO 27001 A.5.18A.8.2
CC6.4Physical access to facilitiesRestrict physical access to facilities and protected assets to authorised people.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Badge logs, data-centre provider SOC report
- Maps to
- ISO 27001 A.7.2
CC6.5Disposal of data and physical assetsDiscontinue protection only after data is removed from disposed assets.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Disposal certificates
- Maps to
- ISO 27001 A.7.14
CC6.6Protection against external threatsProtect against threats from sources outside system boundaries.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Firewall and WAF configuration
- Maps to
- ISO 27001 A.8.20
CC6.7Restricting transmission of informationRestrict transmission, movement and removal of information to authorised users and processes.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Encryption-in-transit settings, DLP rules
- Maps to
- ISO 27001 A.8.12A.5.14
CC6.8Preventing malicious softwarePrevent or detect unauthorised or malicious software.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Endpoint protection console export
- Maps to
- ISO 27001 A.8.7
CC7.1Detecting configuration changes and vulnerabilitiesUse detection and monitoring to find configuration changes and new vulnerabilities.
In QULDEXScan reports attach each cycle; overdue findings become CAPA items.
- Typical evidence
- Vulnerability scans, patch tickets
- Maps to
- ISO 27001 A.8.8NIST ID.RA-01
CC7.2Monitoring for anomaliesMonitor system components for anomalies that indicate malicious acts, errors or natural disasters.
In QULDEXLog review evidence is collected on schedule for the whole observation period.
- Typical evidence
- SIEM alerts, log review records
- Maps to
- ISO 27001 A.8.15A.8.16NIST DE.CM-01
CC7.3Evaluating security eventsEvaluate security events to decide whether they are incidents.
In QULDEXIncidents are logged with triage notes and linked evidence.
- Typical evidence
- Incident tickets with triage
- Maps to
- ISO 27001 A.5.25
CC7.4Responding to security incidentsRespond to identified incidents with a defined programme.
In QULDEXIncident response steps and lessons learned feed CAPA.
- Typical evidence
- Incident response plan, tabletop test
- Maps to
- ISO 27001 A.5.26NIST RS.MA-01
CC7.5Recovering from security incidentsIdentify, develop and carry out activities to recover from incidents.
In QULDEXRecovery actions are tracked to closure with evidence.
- Typical evidence
- Post-incident reviews
- Maps to
- ISO 27001 A.5.27
CC8.1Change managementAuthorise, design, develop, test, approve and implement changes to infrastructure, data, software and procedures.
In QULDEXChange tickets are sampled directly; unapproved changes raise a finding.
- Typical evidence
- Change tickets with approvals and tests
- Maps to
- ISO 27001 A.8.32NIST ID.RA-07
CC9.1Risk mitigation for business disruptionIdentify, select and develop activities to mitigate risks from business disruption.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Business continuity plan
- Maps to
- ISO 27001 A.5.29
CC9.2Vendor and business partner riskAssess and manage risks from vendors and business partners.
In QULDEXEach vendor gets one record with assessment, contract and renewal date.
- Typical evidence
- Vendor inventory, assessments, contracts
- Maps to
- ISO 27001 A.5.19NIST GV.SC-07
Availability 3
A1.1Capacity managementMaintain, monitor and evaluate processing capacity and use to meet availability commitments.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Capacity dashboards, scaling alerts
- Maps to
- ISO 27001 A.8.6
A1.2Environmental protections, backup and recoveryPut environmental protections, software, data backup and recovery infrastructure in place.
In QULDEXBackup job logs and restore tests are scheduled and kept as evidence.
- Typical evidence
- Backup logs, restore tests
- Maps to
- ISO 27001 A.8.13NIST PR.DS-11
A1.3Recovery plan testingTest recovery plan procedures that support system recovery.
In QULDEXRecovery tests are recurring tasks with results attached.
- Typical evidence
- DR test report
- Maps to
- ISO 27001 A.5.30
Processing integrity 5
PI1.1Definitions of data and specificationsObtain or generate quality information about processing objectives, including definitions of data processed.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
PI1.2Controls over system inputsEnsure system inputs are complete and accurate.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Input validation rules
PI1.3Controls over processingEnsure processing is complete, accurate and timely.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Job monitoring, reconciliation reports
PI1.4Controls over outputsDeliver outputs completely, accurately and on time to the intended parties.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
PI1.5Controls over stored inputs and outputsStore inputs and outputs completely, accurately and on time.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
Confidentiality 2
C1.1Identifying and maintaining confidential informationIdentify and protect confidential information in line with commitments.
In QULDEXClassification and handling evidence is linked once for SOC 2 and ISO 27001.
- Typical evidence
- Data classification policy, inventory
- Maps to
- ISO 27001 A.5.12
C1.2Disposing of confidential informationDispose of confidential information in line with commitments.
In QULDEXQULDEX assigns an owner and test steps to this criterion, collects evidence across the observation period and maps it to ISO 27001 and NIST CSF.
- Typical evidence
- Retention schedule, deletion logs
- Maps to
- ISO 27001 A.8.10
Privacy 18
P1.1Privacy noticeGive data subjects notice about privacy practices.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
- Typical evidence
- Published privacy notice
- Maps to
- GDPR Art. 13–14
P2.1Choice and consentCommunicate choices about collection, use and disclosure, and obtain consent where needed.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
- Typical evidence
- Consent records
- Maps to
- GDPR Art. 7
P3.1Collection consistent with objectivesCollect personal information only for the identified objectives.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
P3.2Explicit consent for collectionObtain explicit consent when required before collecting personal information.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
P4.1Use of personal informationLimit use of personal information to the identified purposes.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
P4.2Retention of personal informationRetain personal information only as long as needed.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
- Typical evidence
- Retention schedule
P4.3Disposal of personal informationSecurely dispose of personal information.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
- Typical evidence
- Deletion logs
P5.1Access by data subjectsGive data subjects access to their personal information.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
- Typical evidence
- Access request log
- Maps to
- GDPR Art. 15
P5.2Correction of personal informationCorrect, amend or append personal information on request.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
- Maps to
- GDPR Art. 16
P6.1Disclosure to third partiesDisclose personal information to third parties only with consent or for identified purposes.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
P6.2Record of authorised disclosuresKeep a complete, accurate record of authorised disclosures.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
P6.3Record of unauthorised disclosuresKeep a record of detected or reported unauthorised disclosures, including breaches.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
P6.4Commitments from third partiesObtain privacy commitments from vendors and other third parties.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
- Typical evidence
- Data processing agreements
- Maps to
- GDPR Art. 28
P6.5Notification from third partiesGet notified by third parties about unauthorised disclosures.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
P6.6Breach notificationNotify affected data subjects, regulators and others of breaches as required.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
- Typical evidence
- Breach register, notification records
- Maps to
- GDPR Art. 33–34
P6.7Accounting of disclosuresGive data subjects an accounting of disclosures on request.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
P7.1Quality of personal informationKeep personal information accurate, complete and relevant.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
P8.1Inquiries, complaints and disputesHandle privacy inquiries, complaints and disputes, and monitor compliance.
In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.
- Typical evidence
- Complaint log, resolution records
Nothing matches that search.
Criterion IDs follow the AICPA 2017 Trust Services Criteria. Names and summaries are QULDEX paraphrases; the AICPA text is the authority.
How does a SOC 2 audit work, from readiness to Type II?
Define the system and categories, close gaps, then a CPA firm examines your controls. Most first-time companies get a Type I in 3–6 months and a Type II 6–12 months after that.
Define the system, scope and categories
Decide which services, infrastructure, data and teams are in the system description, and which categories beyond security your customers need.
Run a readiness assessment
Compare current controls with the criteria and list the gaps a CPA firm would flag.
Close gaps and start collecting evidence
Put missing controls in place and make sure each one leaves a record: tickets, logs, reviews, approvals.
Type I examination
The CPA firm tests whether controls are suitably designed and in place at a specific date.
Observation period
Controls must operate consistently. Every sample the auditor pulls later comes from this window.
Type II examination and report
The auditor samples evidence across the period and issues an opinion: unqualified, qualified, adverse or a disclaimer.
Repeat every year
Months 0–12Next observation periodBetween reportsBridge letter for customersYear endNew Type II report
Durations are typical planning ranges from QULDEX audit delivery. The observation period is agreed with your CPA firm.
What is in a SOC 2 report?
A SOC 2 report has the auditor's opinion, management's assertion, the system description and, for Type II, every test and its result. Customers read the exceptions first.
| Section | Reference | Where it comes from in QULDEX |
|---|---|---|
| Independent service auditor's report (opinion) | AT-C 205 | Auditor workspace |
| Management's assertion | AT-C 205 | Approval workflow with sign-off |
| System description | DC 200 | Drafted from scoped assets, people and vendors |
| Criteria and related controls | TSP 100 | Pre-mapped control library |
| Tests of controls and results (Type II) | AT-C 205 | Evidence vault samples and test sheets |
| Complementary user entity controls (CUECs) | DC 200 | Customer responsibilities list |
| Subservice organisations (carve-out or inclusive) | DC 200 | Vendor register with their SOC reports |
Section names follow common SOC 2 report structure under AICPA standards; exact layout varies by CPA firm.
How long does SOC 2 take and what drives the cost?
A Type I usually takes 3 to 6 months from scoping. A Type II adds an observation period of 3 to 12 months. Cost depends on the number of categories, the size of the system and the CPA firm.
Where the time goes
Bars show the upper end of each range on one scale (12 months = full width).
What changes the effort
- Categories in scope: each optional category adds criteria and tests
- System size: more services, environments and vendors mean more samples
- Observation length: a longer period means more evidence to collect
- Existing ISO 27001: reused controls and evidence shorten readiness
- Carve-out vendors: relying on vendors' own SOC reports keeps scope smaller
Are you ready for a SOC 2 Type I?
CPA firms check these eight things early. Answer them to see where you stand. Nothing you enter leaves this page.
How SOC 2 maps to ISO 27001 and NIST CSF 2.0
Most SOC 2 criteria have a direct ISO 27001 counterpart, so one tested control and one evidence item can support both reports. QULDEX keeps this mapping in its pre-mapped control library.
SOC 2 vs ISO 27001 at a glance
| SOC 2 | ISO 27001 | |
|---|---|---|
| What it is | Attestation report on controls (AICPA) | International management-system standard |
| Who issues it | Licensed CPA firm | Accredited certification body |
| What you get | Restricted-use report, Type I or Type II | Public certificate |
| Validity | Covers a set period; usually renewed yearly | 3 years with annual surveillance audits |
| Where it's asked for | Mostly North America | Worldwide; strongest in Europe, the Middle East and Asia |
| Scope | Criteria for the categories you select | The ISMS plus Annex A controls chosen by risk |
| In QULDEX | One control set and one evidence vault serve both. Test a control once and it counts toward both. | |
Criteria crosswalk
| SOC 2 (TSC 2017) | ISO 27001:2022 | NIST CSF 2.0 | Shared evidence |
|---|---|---|---|
| CC3.2 Risk identification | 6.1.2 | ID.RA-05 | Risk register |
| CC6.1 Logical access | A.5.15 · A.8.5 | PR.AA-05 | Access policy, MFA settings |
| CC6.3 Least privilege | A.5.18 · A.8.2 | PR.AA-05 | Quarterly access reviews |
| CC7.1 Vulnerabilities | A.8.8 | ID.RA-01 | Scan reports, patch tickets |
| CC7.2 Monitoring | A.8.15 · A.8.16 | DE.CM-01 | SIEM alerts, log reviews |
| CC7.3–CC7.5 Incidents | A.5.24–A.5.27 | RS.MA-01 | Incident plan, post-incident reviews |
| CC8.1 Change management | A.8.32 | ID.RA-07 | Change tickets with approvals |
| CC9.2 Vendors | A.5.19–A.5.22 | GV.SC-07 | Vendor assessments, contracts |
| A1.2 Backup and recovery | A.8.13 · A.8.14 | PR.DS-11 | Backup logs, restore tests |
Indicative mapping for planning. The full crosswalk is in the QULDEX control library.
How QULDEX runs SOC 2 from readiness to Type II report
QULDEX is SOC 2 compliance and audit management software built from EGV Group's audit delivery, used by the company being examined and by the auditors who test it. Pick your role to see who does what.
For SaaS and service companies preparing a first report or renewing one.
- ScopeChoose the system and categoriesSystem description drafted from scoped assets and vendors
- ReadinessFix the gapsGap list mapped to every criterion with owners
- EvidenceRun controls through the periodRecurring evidence requests so nothing is missed mid-period
- Type ISupport the auditorControlled evidence sharing with the CPA firm
- Type IIAnswer sample requestsSamples served from the vault with full history
- CustomersShare the reportSecure, logged report sharing and bridge letters
For readiness consultants and internal audit teams.
- ScopeRun the readiness assessmentA reusable SOC 2 readiness template
- ReadinessGuide the clientYour methodology saved as a control set
- EvidenceReview evidenceReview and approval states on every item
- Type IPre-audit checkMock tests and sampling in the audit workspace
- Type IITrack exceptionsExceptions become CAPA items
- CustomersStay on retainerOne dashboard across clients and report dates
For audit firms performing SOC 2 examinations.
- PlanningAgree scope and periodScope, criteria and system description in a standard format
- WalkthroughsUnderstand the controlsControl narratives linked to criteria
- TestingSample evidenceView-only evidence access with download control and an access log
- ExceptionsRecord deviationsExceptions recorded against criteria
- ReportIssue the opinionTraceable workpapers for the opinion
- Next yearRoll forwardHistory kept for the next period
Pre-mapped control library
Requirements with owners, test steps and the crosswalk to 50+ frameworks.
Explore →EvidenceSecure evidence vault
Evidence linked to controls and findings, with upload, review and approval history.
Explore →RiskRisk register
Risk assessment and treatment, with decisions traced to the controls they drive.
Explore →FindingsCAPA remediation
Findings from internal and external audits tracked to closure with due dates.
Explore →SOC 2 questions people ask
Is SOC 2 a certification?
No. SOC 2 is an attestation report: a licensed CPA firm gives an opinion on your controls. There is no certificate, though people often say "SOC 2 certified".
What is the difference between SOC 2 Type I and Type II?
Type I reports on whether controls are suitably designed at a specific date. Type II also tests whether they operated effectively over a period, usually 3 to 12 months. Buyers usually want Type II.
Which trust services categories do we need?
Security is always required. Add availability, processing integrity, confidentiality or privacy only when customers or contracts ask for them, since each adds criteria and testing.
How long is a SOC 2 report valid?
A report covers a set period and doesn't formally expire, but most customers expect one no older than 12 months. A bridge letter covers the gap until the next report.
Who can perform a SOC 2 audit?
Only a licensed CPA firm can issue a SOC 2 report under AICPA attestation standards. Readiness consultants can help you prepare but can't issue the report.
What is the difference between SOC 2 and ISO 27001?
SOC 2 is a CPA attestation report mostly requested in North America. ISO 27001 is a certifiable international standard for a management system. Many controls overlap.
Can QULDEX run SOC 2 alongside ISO 27001?
Yes. Criteria and evidence are mapped once in the control library, so the same work supports SOC 2, ISO 27001, NIST CSF 2.0 and others, each with its own report.
Go deeper on SOC 2
SOC 2 observation period: how long should it be?
How auditors and buyers look at 3, 6 and 12-month windows.
blog.quldex.comSOC 2 bridge letter
What a bridge letter covers and when customers ask for one.
blog.quldex.comAudit evidence naming convention
A file-naming scheme that lets auditors sample without asking.
blog.quldex.comAudit sampling size for compliance
How many samples auditors pull per control, and why.
References
- AICPA, 2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (with revised points of focus, 2022). aicpa-cima.com
- AICPA, DC 200: 2018 Description Criteria for a Description of a Service Organization's System in a SOC 2 Report. aicpa-cima.com
- AICPA, SSAE 18 / AT-C 205 examination engagements. aicpa-cima.com
- AICPA Guide, SOC 2 Reporting on an Examination of Controls at a Service Organization. aicpa-cima.com
- ISO/IEC 27001:2022. iso.org
Reviewed by
Page history
- : Rebuilt with all 61 criteria, Type I vs Type II path, report anatomy and readiness check
- : Page first published
Find your SOC 2 gaps before the auditor does
Answer a short readiness check and get a gap summary by criterion. No sales call needed to see the result.