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.

Key takeaways

What you need to know about SOC 2

AttestationA CPA firm gives an opinion on your controls; there is no certificate.
Security firstThe common criteria (CC1–CC9) are always in scope.
Type II winsMost enterprise buyers ask for Type II, which tests controls over 3–12 months.
You choosePick the extra categories your customers and contracts actually need.
ReusableAbout two thirds of the work overlaps with ISO 27001.

Who needs SOC 2?

No law requires it, but these situations usually make it a requirement in practice.

B2B SaaS companiesUS enterprise buyers ask for a SOC 2 Type II during security review.
Cloud and hosting providersCustomers rely on your report for their own audits.
Payment and fintech platformsPartners and banks look for independent assurance over controls.
Managed service providersClients need evidence that you protect their systems and data.
Companies selling into North AmericaSOC 2 is the default security assurance request there.

QULDEX helps here first: the readiness check shows where you stand before you commit budget.

Trust services categories

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.

CC1–CC9 Required

Security

Common criteria covering governance, risk, monitoring, access, operations, change and vendors.

In QULDEX: One control set reused for ISO 27001 and NIST CSF
A1 Optional

Availability

Capacity, backup, recovery and recovery testing.

In QULDEX: Backup and DR tests scheduled with results attached
PI1 Optional

Processing integrity

Complete, accurate and timely processing.

In QULDEX: Reconciliation evidence collected per cycle
C1 Optional

Confidentiality

Identify, protect and dispose of confidential information.

In QULDEX: Classification evidence shared with ISO 27001
P1–P8 Optional

Privacy

Notice, consent, use, access, disclosure, quality and complaints.

In QULDEX: Privacy evidence reused for ISO 27701 and GDPR
DC 200 Required

System description

Describe services, boundaries, infrastructure, people, data and controls.

In QULDEX: System description drafted from your scoped assets
AT-C 205 Auditor

Examination

The CPA firm tests controls and issues its opinion.

In QULDEX: Auditors sample evidence in a controlled view
Trust Services Criteria

What 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.

5trust services categories
33common criteria, always in scope
28criteria in the optional categories
2022points of focus revised

Showing up to 6 per group. Search, filter, or open a group to see all 61.

