Secure Software and Systems Needs for Configuration Management
Applying strong configuration management practices protects software integrity, prevents unauthorized modifications, and maintains stable deployment environments. NO M OMO
2 slides · 1 min read · Domain 8
Clearly, secure software cannot be
The ability to measure
developed and kept secure if at any point in and track the state of its development pipeline its specifications,
configurations provides the
designs, or source code can be tampered necessary information and with, or its builds and controls scripts, control to proactively manage configuration data, and other process risks and ensure the security, information are modified to allow for the substitution of foreign, untrustworthy code.
safety, and resilience of an organization's operations.
Much of the evolution of software development methodologies reflects the
In other domains, systems such as constant balance between conflicting integrated identity management and access priorities and belief structures. It also control, next-generation firewalls, and reflects the growing realization that systems security information and event management have become far too complex to remain systems have been explored. These unmanaged.
technologies support similar functions that configuration management (CM) and configuration control (CC) provide for software, metadata, operational process knowledge, procedural know-how, and even database content.