Review vendor SOC 2 reports against contract promises, offline
Find auditor exceptions and compare incident-notification terms with a fictional SOC 2 report and MSA. Includes separate practice files and a verification checklist.
A vendor report and a signed MSA answer different questions. The report describes controls and testing over a period; the contract records commitments to a customer. Compare the exact statements before treating either one as proof that the other has been satisfied.
The question this exercise answers
The useful question is whether the operating procedure and the contractual promise agree on the event, recipient, deadline, and starting point. A 72-hour disclosure rule after confirmation is not the same as a 24-hour notification rule after discovery or suspicion.
Download the fictional records
Download the separate records as a ZIP, extract it, and import the TXT files individually:
- Record 1: Cloudscale technologies inc. — soc 2 type ii examination report
- Record 2: Enterprise cloud services master agreement (excerpt)
The combined reading copy remains available. Import either the separate files or the combined copy, not both. Question Scope selects whole imported Documents; headings such as “Record 1” inside a single TXT file cannot be selected independently. Use the separate files for this walkthrough.
These are fictional teaching records, including any future dates, statute references, and professional opinions. They are not authentic filings, standards, advice, or a benchmark of OriginPage’s answer quality.
Locate the passages before asking for a comparison
Create a separate Workspace for the exercise. Import the individual records and wait for each to show Ready. Open Document details and check the retained text. These TXT exercises do not demonstrate PDF layout extraction or OCR.
In Search, try Exception Noted in Exact phrase mode, without adding quotation marks. Search each relevant file as well as the collection. If wording differs, try Keyword or Hybrid and inspect the returned passages. A missing result is a reason to check wording, scope, and extraction—not proof of absence.
Choose the records allowed to answer
Select record-01.txt and record-02.txt in a Workspace named CloudScale review. In Chat, use Answering from → Selected documents. Search filters and Question Scope are separate controls; setting one does not set the other.
Try this focused question:
Compare the incident-notification rule in the SOC 2 description with MSA section 9.2. Give each deadline, its trigger and recipient, with supporting passages. Keep auditor observations separate from management statements.
Check the result against the source
The following is an editorial answer key derived from the fictional files, not a recorded model response. Answers may omit relevant evidence; use Direct Search and the original records to complete the review.
| Check | What the fictional records say | Follow-up |
|---|---|---|
| Incident notification | Record 1 allows customer disclosure within 72 hours of root-cause confirmation; record 2 requires written notice within 24 hours of discovery or suspicion. | Ask the vendor how it meets the earlier contractual trigger. |
| Restore testing | Record 1 reports two failures in 25 sampled snapshots; record 2 warrants that all production backups are validated and recoverable. | Request evidence of remediation and clarify the population and period. |
| Liability wording | Record 2, section 12.4, excludes listed matters from the section 12.1 cap. | Have counsel assess the full agreement and applicable law. |
Do not turn two failures in a sample into a measured failure rate for all backups. Nor does an exception automatically establish a contract breach. Preserve sampling dates, management response, and later remediation evidence. The control identifiers in this teaching pack are illustrative, not an authoritative mapping of Trust Services Criteria.
Keep a review record
Record the control or promise, report period, quoted exception, contract clause, evidence requested, owner, and review status. Keep a finding open until the vendor supplies the missing evidence.
When a question needs two sides, open evidence from both. Check the filename, retained passage, surrounding conditions, and the original source where layout matters. A saved citation supports inspection; it does not certify the source or the conclusion.
Processing and professional boundaries
Review the report’s distribution restrictions and your NDA before import or sharing. A local workflow avoids sending these files to an AI provider, but does not itself satisfy an NDA, access-control policy, or assurance requirement.
OriginPage processes supported documents locally during ordinary use. The privacy statement explains the limits, including Windows services and local account access. For formats and supported behavior, see what OriginPage supports.
Method
Revised September 21, 2026. The two screenshots show the downloadable fictional records imported separately into the locally installed OriginPage 1.0.35.0 candidate. We ran the stated Exact phrase query, opened the shown source passage, and applied the illustrated Selected documents scope. These captures demonstrate retrieval and scope, not generated-answer quality or professional validation. The source inspector clips part of the main pane in this candidate; the screenshots preserve that observed layout. The exercise findings are an editorial answer key, not a captured model response.