USA

SOC 2 Certification USA

CertPro is a Licensed CPA Firm that performs independent SOC 2 examinations for organizations in the USA under AICPA attestation standards. Each engagement evaluates controls against the applicable Trust Services Criteria, with security required in every examination, and results in a Type 1 or Type 2 report. Engagements cover the Technology and software, Financial services, and Healthcare sectors.

OUR CLIENTS

Hacker Rank
Drivetrain
Entytle
Giift
Flyt Base
Anaconda Inc
Murf Ai
NORLEE GROUP
Vlex
Carestack.C

What SOC 2 Certification in USA Means: An Attestation Issued by a Licensed CPA Firm

Executive Summary: SOC 2 Attestation by a Licensed CPA Firm

SOC 2 certification USA is an independent attestation issued by CertPro, a Licensed CPA Firm, after it examines a service organization’s controls against the AICPA Trust Services Criteria. Each engagement covers a defined system, the criteria selected for that system, and either a Type 1 or a Type 2 examination. CertPro performs these examinations for organizations operating anywhere in the United States.

SOC 2 compliance USA expectations come from customers, partners and investors. These parties ask service organizations to show that the systems holding their data are properly controlled. For a US service organization, SOC 2 certification in USA terms means holding a current SOC 2 attestation report. In that report, an independent CPA auditor describes the system, identifies the controls management has placed in operation and states a formal opinion on them.

Requests for SOC 2 reports are especially common among companies based in, or selling into, the major US technology and finance hubs. These include Silicon Valley, Wall Street, Research Triangle Park in North Carolina and Kendall Square in Cambridge, Massachusetts. The examination standard, however, is national. A SOC 2 report issued for a company in Texas is evaluated under the same AICPA attestation standards as one issued for a company in New York or California, and US report users read both reports the same way.

SOC 2 Certification vs SOC 2 Attestation: Terminology Defined

SOC 2 certification is an attestation engagement in which a licensed CPA firm examines a service organization’s description of its system and the controls within that system. The firm then issues a report containing the auditor’s opinion, measured against the AICPA Trust Services Criteria.

The market uses the word “certification” informally. The formal terms are “SOC 2 attestation” and “SOC 2 examination”, and the deliverable is a report rather than a certificate. No official registry of SOC 2 certified companies exists, and no logo or badge carries the authority of the report itself. When a US company states that it is “SOC 2 certified”, the accurate meaning is that a CPA firm has tested its controls and expressed an opinion on them.

This is what separates attestation from compliance. A company that calls itself “SOC 2 compliant” may follow controls aligned to the criteria without any independent verification. A SOC 2 attested company, by contrast, holds a report in which an outside auditor has evaluated the evidence. For this reason, US reviewers ask for the report rather than a statement of compliance, and they read the auditor’s opinion before relying on any vendor claim.

Why Only a Licensed CPA Firm Can Issue a SOC 2 Report

SOC 2 examinations are performed under the attestation standards of the American Institute of Certified Public Accountants (AICPA). These are the Statements on Standards for Attestation Engagements, and SSAE 18 established their current framework. Because these are professional attestation standards, only a licensed CPA firm can issue a SOC 2 report. A software vendor, a compliance automation platform or a non-CPA assessor cannot sign the opinion.

Licensed CPA firms are subject to state board of accountancy licensing, AICPA independence rules and peer review of their attestation practice. Together, these give report users a basis for relying on the work.

Independence is the central requirement. A licensed CPA firm for SOC 2 audit engagements must not design, implement or operate the controls it later tests, because doing so would place the auditor in the position of evaluating its own work. CertPro performs the independent examination and issues the opinion; it does not build or remediate the client’s control environment. When US organizations evaluate SOC 2 audit firms in the USA, they ask about licensure, independence and peer review status, because these factors determine whether a report can be relied on.

ENQUIRE NOW



SOC 2 Trust Services Criteria Evaluated in a US Audit

