Secure software installation isn't enough on its own — configuration enforcement ensures applications and devices are consistently locked down to meet security and operational requirements.
Configuration Enforcement
Just because we install a program doesn't mean that it's configured securely. So another thing we want to do is have some sort of configuration enforcement.
Programs usually have a lot of options to them — configurations, things that we can go in and control. Some configurations are more secure than other configurations. Sometimes they're deployed insecurely and we need to secure them. Other times they're deployed too securely and we need some functionality. So we need to control these configurations. There is some way that we want to control or enforce the configurations of certain programs.
This really is one of the main reasons for mobile device management, or MDM. Mobile device management allows us to have some sort of software or some sort of service that allows us to configure and control the configurations of these mobile devices.
There are several options to enforce these configurations. One example of this is group policy. Group policy, we largely use it to configure Windows machines, but it also can deploy other changes to other software that's installed on those Windows machines. Sometimes that requires some third-party downloads or some third-party installations, but we can still control certain aspects of the machine and certain software on the machine through group policy. There are other software solutions that will help us manage this as well.
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 →