logo

IT Asset Configuration Management

nested configuration management hierachyMany businesses see having knowledge of their physical assets as a vital step in preventing theft, and external auditors are required to confirm that the items listed in a company's books are in fact real, albeit perhaps a sample check.
 
IT asset configuration management is different. The Infrastructure Manager is responsible for ensuring that the servers, their firewalls, and their load balancers all have the identical configurations, with the exception of their identities (names). If a new server system is built, it should match the configuration of the existing servers, unless there is a specific reason to make it different.
 
One of the most significant dangers to IT operations is the presence of an unchecked "Keys of the Kingdom" technical specialist who disregards the fundamentals of configuration management. This is especially true in situations when the individual is skilled at covering up their errors.

During my very first project as a Service Management Analyst, I discovered that the only reason an application worked was because two copies of a database were being synchronised on the server every weekday through the original developer's laptop. This was the only way the programme could function. One day, for reasons unrelated to the situation, the developer was denied access to the server. After a few days of their absence, it was noticed that this database appeared to have an inconsistent corruption: the results depended on which copy of the database was being accessed. In addition to rewriting the code so that only one copy was required, an automated checking of the deployment catalogue was set up to detect any repetition. This utilised an in-built service of the server software.
In order to track down technician and engineer errors, I developed a variety of automations that "sweep up" and report irregularities. One automation was designed to report all production code modifications. This was done so that the modifications could be recorded in the configuration management database. The implementation of this automation had an immediate and positive impact: privileged access users started adopting the change control protocols as they did not want to be "caught out" by the automated report.

Next Steps
For more information on how we can help you with improving IT asset configuration management, and reducing transition risks, please write to robert@esm.solutions