A SOC 2 audit USA engagement evaluates controls against the AICPA SOC 2 Trust Services Criteria, published in TSP section 100. The criteria are organized into five categories, and only one of them is mandatory in every examination:

  • ✓Security (Common Criteria): protection of information and systems against unauthorized access, disclosure and damage
  • ✓Availability: accessibility of the system for operation and use as committed or agreed
  • ✓Processing Integrity: complete, valid, accurate, timely and authorized system processing
  • ✓Confidentiality: protection of information designated as confidential
  • ✓Privacy: collection, use, retention, disclosure and disposal of personal information

Security, also called the Common Criteria, is included in every SOC 2 examination and forms the core of SOC 2 requirements in the USA. The Common Criteria are organized into nine series, CC1 through CC9:

  • Control environment
  • Communication and information
  • Risk assessment
  • Monitoring activities
  • Control activities
  • Logical and physical access controls
  • System operations
  • Change management
  • Risk mitigation

The first five series align with the COSO 2013 internal control framework, which is why SOC 2 reports frequently reference COSO principles. In practice, the auditor tests controls such as user provisioning and deprovisioning, multi-factor authentication, periodic access reviews, vulnerability scanning, encryption of data at rest and in transit, incident response procedures, vendor risk management and change approval workflows.

The Common Criteria also apply to the other four categories. As a result, a control tested under Security often provides evidence for Availability or Confidentiality as well. Security is the baseline of SOC 2 compliance USA report users expect, and no SOC 2 report can be issued without it.

Each of the four remaining categories requires its own testing:

  • Availability: Auditors examine capacity monitoring, backup execution, disaster recovery testing and incident communication against the service level commitments in the system description.
  • Processing Integrity: This category is relevant to organizations that calculate payroll, process payments, adjudicate claims or transform customer data. Testing focuses on input validation, reconciliation, output review and error handling.
  • Confidentiality: This category covers information such as customer intellectual property, financial data or contract terms. Auditors test classification, access restriction, retention and secure disposal controls.
  • Privacy: Auditors evaluate the handling of personal information against the organization’s privacy notice. This includes notice, choice and consent, individual access requests, disclosure to third parties and data quality.

In a SOC 2 audit USA engagement, Privacy is most relevant when the organization collects personal information directly from individuals. When it processes personal information on behalf of business customers, Confidentiality is frequently selected instead.

Management selects the categories in scope, and that selection is recorded in management’s assertion and the system description. The selection follows the service commitments the organization makes to customers in contracts, service level agreements and public statements. For example, an infrastructure provider with uptime commitments typically includes Availability, while a payment processor typically includes Processing Integrity. The selected criteria determine three outcomes in the SOC 2 attestation:

  • Controls tested: The criteria define which controls the auditor maps and tests.
  • Opinion scope: The auditor expresses an opinion only on the categories included.
  • Buyer interpretation: The criteria shape how report users read the report. A customer that depends on Availability will treat a Security-only report as incomplete.

Adding a category expands the control population and the evidence the auditor requests. For this reason, the category selection is aligned with documented customer commitments rather than with criteria that no contract or service obligation requires.

SOC 2 Requirements
  • ✓Security (Common Criteria): The Mandatory Criterion
  • ✓Availability, Processing Integrity, Confidentiality and Privacy
  • ✓How Selected Criteria Determine Controls Tested and the Report Opinion

SOC 2 Type 1 vs SOC 2 Type 2 in USA: How the Two Examinations Differ

Choosing between SOC 2 Type 1 and Type 2 is the most common scoping decision in SOC 2 certification USA engagements. Both examinations apply the same Trust Services Criteria and result in a SOC 2 attestation report. They differ in what the auditor tests and in the degree of assurance the report conveys.

SOC 2 Type 1 USA: Design of Controls at a Point in Time

A SOC 2 Type 1 examination evaluates two matters as of a specific date. The first is whether the system description is fairly presented. The second is whether controls are suitably designed to meet the selected criteria. The auditor inspects policies, configurations and procedures, performs walkthroughs with control owners and confirms that each control has been implemented.

The auditor does not test whether controls operated over time. The Type 1 report therefore answers one narrow question: on the report date, were appropriately designed controls in place?

