Sample CA ACF2 for z/VM Implementation Schedule

Planning the Implementation › Preparing the Implementation Schedule › Sample CA ACF2 for z/VM Implementation Schedule

Sample CA ACF2 for z/VM Implementation Schedule

The following is an example of an implementation schedule.

Week	Task
Week 0	Order CA ACF2 for z/VM after preliminary requirements and product review.
Week 1	Appoint a Security Administrator.
	Establish the Implementation Team.
	Hold an organizational meeting.
	Distribute CA ACF2 for z/VM documentation to team members.
	Suggest that the SA and systems programmers attend an CA ACF2 for z/VM training class. (This is recommended, but not mandatory.)
Week 2	Establish a general timetable and responsibility assignments.
	Identify existing government, corporate, industry, and local security policies, goals, and objectives.
	Identify local conditions or operating environment, such as naming conventions.
	Identify system users and user groups.
Week 3	Make preliminary option selections.
	Refine the schedule and responsibility assignments.
	Perform a test install of CA ACF2 for z/VM on a second level VM test system.
Week 4	Finalize schedule and responsibilities.
	Refine option selections.
	Perform initial training, if needed(administrators or computer operators).
	Prepare for a test IPL of target system write or tailor any local exits, check option selections, select sample users, jobs, rules, or prepare test procedures.
Week 5	Test IPL (in LOG mode or RULE mode).
	Review results, including report outputs.
	Modify option selections as necessary.
	Modify procedures and operator instructions as necessary.
	Test backup and recovery procedures.
	Prepare to install CA ACF2 for z/VM on production systems.
	Handle additional training and announcements.
Week 6	Install CA ACF2 for z/VM on first level VM production system (LOG mode or ABORT mode on selective rule sets using RULE mode).
	Establish initial users.
	Write, compile, and store initial rules.
	Closely monitor reports.
	Retest backup and recovery procedures.
Weeks 7‑12	Readjust system options and exits if necessary.
	Complete user definitions.
	Complete rules.
	Continue to closely monitor reports.
	Test maintenance procedures.
	Migrate remaining portions of the system to WARN mode and finally to ABORT mode.

You can phase in the CA ACF2 for z/VM modes (QUIET, LOG, WARN, RULE, and ABORT) on a rule set basis with the RULE setting in the MODE operand of the OPTS VMO record. See the “Converting to Full Security,” chapter for details. The above schedule provides guidelines for the timing of these implementation activities. This timing can vary significantly, depending on the circumstances at your site. Many of these activities can occur concurrently or can proceed at different rates independently. For example, the technical installation and IPL of the target system can occur before or after the less technical activities listed in Weeks 4 and 5. Detailed information on some of these topics, such as what should be done to perform the install or during the first IPL, is presented in later chapters of this guide.