Hello,
We are configuring FACEIO for Mediva, a healthcare shift-management platform. Facial authentication and liveness detection will validate professionals during check-in and check-out.
We plan to use these settings:
Prevent duplicate enrollment: Enabled
Deepfake and face-spoof protection: Enabled
Prevent minors from enrolling: Enabled
Always require PIN during authentication: Disabled
Reject weak PINs: Enabled
Enforce PIN uniqueness among users: Disabled
Reject missing Origin/Referer: Enabled
Authorized domain: plantoes.mediva.app.br
Country restriction: Disabled
Application metrics: Disabled
Webhooks: Enabled
Could you please confirm whether this configuration is recommended for our use case, especially regarding liveness security and PIN requirements?
Thank you.
Best Practices for FACEIO Configuration in Healthcare Shift Management
✓ Accepted Solution
Dear Daniel,
Yes, this is adequate. However, we strongly recommend that you do not disable the PIN code confirmation. It serves as your primary security feature right now.
Please note that our deepfake and face anti-spoofing features are currently reserved exclusively for the Business plan. These features will be generalized to the Pro plan in November. Until then, keeping the PIN code active is essential for your security.
Let us know if you need any further assistance.
Olá Daniel,
Obrigado por entrar em contato conosco. Sim, isso é adequado.
No entanto, recomendamos fortemente que você não desative a confirmação por código PIN. Ele atua como seu principal recurso de segurança no momento. Por favor, note que nossos recursos de detecção de deepfake e anti-spoofing facial estão atualmente reservados exclusivamente para o plano Business. Esses recursos serão generalizados para o plano Pro em novembro. Até lá, manter o código PIN ativo é essencial para a sua segurança.
Informe-nos se precisar de mais assistência.
Equipe de Suporte FACEIO
