Securing CA NSM Objects › How Security Management Is Implemented

How Security Management Is Implemented

The implementation of a security policy for a server is the result of planning, implementing, testing, evaluating, and adjusting. Understanding the implementation process, including why specific procedures are performed in a particular order, is critical to the success of your Security Management solution.

Security Management is implemented in the following phases:

• Phase 1--Review your Security Management Options and Client and Server Preferences, to ensure that needed components are available. Customize options to your site’s security requirements.
• Phase 2--Start Security Management daemons (service providers) in QUIET mode.
• Phase 3--Create security rules for users, user groups, access permissions, and asset groups in WARN mode and verify user access, adjusting rules based on results, then re‑execute the commit process. Consider any optional features you may need. For more information, see Optional Features.
• Phase 4--Customize Security Management options for FAIL mode production operations.

This chapter provides detailed information and points you to procedures that allow you to accomplish each of the phases of implementation.