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

3.1 PIV Middleware Tests

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

Title

PIV Middleware Tests

Control changed

Before · SP 800-85A-2

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 the PIV card command interface to communicate with the PIV Card Application and return the prescribed response codes to the calling agency application. This test, however, does not validate the functional requirements or the testing of the FIPS 201-mandated card application parameters, which are covered under the PIV data model tests. The following client API functions are tested for conformance: pivConnect

pivDisconnect

pivSelectCardApplication

pivLogIntoCardApplication

pivGetData

pivLogoutOfCardApplication

pivCrypt

pivPutData

pivGenerateKeyPair

pivMiddlewareVersion

These functions will be tested for their response to both the valid and the error conditions as defined by this document. To conduct these tests, a smart card with an “SP 800-73-3- conformant PIV Card Application” (refer to section 7.2 for definition) must be accessible.

After · SP 800-85A-4

These tests will validate that the PIV Middleware conforms to the specification in Part 3 of SP 800-73-3800-73-4 . Conformance criteria includesinclude correct implementation of allthe functions infor the PIV client API, generation of appropriate commands for the PIV card command interface to communicate with the PIV Card Application, and return of the prescribed response codes to the calling agency application. This test, however, does not validate the functional requirements or the testing of the FIPS 201-mandated201 -mandated card application parameters, which are covered under the PIV data model tests as specified in SP 800-85B . The following clientPIV APIMiddleware functions are tested for conformance of the PIV Middleware without support for secure messaging (SM) and the virtual contact interface (VCI): 1. pivConnect

 2. pivDisconnect

 3. pivSelectCardApplication

 4. pivLogIntoCardApplication

 5. pivGetData

 6. pivLogoutOfCardApplication

 7. pivCrypt

 8. pivPutData

 9. pivGenerateKeyPair

 10. pivMiddlewareVersion

 For PIV Middleware with support for SM and VCI, the following additional PIV Middleware function is tested for conformance: 11. pivEstablishSecureMessaging These functions will be tested for their response to both the valid and the error conditions as defined by this document. To conduct these tests, a smart card with an “ SP 800-73-3-800-73-4 - conformant PIV Card Application” (refer to sectionSection 7.2 for definition) must be accessible.