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

8.6 Role-Based Access Control

NIST PIV and digital identity SP 800-116 Rev. 1 against SP 800-116
All changes in this version
removed 8 PACS Use Cases part of 8

Title changed

Before · SP 800-116

Role-Based Access Control

After · SP 800-116 Rev. 1

Role-Based Access Control

Control changed

Before · SP 800-116

Authorization of identities enrolled in a PACS is viewed as separate from cardholder authentication. PACS may grant access only to cardholders who were enrolled and authorized in the PACS Server prior to presenting their credentials for authentication, or they may make on- the-fly access control decisions by evaluating the information on presented PIV Cards against a set of access control rules. Because PIV Cards contain only a few mandatory subject attributes (just the Agency Code, Employee Affiliation, and Investigation Status Indicator) that may be used for role-based access control, role or group permissions will usually be derived from off- card information. In the future, standardized role information may be available on-card, especially for Emergency Response Officials or Continuity of Operations (COOP) procedures. Recommendation: Because having on-card role and permission information would raise difficult challenges concerning update and revocation, PACS permissions should generally be stored in a PACS facilities-based component, such as a panel or controller database.

After · SP 800-116 Rev. 1

Authorization of identities enrolled in a PACS is viewed as separate from cardholder authentication. PACS may grant access only to cardholders who were enrolled and authorized in the PACS Server prior to presenting their credentials for authentication, or they may make on- the-fly access control decisions by evaluating the information on presented PIV Cards against a set of access control rules. Because PIV Cards contain only a few mandatory subject attributes (just the Agency Code, Employee Affiliation, and Investigation Status Indicator) that may be used for role-based access control, role or group permissions will usually be derived from off- card information. In the future, standardized role information may be available on-card, especially for Emergency Response Officials or Continuity of Operations (COOP) procedures. Recommendation: Because having on-card role and permission information would raise difficult challenges concerning update and revocation, PACS permissions should generally be stored in a PACS facilities-based component, such as a panel or controller database.