Control: definition for compliance teams | Compliance Automation Tools

[Skip to content](#main)
[Compliance Automation Tools](https://complianceautomationtools.com/)
- [Index](https://complianceautomationtools.com/)
- [Platforms](https://complianceautomationtools.com/platforms/)
- [Frameworks](https://complianceautomationtools.com/frameworks/)
- [Best for](https://complianceautomationtools.com/best-for/)
- [Guides](https://complianceautomationtools.com/guides/)
- [Glossary](https://complianceautomationtools.com/glossary/)
- [Method](https://complianceautomationtools.com/method/)

Menu
- [Index](https://complianceautomationtools.com/)
- [Platforms](https://complianceautomationtools.com/platforms/)
- [Frameworks](https://complianceautomationtools.com/frameworks/)
- [Best for](https://complianceautomationtools.com/best-for/)
- [Guides](https://complianceautomationtools.com/guides/)
- [Glossary](https://complianceautomationtools.com/glossary/)
- [Method](https://complianceautomationtools.com/method/)

Glossary, read 12 Nov 2026

# Control, defined with a sourced example

**In short:** Control: a policy, procedure, technical setting or practice that modifies risk and that an assessor can test. In a compliance platform each control is one record with an owner, linked tests and evidence, and mappings to every framework requirement it satisfies, so one control can serve several frameworks.

[All terms](https://complianceautomationtools.com/glossary/) | [The guides](https://complianceautomationtools.com/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](https://complianceautomationtools.com/glossary/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.

## Related terms

- [Control owner](https://complianceautomationtools.com/glossary/control-owner/)
- [Common controls framework](https://complianceautomationtools.com/glossary/common-controls-framework/)
- [Control mapping](https://complianceautomationtools.com/glossary/control-mapping/)

## Sources

- [csrc.nist.gov/glossary/term/control](https://csrc.nist.gov/glossary/term/control), read 12 Nov 2026
- [raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json](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
Last reviewed 12 Nov 2026.

- [Matrix](https://complianceautomationtools.com/matrix/)
- [Integrations](https://complianceautomationtools.com/integrations/)
- [Datasets](https://complianceautomationtools.com/datasets/)
- [News](https://complianceautomationtools.com/news/)
- [FAQ](https://complianceautomationtools.com/faq/)
- [About](https://complianceautomationtools.com/about/)
- [Editorial policy](https://complianceautomationtools.com/editorial-policy/)
- [Corrections](https://complianceautomationtools.com/corrections/)
- [Contact](https://complianceautomationtools.com/contact/)
- [Privacy](https://complianceautomationtools.com/privacy/)
- [Terms](https://complianceautomationtools.com/terms/)
- [llms.txt](https://complianceautomationtools.com/llms.txt)
- [llms-full.txt](https://complianceautomationtools.com/llms-full.txt)
- [Sitemap](https://complianceautomationtools.com/sitemap.xml)
- [RSS](https://complianceautomationtools.com/feed.xml)

Compliance Automation Tools. Every platform fact carries its source and read date. Read 13 Nov 2026.

Canonical: https://complianceautomationtools.com/glossary/control/
