All right, let's move on to domain six, which is configuration management. And, of course, configuration management is so very essential to protecting the stability of the system and an environment. So we look at the basic security requirements here, and the first basic requirement essentially says,
establish and maintain a baseline configuration.
So the first piece of that essentially saying Look, we've gotta have security baselines, thes minimum acceptable configurations, and we've gotta maintain them. We've got to control changes to them.
Ah, we've got to make sure that the stability of the environment is not affected by any sort of unauthorized
mechanism or installation or whatever that might be. We also got to keep track of the inventory of our information systems. Of course, you know that helps us figure out what we have. What we need are things intact. Have they been modified?
And that's include hardware, software firmware as well as any of the documents
that would indicate processes. And this is gonna be that we have to keep them throughout the entire system. Development Life's like,
Ah, we're going to establish in four security configuration settings for our tea products. So it's it's enoughto have it's not enough just to have a baseline configuration. We're gonna make sure that that's well documented and that it's enforced. We can't leave these decisions up to the user and hope they make good decisions.
So we're gonna lock down those systems
and restrict their ability to make changes as well.
Now, for the derived security requirements here, we're gonna the very first bullet point track review, approve, disapprove and audit changes that is change control, right? That is change management. And that's, you know, not too bad a definition for configuration management
in change management course, apart of configuration management.
But basically nothing happens on the fly. We don't install a quick fix or a patch or this or the other. We follow the process always, and in second Bullet Point analyzed the security impact of a change prior to implementation. Absolutely.
And you know, that really comes from the point in time when we look at
hey, will this change work? Oh, is it secure? Well, we can't think that way anymore. Does it work securely or does not work at all? All right, define document approved and enforce physical and technical or logical access.
Any sort of restrictions that are associated with that system.
To find them, document approved them, so make sure it's formalized. But then, most importantly, enforcing a policy is only as good as its enforcement.
Employ the principle of least functionality. So we're gonna configure that system to provide Onley essential capabilities. If you've ever been in a computer that's at a kiosk or maybe young Ah, hotel lobby and you go and you try to access this function or another and it's not available because the admin has removed
a certain piece of functionality.
That's what we have to do to make sure that files that shouldn't be accessed our access to our functions turned on our all for disabled. We're gonna lock down that system and, along with that, the next bullet point. Restrict disabled, prevent use of nonessential programs. That's hardening system
that's added to that system, whether it's hardware or software or firm lier. Any service is protocols, whatever that adds, and ads and ants to what we call the attack surface. So the more of these functions you add, you want having a huge attack surface.
Well, when you're not using those functions, disabled them turn them off, removed them,
and that will lessen your tax surface to the smallest area. It could be
all right. The next bullet points 2nd 1 from the bottom. We're gonna either use blacklisting or white listing, Blacklisting says. Allow everything except what's on the blacklist. White listing says block everything except what's allowed on the white list.
So basically, use a combination of those
to deny access to your resource is and then the last bullet point control and monitor user and spelt software.
You know, it really depends on in your environment whether or not you're even gonna allow users to install software. But environments that do you need an accurate log and an auditing mechanism to make sure that our users are installing only business related software and also software
that wouldn't have any short of negatives.
Impact on the on the system.
All right, so that's configuration management. Extremely important to keep a system operating per its baseline settings and create a stable, reliable system