Under active development Content is continuously updated and improved

CM-10(1)Software Usage Restrictions | Open-source Software

IL5
IL6

>Control Description

Establish the following restrictions on the use of open-source software: organization-defined restrictions.

>DoD Impact Level Requirements

No specific parameter values or requirements for this impact level.

>Discussion

Open-source software refers to software that is available in source code form. Certain software rights normally reserved for copyright holders are routinely provided under software license agreements that permit individuals to study, change, and improve the software. From a security perspective, the major advantage of open-source software is that it provides organizations with the ability to examine the source code.

In some cases, there is an online community associated with the software that inspects, tests, updates, and reports on issues found in software on an ongoing basis. However, remediating vulnerabilities in open-source software may be problematic. There may also be licensing issues associated with open-source software, including the constraints on derivative use of such software.

Open-source software that is available only in binary form may increase the level of risk in using such software.

>Related Controls

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

  • What formal policies and procedures govern the implementation of CM-10(1) (Open-Source Software)?
  • Who are the designated roles responsible for implementing, maintaining, and monitoring CM-10(1)?
  • How frequently is the CM-10(1) policy reviewed and updated, and what triggers policy changes?
  • What training or awareness programs ensure personnel understand their responsibilities related to CM-10(1)?

Technical Implementation:

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

Evidence & Documentation:

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

Ask AI

Configure your API key to use AI features.