Skip to content

Changelog

das-Face v3.3 (2021-Q3)

  • Improved active antispoofing performance on HTML.
    • For a threshold of 0.7 BPCER is 82% lower with respect to the previous release. APCER has no measurable differences
    • For a threshold of 0.9 BPCER is 80% lower with respect to the previous release. APCER has no measurable differences.

Deprecation enforcement

Enforcement of deprecation for the model identified with:

  • Tag: 20190813
  • Hash: 3a9e9d5ffd5de4c212c2aff26eeca523fb69754e604894520b32e4ed

Existing credentials generated with such model won’t be compatible anymore with das-Face.

das-Face v3.2 (2021-Q2)

  • Passive antispoofing performance has been improved.
    • For a threshold of 0.7 APCER is 46% lower with respect to the previous release. BPCER has no measurable differences
    • For a threshold of 0.9 APCER is 57% lower with respect to the previous release. BPCER has no measurable differences.
  • verification/photo average processing time improved 22,48% from the previous release.
  • challenges/analysis/video-photo average processing time improved 8% from the previous re- lease.
  • Unique ID will be returned to the VeriSaaS API users using the X-Request-Id header.

das-Face v3.0 (2021-Q1)

This version comes with two major changes related to biometric models and antispoofing techniques.

  • New biometric model which reduces false positive and false negative rates, and improves the accuracy on different demographic cases (Caucasian, African, Indian, Asian). The model improves the accuracy of selfie-mode from 99.8% to 99.9% and the funnel of document- mode is improved by two points maintaining the same security level, obtaining TPR=2.43% @ FPR=0.62% at 0.7 threshold. The new model is identified by: - Model hash: 904fa9ef6e71ef541f20a95d3dc97821b7af43b8cd2c1bb3eb09df15 - Model tag: 20210203
  • Because model 20210203 generates larger biometric credentials than earlier models, the default endpoint /credential/photo will generate them using model 20200514, so by default credentials have the 2896 bits length as usual.

  • When security is a must, and having a use case that could afford using larger biometric cre- dentials, the model 20210203 is available at the endpoint:

    • /models/<hash>/<mode>/credential/photo

    The biometric credentials for model 20210203 are of 9040 bits length.

  • An update of the Selfie-Alive Pro (SAP) use case (/challenges/analysis/video-photo) de- creasing the time of the operation in a 26%. The system is calibrated at threshold 0.7 for BPCER=2.7% and APCER=0.9%.
  • An update of the passive AS solution (/authenticity/photo) calibrated at threshold 0.7 for BPCER=3.2% and APCER=7.8%, reducing a 50% the APCER of the previous das-Face ver- sion. The system requires additional 300ms per query (a total of 1185ms per query).
  • Deprecation announcement: The biometric model with model hash 3a9e9d5ffd5de4c212c2aff26eeca523fb69754e604894520b32e4ed and model tag 20190813 is marked as deprecated, enforcing deprecation for the 2021 Q3 release. Existing credentials generated with that model have to be re-generated before the 2021 Q3 release with one of the supported models to continue being functional. Keep in mind that after the 2021 Q3 release, existing credentials generated with that model won’t work anymore. Remember that there is available a new endpoint to check the model used for creating the credentials /models/metadata/from-credential.

das-Face v2.7.2 (2021-Q1)

  • Fixes low scores at /verification/video when using mode=document-mode.

das-Face v2.9 (2021-Q1)

  • Add support for BBVA SEMaaS traceId field (using the x-rho-traceid header).

das-Face v2.8 (2021-Q1)

  • Added support for JPEG blobs.

das-Face v2.7 (2020-Q4)

