Configuration Management is a systematic approach to identifying, controlling, and maintaining configuration items throughout their lifecycle. This method helps organizations manage systems efficiently and control changes effectively.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Configuration management keeps a product's technical attributes consistent, traceable and controllably changeable throughout its life cycle.
Configuration management became a formal discipline in product and software development. Susan Katz documented core concepts in a 1991 NIST report; NIST SP 800-128 applies them to security-focused system configuration.
Keep a dependable map for each system: its baseline, approved changes and current state must line up at all times.
Identities, versions, baselines and changes are controlled and traceable.
Inventory, change control and deviation review protect systems from unnoticed drift.
Configuration management provides transparency and prevents unplanned changes from undermining system integrity.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.