BaselineWatch
Desk

4.9 Other Threats

NIST PIV and digital identity SP 800-116 Rev. 1 against SP 800-116
All changes in this version
removed 4 Threat Environment part of 4

Title changed

Before · SP 800-116

Other Threats

After · SP 800-116 Rev. 1

Other Threats

Control changed

Before · SP 800-116

The PIV System and PACS are complex, and this brief discussion has focused on properties of the PIV Card. A number of other attack vectors have not been discussed in detail, including sophisticated technical attacks against the integrity of the PIV Card, PIV System, or PACS components, and cryptanalysis of the PIV cryptographic algorithms. While the impact of successful attacks such as these could be moderate to high, the probability of success is believed to be extremely low. Recommendation: This section emphasizes the technical risks that remain with the CHUID authentication mechanism. If the CHUID authentication mechanism were implemented without restriction, operational risk would increase as the value of targets and the availability of cloning and counterfeiting tools increase. NIST therefore recommends that the CHUID authentication mechanism be implemented in only two situations: 1) access control points separating two areas at the same impact level, either Controlled or Limited; and 2) combined with the VIS authentication mechanism at access points between Unrestricted and Controlled areas. See Section 7 for further detail. NIST further recommends that the asymmetric CAK authentication mechanism be used instead of the CHUID authentication mechanism to the greatest extent practical.

After · SP 800-116 Rev. 1

The PIV System and PACS are complex, and this brief discussion has focused on properties of the PIV Card. A number of other attack vectors have not been discussed in detail, including sophisticated technical attacks against the integrity of the PIV Card, PIV System, or PACS components, and cryptanalysis of the PIV cryptographic algorithms. While the impact of successful attacks such as these could be moderate to high, the probability of success is believed to be extremely low. Recommendation: This section emphasizes the technical risks that remain with the CHUID authentication mechanism. If the CHUID authentication mechanism were implemented without restriction, operational risk would increase as the value of targets and the availability of cloning and counterfeiting tools increase. NIST therefore recommends that the CHUID authentication mechanism be implemented in only two situations: 1) access control points separating two areas at the same impact level, either Controlled or Limited; and 2) combined with the VIS authentication mechanism at access points between Unrestricted and Controlled areas. See Section 7 for further detail. NIST further recommends that the asymmetric CAK authentication mechanism be used instead of the CHUID authentication mechanism to the greatest extent practical.