SOC 2 report
A US audit firm's report on a service provider's controls against AICPA criteria; cyber underwriters read it to assess an insured software vendor or a critical supplier the insured depends on.
A SOC 2 (System and Organization Controls 2) report is the report in which a US certified public accounting firm gives its opinion on a service provider's controls, measured against the Trust Services Criteria of the American Institute of Certified Public Accountants (AICPA). The criteria cover security, which is always in scope, plus any of availability, processing integrity, confidentiality and privacy. A Type I report describes the controls and judges their design at a single date. A Type II tests how they operated over a period, often six to twelve months, and lists the exceptions found. For an underwriter, only Type II shows that a control actually ran. The report is not a certification: there is no score and no pass mark, and the opinion can be qualified. It has to be read in at least four places. The period covered first, with the bridge letter that fills the gap up to the quote date. Then the exceptions. Then the complementary user entity controls, where the provider writes down what it leaves to the customer, MFA on customer accounts for instance. Last, the subservice organizations carved out of scope, often the hosting provider. The cyber market uses it in two situations. When the insured is a software-as-a-service vendor, the underwriter asks for its SOC 2 as first-rank evidence, stronger than a signed questionnaire. When the insured depends on a critical provider, the provider's report sheds light on the contingent business interruption exposure. The caveat lies in the method: the auditor samples controls the provider described itself. The software supply chain compromises at SolarWinds in 2020 and Kaseya in 2021 were a reminder that a booby-trapped update slips under that kind of control.
Textbook case, made-up figures: a payroll software-as-a-service vendor with 40 million euros in revenue attaches its SOC 2 Type II report. The period runs from January to September; the quote happens the following March, with a bridge letter. The auditor noted two exceptions: 3 of 25 sampled accounts still had access a month after the employee left, and a scheduled restore test never took place. The underwriter sends a question on access reviews and makes evidence of a restore test a subjectivity before inception.
SOC 2, SOC 2 Type II report, SOC 2 Type 1, System and Organization Controls 2
Follow the research
One letter a week. First, the week's underwriting note, when one is published: a dated, argued decision, signed by Paul Bernardski. Then what the observatory published on cyber risk, political risk and insurance. No account, no tracking.
No spam, one-click unsubscribe, no data ever sold.