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

8 Test and Compliance Process

NIST PIV and digital identity SP 800-85A-4 against SP 800-85A-2
All changes in this version
modified 8 Test and Compliance Process

Title

Test and Compliance Process

Control changed

Before · SP 800-85A-2

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, compliance means— Passing the related test assertions explained in this document

Passing the inspection/verification of the required vendor documentation.

The certified and/or accredited test laboratory that will conduct the testing has the following responsibilities— Prepare and provide the test application forms and the documentation

Receive and configure the PIV software component to be tested

Conduct the test with a testing toolkit

Review the test results and report failures

Inspect the vendor documentation

Communicate the results.

Upon vendor’s submission of the request for PIV component certification, the required documentation, and the PIV software components to be tested, the test laboratory configures the test system, records all preconditions, and runs the applicable suite of tests for the submitted PIV component. After conducting the tests, the test laboratory evaluates the test results and communicates the Test Results Summary (TRS) and Test Run Details (TRD) to the vendor. The Test Results Summary provides the overall environmental information (date and time the tests were conducted, the tester name and vendor product identifier, etc.) as well as the summary conclusion for tests associated with that particular class. The format of the summary report will vary depending upon the test classes. The sample format for each of the above types of summary reports is given in Appendix F. The TRS associated with each of the three classes are: PIV Client API Test Summary Card Command Interface Test Summary PIV Data Objects Accessibility and Storage Test Summary

The TRD are used to log the details of each test run associated with each of the three classes in the test suite. They provide the details of the outcome of each test run for various execution conditions. This detailed report will enable the product vendor to make the necessary logic changes to the implementation of the various commands/interfaces and data object representations in order to become fully conformant.

After · SP 800-85A-4

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, compliance means—: + Passing the related test assertions explained in this document

, and + Passing the inspection/verification of the required vendor documentation.

 The certified and/or accredited test laboratory that will conduct the testing has the following responsibilities—: + Prepare and provide the test application forms and the documentation

, + Receive and configure the PIV software component to be tested

, + Conduct the test with athe testing toolkit

, + Review the test results and report failures

, + Inspect the vendor documentation

, and + Communicate the results.

 Upon vendor’s submission of the request for PIV component certification, the required documentation, and the PIV software components to be tested, the test laboratory configures the test system, records all preconditions, and runs the applicable suite of tests for the submitted PIV component. After conducting the tests, the test laboratory evaluates the test results and communicates the Test Results Summary (TRS) and Test Run Details (TRD) to the vendor. The Test Results Summary provides the overall environmental information (date and time the tests were conducted, the tester name and, vendor product identifier, etc.) as well as the summary conclusion for tests associated with that particular class. The format of the summary report will vary depending upon the test classes. The sample format for each of the above types of summary reports is given in Appendix F. The TRS associated with each of the three classes are: + PIV Client API Test Summary. + Card Command Interface Test Summary. + PIV Data Objects Accessibility and Storage Test Summary

. The TRDTRDs are used to log the details of each test run associated with each of the three classes in the test suite. They provide the details of the outcome of each test run for various execution conditions. This detailed report will enable the product vendor to make the necessary logic changes to the implementation of the various commands/interfaces and data object representations in order to become fully conformant.