CM-6 Configuration Settings

Description

Configuration settings are the set of parameters that can be changed in hardware, software, or firmware components of the information system that affect the security posture and/or functionality of the system.

Information technology products for which security-related configuration settings can be defined include, for example:

1. mainframe computers,
2. servers (e.g., database, electronic mail, authentication, web, proxy, file, domain name),
3. workstations,
4. input/output devices (e.g., scanners, copiers, and printers),
5. network components (e.g., firewalls, routers, gateways, voice and data switches, wireless access points, network appliances, sensors),
6. operating systems,
7. middleware, and
8. applications.

Security-related parameters are those parameters impacting the security state of information systems including the parameters required to satisfy other security control requirements. Security-related parameters include, for example:

1. registry settings;
2. account, file, and directory permission settings; and
3. settings for functions, ports, protocols, services, and remote connections.

Organizations establish organization-wide configuration settings and subsequently derive specific settings for information systems. The established settings become part of the systems configuration baseline.

Common secure configurations (also referred to as security configuration checklists, lockdown and hardening guides, security reference guides, security technical implementation guides) provide recognized, standardized, and established benchmarks that stipulate secure configuration settings for specific information technology platforms/products and instructions for configuring those information system components to meet operational requirements.

Common secure configurations can be developed by a variety of organizations including, for example, information technology product developers, manufacturers, vendors, consortia, academia, industry, federal agencies, and other organizations in the public and private sectors. Common secure configurations include the United States Government Configuration Baseline (USGCB) which affects the implementation of CM-6 and other controls such as AC-19 and CM-7.

The Security Content Automation Protocol (SCAP) and the defined standards within the protocol (e.g., Common Configuration Enumeration) provide an effective method to uniquely identify, track, and control configuration settings.

OMB establishes federal policy on configuration requirements for federal information systems.

Applicability

The intended audience includes information resource owners and custodians; and pertains to information resources considered moderate or high impact.

Implementation

TAMU-CC shall:

1. Establish and document configuration settings for information technology products employed within the information system using security configuration procedure that reflect the most restrictive mode consistent with operational requirements, establishes mandatory configuration settings for information technology products employed within the information system. TAMU-CC adopts baseline security configuration checklists that meet or exceed published industry best practice sources (e.g., Center for Internet Security Benchmarks [CIS Benchmarks], NIST National Checklist Program [NCP]) when available, or locally develops security configuration checklists otherwise, for all System-owned or -managed major and mission-critical information systems, and systems processing confidential information;
2. Implement the configuration settings, configures the security settings of information technology products to the most restrictive mode consistent with operational requirements;
3. Identify, document, and approve any deviations from established configuration settings for information system components based on security configuration procedure, documents the configuration settings; and
4. Monitor and control change to the configuration settings in accordance with organizational policies and procedures. Enforces the configuration settings in all components of the information system.

Revision History

Last Updated: February 21, 2025

Previous Versions:

• June 29, 2023
• May 31, 2022
• March 25, 2021
• September 16, 2019