Knowledge is Power
BARE METAL CYBERKnowledge is Power

Sitewide Search

Search Bare Metal Cyber

Search courses, individual lessons, wiki entries, books, podcasts, magazine articles, Daily Cyber News, and Darwin.

NIST SP 800-171 CUI Protection Center

03.14.08 — Information Management and Retention

Read the official CUI requirement and assessment content, then use the separately labeled Bare Metal Cyber perspective to connect it to implementation, evidence, and sustained operation.

1Source controls
4Assessment objectives
3Assessment methods

03.14 — System and Information Integrity · NIST SP 800-171 Revision 3

Active
Official NIST requirement content

Security requirement

Manage and retain CUI within the system and CUI output from the system in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.

Official NIST discussion

Discussion

Federal agencies consider data retention requirements for nonfederal organizations. Retaining CUI on nonfederal systems after contracts or agreements have concluded increases the attack surface for those systems and the risk of the information being compromised. NARA provides federal policy and guidance on records retention and schedules.

Bare Metal Cyber interpretation

Implementation perspective

Treat Information Management and Retention as a CUI protection outcome that must be reflected in the system boundary, documented implementation, operational behavior, and assessment evidence. Pay particular attention to flaw remediation, malicious-code protection, monitoring, integrity, and trustworthy handling of CUI.

  1. Confirm the requirement is in scope for the CUI system components, services, users, and external connections being assessed.
  2. Resolve every organization-defined parameter through an approved governance and tailoring process.
  3. Map each clause of the requirement to an accountable owner, implementation mechanism, and evidence source.
  4. Verify that inherited and shared implementations are supported by current provider evidence and responsibility boundaries.
  5. Collect evidence during normal operation and review changes, exceptions, and deficiencies on a risk-based cadence.

Questions to ask

  • Which CUI assets, data flows, users, and services are protected by this requirement?
  • Which portions are implemented locally, inherited, shared, or not applicable, and what evidence supports that determination?
  • Do the system security plan, deployed configuration, operating process, and assessment evidence tell the same story?
  • What change, incident, or threshold should trigger reassessment?

Evidence and validation

  • patch and remediation records
  • malware protection configuration
  • monitoring alerts and response records
  • integrity validation and exception reports

Common failure patterns

  • patch compliance hiding unsupported assets
  • alerts generated without response ownership
  • exceptions that never expire
  • integrity monitoring excluding critical configurations
Official NIST SP 800-171A content

Assessment objectives and methods

Assessment objectives (4)
  1. SR-03.14.8.

    CUI within the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.

  2. SR-03.14.8.

    CUI within the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.

  3. SR-03.14.8.

    CUI output from the system is managed in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.

  4. SR-03.14.8.

    CUI output from the system is retained in accordance with applicable laws, Executive Orders, directives, regulations, policies, standards, guidelines, and operational requirements.

Examine

  • system and information integrity policy and procedures
  • laws, Executive Orders, directives, policies, regulations, standards, and operational requirements applicable to information management and retention
  • records retention and disposition policy
  • records retention and disposition procedures
  • media protection policy
  • media protection procedures
  • audit findings
  • system security plan
  • other relevant documents or records

Interview

  • personnel with information and records management, retention, and disposition responsibilities
  • personnel with information security responsibilities
  • system administrators

Test

  • processes for information management, retention, and disposition
  • mechanisms for supporting or implementing information management, retention, and disposition
Official source-control relationships

Source NIST SP 800-53 controls

These controls are referenced by the official SP 800-171 Rev. 3 OSCAL record. Open the corresponding control pages for complete control text, enhancements, D3FEND mappings, and related learning.

Source controlSI-12Open SP 800-53 control →
Source record

Authoritative sources

Bare Metal Cyber is an independent educational publisher and is not affiliated with or endorsed by NIST. The official publications, the responsible federal agency, and the governing contract or agreement determine applicability, tailoring, assessment depth, and required implementation.