Organizations undergoing a first SOC 2 audit USA engagement often begin with Type 1. It produces a documented, auditor-reviewed baseline and gives early customers a report to evaluate. Type 1 is also selected when a company has recently launched a product, restructured its infrastructure or migrated hosting providers, which leaves no operating history to sample. Because it contains no test of operating effectiveness, many report users accept a SOC 2 Type 1 USA report only as an interim document until a Type 2 report is issued.

SOC 2 Type 2 USA: Operating Effectiveness Over an Observation Period

A SOC 2 Type 2 examination evaluates whether controls are suitably designed and whether they operated effectively throughout a defined observation period. The period is fixed during scoping with a start date and an end date, and it defines the population from which the auditor draws samples. A first Type 2 period begins only after controls are in place.

For each control, the auditor selects instances that occurred within the period and verifies that the control functioned as described in each one. Typical sample sources include:

  • ✓Access requests and approvals
  • ✓Change tickets
  • ✓Terminated employee records
  • ✓Backup logs
  • ✓Incident tickets

The Type 2 report describes every test performed and its result, including any exception where a control did not operate as designed. Report users can therefore see which controls failed and in which sampled instances.

Type 2 Reports in U.S. Vendor Evaluations

Because it shows sustained operation rather than design alone, the SOC 2 Type 2 USA report is the version most often requested when service organizations are evaluated as vendors. In a representative case, a U.S. hospital system asks a cloud software vendor to complete a security questionnaire and to provide a SOC 2 Type II report before it will sign a contract involving patient data. A Type 1 report does not meet that stated requirement, because it contains no testing of operating effectiveness.

Type 1 vs Type 2 Comparison

  • ✓Question answered: Type 1 asks whether controls are suitably designed and implemented. Type 2 asks whether controls are suitably designed and operating effectively.
  • ✓Time frame: Type 1 is as of a specific date. Type 2 covers a defined observation period.
  • ✓Testing performed: Type 1 relies on inquiry, inspection and walkthroughs of design. Type 2 adds sample-based tests of operation to the design evaluation.
  • ✓Report content: Type 1 contains the opinion, management’s assertion, system description, criteria and controls. Type 2 contains all Type 1 content plus tests of controls, results and exceptions.
  • ✓Typical use: Type 1 serves as a baseline report for new systems or first examinations. Type 2 serves as primary evidence in enterprise vendor evaluations.
SOC 2 Type 1 and SOC 2 Type 2 examinations compared
Attribute SOC 2 Type 1 SOC 2 Type 2
Question answered Are controls suitably designed and implemented? Are controls suitably designed and operating effectively?
Time frame As of a specific date Across a defined observation period
Testing performed Inquiry, inspection and walkthroughs of design Design evaluation plus sample-based tests of operation
Report content Opinion, assertion, system description, criteria and controls All Type 1 content plus tests of controls, results and exceptions
Typical use Baseline report for new systems or first examinations Primary evidence in enterprise vendor evaluations

SOC 2 Audit Scope in USA: Systems, Criteria and the US Privacy Law Patchwork

SOC 2 audit scope in USA engagements is defined by four elements:

  • The system boundaries
  • The selected Trust Services Criteria
  • The in-scope infrastructure
  • Any subservice organizations

Scope decisions are documented before fieldwork begins and are reflected in the system description that the auditor evaluates.

The system boundary identifies which services the SOC 2 attestation covers and which components support those services. The AICPA description criteria (DC section 200) require the system description to address infrastructure, software, people, procedures and data, along with the principal service commitments and system requirements. The boundary differs by environment:

  • Cloud-native SaaS: In-scope infrastructure usually includes production accounts in a public cloud platform, identity providers, source code repositories, CI/CD pipelines, logging and monitoring tools, and endpoint management for employees with production access.
  • Colocation or owned data center: The boundary also includes physical access controls, environmental protections such as power and fire suppression, and hardware lifecycle procedures.
  • Hybrid: Where some workloads run in a public cloud and others in a private data center, the description states which controls apply to each environment.

