A regular problem in many fortune 1000 organizations is that policies that govern change are very complicated. The rules for changing complex application stacks can be carved up horizontally and vertically in addition to across multiple different applications. Changes can be made by various stakeholders ranging from Server administrators, Application owners, Network managers, Database Ddministrators, and many more. Each stakeholder likely has his own rules for change, what can change, and when. With all this complexity and the overlapping of various change policies, it is little wonder that companies often suffer from changes being made "out of process". Change prevention at the end-point is the key to dealing with this level of complexity. Physically enforcing blackout windows, preventing any change from happening during those periods, virtually eliminates the possibility of someone unknowingly installing something on the wrong server at the wrong time. Once a change enforcement technology is deployed, only changes that are approved -- within specific change windows -- and even to specific files, can be made. Why rely on human nature and written or verbal policy to control behavior? End-point change control cuts through the complications. by
Bill Lapcevic, Alliances
Bill@solidcore.com | 
