Write each control once: one statement, one owner, one test, one evidence type | 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/)

Guide, read 13 Nov 2026

# Write each control once: one statement, one owner, one test, one evidence type

**The short answer:** A house control set works when each control has one statement, one owner, one test and one evidence type. NIST SP 800-53 Rev. 5 holds 1,196 entries in 20 families, 182 of them withdrawn, and CIS Controls v8.1 has 18 controls, so copy their structure, not their size.

[Framework Coverage Matrix](https://complianceautomationtools.com/matrix/) | [All guides](https://complianceautomationtools.com/guides/)

## One statement format for every control

A house control set is the list you write once and test every cycle. Each row must read the same way, or nobody can test it the same way. The format that survives audits is short: who does what, on what scope, how often.

Use this template: "[Role] [verb] [object] [for scope] [at frequency]." Example: "The IT lead removes access for departed staff from all production systems within 1 business day of the HR termination date." The statement names a role, an action, a scope and a clock. A tester can check it without asking what you meant.

NIST SP 800-53 Rev. 5 is a good model for structure, not for length. Each control in its OSCAL catalog (release 5.2.0, file last modified 22 Oct 2026) has a statement split into lettered parts, a discussion, and related controls. Enhancements get their own IDs, for example AC-2(1). By my count of that file the catalog lists 1,196 controls and enhancements, of which 182 are marked withdrawn, across 20 families.

Keep your own discussion text out of the statement. Put the why in a separate field. If a statement needs the word "and" twice, it is two controls.

Add four more fields beside the statement: owner role, test, evidence type and review date. A statement without those four is a policy sentence, not a control. Write the test in the same sitting as the statement, since a statement you cannot test is usually too vague to keep. Then read each row aloud to the owner and ask what they would do on Monday to prove it.

## One owner, one test, one evidence type

Three limits do most of the work. Each control gets one owner, one test and one evidence type. If you cannot name all three, the control is not ready to enter the set.

NIST SP 800-53A Rev. 5 (January 2022) gives the vocabulary. An assessment procedure uses three methods: examine, interview and test. It looks at four kinds of assessment object: specifications (documents), mechanisms (hardware or software safeguards), activities (actions that involve people) and individuals. Its objectives are numbered by control and part, for example AC-17a.[01], so a finding traces back to one line of the control.

Borrow that split. A control that depends on a document gets a specification as its evidence type. A control that depends on a system setting gets a mechanism. A control that depends on a recurring human step gets an activity. Mixing them in one control is how a control ends up with three owners and a test nobody runs. See [evidence that survives an audit](https://complianceautomationtools.com/guides/evidence-that-survives-an-audit/) for what each type has to show.

| Field | Rule | Weak example | Written once |
|---|---|---|---|
| Statement | Role, verb, object, scope, frequency | Access is managed appropriately | The IT lead removes departed staff from all production systems within 1 business day |
| Owner | One named role, not a team | Security team | Head of IT Operations |
| Test | One pass or fail check, same each cycle | Review access | Compare the HR leaver list to active accounts; zero mismatches older than 1 business day |
| Evidence type | One of: specification, mechanism, activity | Screenshots, tickets and a policy | Mechanism: the exported account list with timestamp |
| Frequency | A number and a unit | Regularly | Weekly |

## Naming and numbering that survives reorganizations

Pick the ID scheme before you write control 1. Use a short family code and a sequence number: ACC-01, ACC-02, LOG-01. Never encode a framework clause in the ID, because clauses change and your IDs must not. Mapping to frameworks is a separate table, covered in [one control set for many frameworks](https://complianceautomationtools.com/guides/one-control-set-for-many-frameworks/).

NIST uses the same idea. Rev. 5 IDs are a two-letter family code and a number (AC-2, AU-6), and enhancements append a bracketed number. CIS Controls v8.1, which the Center for Internet Security describes on its page as adding a Governance security function, has 18 numbered controls, each with a short stated aim. A flat, short list is easy to remember and easy to cite in a ticket.

Name each control with a verb phrase a manager would say aloud: "Remove leaver access", not "Logical access deprovisioning procedure". Never reuse a retired ID for a new control. A reused ID makes last year's evidence look like this year's.

## How many controls is too many

There is no standard number. The Secure Controls Framework says on its download page that it carries more than 1,500 controls in 34 domains, and that is a catalog built to map to over 200 frameworks, not a set one team tests every quarter. NIST SP 800-53 Rev. 5 has 1,014 active entries after the withdrawn ones are removed. Both are libraries you draw from.

My working rule, from running six frameworks on one set: the set is too big when the owners cannot name their own controls from memory, or when a quarter's tests do not finish inside the quarter. For a company of 100 to 500 staff that usually lands between 100 and 250 testable statements. Treat that as an experience range, not a source.

Three checks keep the count honest. First, merge two controls that share an owner, a test and an evidence source. Second, split a control that has two tests. Third, count tests per owner: more than about 25 per person and they will stop doing them properly. These are judgment calls, so write the reason in the change log.

## Retiring controls without losing the audit trail

A control leaves the set for one of three reasons: the risk is gone, a better control replaced it, or two controls merged. Record which. NIST marks the same event in its catalog with a withdrawn status, and the Rev. 5 file still lists 182 withdrawn entries.

Do the same. Never delete a retired control. Change its status to retired, record the date, the approver and the replacement ID, and stop scheduling tests. Keep its evidence for the period your longest framework requires.

Review the set on a fixed date each year and after any scope change. At the review, ask each owner one question: what would you stop testing if nobody objected. Those answers are your retirement list.

## Where this shows up in the index

14 of 16 tools have a record of custom framework support among the facts read on 12 Nov 2026; see the [coverage criterion](https://complianceautomationtools.com/method/coverage/) for how it is scored.

## Sources

- [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
- [csrc.nist.gov/pubs/sp/800/53/r5/upd1/final](https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final), read 12 Nov 2026
- [csrc.nist.gov/pubs/sp/800/53/a/r5/final](https://csrc.nist.gov/pubs/sp/800/53/a/r5/final), read 12 Nov 2026
- [nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53Ar5.pdf](https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53Ar5.pdf), read 12 Nov 2026
- [cisecurity.org/controls/cis-controls-list](https://www.cisecurity.org/controls/cis-controls-list), read 12 Nov 2026
- [securecontrolsframework.com/free-content/scf-download](https://securecontrolsframework.com/free-content/scf-download), read 12 Nov 2026
Last reviewed 13 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/guides/writing-a-common-control-framework/
