Skip to content
Compliance Automation Tools

Home / Glossary / Common controls framework

Glossary, read 12 Nov 2026

Common controls framework, defined with a sourced example

All termsThe guides

Common controls framework in practice

The reason to build one is duplication. Vanta's article says organizations often pursue frameworks one at a time, which leads to duplicated control documentation, redundant evidence collection and fragmented programs. A common controls framework replaces that with a control-first model that Vanta calls "test once, comply with many."

Do not confuse it with NIST's term "common control," which means a control inherited by multiple systems or programs (SP 800-37 Rev. 2, from OMB Circular A-130). Hyperproof's guide, updated 17 December 2025, uses the compliance sense: a set of validated controls that forms the basis for compliance with a variety of frameworks. The practical guide is one control set for many frameworks.

Example: Vanta's article says the baseline rule is to take the strictest criterion in each compliance area, so that meeting it satisfies less restrictive frameworks by default. That is a vendor's description, and the strictest criterion still has to be checked against each framework's own wording.

Sources

  1. vanta.com/resources/common-controls-framework, read 12 Nov 2026
  2. csrc.nist.gov/glossary/term/common_control, read 12 Nov 2026
  3. hyperproof.io/resource/common-controls-framework, read 12 Nov 2026

Last reviewed 12 Nov 2026.