BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

9.3 Business and Functional Requirements

NIST PIV and digital identity SP 800-116
All changes in this version
first version loaded 9 Migration Strategy part of 9

Title

Business and Functional Requirements

Control

Each agency has a unique operational environment. Agencies vary in size, organizational structure, and geographic topography. Moreover, their PACS requirements are driven by their mission and by risk and vulnerability assessment. The result is today’s PACS environment, which is site-specific and hardly interoperable with other agency implementations. HSPD-12 adds two requirements to these implementations, namely enhanced security and government-wide use of common identification. In other words, an identity credential issued by agency A must be usable by agency B. Note that HSPD-12 leaves the authorization decision to individual agencies. Section 6 provides characteristics of a future PIV-enabled PACS system that substantiates the goals of HSPD-12. Agencies are encouraged to use these characteristics to determine business and functional requirements applicable to their environment.