In an effort to provide clarification and a better understanding regarding the ISO Presentation Attack Detection testing that iBeta conducts in accordance with the ISO/IEC 30107-3 standard and in alignment with the ISO/IEC 30107-1 framework, we provide the following explanation.
iBeta posts, by written vendor consent, the Presentation Attack Detection (PAD) Confirmation letters that provide the results of the iBeta PAD testing. These letters specify the type of PAD testing and the configuration of the vendor product that was tested. In order to fully assess the vendor product, the audience of these letters should understand the test method used to assess conformance with the ISO 30107-3 Standard.
Understanding the Test Method
iBeta is accredited by NIST NVLAP as an Independent Test Lab and ISO 30107-3 is included in our scope of accreditation. As such, the specific test procedures, processes, and report templates, as developed by iBeta, are audited and approved as part of the NIST administration of the NVLAP.
Prior to test start, the PAD mechanism is determined:
PAD subsystem test – evaluates presentation attack detection only
Data capture test – evaluates the coupled presentation attack and quality checks
Full system test – evaluates the biometric comparison capabilities of the full biometric subsystem
The type of PAD mechanism determines the ISO/IEC 30107-3 mandated reporting metrics for the evaluation. For subsystem PAD evaluations, the classification error rates (APCER, BPCER and associated non-response rates) are determined whereas when evaluating full systems, the imposter attack presentation match rates (IAPMR and associated FNMR/FMR) is determined.
In order to specify more exactly the test method, iBeta identified levels of testing (although similar to the FIDO Alliance Levels A & B, there are significant differences). The testing levels and performance requirements are identified as:
|1||8 hours per subject or species||None||Cooperative subject and equipment is readily available in a normal home or office environment||0% penetration or match rate allowed|
|2||2-4 days per subject or species||Moderate – participated in at least 1 other PAD test with the target modality and has an understanding of the liveness detection functionality of the test target||Cooperative subject and equipment is more expensive (such as a 3D printer, resin mask, latex mask)||1% penetration or match rate allowed|
In order to maintain uniformity between vendor solutions and modalities and to apply the test methods to each vendor consistently, the 6 species of attacks (called “PAIS” in ISO 30107-3 ) are selected as uniformly as possible. If the application uses an active liveness detector to elicit a “voluntary response” (the ISO 30107-1 term), then the species of attacks are tailored just as an impostor would tailor them to provide the movement, smile, blink, etc. Our procedure sets a material cost limit such that Level 1 artefacts cannot exceed $30 and Level 2 are limited to $300. This keeps the artefacts creation or procurement costs generally consistent across all vendor solutions.
In addition, each species set of artefacts is created and applied to the PAD within a time limit. For Level 1, if liveness detection only is being assessed, then iBeta will create and apply each of the species artefacts within 8 hours, targeting to present 150 attacks alternated with 50 genuine presentations. If a full system is under evaluation, then the artefacts associated with the species for a single genuine subject are created and applied within 8 hours. With 6 subjects and/or 6 species, the testing therefore requires 48 hours.
ISO 30107-3 discusses cooperative versus uncooperative subjects. iBeta uses cooperative subjects in that the artefacts are created from biometric characteristics provided by volunteer data subjects (if not purchased) who are willing and able to pose for photos, record videos, provide their fingerprints in molding material or sit for a live cast. We only use cooperative subjects as the artefacts created from willing volunteers are of better quality making for a more conservative test. iBeta is evaluating the vendor solution and not the ability of our testers to obtain latent prints, as an example.
Prior to applying any presentation attack, the configuration of the vendor solution is recorded and the version is referenced in the confirmation letter. In addition, because the device used to capture the biometric sample impacts the results, the exact device configuration is recorded and also referenced in the confirmation letter.
During the test effort, bona fide biometric presentations to the PAD device not only provide the reporting metrics required by ISO 30107-3 but also provide the indication of usability by the data subjects. For this reason, iBeta is now limiting the BPCER and FNMR to 15% to obtain a “PASS” rating. If a bona fide data subject cannot be recognized as live and/or matching to the enrolment reference, iBeta will suspend testing as a high BPCER or FNMR biases the test result. These error rates were originally unconstrained but have been limited to 20% and now recently reduced to 15%. This limit is reviewed every 6 months and is subject to further reduction as PAD technology improves.
The iBeta testing and reporting provides results that indicate that the solution testing is compliant or conforms with the ISO 30107-3 testing and reporting requirements. This itself, however, does not translate to a certification of the vendor product.
Certification vs. Conformance
When iBeta was initially accredited, the term certification was used but was corrected during the NIST/NVLAP audit in March 2019. There is no difference in our test methods, procedures, or processes between the earlier testing and the testing after that date with the exception that the allowed limit for genuine or Bona Fide presentations is now stricter.
|Date of Letter||Vendor||PAD Level||Product tested||Version(s) tested||FNMR or BPCER limit||PDF Link|
|06/25/21||HyperVerge||Level 1||HyperVerge Onboard|
|04/26/21||Innovatrics||Level 2||Digital Onboarding Toolkit||4.0 Android|
|04/16/21||NEC Asia Pacific||Level 2||Luma||2.1.44 iOS|
|04/13/21||EyeVerify||Level 2||EyeVerify||2.0 (20)||15%|
|04/12/21||EyeVerify||Level 2||EyeVerify||2.0 (29)||15%|
|03/29/21||VU Security||Level 1||Secure Onboarding Process||v22.214.171.124 Android |
|03/23/21||EyeVerify||Level 1||EyeVerify||2.0 (28)||15%|
|03/12/21||Daon||Level 1||DaonFace||126.96.36.199 iOS|
5.1.0 (26) Android
|03/02/21||EyeVerify||Level 1||EyeVerify||2.0 (16)||15%|
|02/25/21||Oz Forensics||Level 1||Liveness||SDK 2.0.0 iOS|
SDK 4.4.10 Android
Server ML models 0039
|01/07/21||Raizomat||Level 1||Identomat||Release 12||15%|
|01/04/21||NEC Asia Pacific||Level 1||Luma||2.1.44 iOS|
SDK v3.0.0 iOS
SDK v3.2.0 Android
|10/01/20||iProov||Level 2||Liveness Asurance||v7.0.0||20%|
|09/30/20||ID R&D||Level 2||IDLive||1.16.0||15%|
|09/16/20||Innovatrics||Level 1||Digital Onboarding Toolkit||3.0.0 Android|
|09/16/20||iProov||Level 1||Liveness Asurance||v7.0.0||20%|
|08/18/20||iProov||Level 2||iProov SDK||App 7.4.1(219)|
SDK 7.5.0 (1)
|08/17/20||Aware||Level 2||FaceLiveness||188.8.131.52 iOS|
|07/27/20||Aware||Level 1||FaceLiveness||184.108.40.206 iOS|
|07/24/20||iProov||Level 1||iProov SDK||App 7.4.1(219)|
SDK 7.5.0 (1)
|06/30/20||OCR Labs||Level 2||Digital Identification Process||v1.0||None|
|05/22/20||Idemia - Passive||Level 2||Web Capture||SDK V 3.10.0||20%|
|04/30/20||Idemia - Passive||Level 1||Web Capture||SDK V 3.10.0||20%|
|04/08/20||ImageWare||Level 1||GoVerifyID||7.5.81 iOS|
|02/27/20||Zoloz||Level 2||ZOLOZ||SDK v18.0 iOS||None|
|12/31/19||ID R&D||Level 1||IDLive||1.9.0||None|
|12/27/19||Idemia - Active||Level 2||SmartBioSdk||SDK V 4.20.0 (2.37)||20%|
|12/13/19||HID Global||Level 2||M-Series||SDK 0.20||20%|
|12/10/19||Idemia - Active||Level 1||SmartBioSdk||SDK V 4.20.0 (2.37)||None|
|09/03/19||OCR Labs||Level 1||Digital Identification Process||v1.0||None|
|08/23/19||Incode||Level 1||Omni Face highfive||v1.0||None|
|07/17/19||Redrock||Level 1||PalmID Login||v220.127.116.11||None|
|05/22/19||HID Global||Level 1||M-Series||v 7.00.00 driver|
SDK v 6.01.26
|09/19/18||HID Global||Level 1||V-Series||v 7.00.00 driver|
SDK v 6.01.26