This new version of das-Face comes with new liveness detection capabilities.

  • Improved passive liveness detection with the following figures:
  • Improves replay-attacks APCER from 27% in das-Face v2.5.2 to 5.3% in das-Fave v2.6.7.
  • Achieves BPCER=11.7%
  • These operational figures are valid for selfie-alive and vali-Das on-boarding products.
  • Adds Selfie-Alive Pro use case, VERIDAS liveness detection using an active procedure.
  • The system performs with APCER=0.1% and BPCER=12.9%.
  • Supports videos recording a sequence of random head movements.
  • This solution is in compliance to ISO 30107-3 PAD level 1, as tested by iBeta.
  • Support for a contextual data header: X-Veridas-RTag header is logged in every query allowing to build statistics and billing segregated by customer, use cases, sub-clients and so on.

Deprecation enforcement

Enforcement of deprecation for the model identified with:

  • Tag: 20180827
  • Hash: b0bf475e5344e816f12b83c13c075a3256ef95e60ac1cdc273aef59f

Existing credentials generated with such model won’t be compatible any more with das-Face.

das-Face v2.6 (never released)

This version was used internally to calibrate the liveness detection released in das-Face v2.7.

das-Face v2.5 (2020-mid-Q3)

  • Fix bug in v2/verification/video when more than one face was detected in the video.

das-Face v2.4 (2020-Q2)

  • New biometric model which reduces false positive and false negative rates, and improves the accuracy on different demographic cases (Caucasian, African, Indian, Asian). The model improves accuracy of selfie-mode form 99.6% to 99.8% and document-mode from 97.87% to 98.34%. The new model is identified by:
  • Model hash: 904fa9ef6e71ef541f20a95d3dc97821b7af43b8cd2c1bb3eb09df15
  • Model tag: 20200514
  • Added a new endpoint to retrieve the operational model from the biometric credential meta- data, i.e., model hash and operation mode chosen to generate the given credential.
  • Added a new endpoint to get the operational models active in das-Face.
  • Added a description of the orchestration required for selfie-alive.
  • Deprecation announcement The biometric model with:
  • model hash: b0bf475e5344e816f12b83c13c075a3256ef95e60ac1cdc273aef59f
  • model tag: 20180827

is marked as deprecated, enforcing deprecation for 2020 Q4 release. Existing credentials generated with that model have to be re-generated before 2020 Q4 release with one of the supported models to continue being functional. Keep in mind that after 2020 Q4 release, existing credentials generated with that model won’t work anymore. Remember that from this release there is available a new endpoint to check the model used for creating the credentials.

das-Face v2.3 (2020-Q1)

  • The endpoint POST /v2/authenticity/photo (antispoofing) accepts images images taken with Veridas HTML SDKs.
  • Deprecation reminder: API v1 endpoints are not supported any more.

das-Face v2.2 (2019-Q4)

  • Improved log messages, increasing their exploitability.
  • Recall deprecation of API v1 endpoints, it will be enforced at 2020 Q1.

das-Face v2.1 (2019-Q3)

  • Improved document-mode biometric model for selfie-vs-document functionality.
  • Improved selfie-mode biometric model for selfie-vs-selfie functionality.
  • Improved anti-spoofing detection for photo authenticity endpoint, increasing accuracy from 90.3% to 92.2% for replay-attacks.
  • Replacement of dataset used to compute photo authenticity performance curve (anti-spoofing). The new replay-attack dataset is larger, uses more devices and has been carried out under more complex conditions.
  • Notice that due to the new biometric model for document-mode and selfie-mode, all endpoints are expected to use the new model.
  • Recall the deprecation of API v1 endpoints. We encourage our customers to start using the new API v2 because API v1 will be removed at 2020 Q1.

das-Face v2.0 (2019-Q2)

  • New API v2 with better semantics, syntax and improved error handling.
  • New endpoint /v2/credential/photo to generate a biometric credential from an image. The returned credential contains the biometric data of the face found in the image.
  • New endpoint /v2/verification/credential to compare the image of a face with a previously generated biometric credential.
  • Deprecation of API v1 endpoints. We encourage migration to API v2 as soon as possible.