Where should safeguards for an electronic CUI file be reflected?

• A. In the metadata or header of the file.
• B. In the file name only
• C. In a separate document
• D. Not required

Answer: (A)

Safeguards for an electronic CUI file should be reflected in the file’s metadata or header because these markings travel with the file as it moves across systems and users. By encoding the required handling instructions, classification, and access controls directly in the metadata or header, any system or person that encounters the file can see how to protect it without needing to look elsewhere. Relying on the file name is insufficient since names can be changed, lost, or become ambiguous and don’t carry the full protection requirements. A separate document is easy to misplace or fail to accompany the file, breaking the guardrails. Embedding safeguards in the metadata or header supports consistent, automated enforcement of CUI protections across platforms.