Security (common criteria) 33

  1. CC1.1Commitment to integrity and ethical values

    Show 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

  2. CC1.2Board independence and oversight

    The 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

  3. CC1.3Structures, reporting lines and authorities

    Management 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

  4. CC1.4Commitment to competence

    Attract, 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

  5. CC1.5Accountability for internal control

    Hold 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

  6. CC2.1Quality information to support internal control

    Obtain 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.

  7. CC2.2Internal communication of objectives and responsibilities

    Communicate 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

  8. CC2.3Communication with external parties

    Communicate 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

  9. CC3.1Objectives specified clearly enough to identify risks

    Set objectives clearly enough to identify and assess related risks.

    In QULDEXObjectives live in the risk register next to the risks they drive.

  10. CC3.2Risk identification and analysis

    Identify 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

  11. CC3.3Fraud risk assessment

    Consider the potential for fraud when assessing risks.

    In QULDEXFraud scenarios sit in the same risk register with owners and reviews.

  12. CC3.4Changes that could impact internal control

    Identify and assess changes that could significantly affect internal control.

    In QULDEXSignificant changes trigger a risk review task in QULDEX.

  13. CC4.1Ongoing and separate evaluations

    Run 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

  14. CC4.2Communicating internal control deficiencies

    Communicate deficiencies to those responsible for corrective action in time.

    In QULDEXDeficiencies become CAPA items with owners and due dates.

  15. CC5.1Control activities that mitigate risk

    Select 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.

  16. CC5.2General controls over technology

    Select 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.

  17. CC5.3Policies and procedures that put controls in place

    Deploy 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

  18. CC6.1Logical access security

    Implement 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

  19. CC6.2User registration and authorisation

    Register 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

  20. CC6.3Role-based access and least privilege

    Authorise, 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

  21. CC6.4Physical access to facilities

    Restrict 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

  22. CC6.5Disposal of data and physical assets

    Discontinue 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

  23. CC6.6Protection against external threats

    Protect 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

  24. CC6.7Restricting transmission of information

    Restrict 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

  25. CC6.8Preventing malicious software

    Prevent 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

  26. CC7.1Detecting configuration changes and vulnerabilities

    Use 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

  27. CC7.2Monitoring for anomalies

    Monitor 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

  28. CC7.3Evaluating security events

    Evaluate 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

  29. CC7.4Responding to security incidents

    Respond 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

  30. CC7.5Recovering from security incidents

    Identify, 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

  31. CC8.1Change management

    Authorise, 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

  32. CC9.1Risk mitigation for business disruption

    Identify, 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

  33. CC9.2Vendor and business partner risk

    Assess 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

  1. A1.1Capacity management

    Maintain, 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

  2. A1.2Environmental protections, backup and recovery

    Put 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

  3. A1.3Recovery plan testing

    Test 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

  1. PI1.1Definitions of data and specifications

    Obtain 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.

  2. PI1.2Controls over system inputs

    Ensure 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

  3. PI1.3Controls over processing

    Ensure 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

  4. PI1.4Controls over outputs

    Deliver 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.

  5. PI1.5Controls over stored inputs and outputs

    Store 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

  1. C1.1Identifying and maintaining confidential information

    Identify 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

  2. C1.2Disposing of confidential information

    Dispose 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

  1. P1.1Privacy notice

    Give 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

  2. P2.1Choice and consent

    Communicate 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

  3. P3.1Collection consistent with objectives

    Collect personal information only for the identified objectives.

    In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.

  4. P3.2Explicit consent for collection

    Obtain explicit consent when required before collecting personal information.

    In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.

  5. P4.1Use of personal information

    Limit use of personal information to the identified purposes.

    In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.

  6. P4.2Retention of personal information

    Retain 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

  7. P4.3Disposal of personal information

    Securely dispose of personal information.

    In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.

    Typical evidence
    Deletion logs

  8. P5.1Access by data subjects

    Give 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

  9. P5.2Correction of personal information

    Correct, 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

  10. P6.1Disclosure to third parties

    Disclose 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.

  11. P6.2Record of authorised disclosures

    Keep a complete, accurate record of authorised disclosures.

    In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.

  12. P6.3Record of unauthorised disclosures

    Keep 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.

  13. P6.4Commitments from third parties

    Obtain 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

  14. P6.5Notification from third parties

    Get notified by third parties about unauthorised disclosures.

    In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.

  15. P6.6Breach notification

    Notify 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

  16. P6.7Accounting of disclosures

    Give data subjects an accounting of disclosures on request.

    In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.

  17. P7.1Quality of personal information

    Keep personal information accurate, complete and relevant.

    In QULDEXPrivacy evidence is captured once and also counts toward ISO 27701, GDPR and DPDP programmes.

  18. P8.1Inquiries, complaints and disputes

    Handle 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

Criterion IDs follow the AICPA 2017 Trust Services Criteria. Names and summaries are QULDEX paraphrases; the AICPA text is the authority.

Audit path

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.

  1. 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.

  2. Run a readiness assessment

    Compare current controls with the criteria and list the gaps a CPA firm would flag.

  3. Close gaps and start collecting evidence

    Put missing controls in place and make sure each one leaves a record: tickets, logs, reviews, approvals.

  4. Type I examination

    The CPA firm tests whether controls are suitably designed and in place at a specific date.

    2–6 weeks including report
  5. Observation period

    Controls must operate consistently. Every sample the auditor pulls later comes from this window.

    3–12 monthsCAPA automation →
  6. Type II examination and report

    The auditor samples evidence across the period and issues an opinion: unqualified, qualified, adverse or a disclaimer.

  7. Repeat every year

    Months 0–12Next observation period
    Between reportsBridge letter for customers
    Year endNew Type II report

Durations are typical planning ranges from QULDEX audit delivery. The observation period is agreed with your CPA firm.

Inside the report

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.

SectionReferenceWhere it comes from in QULDEX
Independent service auditor's report (opinion)AT-C 205Auditor workspace
Management's assertionAT-C 205Approval workflow with sign-off
System descriptionDC 200Drafted from scoped assets, people and vendors
Criteria and related controlsTSP 100Pre-mapped control library
Tests of controls and results (Type II)AT-C 205Evidence vault samples and test sheets
Complementary user entity controls (CUECs)DC 200Customer responsibilities list
Subservice organisations (carve-out or inclusive)DC 200Vendor register with their SOC reports

