Implementation Considerations

This section contains the following topics:

Introduction

Planning and scheduling the security implementation can help set proper direction and keep the implementation on course.

It might also require cooperation and contribution from the other affected areas in the organization. Many organizations create a security implementation project team with individuals from:

Security Administration
Systems Software
Applications Software
Operations
Auditors
End users

Develop a Security Policy

The initial assignment of the security implementation project team might be to develop and recommend the security policy and objectives. The team is an ideal committee to develop this document, because the concerns of each area can be taken into account.

If the security policy or document of security objectives has already been developed, the implementation team can use this document as its mandate.

Construct a Flexible Schedule

The implementation team should draft a flexible schedule. If at all possible, avoid setting a final implementation date until the inventory and design phases are completed. Plan to take care of the emergency requirements first and then phase in the remainder of the organization.

It is not as important to put timeframes on each phase of the implementation plan as it is to be certain that the implementation attends to all requirements.

Create a task list showing all tasks that must be accomplished to implement security at your site. This allows you to determine which tasks must be done as part of a step‑by‑step procedure, and which are independent.