Who can you send your SOC 2 report to? Restricted use, NDAs and the SOC 3 option
Updated
You can send it to customers, prospective customers and the auditors who serve them, and you should not post it publicly. A SOC 2 report is a restricted use report: the accounting firm Withum says it is intended for the service organization's management, customers and prospective customers. No source fetched for this page says the AICPA requires an NDA, so the NDA is your own practice. If you want something anyone can download, that is a SOC 3 report.
What "restricted use" means, in three firms' words
The restriction is written into the report itself. Near the end of the auditor's opinion there is a paragraph that names who the report is for. Read that paragraph in your own report first; it is the wording that applies to you. Three accounting firms describe it this way:
| Source | Who the report is for | What it says about the public |
|---|---|---|
| Withum (23 Jul 2019, no named author) | "Intended for the service organization's management, customers, and prospective customers" | SOC 2 is restricted use; a SOC 3 is "freely distributed to the public" |
| Sensiba (Jeffrey R. Stark, 26 Oct 2023) | Quotes opinion wording that the report is "intended solely for the information and use of" the service organization and named parties: user entities, business partners, practitioners, prospective users and regulators with sufficient knowledge | "Not suitable for public distribution" |
| UHY (URL dated September 2022, no byline) | External distribution is "generally restricted to current and prospective customers", business partners and the CPAs who serve them | Should not be made available for general use or posted on the company website |
All three firms sell SOC examinations (Withum) (Sensiba) (UHY). Withum's page is from 2019 and UHY's shows no date outside its URL, which is why three are shown side by side. They agree on the core: the report goes to people who use or are evaluating your service and to the professionals who work for them, and it stays off the open web. UHY adds that restricted does not mean hard to get: the intended readers should be able to obtain it without a struggle.
The phrase "with sufficient knowledge" matters too. The report assumes a reader who understands the service and how controls work. If you are on the receiving side, the order to read it in is in how to read a SOC 2 report.
The NDA is your practice, not the AICPA's rule
Many companies send the report only under a non-disclosure agreement, and buyers often assume that is a SOC 2 rule. The sources fetched here do not support that:
- SOC2Auditors.org (Peter Korpak, updated 21 October 2026) writes that companies commonly share the report through a request process, sometimes under an NDA, and that "the AICPA's restricted-use designation does not itself require every recipient to sign one" (SOC2Auditors.org). It is a directory of audit firms, not an audit firm.
- UHY recommends that the staff who handle requests follow written criteria, which generally include a recipient certification and an NDA. It suggests a click-through agreement in place of paper-signed NDAs, and says to involve legal counsel (UHY).
- Sensiba's article does not mention NDAs at all.
So the restriction on who may use the report comes from the report, and the confidentiality terms come from you. There are good reasons to have terms: the report describes your systems, your vendors and any exceptions the auditor found. OneUptime, a vendor that sells a trust center product, puts the limit of the paper plainly: "The NDA alone is not a security control" (OneUptime).
A sharing routine for a small team
Three sources describe steps, and they overlap. SOC2Auditors.org lists three: check each recipient, watermark each copy with the recipient's name and the date, and keep a log of who received the report and when. UHY adds written criteria for the people who handle requests. OneUptime (Nawaz Dhandala, 4 August 2026) adds cautions. Put together:
- One way in. A request form, or one address such as security@. Sales should not attach the PDF to a first email.
- Check the requester. Is this a customer, a prospect in an open deal, or their auditor? OneUptime: "A prospect's email address alone does not establish authorization under the report owner's policy." Ask the account owner to confirm the person.
- Apply your terms. An existing contract with confidentiality terms, an NDA or click-through terms, whichever your written rule calls for.
- Send a marked copy. Recipient, company and date on each page. OneUptime notes that a watermark "can discourage casual redistribution, but it is not access control."
- Limit the access. A link limited to named people that expires, not an open folder. OneUptime: "Give access only to requested documents for a defined time."
- Write one log line. Who asked, who approved, which report, under what terms, the date sent. Keep the log free of copies of the report itself.
- Send the whole report. OneUptime warns against a shortened excerpt that removes the opinion, scope, exceptions or CUECs. A reader who gets half a report cannot do the review their own vendor process asks for.
None of the sources gives a number for how long access should last or how many requests to expect, and this page does not invent one. Pick a period you can keep and write it down.
The public option: a SOC 3 report
A SOC 3 report comes from the same examination and is written for anyone. Withum calls it "a general use report that is freely distributed to the public" and says it "cannot be generated without first executing the steps necessary to complete a SOC 2 examination". It leaves out the detail a reviewer wants: per Withum, no listing of controls and no details of the tests performed (Withum). UHY says it can be "used as a marketing document".
That is also its limit. SOC2Auditors.org says a SOC 3 does not replace the SOC 2 when a customer asks for one, because it lacks the controls, test results and complementary user entity controls that reviewers look for (SOC2Auditors.org). A customer running a vendor review will still request the full report. On cost, the same page says the fieldwork is shared when both are issued for the same system and period, reports that the audit firm Schellman describes the added cost as minimal, and advises: "Ask each firm to price the SOC 3 as its own line." No dollar figure appears in the fetched sources, so none is printed here. Questions to put to audit firms are in how to choose a SOC 2 auditor.
What to say publicly without a SOC 3
You can state facts about the report without publishing it. A second SOC2Auditors.org page (updated 2 November 2026) describes the common split: a public page shows the report type, the audit period, the CPA firm, the criteria in scope and the subprocessors, and the full report goes out on request (SOC2Auditors.org). UHY says a company can announce that it completed the examination and use the AICPA's SOC logo under its guidelines.
The free trust page generator writes that page, including the line on how to request the report, and the security overview one-pager puts the same facts in a file a sales contact can send before any NDA. For the logo, see SOC 2 logo rules; for wording that does not overclaim, see is SOC 2 a certification?.
Between reports: the bridge letter
A report covers a stated period, and requests arrive months after it ends. The usual answer is the last report plus a bridge letter, a letter from your management about the time since. Share it under the same routine as the report, and log it the same way. How old a report can get before buyers push back is in how long a SOC 2 report is valid.
What your own policy already says
Your report is confidential information about your company, so your data handling rules apply to it like any other document. Policyseed sells a kit, so read this as one example, not a requirement: the generated Data Classification and Handling Policy sets the terms for sharing confidential information outside the company, and an auditor can test your report sharing against it.
Confidential and Restricted information is shared externally only with a party under a signed agreement with confidentiality terms, through approved channels with encryption and access control, with the minimum content required, and with the information owner's approval; Restricted information additionally requires Security Owner approval unless it is being returned to the customer who owns it through Northwind. Public links, open shares and personal email are never used for these levels.
Data Classification and Handling Policy, item 4.7
External sharing. A person who needs to share Confidential or Restricted information externally raises a request naming the recipient, the agreement covering them, the content and the channel. The information owner approves Confidential sharing; the Security Owner additionally approves Restricted sharing. The approved channel is limited to named recipients, with expiring links where supported, and the request is retained as evidence.
Data Classification and Handling Policy, item 5.3
Read the full Data Classification and Handling Policy. Note what item 4.7 does to the NDA question: a company that adopts this text has chosen to share confidential documents only under a signed agreement with confidentiality terms. If you want to send the report on lighter terms, change the policy before you change the practice, because the written rule is what gets tested.
Frequently asked questions
- Is a SOC 2 report public?
- No. Three accounting firms fetched for this page say the same thing: Withum calls it a restricted use report, Sensiba writes that it is "by definition, a restricted use report" and "not suitable for public distribution", and UHY says it should not be made available for general use or posted on the company website. The public counterpart is a SOC 3 report, which the same firms describe as general use.
- Can a prospect get our SOC 2 report before signing a contract?
- Usually yes, on your terms. Withum's table lists prospective customers among the intended readers, UHY says external distribution is generally restricted to current and prospective customers, business partners and the CPAs who serve them, and the opinion wording Sensiba quotes names prospective users with sufficient knowledge. Read the restricted-use paragraph in your own report, then apply your own sharing terms: check who is asking, and use an NDA or click-through terms if that is your practice.
- Do we have to require an NDA before sending the report?
- No source fetched for this page says the AICPA requires one. SOC2Auditors.org, a directory site, writes that "the AICPA's restricted-use designation does not itself require every recipient to sign one". UHY, an accounting firm, still recommends one: its criteria for staff who handle requests include a recipient certification and a non-disclosure agreement, and it suggests a click-through agreement in place of paper signatures, with legal counsel consulted. So the NDA is your company's choice, and your customer contracts or your own data handling policy may already make it for you.
- Can our customer forward the report to their own auditor?
- The sources point to yes for the auditor, but none sets out a procedure. The opinion wording Sensiba quotes names practitioners among the specified parties, and UHY lists the CPAs providing services to customers and business partners. What decides it in practice is the wording in your report and the terms you shared it under, so say in those terms whether the recipient may pass the report to its auditors, and ask to be told when it does.
- Can we post just the auditor's opinion page on our website?
- None of the sources covers posting the opinion alone, so ask your CPA firm before doing it. Two points weigh against it. The restricted-use wording Sensiba quotes sits inside the auditor's report and speaks about the report as a whole. And OneUptime, a vendor, warns against a shortened excerpt that removes the opinion, scope, exceptions or CUECs, because a partial document can be read as the report. A sentence that states the report type, period, criteria and CPA firm, plus a way to request the report, says the same thing without publishing part of it.
- How much does a SOC 3 report add to the audit fee?
- This page prints no dollar figure, because none of the fetched sources gives one. SOC2Auditors.org says that when a SOC 3 is issued with a SOC 2 for the same system and period the fieldwork is shared, and that the audit firm Schellman describes the added cost as minimal; it advises asking each firm to price the SOC 3 as its own line so proposals can be compared. Withum notes that a SOC 3 cannot be produced without the SOC 2 examination work.
Policyseed provides governance policy templates and AI tailoring. It is not legal advice and not a compliance guarantee. Management adopts the policies; the CPA firm performs the SOC 2 examination.