BaselineWatch
24 requirements
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

NIST PIV and digital identity SP 800-85A-2

24 requirements · published 2010-07-28
Changes in this version
All1 It implements the functions in the PIV Client Application Programming Interface2 It generates the appropriate commands (also called Application Protocol Data3 Test Suite Elements4 Derived Test Requirements5 Test Assertions6 Test and Compliance Documentation7 Acceptance Criteria8 Test and Compliance Process
RefTitleText
1 It implements the functions in the PIV Client Application Programming Interface (Part 3 of SP 800-73-3).
2 It generates the appropriate commands (also called Application Protocol Data Units or APDUs) for the PIV Card Command Interface (card edge interface - Part 2 of SP 800-73-3) and thus communicates with the PIV Card Application. The PIV Card Application resides on the card, implements the commands in the PIV Card Com
2.1
in 2
 Test Plan The test plan identifies the tasks/artifacts required for testing the PIV Middleware and PIV Card Applications. These artifacts include the following: PIV Middleware and smart card populated with a PIV Card Application; the test toolkit (or
2.2
in 2
 Test Set-up The test system consists of the following components: 2 A test toolkit application software that resides on a personal computer (PC) Smart card (SC) readers: ƒ An ISO/IEC 7816 and PC/SC-compliant contact-based smart card reader and ƒ An
2.3
in 2
 Test System Configuration The test system shown in Figure 2 will be configured in both the PIV Middleware tests and the PIV Card Application tests to accommodate the different components to be tested, as explained in Section 3. 2 Compliance of the readers and input
2.3.1
in 2.3
 PIV Middleware Test Configuration The middleware test configuration is used to test a vendor’s middleware software application that implements the PIV client API and generates the appropriate commands in the PIV card command interface (refer to Table A-1 for mapping between
2.3.2
in 2.3
 PIV Card Application Test Configuration The card application test configuration is used to test any PIV Card Application through commands of the PIV card command interface defined in SP 800-73-3 Part 2. The following list shows the test system components included in this configur
3 Test Suite Elements Based on the conceptual software architecture shown in Figure 1, the PIV software components that are involved in and are subject to testing are as follows: PIV Middleware that implements the functions in the PIV Client API and interfaces w
3.1
in 3
 PIV Middleware Tests These tests will validate that the PIV Middleware conforms to the specification in Part 3 of SP 800-73-3. Conformance criteria includes correct implementation of all functions in the PIV client API, generation of appropriate commands for th
3.2
in 3
 PIV Card Application Tests PIV Card Application tests cover the following: The PIV Card Application card command interface as per Part 2 of SP 800-73-3, including the security conditions for executing each command in the interface as well as the security conditions f
3.2.1
in 3.2
 PIV Card Application Card Command Interface Tests These tests will validate that the card under test can successfully execute the commands in the PIV card command interface. Successful execution constitutes the card responding with appropriate data and response status codes to the commands
3.2.2
in 3.2
 PIV Data Objects Accessibility and Storage Tests The testing covers the following data objects The five mandatory data objects as defined in Part 1 of SP 800-73-3 ƒ Card Capability Container ƒ Card Holder Unique Identifier (CHUID) ƒ X.509 Certificate for PIV authentication ƒ Cardholder F
4 Derived Test Requirements DTRs show the type of tests required based on the specifications in SP 800-73-3. These specifications cover expected command behavior (in the case of interface specification), data object representation (in the case of PIV data model) and d
5 Test Assertions Test assertions are statements of behavior, action, or condition that can be measured or tested. They provide the procedures to guide the tester in executing and managing the test. They include the purpose of the test, starting conditions a
5.1
in 5
 Mapping from Test Categories to Test Assertions All the DTRs in Appendix A conceptually come under one of the two broad categories of tests stated in Section 3 i.e., PIV Middleware tests and PIV Card Application tests. Similarly, each test assertion makes specific references to the relat
5.2
in 5
 PIV Client API Test Assertions This section provides conformance tests in the form of test assertions for the functions specified in Chapter 3, Part 3 of SP 800-73-3 (called client API) that the PIV Middleware is expected to support. The test assertions are described thr
5.3
in 5
 PIV Card Command Interface Test Assertions This section provides conformance tests in the form of test assertions for the command set that is specified in Chapter 3, Part 2 of SP 800-73-3 (Card Application Card Command Interface) that the PIV Card Application is required to support.
5.4
in 5
 PIV Data Objects Accessibility and Storage Test Assertions The following assumptions have been made with respect to the PIV data object representation test assertions: A PIV Card Application with a valid Application Identifier (AID) is resident on the card. The PIV Card Application is expected to
6 Test and Compliance Documentation There are two sets of compliance documentation: vendor required and test facility generated. The vendor-required documents consist of the following: Installation and Execution instructions (for PIV Middleware): The vendor provides technical
7 Acceptance Criteria Acceptance criteria are based on the compliance of the item under test with the requirements defined in FIPS 201 and the accompanying special publication documents. The criteria are further specified in the following sections, based on the
7.1
in 7
 Acceptance Criteria for the PIV Middleware Test The PIV Middleware test acceptance criteria will be based on the middleware application under test passing all the PIV client API test assertions. The middleware should return appropriate return codes in response to executing the client API
7.2
in 7
 Acceptance Criteria for the PIV Card Application Tests Acceptance criteria for the PIV Card Application tests are based on the PIV Card Application passing the following two classes of tests: PIV Card Application card command interface tests and PIV data objects accessibility and storage tests.
8 Test and Compliance Process The PIV software component that passes all applicable tests, as explained in this document, will be considered conformant. This document provides the technical details for the testing of the two PIV software components. In this context, com
8.1
in 8
 Failure Review The test will be repeated once for components that do not pass the tests. After the retest, the tester prepares for each failure a discrepancy report that summarizes the purpose of the test, the progression of steps, and the responses recei

24 of 24.