The IA Process - Information Assurance Architecture - page 62

table 3.7 iA 2 F Views: inpu t Guidance

IA 2 F Views Details

People Roles (governance, management, operations,

users)

Policy Internal policy that reflects compliance

requirements and enterprise mission

Business process Documents, owners, practitioners, users; see ECF

Systems and applications Location, function, owner, custodian, O&M,

documentation, vendor, product, version, release,
patch

Data/information Location, producer, consumer, owner,

classification

Infrastructure Physical, technical, mechanisms, services

Internal to the organization Mission, policy, standards, procedures

External to the organization Compliance requirements, industry standards

3.3.4 Identify Inputs to the IA 2 (Influences

and Dependencies)

3.3.4.1 Define What You Need to Know

This phase in the IA 2 Process identifies the inputs necessary to generate an IA
architecture. Inputs may include formal documentation, interviews with person-
nel, or other artifacts and actions from outside the organization. Some artifacts and
actions may not be direct input with direct relevance to the IA 2 ; however, they may
have inluence on how to proceed with the IA 2 . Dependencies are those inputs that
the IA 2 must have to produce quality results. Table 3.7 presents input guidance;
Table 3.8 continues the example IA 2 Process.

3.3.5 Discovery of As-Is (Current Organizational Posture)
3.3.5.1 Document the Current State

The articulation of intent, the definition of environment and scope, and the enu-
meration of required inputs, influences, and dependencies are all scope parameters
for the as-is discovery process. Discovery is the process of gathering documents,
interviewing personnel, and other activity with respect to obtaining details about
the current state of the organization within scope. Expect the discovery process to
produce additional insight and modifications to environment, scope, and inputs.