Skip to content

Commit

Permalink
Test procedure update
Browse files Browse the repository at this point in the history
This is to close #23 related to clarifying the overall testing description.

The table was also updated to follow a more "standard" format.

The PP name was updated to match the current.
  • Loading branch information
Brian Wood committed Dec 6, 2019
1 parent 72b6d05 commit cb9b1f9
Showing 1 changed file with 37 additions and 16 deletions.
53 changes: 37 additions & 16 deletions toolbox.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,8 @@
:sectnums:
:imagesdir: images
:icons: font
:revnumber: 0.4
:revdate: 2019-07-22
:revnumber: 0.5
:revdate: 2019-12-06

== Introduction
This document an its child documents contain a toolbox of Presentation Attack Instruments (PAI) for various biometric modalities. This toolbox shall be used to test the PAD functionality of a TOE during an evaluation in compliance to <<PP>> in the context of the assurance classes. It should be noted that - while there may be some overlap to the area of penetration testing - this toolbox has not been developed for the use in the context of the assurance class AVA.
Expand Down Expand Up @@ -55,11 +55,13 @@ The production of the PAI for each toolbox shall be performed as follows:
* Each produced artefact shall be identified by a unique identifier. This identifier shall be be attached to the artefact at all times (as far as this is possible without destroying the artefact).

=== Testing
The actual test of each PAI shall be conducted as follows:
The actual test of each PAI shall be conducted generally as follows (specific details are provided with the attack instructions):

* The artefact shall be applied to the TOE 10 times.
** If the TOE matches the previously enrolled user by the use of the artefact, the attempt is considered a failed attempt.
** If the TOE rejects the attempt, this is considered being a passed attempt.
* The user is enrolled to the TOE
* Artefacts are created according to the attack instructions
* The artefact shall be applied to the TOE 10 times
** If the TOE matches the artefact to the enrolled user, the attempt is considered a failed attempt.
** If the TOE rejects the artefact, this is considered being a passed attempt.

=== Pass/Fail Criteria
The following pass criteria shall be applied if no other criteria are defined in the individual modality toolbox documents.
Expand All @@ -69,19 +71,38 @@ A TOE passes the test if and only if it reliably defeats the use of *all artefac
To reproducibly overcome the TOE by the use of a *certain artefact* in the outlined test scenario is defined as follows:

.Pass/Fail Criteria
[width="100%",options="header"]
|====================
|Attempts |PAI Matches |Outcome
|10 |0 |TOE passes this PAI
|10 |1 |TOE passes this PAI
|10 |2 |Additional ten (10) attempts are allowed with this PAI
|20 |2 |TOE passes this PAI
|Up to 20 |3 or more |TOE fails this PAI
|====================
[cols="1,1,3",options="header"]
|===

|Attempts
|PAI Matches
|Outcome

|10
|0
|TOE passes this PAI

|10
|1
|TOE passes this PAI

|10
|2
|Additional ten (10) attempts are allowed with this PAI

|20
|2
|TOE passes this PAI

|Up to 20
|3 or more
|TOE fails this PAI

|===

The maximum number of attempts allowed with a PAI is twenty (20). If three (3) matches are made to the PAI, the test fails (further attempts are not necessary even if 20 total attempts have not yet been made).

== Literature

- [#PP]#[PP]# collaborative Protection Profile Module for Mobile biometric enrolment and verification - for unlocking the device
- [#PP]#[PP]# collaborative PP-Module for Biometric enrolment and verification - for unlocking the device

0 comments on commit cb9b1f9

Please sign in to comment.