CM-7(8)—Least Functionality | Binary or Machine Executable Code

IL5

IL6

>Control Description

(a) Prohibit the use of binary or machine-executable code from sources with limited or no warranty or without the provision of source code; and (b) Allow exceptions only for compelling mission or operational requirements and with the approval of the authorizing official.

>DoD Impact Level Requirements

No specific parameter values or requirements for this impact level.

>Discussion

Binary or machine executable code applies to all sources of binary or machine-executable code, including commercial software and firmware and open-source software. Organizations assess software products without accompanying source code or from sources with limited or no warranty for potential security impacts. The assessments address the fact that software products without the provision of source code may be difficult to review, repair, or extend.

In addition, there may be no owners to make such repairs on behalf of organizations. If open-source software is used, the assessments address the fact that there is no warranty, the open-source software could contain back doors or malware, and there may be no support available.

>Related Controls

SA-5

SA-22

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

•What formal policies and procedures govern the implementation of CM-7(8) (Binary Or Machine Executable Code)?
•Who are the designated roles responsible for implementing, maintaining, and monitoring CM-7(8)?
•How frequently is the CM-7(8) policy reviewed and updated, and what triggers policy changes?
•What training or awareness programs ensure personnel understand their responsibilities related to CM-7(8)?

Technical Implementation:

•Describe the specific technical mechanisms or controls used to enforce CM-7(8) requirements.
•What automated tools, systems, or technologies are deployed to implement CM-7(8)?
•How is CM-7(8) integrated into your system architecture and overall security posture?
•What configuration settings, parameters, or technical specifications enforce CM-7(8) requirements?

Evidence & Documentation:

•What documentation demonstrates the complete implementation of CM-7(8)?
•What audit logs, records, reports, or monitoring data validate CM-7(8) compliance?
•Can you provide evidence of periodic reviews, assessments, or testing of CM-7(8) effectiveness?
•What artifacts would you present during a FedRAMP assessment to demonstrate CM-7(8) compliance?

Ask AI

Configure your API key to use AI features.