← AC-4
AC-4(12) AC · Access Control

Data Type Identifiers

LOW MODERATE HIGH
1 Overlay 0 Related Controls
Graph
Export ▾

Requirements NIST SOURCE

When transferring information between different security domains, use [data type identifiers] to validate data essential for information flow decisions.

Discussion (NIST Supplemental Guidance)

Data type identifiers include filenames, file types, file signatures or tokens, and multiple internal file signatures or tokens. Systems only allow transfer of data that is compliant with data type format specifications. Identification and validation of data types is based on defined specifications associated with each allowed data format. The filename and number alone are not used for data type identification. Content is validated syntactically and semantically against its specification to ensure that it is the proper data type.

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 AC-4(12) 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. data type identifiers to be used to validate data essential for information flow decisions are defined;
  2. when transferring information between different security domains, <AC-04(12)_ODP data type identifiers> are used to validate data essential for information flow decisions.

Examine

[SELECT FROM: Access control policy; information flow control policies; procedures addressing information flow enforcement; system design documentation; system configuration settings and associated documentation; list of data type identifiers; system audit records; system security plan; other relevant documents or records].

Interview

[SELECT FROM: System/network administrators; organizational personnel with information security responsibilities; system developers].

Test

[SELECT FROM: Mechanisms implementing information flow enforcement policy].

Overlays

Showing the OT/ICS overlay for the parent control AC-4 — see the AC-4(12) 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

Not applicable at this tier.

MODERATE

  • Base control: Included (matches standard baseline)

HIGH

  • Base control: Included (matches standard baseline)
  • Included: (4)

STIGs & CCIs

No STIG checks or CCI mappings are currently loaded for AC-4(12). 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

  • Access control policy
  • information flow control policies
  • system security plan

Configuration

  • system design documentation
  • system configuration settings and associated documentation

Testing

  • Mechanisms implementing information flow enforcement policy

Other Records

  • procedures addressing information flow enforcement
  • list of data type identifiers
  • system audit records
  • other relevant documents or records