Corporate systems unrelated to the service, such as marketing websites, are normally excluded. Clear boundaries determine which assets the auditor samples. Ambiguous boundaries produce scope disputes during fieldwork and confusion for report readers.

Most US service organizations rely on subservice organizations such as cloud infrastructure providers, colocation facilities or payment processors. A SOC 2 report addresses them using one of two methods:

  • Carve-out method: The subservice organization’s controls are excluded from the examination. The system description identifies the subservice organization and lists the complementary subservice organization controls (CSOCs) the provider is expected to perform. Report users obtain the provider’s own SOC 2 report to evaluate those controls. This is the predominant approach for large public cloud providers.
  • Inclusive method: The subservice organization’s relevant controls are included in the description and tested by the auditor. This requires the provider’s cooperation and a written assertion from its management.

The report also lists complementary user entity controls (CUECs). These are controls that customers must operate themselves, such as managing their own user accounts and reviewing their own access lists. Accurate CSOC and CUEC disclosures are a component of SOC 2 compliance USA report users evaluate when deciding how much reliance a report supports.

The USA has no single comprehensive federal privacy law. Organizations must reconcile state statutes with sector-specific federal rules:

  • State statutes: the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA); the New York Stop Hacks and Improve Electronic Data Security Act (SHIELD Act); and the Illinois Biometric Information Privacy Act (BIPA).
  • Federal sector rules: HIPAA for protected health information and the Gramm-Leach-Bliley Act (GLBA) for financial institutions.

Each regime imposes its own safeguard, breach-notification or data-handling obligations, and many organizations are subject to several at once. SOC 2 audit evidence is valuable in this patchwork because a single tested control set can be mapped to multiple frameworks. For example, access, encryption, incident response and vendor management controls tested under the Common Criteria also address safeguard expectations in state laws and in the HIPAA Security Rule. This reduces duplicated evidence collection.

A SOC 2 report does not constitute legal compliance with any statute. The auditor’s opinion addresses whether controls meet the Trust Services Criteria. Whether an organization satisfies CCPA, SHIELD Act, BIPA, HIPAA or GLBA requirements is a legal determination outside the scope of the attestation.

  • ✓Defining System Boundaries in Cloud and Data-Center Hosted Environments
  • ✓Subservice Organizations: Carve-Out and Inclusive Methods
  • ✓State Privacy Laws, HIPAA and GLBA: Multi-Framework Audit Evidence

SOC 2 Certification Audit Process in USA: 9 Evaluation Stages

A Licensed CPA Firm conducts the SOC 2 certification USA audit in nine sequential evaluation stages. Each stage produces workpapers that the engagement team retains as support for the final opinion.

  • ✓Scope Definition
  • ✓Audit Program Determination
  • ✓Stage 1 Audit
  • ✓Type I or Type II Assessment
  • ✓Control Testing
  • ✓Nonconformity (Exception) Review
  • ✓Certification Decision
  • ✓Issuance of Attestation
  • ✓Surveillance and Recertification

Stage 1: Scope Definition. Management and the auditor fix four elements: the services under examination, the system boundaries, the Trust Services Criteria in scope, and the subservice organizations. These elements are written into the engagement letter, and every later test procedure traces back to that document.

Stage 2: Audit Program Determination. The auditor links each control to the selected criteria and writes a test procedure for it. A risk assessment then marks the controls that need larger samples or extra procedures. The United States has no single comprehensive federal privacy law, and HIPAA and GLBA apply by sector. Organizations subject to these rules can ask that the control mapping be documented so the same evidence can be referenced in other compliance reviews. The finished audit program lists every item the auditor will request from management.

Stage 3: Stage 1 Audit. The auditor reads the draft system description, policies and control documentation to confirm the environment is ready for examination. Gaps are reported to management before testing begins. Typical gaps are an absent policy, a control with no named owner, or a system boundary that does not match the scope in the engagement letter.

Stage 4: Type I or Type II Assessment. The auditor confirms the report type and the report date or period stated in the engagement letter. For a Type II engagement, the auditor then requests the source records. Examples include user access listings, change tickets and incident logs. For each record set, the auditor identifies the system that produced it.

