Implementation Guide › Planning Your Enterprise Implementation › Preparing an Implementation Plan

Preparing an Implementation Plan

While defining the implementation plan, check repeatedly that the plan's goals come from the security policy. The new security controls should be phased-in gradually to provide users a period of adjustment.

• Define specific goals based on the security plan

  Define the goals to help you implement the security plan.

• Define a pilot group of users as a prototype for implementing CA ControlMinder.

  Test all CA ControlMinder features on the pilot group before protecting entities outside of the group. Testing with the pilot group can help you learn how to protect the rest of the organization.

• Decide what to protect

  CA ControlMinder protects business data, jobs, and users in the pilot group

• Define a method for rolling out the security control

  Consider how to phase-in the new security controls with minimum disruption of current work patterns. Consider a period of only auditing access, and not restricting access, for various resources and classes. The resulting audit records show which users tend to require access to the resources.

Note: For more information about Warning mode (audit-only mode), see the Endpoint Administration Guide for UNIX and the Endpoint Administration Guide for Windows.