Under active development Content is continuously updated and improved

CM-7 (02)Least Functionality | Prevent Program Execution

Moderate
High

>Control Description

Prevent program execution in accordance with [Selection (one or more): organization-defined policies, rules of behavior, and/or access agreements regarding software program usage and restrictions; rules authorizing the terms and conditions of software program usage].

>FedRAMP Baseline Requirements

Additional Requirements and Guidance

CM-7 (2) Guidance: This control refers to software deployment by CSP personnel into the production environment. The control requires a policy that states conditions for deploying software. This control shall be implemented in a technical manner on the information system to only allow programs to run that adhere to the policy (i.e. allow-listing). This control is not to be based off of strictly written policy on what is allowed or not allowed to run.

>Discussion

Prevention of program execution addresses organizational policies, rules of behavior, and/or access agreements that restrict software usage and the terms and conditions imposed by the developer or manufacturer, including software licensing and copyrights. Restrictions include prohibiting auto-execute features, restricting roles allowed to approve program execution, permitting or prohibiting specific software programs, or restricting the number of program instances executed at the same time.

>Assessment Interview Topics

Questions assessors commonly ask

Process & Governance:

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

Technical Implementation:

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

Evidence & Documentation:

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

Ask AI

Configure your API key to use AI features.