← All posts
SOC 2 for customer-hosted softwareself-hosted software SOC 2SOC 2 scope

SOC 2 for Customer-Hosted Software: What Can Your Report Cover?

If customers host your software, map the vendor services you operate, the customer-run environment, and the exact SOC 2 report boundary before making a claim.

A customer-hosted product has a vendor service boundary and a customer-run deployment boundary.
A customer-hosted product has a vendor service boundary and a customer-run deployment boundary.

If customers host your software, a SOC 2 report can address a service your company actually operates, but it does not automatically cover each customer’s installation. First identify the service: perhaps a release and update channel, vendor-run support, a hosted control plane, or managed work inside a customer environment. Then separate the systems and controls your team runs from the customer’s runtime. Ask the buyer what assurance it needs and a CPA firm whether the proposed service boundary fits an examination.

Does SOC 2 apply to customer-hosted software?

The delivery model alone does not answer that question. The AICPA SOC 2 Description Criteria ask management to identify the services under examination, the commitments made to customers, and the infrastructure, software, people, procedures, and data used to provide them. The CPA firm examines the defined system and controls. A package name or public repository is not a complete system description.

Suppose your company sells an application that customers deploy in their own cloud accounts. Your team may still build and publish updates, operate an activation service, receive support logs, or access a customer’s environment during an incident. Those activities may matter to a buyer and to a proposed SOC 2 scope. Whether they form the service for a particular engagement is a question to work through with the CPA firm. If your company only hands over a package and does no ongoing service work, ask the buyer which assurance would answer its concern before promising a SOC 2 report.

Draw the vendor and customer boundary

Make one map for a representative customer installation. Start with the product’s actual behavior and the contract, not a standard control list.

Work or system Vendor question Customer question
Build and release Who can change source, approve a build, and publish an artifact? Who decides when to install it and verifies the source of the update?
Runtime Does the vendor operate any service or agent that the installation calls? Who runs the compute, storage, network, backups, and monitoring?
Access Can vendor staff or a hosted component reach customer data or an admin path? Who grants and removes local user and administrator access?
Support What logs, exports, credentials, or remote access can support receive? Who authorizes access and limits what leaves the environment?
Incidents Which vendor events trigger customer notice or an update? Who detects, contains, and recovers the customer deployment?

The answers may vary by contract or deployment tier. A vendor-managed installation in a customer’s cloud account has a different boundary from a package the customer runs alone. A hosted activation service can have its own data and availability path even when the main application is local. List each mode, then decide with the CPA firm which mode the proposed report will describe. The general SOC 2 scope guide explains how to record inclusions and exclusions.

Write a report claim a buyer can check

Use wording that names the service and avoids implying coverage of customer operations. For example:

Our proposed SOC 2 scope covers our software release and customer support services, including the systems and people we use to build, publish, and support updates. Customers operate their own application instances, infrastructure, identity, backups, and monitoring. The final scope and report wording are subject to the CPA firm’s examination.

That is a planning example, not a claim about an issued report. Once you have a report, quote its actual system description and report period instead of reusing a draft. If a buyer asks whether its deployment is covered, point to the description and any excluded systems. Identify any complementary user entity controls the report lists, then use the contract or customer guidance to explain other installation duties. The AICPA says a description should identify the examined services clearly and should not imply that controls operate when they do not. A report about vendor services cannot prove that a particular customer configured, patched, or monitored its own installation.

The AICPA criteria distinguish complementary user entity controls from other customer responsibilities. A customer action is a complementary control only when the vendor’s system design assumes it and needs it, together with vendor controls, to meet the vendor’s commitments or system requirements. Do not label every installation task a complementary control. The customer control guide shows how to review those dependencies.

Keep evidence for the service you actually run

For each proposed vendor control, name its owner, action, timing, and source record. A release control might need the approved change, source revision, build result, artifact identity, publication record, and exception handling. Support access might need the customer’s authorization, the access grant and removal, the case record, and any data transfer. A hosted component needs evidence from its actual runtime and providers. Keep a dated record of the population so a CPA firm can select and test items for the agreed period.

Do not turn a policy or future plan into a statement that a control operated. A customer can ask for a security questionnaire or release-process evidence while your report is still planned; answer with current facts and flag gaps. The guide for a first customer SOC 2 request covers that response.

FileGRC is a Git-native GRC workspace for SOC 2 work. JSON holds structured records, Markdown holds long-form work, and Git supplies the change history. Your team can map the vendor service, customer dependencies, control owners, and evidence references so an agent can inspect gaps and prepare answers from current records. Starter records are proposals, not compliance claims. Source control, CI, identity, support, cloud, and customer systems operate the controls and produce source evidence; FileGRC organizes the program work. The independent CPA firm performs the examination and decides whether the evidence is sufficient.

Open source · MIT

Run your SOC 2 program as files in Git.

Keep policies, controls, work, and evidence indexes in a repository your team and agents can inspect. Add optional FileGRC Autopilot email and Slack reminders to keep work moving.

Frequently asked questions

Can a customer-hosted software vendor get a SOC 2 report?

Possibly. A CPA firm can examine a defined service organization system and its controls. A vendor should identify the services it operates, such as a managed update channel, support, or a hosted component, and agree with the CPA firm on a meaningful scope. The report does not automatically cover every customer installation.

Does the vendor's SOC 2 report cover our self-hosted deployment?

Read the report's system description. It identifies the services and controls examined. A report on the vendor's release or support service does not by itself examine the infrastructure, identity, configuration, monitoring, and operations that your team runs for its own installation.

Can a software package itself get a SOC 2 report?

A SOC 2 report addresses controls over a described service organization system, not a package or source repository by itself. Ask which vendor service and controls the report describes and what remains with the customer.

Are all customer responsibilities complementary user entity controls?

No. The AICPA distinguishes complementary user entity controls that the service organization's control design depends on from other user responsibilities. Management and the CPA firm should review which customer actions belong in the system description.

What should a vendor show a buyer before its first SOC 2 report?

Show the actual delivery model, a written responsibility split, current security and release practices, source-backed answers, and an honest report plan. Do not call proposed controls or a planned report completed work.