- The search and reporting features of a mainstream log platform carry this requirement; the work is confirming your in-scope sources are actually queryable in it.
- Verify that reduction and reporting read from the record without changing it — original records stay intact for later investigation.
3.3.6 — Audit reduction and reporting
3.3 Audit and Accountability · NIST SP 800-171 Rev. 2 · The heading label is this site's navigational shorthand; the official language is the statement below.
Provide audit record reduction and report generation to support on-demand analysis and reporting.
NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems ↗NIST SP 800-171A — Assessing Security Requirements for CUI ↗What this requirement is after
When a question needs answering — what did this account touch last Tuesday? — you must be able to filter mountains of log data down to the relevant records and produce a report on demand, without altering the originals.
Brilliant at the Basics practices that support this requirement
The campaign’s twenty practices are a priority list, not a control catalog, and none of them works this requirement’s substance directly. It still applies to you if it is in your contract’s scope: address it through your own implementation and the related artifacts below, and treat the absence of a mapping here as honesty, not permission to skip it.
Implementation considerations and evidence
- A generated on-demand report answering a concrete question from the records
- Platform documentation or configuration showing originals are preserved
Templates and worksheets with a mapped relationship
No artifact in the library names this requirement yet. The library index groups everything by category and practice.
Where this lands in Rev. 3
Sources and review status
| Primary sources | NIST SP 800-171 Rev. 2 — Protecting CUI in Nonfederal Systems · NIST SP 800-171A — Assessing Security Requirements for CUI |
|---|---|
| Review status | Pending NIST SME review |
| Content version | 1.0 |
| Updated |