Stage 5: Control Testing. Controls are tested through inquiry, observation, inspection and reperformance. Inquiry alone is not sufficient evidence, so it is always combined with at least one other method. Before sampling from a system-generated report, the auditor checks that the report is complete and accurate by tracing its query logic and record counts back to the source system.

Stage 6: Nonconformity (Exception) Review. The auditor examines each deviation for its root cause and how often it occurred. The auditor also checks whether another control still met the same criterion. Deviations are then assessed together to decide whether they are isolated or point to a systemic failure that affects the opinion.

Stage 7: Certification Decision. The engagement team reviews the combined test results against the selected criteria. It then selects one of four opinion types: unqualified, qualified, adverse or disclaimer. Before the opinion is final, a partner who did not take part in fieldwork performs a quality review. This review confirms that the evidence supports the conclusion.

Stage 8: Issuance of Attestation. The Licensed CPA Firm signs and issues the SOC 2 attestation report with management’s signed assertion attached. The report contains the auditor’s opinion, management’s assertion and the system description. For Type II, it also contains the tests performed and their results. Management distributes the report to customers under the use restrictions set out in the next section.

Stage 9: Surveillance and Recertification. The next examination tests the controls again and reviews system changes made since the prior report. It also checks that the remediation of each previously reported deviation has been carried out and is operating.

  • ✓Stages 1-3: Scope Definition, Audit Program Determination and Stage 1 Audit
  • ✓Stages 4-6: Type I or Type II Assessment, Control Testing and Nonconformity Review
  • ✓Stages 7-9: Certification Decision, Issuance of Attestation and Surveillance and Recertification

The SOC 2 Attestation Report: Sections, Opinion Types and Distribution

The SOC 2 attestation report is the formal output of the examination. An SSAE 18 SOC 2 report uses a standardized structure, so US reviewers can compare reports issued to different service organizations on a like-for-like basis.

Five Components of a SOC 2 Report

  • ✓Independent service auditor’s report: sets out the scope, the criteria applied, the date or period covered and the auditor’s opinion
  • ✓Management’s assertion: a signed statement by management that the description is fairly presented and that controls meet the selected criteria
  • ✓System description: services, boundaries, infrastructure, software, people, procedures, data, service commitments, complementary subservice organization controls (CSOCs) and complementary user entity controls (CUECs)
  • ✓Trust Services Criteria and related controls: a mapping of each applicable criterion to the controls designed to address it
  • ✓Tests of controls and results (Type 2 only): the procedures the auditor performed, the sample sizes selected and the outcome of each test

CPA firms order these sections slightly differently, but the required content does not change.

How Reviewers Read the Report

Experienced reviewers work through the report in a fixed sequence:

  • ✓The opinion
  • ✓Management’s assertion
  • ✓The system description, to confirm that the services they purchase fall within scope
  • ✓The tests of controls, in Type 2 reports, to assess how each control performed over the period

Reviewers also compare the listed CUECs against their own control environment, because the report assumes those controls operate at the customer. If the description omits a service the customer relies on, the report provides no assurance over that service under any opinion type.

Unqualified, Qualified, Adverse and Disclaimer Opinions

  • ✓Unqualified: controls met the selected criteria in all material respects. Reviewers rely on the report but still examine individual exceptions.
  • ✓Qualified: criteria were met except for specific, identified matters. Reviewers focus on the affected criteria.
  • ✓Adverse: deficiencies are material and pervasive, and the criteria were not met. The report generally does not support vendor approval.
  • ✓Disclaimer: the auditor could not obtain sufficient evidence to form an opinion. The report provides no assurance over the controls.

An unqualified opinion does not indicate an exception-free report. Type 2 reports with unqualified opinions frequently contain isolated exceptions, where the auditor concluded the criteria were still met despite individual control failures.

A qualified opinion names the specific criteria the auditor could not conclude were met. Report users then assess whether those criteria relate to the services they purchase. In a SOC 2 audit USA engagement, any modified opinion includes a paragraph that states the basis for the modification in direct terms.

