Because configuration management is a critical component of your overall security, you should consider how you can best implement it to give your site the maximum protection at the archive level.

No matter how stringently you manage the change history of your source files and the relationships between them, the effort is wasted if unauthorized users can—inadvertently or maliciously—damage or delete files.

In a network environment, you can take steps to improve your overall security:

Integrity Lifecycle Manager uses client/server architecture to provide enhanced security in managing the software development process. The client/server structure improves security because all project information can be kept on a single server and only accessed from a common client application. Client access is controlled through ACL settings and users cannot directly access or modify any files on the Integrity Lifecycle Manager server.

Client/server architecture allows you to directly control the type of access granted to users. For example, you can set up a structure:

In this example, files can only be manipulated by the Integrity Lifecycle Manager server and the administrator. Other users are not permitted to manipulate files under the control of Integrity Lifecycle Manager.