About this interactive
The lesson says the two terms overlap and are often confused, and then separates them.
Configuration management is about settings. You capture a system's approved settings as a baseline, keep that record current, and audit systems to check their settings still match it. Security+ calls this establishing, deploying and maintaining secure baselines.
Change management is about the act of changing something in the organization. It runs every change through the same process: a request, an owner, a plan, an evaluation (often by a change advisory board), implementation, monitoring and closure. The lesson's example is rolling out new software on a server: that is not configuring the server, it is a change, so it goes through change management.
The overlap is real: configuration management has its own change control, and every change alters some configuration. The rest of the module mostly talks about change management. A quick test for each card: is it about knowing and checking what the settings are, or about taking a change through the process?
About TechKnowSurge
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →