Video Injection Prevention
Video Injection Attack Prevention is securing the identity verification from injecting images into the verification process, whether deepfakes or images of the victim, and from man-in-the-middle attacks.
Capture components
Mobile and web Capture components collect the images as well as the camera and platform metadata, encrypt it and return in a binary file. These files need to be delivered by your solution to the platform's Workflow API, in order for the platform to check for injection attacks.
Considerations on Platform and Browser
If your project requires a very high level of security, preventing the web application from running on desktops or laptops is recommended. These platforms provide more tools to disassemble and attack your application.
You may also increase the security by restricting the use of the Firefox browser, as this browser guarantees the highest level of privacy for the fraudsters. Firefox is marked as deprecated and will be removed in the next major release of Web Components (9.x.x).
Size of the binary content data
The size of the data to be transferred will depend on the camera resolution (whether it is 1920x1080 or 1280x720 pixels), on the quality of image and noise and on the background in the image. You can assume following sizes for the following components with a tolerance of +10% / -50%.
| Capture component output | Average data size @ 1920x1080 |
|---|---|
| Document auto capture | 600 kB |
| Face auto capture (passive) | 300 kB |
| Smile Liveness capture | 600 kB |
| Multi-range Liveness capture | 1 200 kB |