NIST PIV and digital identity SP 800-157 Rev. 1 (Draft)
All1 Use of public key infrastructure (PKI) technology. PKI-based derived PIV credentials2 Use of non-PKI-based authenticators. Non-PKI authenticators rely on IdAM3 Technical Requirements 594Appendix A Digital Signature and Key Management Keys 811Appendix B Data Model and Interfaces for Removable or Wireless PKI-Based Cryptographic 840Appendix C Example Issuance Processes 1053Appendix D Physical Access 1151Appendix E Glossary 1360Appendix F Acronyms and Abbreviations 1407Appendix G Change Log 1436
| Ref | Title | Text | |
|---|---|---|---|
| 1 | Use of public key infrastructure (PKI) technology. PKI-based derived PIV credentials | rely on the same infrastructure used for authentication with a PIV Card. Cross- domain use of PKI-based derived PIV credentials is supported in the same manner as for PIV Cards. | |
| 2 | Use of non-PKI-based authenticators. Non-PKI authenticators rely on IdAM | infrastructure to allow for direct authentication by the home agency. Cross- domain use of non-PKI-based derived PIV credentials is supported through federation protocols, as specified in [SP800-217] . The derived PIV credentials specified | |
| 2.1 in 2 |
Derived PIV Credential Life Cycle Activities | The derived PIV credential life cycle consists of the activities described above: initial issuance, maintenance, and termination. The activities at the manufacturer during fabrication and pre-personalization of the authenticator (as applica | |
| 2.2 in 2 |
Initial Issuance | Issuing a derived PIV credential is an instance of the post-enrollment binding of an authenticator described in [SP800-63B] . Issuance SHALL be performed in accordance with the requirements that apply to cryptographic authenticators and the | |
| 2.2.1 in 2.2 |
PKI-Based Derived PIV Credential Issuance | Issuing a PKI-based derived PIV credential requires the generation of a public/private key pair followed by the creation of a corresponding authentication certificate by the certificate authority (CA). For a derived PIV credential capable o | |
| 2.2.2 in 2.2 |
Non-PKI-Based Derived PIV Credential Issuance 485 | 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 The applicant SHALL be provided with or supply an approved physical authenticator for the highest AAL th | |
| 2.2.3 in 2.2 |
Derived PIV Issuance Without PIV Card | Some operational situations may motivate the issuance of a derived PIV credential when a PIV Card is unavailable. For example, it may be desirable to: • Issue a derived PIV credential to a new subscriber in a field location where productio | |
| 2.3 in 2 |
Maintenance 518 | 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 The maintenance activities required for derived PIV credentials depend on the type of derived PIV creden | |
| 2.3.1 in 2.3 |
PKI-Based Derived PIV Credential Maintenance | PKI-based derived PIV credentials require typical maintenance activities applicable to asymmetric cryptographic credentials, including rekeying and modification. These activities MAY be performed either remotely or in person and SHALL be co | |
| 2.3.2 in 2.3 |
Non-PKI-Based Derived PIV Credential Maintenance 552 | 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 Maintenance activities for non-PKI-based derived PIV credentials are simpler than those for PKI-ba | |
| 2.4 in 2 |
Invalidation | When an authenticator associated with a derived PIV credential is compromised (e.g., lost, stolen, or damaged), that derived PIV credential SHALL be invalidated as described below. All derived PIV credentials associated with a given PIV id | |
| 2.4.1 in 2.4 |
PKI-based Derived PIV Credential Invalidation | If the derived PIV authentication private key was created and stored on a hardware module that does not permit private key export and the token is collected and either zeroized or destroyed, then the derived PIV authentication certificate S | |
| 2.4.2 in 2.4 |
Non-PKI-Based Derived PIV Credential Invalidation 587 | 588 589 590 591 592 593 Non-PKI-based derived PIV credentials are always directly verified by the home agency IdMS of the associated PIV Card. Therefore, termination of a non-PKI-based derived PIV credential SHALL be accomplished by invalid | |
| 3 | Technical Requirements 594 | 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 This section is normative. This section describes technical requirements for PKI-based and non-PKI-based der | |
| 3.1 in 3 |
PKI-Based Derived PIV Credentials | A PKI-based derived PIV credential is a derived PIV authentication certificate, which is an X.509 public key certificate that has been issued in accordance with the requirements of this document and [COMMON] . All derived PIV credentials cr | |
| 3.1.1 in 3.1 |
Certificate Policies for PKI-Based Derived PIV Credentials | Derived PIV authentication certificates SHALL be issued under either the id-fpki- common-derived-pivAuth-hardware policy (satisfying [SP800-63B] AAL3) or the id-fpki-common-derived-pivAuth policy (satisfying AAL2) of [COMMON] . All derived | |
| 3.1.2 in 3.1 |
Cryptographic Specifications 626 | 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 The cryptographic algorithm and key size requirements for the derived PIV authentication c | |
| 3.1.3 in 3.1 |
Allowable Authenticator Types | A multi-factor cryptographic authenticator as specified in [SP800-63B] Sec. 3.1.7.1 SHALL be used for PKI-based derived PIV authentication. The authenticator SHALL be phishing- resistant, as described in [SP800-63B] Sec. 3.2.5. Authenticato | |
| 3.1.4 in 3.1 |
Activation Data | Activation of PKI-based derived PIV authenticators using an activation secret SHALL meet the requirements of [SP800-63B] Sec. 3.2.10. Activation using a biometric characteristic SHALL meet the requirements of [SP800-63B] Sec. 3.2.3. If the | |
| 3.2 in 3 |
Non-PKI-Based Derived PIV Credentials | Non-PKI-based credentials SHALL only be used to authenticate to verifiers that are authorized by the home agency of the associated PIV Card. All verifiers of non-PKI-based derived PIV credentials SHALL access the home agency IdMS in order t | |
| 3.2.1 in 3.2 |
Allowable Authenticator Types | Multi-factor or single-factor cryptographic authenticators as specified in [SP800-63B] Sec. 3.1.7.1 and Sec. 3.1.6.1, respectively, SHALL be used for non-PKI-based derived PIV authentication. Cryptographic authenticators SHALL be phishing-r | |
| 3.2.2 in 3.2 |
Cryptographic Specifications | Authenticators used as non-PKI-based derived PIV credentials SHALL meet the cryptographic requirements specified in [SP800-63B] Sec. 3.1 for the corresponding authenticator type. | |
| 3.2.3 in 3.2 |
Activation Data | Activation of the derived PIV credential using an activation secret SHALL meet the requirements of [SP800-63B] Sec. 3.2.10. Activation using a biometric characteristic SHALL meet the requirements of [SP800-63B] Sec. 3.2.3. If the activatio | |
| Appendix A | Digital Signature and Key Management Keys 811 | 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 This appendix is informative. In addition to the PIV authentication keys, [FIPS201] also requires each PIV Card to have a di | |
| Appendix B | Data Model and Interfaces for Removable or Wireless PKI-Based Cryptographic 840 | 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 Authenticators This appendix is normative. This appendix provides data model and interface requirements for | |
| B.1 in B |
Derived PIV Application Data Model and Representation | The data model and representation requirements for derived PIV applications are based on the requirements for PIV Card applications, as described in [SP800-73pt1] . Test requirements and test assertions for testing the derived PIV applicati | |
| B.1.1 in B.1 |
Derived PIV Application Identifier | The PIV application ID (AID) SHOULD be used to maximize interoperability with PIV Cards. For reference, that application ID is (in hexadecimal): A0 00 00 03 08 00 00 10 00 01 00 Alternatively, the derived PIV application identifier define | |
| B.1.2 in B.1 |
Derived PIV Application Data Model Elements 871 | 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 The derived PIV application SHALL contain the following mandatory interoperable data object | |
| B.1.2.1 in B.1.2 |
Derived PIV Application Data Object Containers and Associated Access Rules 944 | 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 Section 3.5 of [SP800-73pt1] provides the container IDs and access rules for the mandatory and optional data objects for a derived PIV application with the | |
| B.1.3 in B.1 |
Derived PIV Application Data Objects Representation | The ASN.1 object identifiers (OID) and “basic encoding rules – tag length value” (BER- TLV) tags for the mandatory and optional data objects within the derived PIV application are the same as for the corresponding data objects (mapped per T | |
| B.1.4 in B.1 |
Derived PIV Application Data Types and Their Representation | This appendix describes the data types used in the derived PIV application command interface. | |
| B.1.4.1 in B.1.4 |
Derived PIV Application Key References and Security Conditions of Use 965 | 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 Key references are assigned to keys and secrets of the derived PIV application. Table 8 of [SP800-78] and Table 4 of [SP800-73pt1] define the key referenc | |
| B.1.4.2 in B.1.4 |
Derived PIV Application Cryptographic Algorithm and Mechanism Identifiers | The algorithm identifiers for the cryptographic algorithms that MAY be recognized on the derived PIV application interfaces are the symmetric and asymmetric identifiers specified in Table 9 and Table 10 of [SP800-78] . The cryptographic mec | |
| B.1.4.3 in B.1.4 |
Derived PIV Application Status Words | The status words that MAY be returned on the derived PIV application command interface are as specified in Sec. 5.6 of [SP800-73pt1] . | |
| B.1.5 in B.1 |
Derived PIV Authentication Mechanisms | The derived PIV application supports the following validation steps: • Credential validation (CredV) is established by verifying the certificates retrieved 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1 | |
| B.2 in B |
Derived PIV Application Token Command Interface | This appendix contains the technical specifications for the command interface to the derived PIV application surfaced by the card edge of the integrated circuit card (ICC) that represents the removable cryptographic authenticator. The comma | |
| B.2.1 in B.2 |
Authentication of an Individual | Knowledge of a secret (specifically the derived PIV activation secret) is how an individual can be authenticated to the derived PIV application. The derived PIV activation secret SHALL be between 6 and 8 bytes in length. If the actual leng | |
| Appendix C | Example Issuance Processes 1053 | 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 This appendix is informative. The issuance process fo | |
| C.1 in C |
Example Issuance of a PKI-Based Derived PIV Credential at AAL3 | An employee requires a derived PIV credential to access a relying party application that requires authentication at AAL3. Their endpoint does not easily accommodate their PIV Card, and the application resides at a different agency that does | |
| C.2 in C |
Example Issuance of a PKI-Based Derived PIV Credential at AAL2 | An employee requires a mobile device for work. The mobile device is ordered, and a request to issue a derived PIV credential is submitted to the agency’s approval authority. Following receipt of the device and approval, the employee starts | |
| C.3 in C |
Example Binding of a Non-PKI-Based Derived PIV Credential at AAL3 | An employee requires a derived PIV credential to access a relying party using one or more endpoints that do not accommodate the direct use of a PIV Card. The employee requests a non-PKI-based authenticator capable of authentication at AAL3 | |
| C.4 in C |
Example Binding of a Non-PKI-Based Derived PIV Credential at AAL2 | The binding of a non-PKI-based derived PIV credential at AAL2 is identical to that at AAL3, except that the authenticator needs only to meet the requirements of AAL2. | |
| C.5 in C |
Example Binding of PACS Credential | To enable a derived PIV credential to be used for physical access as described in Appendix D , the applicant first authenticates using their PIV Card and the PKI-AUTH authentication method. Having authenticated the employee, the server veri | |
| Appendix D | Physical Access 1151 | 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 This appendix is normative. Credentials on PIV cards | |
| D.1 in D |
PACS Derived PIV Application Data Model and Representation | The data model and representation requirements for the derived PIV application are based on the requirements for the PIV Card application, as described in [SP800-73pt1] . Test requirements and test assertions for testing the derived PIV app | |
| D.1.1 in D.1 |
Derived PIV Application Identifier | Either the PIV card application identifier (AID) defined in Sec. 2.2 of [SP800-73pt1] or the derived PIV application AID, defined in Appendix B , SHALL be used. To maximize compatibility with existing PACS readers, the AID of the PIV card a | |
| D.1.2 in D.1 |
PACS Derived PIV Application Data Model Elements | The derived PIV application SHALL contain the following data objects when used for PACS: Derived CHUID Data Object The read access control rule for the derived CHUID data object is as described for the CHUID data object specified in Sec. 3 | |
| D.1.2.1 in D.1.2 |
PACS Derived PIV Application Data Object Containers and Associated Access Rules | Section 3.5 of [SP800-73pt1] provides the container IDs and access rules for the PACS data objects for a derived PIV application with the mappings in Table 3 . Table 3. Mapping of Data Objects Derived PIV Application Data Object PIV Card | |
| D.1.3 in D.1 |
Derived PIV PACS Application Data Objects Representation | The ASN.1 object identifiers (OID) and basic encoding rules – tag length value (BER- TLV) tags for the PACS data objects within the derived PIV application are the same as for the corresponding data objects of the PIV Card application (mapp | |
| D.1.4 in D.1 |
Derived PIV Application PACS Data Types and Representation 1282 | 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 This section describes the data types used in the derived PIV application PACS command interface. | |
| D.1.4.1 in D.1.4 |
Derived PIV Application PACS Key References and Security Conditions | Key references are assigned to keys and secrets of the derived PIV application. Table 8 of [SP800-78] and Table 4 of [SP800-73pt1] define the key reference values that SHALL be used on the derived PIV application interfaces with the mapping | |
| D.1.4.2 in D.1.4 |
Derived PIV Application PACS Cryptographic Algorithm and Mechanism Identi- | fiers The algorithm identifiers for the cryptographic algorithms that MAY be recognized for PACS use on the derived PIV application interfaces are the asymmetric identifiers specified in Table 9 and Table 10 of [SP800-78] . The cryptographi | |
| D.1.4.3 in D.1.4 |
Derived PIV Application Status Words | The status words that MAY be returned for PACS use on the derived PIV application command interface are as specified in Sec. 5.6 of [SP800-73pt1] . | |
| D.1.5 in D.1 |
Derived PIV PACS Authentication Mechanisms | The derived PIV application supports the following validation steps for PACS use: • Credential validation (CredV) is established by verifying the certificates retrieved from the derived PIV application and checking the validity and revocat | |
| D.2 in D |
Derived PIV Application Token Command Interface | This appendix contains the technical specifications for the command interface to the derived PIV application surfaced by the wireless interface to the derived PIV credential for PACS. The command interface for the derived PIV application SH | |
| D.2.1 in D.2 |
Authentication of an Individual for PACS | The two authentication mechanisms for PACS are PKI-CAK and SM-AUTH, which rely only on possession of the derived PIV credential for holder validation (HolderV). Therefore, an activation secret is not used for enhanced holder validation. | |
| D.3 in D |
Invalidation of PACS Derived PIV | A derived PIV credential that is used for physical access SHALL be invalidated when the associated PIV identity account is terminated or when the PACS credential or the device on which it resides has been lost or compromised. The IdMS SHALL | |
| Appendix E | Glossary 1360 | 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 This appendix is informative. Selected terms used in this guidelin | |
| Appendix F | Acronyms and Abbreviations 1407 | 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 This appendix is informative. Selected abbreviations used in this guideline are defin | |
| Appendix G | Change Log 1436 | 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 This appendix is informative. It provides an overview of the changes to SP 800-157 since |
60 of 60.