biometricITC / cPP-biometrics

Contains the development of a Collaborative Protection Profile for biometrics
MIT License
10 stars 2 forks source link

IAPAR update #347

Closed woodbe closed 3 years ago

woodbe commented 3 years ago

This is to close #343

One concern I have here is that I updated FIA_MBE_EXT.3.1 to match, but technically IAPAR is for verification, so I'm not sure we can use that for enrolment. I don't know what to do if we don't, since then the enrolment requirement is vague, but I also don't know if an IAPAR for verification is in any way equivalent for enrolment.

I didn't make any further changes in terms of tables or such that would explain the calculations or anything differently (or more explicitly), so we may end up needing to do something along those lines, but I'm not sure.

gfiumara commented 3 years ago

For enrolment, you maybe want "bona fide presentation classification error rate (BPCER): proportion of bona fide presentations incorrectly classified as presentation attacks in a specific scenario," and/or the inverse, "attack presentation classification error rate (APCER): proportion of attack presentations using the same PAI species incorrectly classified as bona fide presentations in a specific scenario."

Update: suggested this in #348 for merging into this PR for further review.

gfiumara commented 3 years ago

I don't think I agree with creating a new term IAPARE that is not defined by ISO. Enrolment doesn't deal with a verification system at all, it would only deal with the "data capture subsystem," which is the term specified in the published ISO/IEC 30107-3:2017. The second A in IAPAR is about acceptance, formally M for match, but ISO/IEC depreciated using match this way. This wouldn't follow for enrolment.

If anything, the term should be IAPE(nrollment)Rate, but I think that might as well be the attack presentation acquisition rate (APAR) ("proportion of attack presentations using the same PAI species from which the data capture subsystem acquires a biometric sample of sufficient quality").

woodbe commented 3 years ago

Another option would be to not specify anything for IAPAR for enrolment and go back to what it was before.

I will admit I read the comment wrong and thought this was in the draft ISO (when I was reading the comment), so having it there is to capture it. I am not certain how to handle the enrolment case, as it is definitely the most tricky since you don't have anything to compare with readily at that point.

n-kai commented 3 years ago

I agree with "Another option would be to not specify anything for IAPAR for enrolment and go back to what it was before.". PAD for enrolment is optional requirement and ISO/IEC 30107-3 doesn't require to report the error rate like IAPAR.

woodbe commented 3 years ago

I have removed the FIA_MBE_EXT.3 requirement changes to leave it as it was originally at this point. So the changes are now just the IAPAR on the FIA_MBV_EXT.3 requirement

woodbe commented 3 years ago

call this out for comment in the public review

woodbe commented 3 years ago

agreed to be merged on the call