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

5.1 Cardholder Identification

NIST PIV and digital identity SP 800-116 Rev. 1 against SP 800-116
All changes in this version
removed 5 Limitations of Deployed Physical Access Control Systems part of 5

Title changed

Before · SP 800-116

Cardholder Identification

After · SP 800-116 Rev. 1

Cardholder Identification

Control changed

Before · SP 800-116

PACS that are currently deployed in Federal government facilities use cards with data formats that are often proprietary to the specific enterprise. Many of the installed PACS use an ID number based on a 26-bit standard, which is comprised of an 8-bit site code and a 16-bit unique card ID number with 2 bits assigned to parity (the parity bits add confidence that the data transmission has no errors). The 8-bit site code accommodates 256 unique sites and the 16-bit card ID number accommodates 65,536 unique users for that site. Larger ID numbers are used by some systems but they are not necessarily interoperable. A PACS based on the 26-bit format is deployed as a standalone solution at a dedicated site. Typically, these solutions are managed locally, and an individual with an access card for one site cannot use the same card at a second site and must obtain a second card. FIPS 201 changes this dynamic because the credential is issued through a separate process instead of as part of the PACS deployment. Deployed PACS need to be upgraded or re-provisioned to support at least a 14 decimal digit FASC-N Identifier.

After · SP 800-116 Rev. 1

PACS that are currently deployed in Federal government facilities use cards with data formats that are often proprietary to the specific enterprise. Many of the installed PACS use an ID number based on a 26-bit standard, which is comprised of an 8-bit site code and a 16-bit unique card ID number with 2 bits assigned to parity (the parity bits add confidence that the data transmission has no errors). The 8-bit site code accommodates 256 unique sites and the 16-bit card ID number accommodates 65,536 unique users for that site. Larger ID numbers are used by some systems but they are not necessarily interoperable. A PACS based on the 26-bit format is deployed as a standalone solution at a dedicated site. Typically, these solutions are managed locally, and an individual with an access card for one site cannot use the same card at a second site and must obtain a second card. FIPS 201 changes this dynamic because the credential is issued through a separate process instead of as part of the PACS deployment. Deployed PACS need to be upgraded or re-provisioned to support at least a 14 decimal digit FASC-N Identifier.