search

biometricITC / cPP-toolboxes

This repository maintains the toolbox definitions for evaluations according to the biometric cPP
2 stars 1 forks source link

v1.1 Publication update (#62) #65

Closed woodbe closed 2 months ago

woodbe commented 3 months ago

Updated text, added specific number of PAIs to be created in the test (as opposed to having this in individual toolbox tests for consistency)

Editorial corrections

Updated the pass/fail criteria based on @the-fiona comments

Added new test list (with sensor applicability).

Modified test sets to add number of species types to be produced (including all variants).

Removed "Other" section as this is now in main toolbox overview.

Created attack subfolder, moved all attacks there. Renamed "general.md" to "vein_PADtesting.adoc"

No content changes (other than changing Variations to "None")

Moved from TXT files to adoc format, not content change.

Moved files into attacks folder to fit with eye (and PR for vein)

I migrated the remaining docs to adoc. I copied the attack potential table to all the tests (without changes except in tests 5 becasue those are largely blank so I put in "?"). I moved the remaining files to make it follow the other toolbox updates.

I moved the inventory document to adoc as well.

Edited ATE_IND.1 to ATE_FUN.1

undo the ATE_IND to ATE_FUN back to ATE_IND

Remove the TODO line based on discussion on 5/16 to leave it as transactions for vendor flexibility

Based on the 5/30 call this proposed change is to specify the number of subjects to be used in the creation of PAI.

changed date

Similar problem with reference links as in PP-Module

Based on comments from Mary Baisch, this update attempts to clarify that that toolbox is not intended for AVA_VAN but can be used as the basis for those tests with modifications that the evaluator may decide to make.

Also found a misspelling, and added the :icons: font in the header (though I removed the section that specifically needed it).

This reverts commit 05e5e518485624495437872f62b8a98e240f274d.

Based on comments by Mary Baisch this is intended to further clarify how the toolbox could be used as a basis for the creation of AVA_VAN tests while not being written for that purpose.

Also fixed a misspelling and added :icons: font line to the header.

This is in response to #18 about related to having a standardized template for a toolbox.

There are 4 files in the main folder (here BIO is used to mark the modality, so this should be EYE, FACE, FINGER, etc):

PAD Testing - the description of anything specific to this modality that needs to be documented (in addition to the toolbox overview) along with an introduction to the toolbox.

List - a table list of all the tests and any applicability notes (like these are only relevant with certain types of sensors or other considerations)

Inventory - a list of the inventory that is used in the test, things like paper, printers, camera, the things used to make the PAI

References - external references for any of the attacks (a master list)

Within the main folder there would then be subfoldlers marked with XX__attacks. The XX would be numbering for increasing difficulty (i.e. the lowest level PAI, simplest to create would be 01, the most difficult test would be the top number). The would be some sort of title that would provide some clarity as to what the tests will be used as a source for the PAI.

Within each folder then, you would have the files names XX_YY_attack where the XX matches the folder number and YY is the test number.

The List table should match out all the numbers. While I don't have it in here, there is a (Vx) listing for some of the tests, this is when there is a number of variants for the specific test available (so a test with a V1 and V2 would have 2 variants in addition to the "base" test). This could be handled in another way though.

This used the eye tests to fill out the template, but I didn't modify any of the files.

This reverts commit 8a48e39d92791abbe69b1affc3dc689d23fc1c61.

This reverts commit aba98fa3a6ea6f084bfbc3c26dc1c3e1ece85f2f.

This reverts commit 6e2d60807448c26d10d96da5f563c5a0cdf06e90.

This reverts commit 448dbb844bf7dec7aef248f6aaaad29252555138.

This reverts commit 645dcfa2668b8c47cf375893df17ee553e349a3a.

This is in response to #18 about related to having a standardized template for a toolbox.

There are 4 files in the main folder (here BIO is used to mark the modality, so this should be EYE, FACE, FINGER, etc):

PAD Testing - the description of anything specific to this modality that needs to be documented (in addition to the toolbox overview) along with an introduction to the toolbox.

List - a table list of all the tests and any applicability notes (like these are only relevant with certain types of sensors or other considerations)

Inventory - a list of the inventory that is used in the test, things like paper, printers, camera, the things used to make the PAI

References - external references for any of the attacks (a master list)

Within the main folder there would then be subfoldlers marked with XX__attacks. The XX would be numbering for increasing difficulty (i.e. the lowest level PAI, simplest to create would be 01, the most difficult test would be the top number). The would be some sort of title that would provide some clarity as to what the tests will be used as a source for the PAI.

Within each folder then, you would have the files names XX_YY_attack where the XX matches the folder number and YY is the test number.

The List table should match out all the numbers. While I don't have it in here, there is a (Vx) listing for some of the tests, this is when there is a number of variants for the specific test available (so a test with a V1 and V2 would have 2 variants in addition to the "base" test). This could be handled in another way though.

This used the eye tests to fill out the template, but I didn't modify any of the files.

Update to three subjects as noted in #17

This is an update to match the new toolbox template. No changes were made to the attacks themselves. Previous attack set 01 has been removed as the scan and reprint tests have been removed from Face as well.

Added Attack Potential tables for each attack and each species type for each attack. All calculations show under the 13 limit.

This is to close #22 as agreed on the 12/5 call.

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.

My suggested edits to the changes.

I have edited some text (moved a few things around), did some grammar checking, and edited the tables.

I updated the overview to fix some inconsistency or mistakes

One line update to strengthen the use of research papers

Change the text as suggested by @woodbe in #32

I made several updates here. Most focused on language in the reading to be a little clearer. Some table adjustments were also made to present the tables a little better.

This is editorial related to the biometricITC/cPP-biometrics#266 to try to polish the Toolbox for release at the same time.

I added a revision history and changed SD to BIOSD. I also edited the title to match with the rest of the docs.

update based on @n-kai comment to move this to the Toolbox from the SD.

Current face and eye toolboxes have been moved to their own repositories, so these are being deleted.

These files are being removed as out of date

This template is now out of date. A new one may need to be created, but probably not right now.

Updates based on MITRE's review.

These are focused on updating the dates and versions for all the documents in preparation of public release on May 11, 2020.

Added doctype for proper formatting of PDF output

moved all vein to separate repository

Fix the errors in table

Summary of changes:

This reverts commit e7730db16b04ab767cc7389bec158c2f69183afa.

Summary of changes:

This is to close #biometricITC/cPP-biometrics/378

This adds the documentation in the Toolbox Overview about how to find the toolboxes, how they are versioned, and how to reference them in the conformance claims

This adjusts the definition of what needs to be produced to specifically note that the verification list defines which artefacts need to be tested with specific types of sensors.

Adding a section about the visual recording of data since it is not necessary to record (via photos or video) the production and use of each individual artefact.

This is to close #52

This incorporates the new text from @n-kai as well as moving it from section 8 to 5.1.2 as suggested by @gfiumara

added some text for audio. While not part of the current toolboxes, this would lessen the need (and maybe prevent) an update if audio is added as a modality.

updates to resolve points raised in 6/28 call

remove one week timeline for independent testing

Added some text about the lifespan of artefacts, mainly to state that they can be stored according to manufacturer's recommendations to be re-used, but that this must be documented.

This is to close #54

to address comments about ensuring a stored artefact is still acceptable

This adds a reference for IAPAR to the intro

To resolve stored vs fresh artefact checking.

Additional updates to the language

This is just a date update to match the last commit dates

This is updating the doc dates to match up with the PP_MDF release date.

woodbe commented 2 months ago

@n-kai this is to bring the Interpretation branch up to date with the main (published) branch. I figured we were likely to release the update discussion PAD-L2 as an interpretation supporting the PAD-L1 update for the fingerprint (and eventually face) first, and then publish it fully once the new SFR for PAD-L2 is added.