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.2 PIV Client API Test Assertions

NIST PIV and digital identity SP 800-85A-4 against SP 800-85A-2
All changes in this version
modified 5 Test Assertions part of 5

Title

PIV Client API Test Assertions

Control changed

Before · SP 800-85A-2

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 through a test assertions template. The template provides placeholders for describing the purpose of the test, the preconditions required to exercise the test, the parameter values used in test invocation, and the expected results as well as the state of the PIV system (value of state variables), if any, that will be affected by the test run (post-condition). The conformance tests are run against the PIV Middleware, which in turn interacts with the PIV Card Application resident on the PIV Card. Hence, there are two pieces of software (PIV Middleware and PIV Card Application) that determine the outcome of each test run. Because the focus of the tests is the behavior of the PIV Middleware, the test configuration assumes the presence of a validated PIV Card Application.

The test assertions derived from SP 800-73-3, SP 800-78-2 are demonstrated by test cases in Appendix B and are summarized in Table 5-2. Client API Command Number of Test Cases (Appendix B) pivConnect 6 pivDisconnect 4 picSelectCardApplication 4 pivLogIntoCardApplication 4 pivLogOutOfCardApplication 3 pivGetData 3 40 pivPutData 58 pivGenerateKeyPair 8 pivCrypt 13 pivMiddlewareVersion 1

Table 5-2. List of Commands in Client API and Number of Test Cases

The PIV client API test cases are based on the following assumptions: There is a PIV Card with a validated PIV Card Application.

A valid connection description is provided for the Card Application.

A valid physical connection exists between an instance of the PIV card reader and the host where the PIV Middleware (client application) resides.

No other application is currently connected to the PIV Card Application.

3 A SP 800-73-3 conformant PIV Middleware has to be able to recognize and handle all PIV data object. Therefore, the number of test cases for pivGetData and pivPutData includes reading/writing all mandatory and optional PIV data objects.to/from a PIV card.

After · SP 800-85A-4

This section provides conformance tests in the form of test assertions for the functions specified in ChapterSection 3, SP 800-73-4 Part 3 of(referred SPto 800-73-3as (calledthe client API) that the PIV Middleware is expected to support. The test assertions are described through a test assertions template. The template provides placeholders for describing the purpose of the test, the preconditions required to exercise the test, the parameter values used in test invocation, and the expected results as well as the state of the PIV system (value of state variables), if any, that will be affected by the test run (post-condition). The conformance tests are run against the PIV Middleware, which in turn interacts with the PIV Card Application resident on the PIV Card. Hence, there are two pieces of software (PIV Middleware and PIV Card Application) that determine the outcome of each test run. Because the focus of the tests is the behavior of the PIV Middleware, the test configuration assumes the presence of a validated PIV Card Application.

 The test assertions derived from SP 800-73-3,800-73-4 and SP 800-78-2800-78-4 are demonstrated by test cases in Appendix B and are summarized in Table 5-2. Client API Command Number of Test Cases (Appendix B) pivConnect 6 pivDisconnect 4 picSelectCardApplication 4 pivLogIntoCardApplication 4 pivLogOutOfCardApplication 3 pivGetData 3 40 pivPutData 58 pivGenerateKeyPair 8 pivCrypt 13 pivMiddlewareVersion 1

Table 5-2. List of Commands in Client API and Number of Test Cases

The PIV client API test cases are based on the following assumptions: + There is a PIV Card with a validated PIV Card Application.

 + A valid connection description is provided for the PIV Card Application.

 + A valid physical connection exists between an instance of the PIV card reader and the host where the PIV Middleware (client application) resides.

 + No other application is currently connected to the PIV Card Application.

3 A SP 800-73-3 conformant PIV Middleware has to be able to recognize and handle all PIV data object. Therefore, the number of test cases for pivGetData and pivPutData includes reading/writing all mandatory and optional PIV data objects.to/from a PIV card.