Skip to content
Compliance Automation Tools

Home / Glossary / Control

Glossary, read 12 Nov 2026

Control, defined with a sourced example

All termsThe guides

Control in practice

NIST's glossary defines a control as a measure that is modifying risk, and adds that controls include any process, policy, device, practice or other action that modifies risk. The same glossary points to "security control" and "privacy control" in SP 800-53 and SP 800-37. A control is what you operate. A requirement is what a framework asks of you.

Compliance automation tools manage the control, not the requirement. You write the control once, attach tests and evidence to it, name an owner, and map it to the requirements of each framework in scope. That is how a common controls framework cuts duplicate work, and it is why the control record needs a stable ID that survives framework updates.

Example: NIST's SP 800-53 Rev. 5 catalog, in the OSCAL file version 5.2.0 last modified 22 October 2026, groups its controls into 20 families (AC, AU, CA, CM and so on). By our count of that file it holds 324 base controls and 1,196 controls once enhancements are included.

Sources

  1. csrc.nist.gov/glossary/term/control, read 12 Nov 2026
  2. raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json, read 12 Nov 2026

Last reviewed 12 Nov 2026.