188405 Resource 183011 183122 183122 1194049592150 1194049761082 Controlled Change Policy Technical Enforcement: a Must Have

Change policy can be simplified via end-point change control

<p>A regular problem in many fortune 1000 organizations is that <strong>policies that govern change are very complicated</strong>.&nbsp; </p><p>The rules for changing complex application stacks can be <strong>carved up horizontally and vertically</strong> in addition to across multiple different applications.&nbsp; </p><p>Changes can be made by various stakeholders ranging from Server administrators, Application owners, Network managers, Database Ddministrators, and many more.&nbsp; Each stakeholder likely has his own rules for change, what can change, and when.&nbsp; With all this complexity and the overlapping of various change policies, it is little wonder that companies often suffer from changes being made &quot;<strong>out of process</strong>&quot;.</p><p>Change prevention at the end-point is the key to dealing with this level of complexity.&nbsp; Physically enforcing blackout windows, preventing any change from happening during those periods, <strong>virtually eliminates the possibility of someone unknowingly installing something on the wrong server at the wrong time</strong>.&nbsp; Once a change enforcement technology is deployed, only changes that are approved -- within specific change windows -- and even to specific files, can be made.&nbsp; Why rely on human nature and written or verbal policy to control behavior?&nbsp;<strong> End-point change control cuts through the complications.</strong></p><p>by<br /><strong>Bill Lapcevic, Alliances<br /></strong><a href="mailto:Bill@solidcore.com"><strong><u>Bill@solidcore.com</u></strong></a></p> 10 application/xml false change policy Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727) 127.0.0.1 127.0.0.1 erinswanson false true false false true 183020 false false true false false false true 183011 blog blogsite/SolidCore/web