← SA-8

Minimization

LOW MODERATE HIGH
1 Overlay 4 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

Implement the privacy principle of minimization using [processes].

Discussion (NIST Supplemental Guidance)

The principle of minimization states that organizations should only process personally identifiable information that is directly relevant and necessary to accomplish an authorized purpose and should only maintain personally identifiable information for as long as is necessary to accomplish the purpose. Organizations have processes in place, consistent with applicable laws and policies, to implement the principle of minimization.

Implementation Guidance

Engineering Interpretation

Original engineering commentary written for this explorer — not NIST source text and not authoritative guidance.

No engineering interpretation has been authored for SA-8(33) yet. This section is architected to receive it — see the Requirements and Assessment sections above for the authoritative NIST source content in the meantime.

Assessment

NIST SP 800-53A REV 5.2.0

Assessment Objectives

  1. processes that implement the privacy principle of minimization are defined;
  2. the privacy principle of minimization is implemented using <SA-08(33)_ODP processes>.

Examine

[SELECT FROM: System and services acquisition policy; system and services acquisition procedures; personally identifiable information processing policy; procedures addressing the minimization of personally identifiable information in system design; system design documentation; system configuration settings and associated documentation; change control records; information security and privacy requirements and specifications for the system; system security and privacy architecture; system security plan; privacy plan; privacy impact assessment; privacy risk assessment documentation; other relevant documents or records].

Interview

[SELECT FROM: Organizational personnel with information security and privacy responsibilities; organizational personnel with system specification, design, development, implementation, and modification responsibilities; system developers].

Test

[SELECT FROM: Organizational processes for applying the privacy design principle of minimization in system specification, design, development, implementation, and modification; mechanisms supporting the application of the security design principle of sufficient documentation in system specification, design, development, implementation, and modification; mechanisms that enforce security and privacy policy; organizational processes for managing change configuration; mechanisms supporting configuration control].

Overlays

Showing the OT/ICS overlay for the parent control SA-8 — see the SA-8(33) entries within each baseline below.

OT/ICS Overlay SP 800-82r3

NIST SP 800-82r3 Appendix F, Table 22. Blank baseline means the control/control enhancement is not selected in that initial OT baseline.

LOW

  • Base control: Included (matches standard baseline)

MODERATE

  • Base control: Included (matches standard baseline)

HIGH

  • Base control: Included (matches standard baseline)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for SA-8(33). This section is architected to display, per product: STIG ID, Finding ID, Severity, Title, Description, Check, Fix, CCI, and NIST control mapping — but nothing is populated here until a real DISA STIG/CCI dataset is ingested.

Learn more about STIG/CCI integration →

Evidence

Potential Evidence — Derived

Categorized from the SP 800-53A "Examine"/"Test" artifact list above by keyword — not an authoritative NIST evidence list.

Policy

  • System and services acquisition policy
  • personally identifiable information processing policy
  • system security plan
  • privacy plan

Configuration

  • system design documentation
  • system configuration settings and associated documentation
  • system security and privacy architecture

Testing

  • Organizational processes for applying the privacy design principle of minimization in system specification, design, development, implementation, and modification
  • mechanisms supporting the application of the security design principle of sufficient documentation in system specification, design, development, implementation, and modification
  • mechanisms that enforce security and privacy policy
  • organizational processes for managing change configuration
  • mechanisms supporting configuration control

Other Records

  • system and services acquisition procedures
  • procedures addressing the minimization of personally identifiable information in system design
  • change control records
  • information security and privacy requirements and specifications for the system
  • privacy impact assessment
  • privacy risk assessment documentation
  • other relevant documents or records