Section names follow common SOC 2 report structure under AICPA standards; exact layout varies by CPA firm.

Time and cost

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

Scope and readiness4–8 wk
Close gaps1–3 mo
Type I examination2–6 wk
Observation period3–12 mo
Type II examination4–8 wk

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
Readiness check · 2 minutes

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.

DC 200Is your system boundary written down: services, infrastructure, data and people?
TSCHave you chosen which categories beyond security are in scope?
CC5.3Are your security policies approved and reviewed in the last year?
CC3.2Have you run a documented risk assessment in the last 12 months?
CC6.3Do you review user access at least quarterly, with sign-off?
CC8.1Does every production change have a ticket, test and approval?
CC7.4Do you have an incident response plan that has been tested?
CC9.2Do you assess vendors that handle your data or systems?
Crosswalk

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 2ISO 27001
What it isAttestation report on controls (AICPA)International management-system standard
Who issues itLicensed CPA firmAccredited certification body
What you getRestricted-use report, Type I or Type IIPublic certificate
ValidityCovers a set period; usually renewed yearly3 years with annual surveillance audits
Where it's asked forMostly North AmericaWorldwide; strongest in Europe, the Middle East and Asia
ScopeCriteria for the categories you selectThe ISMS plus Annex A controls chosen by risk
In QULDEXOne 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:2022NIST CSF 2.0Shared evidence
CC3.2 Risk identification6.1.2ID.RA-05Risk register
CC6.1 Logical accessA.5.15 · A.8.5PR.AA-05Access policy, MFA settings
CC6.3 Least privilegeA.5.18 · A.8.2PR.AA-05Quarterly access reviews
CC7.1 VulnerabilitiesA.8.8ID.RA-01Scan reports, patch tickets
CC7.2 MonitoringA.8.15 · A.8.16DE.CM-01SIEM alerts, log reviews
CC7.3–CC7.5 IncidentsA.5.24–A.5.27RS.MA-01Incident plan, post-incident reviews
CC8.1 Change managementA.8.32ID.RA-07Change tickets with approvals
CC9.2 VendorsA.5.19–A.5.22GV.SC-07Vendor assessments, contracts
A1.2 Backup and recoveryA.8.13 · A.8.14PR.DS-11Backup logs, restore tests

Indicative mapping for planning. The full crosswalk is in the QULDEX control library.

Where QULDEX fits

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.

  1. ScopeChoose the system and categoriesSystem description drafted from scoped assets and vendors
  2. ReadinessFix the gapsGap list mapped to every criterion with owners
  3. EvidenceRun controls through the periodRecurring evidence requests so nothing is missed mid-period
  4. Type ISupport the auditorControlled evidence sharing with the CPA firm
  5. Type IIAnswer sample requestsSamples served from the vault with full history
  6. CustomersShare the reportSecure, logged report sharing and bridge letters
Without one systemWith QULDEX
Evidence chased by email at audit timeEvidence collected on schedule through the period
Separate spreadsheets for SOC 2 and ISO 27001One control set mapped to both
Auditor requests answered with zip filesControlled, logged sharing with the CPA firm
Report sent as an email attachmentSecure, expiring report links for customers
10+years of audit delivery500+audits deliveredBoth sidesof the audit on one platformRBACand a full audit trail on every action
FAQ

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.

Sources

References

  1. AICPA, 2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy (with revised points of focus, 2022). aicpa-cima.com
  2. AICPA, DC 200: 2018 Description Criteria for a Description of a Service Organization's System in a SOC 2 Report. aicpa-cima.com
  3. AICPA, SSAE 18 / AT-C 205 examination engagements. aicpa-cima.com
  4. AICPA Guide, SOC 2 Reporting on an Examination of Controls at a Service Organization. aicpa-cima.com
  5. ISO/IEC 27001:2022. iso.org

Reviewed by

Ankit Tiwari

Framework reviewer · QULDEX

Reviewed this page against the AICPA 2017 Trust Services Criteria and DC 200: criteria, report structure, audit path and crosswalk.

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.

Schedule
Book a Demo