Report Distribution and Restricted Use

SOC 2 reports are restricted-use documents. They are intended for management, the service organization’s customers and other specified parties with enough knowledge of the system to interpret the report. Organizations typically release them under a nondisclosure agreement, through a trust portal or on direct request.

For example, a U.S. hospital system may require a cloud software vendor to complete a security questionnaire and provide a SOC 2 Type II report before signing a contract involving patient data. The vendor would ordinarily release that report to the hospital under an NDA rather than publish it.

A SOC 3 report summarizes the opinion without control-level detail and is designed for general public distribution.

Report Currency and Bridge Letters

A SOC 2 report covers a past period. US customers generally treat a report as stale once its period ended more than about twelve months earlier. Organizations therefore maintain SOC 2 certification USA status through an annual examination cycle.

Between the end of one report period and the issuance of the next report, management may provide a bridge letter, also called a gap letter. In it, management asserts that no material changes have occurred to the system or the control environment. A bridge letter is a management representation, not an auditor opinion. Report users accept it only to cover limited gaps between reports.

SOC 2 opinion types and their interpretation
Opinion Type Auditor’s Conclusion How US Reviewers Typically Read It
Unqualified Controls met the selected criteria in all material respects Report is relied on; individual exceptions are still reviewed
Qualified Criteria were met except for specific, identified matters Reviewers examine the affected criteria and management’s response
Adverse Deficiencies are material and pervasive; criteria were not met Report generally does not support vendor approval
Disclaimer Auditor could not obtain sufficient evidence to form an opinion Report provides no assurance over the controls

Why US Enterprise Buyers Require SOC 2 Reports in Vendor Security Reviews

US enterprise buyers request SOC 2 reports at three defined points in the vendor lifecycle: onboarding, contract negotiation and renewal. At each point, procurement, security and legal teams use the report to decide whether a vendor may receive data or system access, and on what terms.

How SOC 2 Reports Function in US Vendor Security Reviews

A vendor security review is the process a US buyer uses to assess the risk of granting a third party access to its data or systems. A vendor without a SOC 2 report typically receives a custom security questionnaire that can run to hundreds of questions, and each answer may require supporting evidence. A vendor with a current SOC 2 report can submit it in place of much of that questionnaire, which reduces the number of individual evidence requests.

Many US enterprises assign vendors to risk tiers. Vendors that process sensitive data sit in the highest tier and must provide a report covering an operating period. Lower-tier vendors may complete a shorter questionnaire instead of a full review.

SOC 2 compliance USA evidence also serves the buyer’s own oversight duties. Public companies, regulated financial institutions and healthcare entities must show their external auditors and regulators that they monitor third-party service providers. Vendor SOC 2 reports are filed as part of that third-party oversight record.

Procurement Example: A US Hospital System and a Cloud Software Vendor

A US hospital system requires a cloud software vendor to complete a security questionnaire and provide a SOC 2 Type II report before it signs a contract involving patient data. The hospital’s third-party risk team checks conditions specific to patient data:

  • ✓Security and Confidentiality are among the Trust Services Criteria in scope
  • ✓The platform that stores and processes patient data sits inside the described system boundary
  • ✓No reported exception involves access to protected health information

Once those conditions are confirmed, the hospital narrows its questionnaire to topics the SOC 2 report does not cover. One example is the vendor’s willingness to sign a business associate agreement, which is a contractual obligation and not a control tested in the examination. In this scenario, the SOC 2 Type 2 USA report settles the security questions and the questionnaire handles the remaining legal and contractual items.

SOC 2 Requirements in US Customer Contracts

US customer contracts and master services agreements often convert SOC 2 expectations into enforceable obligations. These clauses specify the report type, criteria and recency the vendor must maintain. As a result, SOC 2 certification USA status becomes a contractual condition and not a voluntary disclosure.

