Control implementation
In the previous chapter, we learned about configuration management, which refers to setting initial baselines for systems and tools so that it becomes easier for the relevant teams to install and manage that software. In this context, configuration management is a preventative control that ensures that no unapproved software and services are installed on the user’s laptop. The same goes for change management as well, where changes have been made to production system code that need to be tested in a test environment before being rolled out to all the users.
On a related note, it is important to ensure that once these changes have been set, the control is also tested in a non-production environment so that any errors from the test environment do not carry over to the production environment and affect a large set of systems or users in terms of unapproved changes. The ideal way to set up this test environment is to have it reflect the production environment...
