Scope
Objectives
Standard
Definitions
Sanctions
Additional Contacts
History
Policy information: IT-12 Configuration Management (CM) Standard
About This Standard
Status: Effective July 9, 2024
Responsible University Office: University Information Policy Office
Responsible University Administrator: Office of the Vice President for Information Technology and Chief Information Officer
Policy Contact: University Information Security Office uiso@iu.edu
Scope
This standard supports Policy IT-12 (Security of Information Technology Resources) and applies to all Indiana University information technology resources, regardless of whether those resources are managed by the university or provisioned from third parties on behalf of the university, and to all users of those resources regardless of affiliation.
Objectives
The key objectives of this standard are to ensure that:
- Baseline configurations and inventories of organizational IT resources are established and maintained throughout the respective system development life cycles; and
- Security configuration settings for information technology resources employed in organizational information systems are established and enforced.
Standard
The following tables detail baseline security controls for audit and accountability to be applied to a particular information technology resource based on its security categorization. Select controls as applicable. For example, all controls may not apply to every system component or technology, or to situations governed by specific regulations.
Control: | Baseline Configurations | ||
Required for: | High | Moderate | |
IU Implementation | Develop, document, and maintain a standard system build, known as a baseline configuration. Review and update the baseline configuration at least annually and when:
| ||
Notes |
| ||
NIST Cross Reference | CM-2 | ||
Control: | Impact Analysis | ||
Required for: | High | Moderate | |
IU Implementation | Prior to change implementation, analyze proposed changes to information technology resources to determine potential impacts. | ||
Notes | Changes to IT resources must be implemented in a test environment before implementation in the production environment. This allows units to look for security and operational impacts due to flaws, weaknesses, incompatibility, or intentional malice. Use of centrally provisioned, common IT infrastructure and services provided by UITS often fulfills many of these requirements. Check with the service owner for details. | ||
NIST Cross Reference | CM-4 | ||
Control: | Least Functionality | ||
Required for: | High | Moderate | |
IU Implementation | Configure systems for only the specific intended function. | ||
Notes | Only install necessary software and services.
Use of centrally provisioned, common IT infrastructure and services provided by UITS often fulfills many of these requirements. Check with the service owner for details. | ||
NIST Cross Reference | CM-7 | ||
Control: | System Inventory | ||
Required for: | High | Moderate | |
IU Implementation | Maintain an inventory of systems. | ||
Notes | Inventories should accurately reflect the systems, including all identifiable IT asset components, such as hardware, software, and firmware. For example, inventories may include system name, system owners, software version numbers, hardware specifications, software license information, security categorization, and network components. Inventories may also include date of receipt, cost, model, serial number, manufacturer, supplier information, component type, and physical location. Use of centrally provisioned, common IT infrastructure and services provided by UITS often fulfills many of these requirements. Check with the service owner for details. | ||
NIST Cross Reference | CM-8 | ||
Definitions
Standard – Standards (like procedures) support policy by further describing specific implementation details (i.e., the "how"). A standard can be thought of as an extension of policy that articulates the rules, mechanisms, technical or procedural requirements, or specifications to be used in carrying out/complying with policy. Standards, along with procedures, promote a consistent approach to following policy. Standards make policies more practically meaningful and effective. Standards are definitional and clarifying in nature, specifying the minimums necessary to meet policy objectives. Because standards directly support policies, compliance with standards is nonoptional and failure to follow standards may result in sanctions imposed by the appropriate university office.
Sanctions
Indiana University will handle reports of misuse and abuse of information and information technology resources in accordance with existing policies and procedures issued by appropriate authorities. Depending on the individual and circumstances involved, this could include the Office of Human Resources, Vice Provost or Vice Chancellor of Faculties (or campus equivalent), Dean of Students (or campus equivalent), Office of the Vice President and General Counsel, and/or appropriate law enforcement agencies. See Policy IT-02 (Misuse and Abuse of Information Technology Resources) for more details.
Failure to comply with Indiana University information technology policies may result in sanctions relating to the individual's use of information technology resources (such as suspension or termination of access, or removal of online material); the individual's employment (up to and including immediate termination of employment in accordance with applicable university policy); the individual's studies within the university (such as student discipline in accordance with applicable university policy); civil or criminal liability; or any combination of these.
Additional Contacts
| Subject | Contact | Phone | |
|---|---|---|---|
| Questions about the standard | University Information Security Office | 812-855-UISO (8476) |
History
Initial draft – February 12, 2022
Revised – April 7, 2023
Effective – July 9, 2024