Home / Glossary / Gap analysis
Glossary, read 12 Nov 2026
Gap analysis in a SOC 2 examination, defined with a sourced example
The definition of Gap analysis
Do it as a table with three columns: the requirement, the control in place, and the evidence that proves the control ran. Rows with an empty middle column are gaps. Rows with a control but no evidence are also gaps, and they are the more common kind, because most small companies do the work but keep no dated record.
People confuse a gap analysis with a risk assessment. The gap analysis starts from the criteria and asks whether you meet them. The risk assessment starts from your threats and asks what matters. SOC 2 expects both. A gap list copied from a template for another company will miss the odd things about your own system, such as a customer-facing data export job nobody owns.
Auditors do not require a gap analysis, but they read the one you made to learn how you scoped the system. Keep it, with the date, and keep the closing evidence beside each row. Keep the closing evidence in the same table, so each row shows the requirement, the control, the proof and the date the proof was captured, which also makes the later sample requests easy to answer.
A sourced example
NIST SP 800-53 states the AC-2 requirement to "Review accounts for compliance with account management requirements" on a set frequency. If a company has a written offboarding policy but never reviewed its accounts, the desired state is the quoted requirement, the current state is no review, and the gap is a missing recurring control plus no dated review record. NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026.
Related terms
Sources
- NIST SP 800-53 Rev. 5 control catalog (OSCAL), read 12 Nov 2026
- NIST CSRC glossary, gap analysis, read 12 Nov 2026
- Journal of Accountancy, AICPA guides peer reviewers to address SOC 2 risks, read 12 Nov 2026
Last reviewed 12 Nov 2026.