Common contract provisions include:

  • ✓Delivery of a current SOC 2 Type 2 report at contract signing and at each renewal
  • ✓Specification of required Trust Services Criteria, such as Security, Availability and Confidentiality
  • ✓A recency requirement defining how recently the report period must have ended
  • ✓Coverage of the specific services and hosting environments being purchased
  • ✓Notification obligations if a subsequent report contains a qualified or adverse opinion
  • ✓Provision of subservice organization reports for providers that support the purchased services
  • ✓Acknowledgment of the complementary user entity controls the customer must operate

When a contract date falls between the end of one report period and the issuance of the next report, buyers commonly ask for a bridge letter. A bridge letter is a management-signed statement that covers the gap. Management issues the bridge letter, not the service auditor, so buyers treat it as a vendor representation until the next examined period is reported.

Some buyers also use standardized questionnaires, such as the Shared Assessments SIG or the Cloud Security Alliance CAIQ, alongside the SOC 2 report. In those cases, the vendor’s report period and scope determine how many questionnaire items the buyer still requires.

US Industries Where SOC 2 Compliance Is Commonly Required

In the USA, SOC 2 reports are requested most often from service organizations that store, process or transmit data on behalf of their customers. Five sectors account for most of these requests: technology and software, financial services, healthcare, manufacturing and retail. Each sector tends to bring a different set of Trust Services Criteria into the examination.

Sector Overview: Service Organizations and Criteria in Scope

  • ✓Technology and software (SaaS): cloud applications, platforms and managed IT services. Criteria commonly in scope are Security, Availability and Confidentiality.
  • ✓Financial services and fintech: payment processors, lending platforms and wealth technology providers. Criteria commonly in scope are Security, Processing Integrity and Confidentiality.
  • ✓Healthcare and healthcare technology: telehealth, practice management and revenue cycle vendors. Criteria commonly in scope are Security, Availability, Confidentiality and Privacy.
  • ✓Manufacturing: supply chain platforms, connected-equipment monitoring and logistics services. Criteria commonly in scope are Security and Availability.
  • ✓Retail: e-commerce platforms, order management systems and customer data platforms. Criteria commonly in scope are Security, Confidentiality, Privacy and Processing Integrity.

SaaS, Technology and Software Providers

For SaaS companies, the examination centers on the production environment that hosts customer data. Testing in a typical SaaS engagement covers:

  • ✓Identity and access management for the cloud console, databases and administrative tools
  • ✓Code review and deployment controls within the CI/CD pipeline
  • ✓Logging, alerting and incident response
  • ✓Encryption key management
  • ✓Security awareness training and background checks for employees

A multi-tenant architecture adds further test points. The auditor examines logical segregation of customer data and the controls that stop one tenant from reaching another tenant’s records.

Newer technologies also fall within scope. If a SaaS product contains AI components that process customer data, the system description names those components and documents the data flows to model providers. The auditor tests the controls governing them in the same way as any other in-scope system element.

Financial Services and Fintech

Fintech examinations typically add Processing Integrity to Security and Confidentiality. Payment processing, lending decisions, account aggregation and reconciliation are the activities most often brought into scope.

Traditional financial services organizations, including asset managers, insurance administrators and benefits platforms, also request SOC 2 reports from the technology vendors that serve them.

Healthcare Technology

Telehealth platforms, practice management systems, revenue cycle services and health data analytics firms handle protected health information on behalf of covered entities. A common US procurement sequence illustrates the demand: a hospital system asks a cloud software vendor to complete a security questionnaire and supply a SOC 2 Type II report before it signs a contract involving patient data.

Healthcare technology examinations frequently include Availability together with Confidentiality or Privacy.

Manufacturing and Retail Service Organizations

Manufacturers and retailers face SOC 2 requests when they act as service organizations to other businesses.

Manufacturing. A manufacturer that offers connected-equipment monitoring, supply chain visibility platforms or managed logistics services processes its customers’ operational data. Business customers request SOC 2 reports covering Security and Availability for those services. Third-party logistics providers that integrate with customer order systems receive comparable requests.

Retail. In the retail sector, SOC 2 is most relevant to e-commerce platform providers, order management systems, loyalty program operators and customer data platforms that hold consumer personal information for retail brands. These organizations frequently include Confidentiality or Privacy because consumer records are subject to state privacy laws.

