The IA Framework - Information Assurance Architecture - page 37

prise locations, ranging from a couple/few to thousands. Each scenario brings a
different set of risks and IA requirements.

2.9.8 Train

Personnel need education and preparation for using the new solution to fulfill the
business objectives. Training occurs concurrently or immediately follows deploy-
ment. Training (including awareness, training, and education) includes manage-
ment, operations, and the user community. Part of the personnel preparation is
security awareness, training, and education.

2.9.9 Operate and Maintain

Architects, builders (see the Organizational Context Framework in chapter 11),
and project managers are the key players up through deployment. Concurrent with
deployment is a transition from building the solution to the operations and main-
tenance (O&M) of that solution. O&M is now the custodian of the solution and is
responsible for solution performance, service level agreements (SLAs), and security.
Aligning business requirements with technology is good practice for projects as
well as for the enterprise. Projects come and go, where the enterprise lives on. The
IA 2 LoS is an enterprise tool as well as a project tool. The enterprise use of IA 2 LoS is
to maintain an ongoing relationship between O&M and the business drivers behind
O&M. Business requirements will change over time, and there is need to periodi-
cally revisit operational constructs to see if they still align with valid business drivers.
If a tactical operation, service, or mechanism is not traceable to a business driver,
then that operational expense is no longer necessary. With no traceable business
justification for X, X is a wasted expense.

2.9.10 Retire

The final phase of ELCM is the retirement of the system. This includes knowing
when to retire the system, who the retirement affects, and how to retire (phase out
versus cut off). ). Knowing when to retire a system is problematic. If the business
driver goes away, there is no longer a need for the continuance of the solution. So,
elimination of the business driver is one motivation to retire a solution. However,
the reason for the existence of a system may be lost with personnel turnover. System
retirement is a useful context to convey one benefit of the IA 2 LoS.
Effective use of the IA 2 LoS aligns business drivers with the O&M of solutions.
The use of IA 2 LoS produces a traceability document that captures the details of the
business driver to O&M alignment. The IA 2 LoS document records and maintains
enterprise knowledge of the motivations behind the creation and operation of a