Glossary, read 12 Nov 2026

# Risk assessment in a SOC 2 examination, defined with a sourced example

**The short answer:** A risk assessment is a systematic examination of risk using disciplined processes, methods and tools (NIST SP 800-30 Rev. 1, via CNSSI 4009). NIST SP 800-53 control RA-3 requires identifying threats and vulnerabilities, judging likelihood and magnitude of harm, documenting results, reviewing them, and updating them after significant system changes.

[All terms](https://soc2compliancesoftware.com/glossary/) | [Read the guides](https://soc2compliancesoftware.com/guides/)

## The definition of Risk assessment

SOC 2 expects a documented risk assessment that management performs on a recurring basis, with risks ranked, owners named and treatments chosen. The output feeds the control list: a risk with no control against it needs either a new control or a recorded decision to accept it. The assessment is the starting point for choosing which controls a company needs, and it has to be redone as the business changes.

Teams usually fail in one of two ways. They write a risk register once, in a spreadsheet, and never touch it again. Or they copy a template risk list for another industry, so nothing in it refers to their own product. The AICPA's 2026 reviewer alert names "identical risk assessments" across engagements as a warning sign at the audit firm level, and the same logic applies to a copied register.

An auditor reads the dates, the approver and the link between each risk and the controls that treat it. A risk assessment done in January that ignores the cloud migration finished in March will draw a question, since RA-3 itself says to update the assessment when the system or environment changes significantly.

## A sourced example

NIST SP 800-53 control RA-3 breaks the task into steps that read like an audit checklist: identify threats and vulnerabilities, determine "the likelihood and magnitude of harm", document results, review them, disseminate them, and "Update the risk assessment ... or when there are significant changes to the system". Each verb is something a reviewer can ask to see dated proof of. [NIST SP 800-53 Rev. 5 control catalog (OSCAL)](https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json), read 12 Nov 2026.

## Related terms

- [Gap analysis](https://soc2compliancesoftware.com/glossary/gap-analysis/)
- [Control activity](https://soc2compliancesoftware.com/glossary/control-activity/)
- [System description](https://soc2compliancesoftware.com/glossary/system-description/)
- [Management assertion](https://soc2compliancesoftware.com/glossary/management-assertion/)

## Sources

- [NIST SP 800-53 Rev. 5 control catalog (OSCAL)](https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json), read 12 Nov 2026
- [NIST CSRC glossary, risk assessment](https://csrc.nist.gov/glossary/term/risk_assessment), read 12 Nov 2026
- [Journal of Accountancy, AICPA guides peer reviewers to address SOC 2 risks](https://www.journalofaccountancy.com/issues/2026/may/aicpa-guides-peer-reviewers-to-address-soc-2-risks/), read 12 Nov 2026
Last reviewed 12 Nov 2026.

Canonical: https://soc2compliancesoftware.com/glossary/risk-assessment/