Retail service providers that handle payment cards also undergo PCI DSS assessments. PCI DSS addresses cardholder data specifically, while SOC 2 addresses the broader control environment of the service. The two reports therefore serve different reviewers.

Typical SOC 2 scope by US sector
Sector Typical Service Organizations Criteria Commonly in Scope
Technology and software (SaaS) Cloud applications, platforms, managed IT services Security, Availability, Confidentiality
Financial services and fintech Payment processors, lending platforms, wealth technology Security, Processing Integrity, Confidentiality
Healthcare and healthcare technology Telehealth, practice management, revenue cycle vendors Security, Availability, Confidentiality, Privacy
Manufacturing Supply chain platforms, connected-equipment monitoring, logistics Security, Availability
Retail E-commerce platforms, order management, customer data platforms Security, Confidentiality, Privacy, Processing Integrity

SOC 2 Cost in USA

This section states the SOC 2 cost for organizations engaging CertPro for SOC 2 certification in USA. The fee statements below apply to CertPro’s independent examination performed by a Licensed CPA Firm.

FAQ

▶

What does a SOC 2 audit evaluate?

A SOC 2 audit evaluates an organization’s controls against the AICPA Trust Services Criteria: security, availability, processing integrity, confidentiality, and privacy. Security is required in every SOC 2 examination. The other four criteria are added when they are relevant to the services provided. CertPro, a Licensed CPA Firm, performs the examination and issues an independent opinion.
▶

Which industries in the USA ask vendors for SOC 2 reports?

In the USA, SOC 2 reports are frequently requested in major sectors including technology and software, financial services, healthcare, manufacturing, and retail. Any service organization that stores, processes, or transmits customer data for clients in these sectors can expect SOC 2 requests during vendor due diligence, contract renewals, or security reviews.
▶

Can a SOC 2 audit scope include controls related to CCPA, the SHIELD Act, or BIPA?

A SOC 2 report does not certify compliance with any statute. When the privacy or confidentiality criteria are in scope, the examination tests controls relevant to obligations under the California Consumer Privacy Act (CCPA), New York’s SHIELD Act, and the Illinois Biometric Information Privacy Act (BIPA). Legal compliance determinations remain a separate matter.
▶

What evidence does a SOC 2 Type II audit require?

A SOC 2 Type II audit requires evidence that controls operated effectively throughout the observation period, not only on a single date. Typical evidence includes access reviews, change management tickets, incident logs, vendor assessments, background checks, and system configurations. The auditor selects samples from each population and tests them against the documented control description.
▶

Is SOC 2 a certificate or a report?

SOC 2 is an attestation report, not a certificate. A licensed CPA firm issues an opinion on the organization’s system description and controls. A Type I report assesses control design at a specific date. A Type II report assesses design and operating effectiveness over a period. Distribution is typically restricted to customers and prospects under nondisclosure agreements.
▶

How often does a SOC 2 report need to be renewed?

SOC 2 reports do not expire on a fixed date, but customers generally expect a new Type II report each year covering a continuous period. Gaps between observation periods are often questioned in vendor reviews. Organizations maintain eligibility by operating controls continuously, retaining evidence, and remediating exceptions identified in the prior examination.
▶

How is SOC 2 different from ISO 27001 for US companies?

SOC 2 is an AICPA attestation report, while ISO 27001 is a certifiable management-system standard. The USA has no single comprehensive federal privacy law, so organizations reconcile state privacy laws with sector-specific federal rules such as HIPAA and GLBA. Mapping SOC 2 controls to ISO 27001 and these rules allows one evidence set to serve multiple frameworks.
▶

Why do US hospitals require a SOC 2 Type II report from software vendors?

A U.S. hospital system may require a cloud software vendor to complete a security questionnaire and provide a SOC 2 Type II report before signing a contract involving patient data. The Type II report gives the hospital independent evidence that the vendor’s controls operated effectively over time, rather than relying solely on self-reported questionnaire answers.

Get In Touch

have a question? let us get back to you.






Schedule A Meeting