- details at the file level. You’ll need this to implement SCM in a manner compliant with your company’s security model.
- Make sure hardware, OS and DBMS security mechanisms are in place prior to attempting further controls for SCM. Work with your security organization to make policy changes if necessary.
- Be sure to secure application runtime environments for production and critical QA testing for better segregation of roles and responsibilities and controlling and limiting changes.
- Work out procedures with “Those With Infinite Access” (the system administrators), such as an approval based change control mechanism for operating system/runtime environment changes.
CCM tools do not usually attempt to manage OS security and runtime environments, nor should they be expected to because of the complexity and the rapidly evolving nature of Windows security functions. And so, OS security is a critical part of achieving effective SCM on the distributed platforms. Thanks to Asad Shaikh of ABN AMRO, N.A. for helpful discussion.
Sean Blanton is Director of Consulting for Catalyst Systems Corporation. Sean has been with Catalyst for 6 years as a distributed platforms change and configuration management consultant and as a developer, trainer and product contributor for Openmake. He has a Ph.D. in Physics from the University of Chicago and a B.S. from Columbia University.