Zero Trust Device Provisioning with Deepfake Defense™

Enhance Cloudflare Access with Deepfake Defense™ identity verification.

Nametag's industry-first integration with Cloudflare helps IT and security teams combat advanced hiring and third-party supplier fraud, including DPRK IT workers, by verifying the actual person setting up a new device before they reach your networks and apps.

When a new hire or contractor first authenticates to internal systems or begins credential enrollment, Cloudflare Access invokes Nametag’s Deepfake Defense™ identity verification engine to verify that the user is both a real person and the right person.

How to Use It: Nametag + Cloudflare

This integration is architected to be both highly flexible and as turnkey as possible.

Here are two examples of how you can use this integration to verify new users at the moment they connect a new device. You can get started using our dev docs here.

Example Implementation 1: Using Directory credentials for Login

1. IT creates a shell account for a new employee in your identity provider.
2. IT configures and ships a laptop, and shares their username and password.
3. In order to access applications, the employee authenticates via Cloudflare.
4. Cloudflare Access uses Nametag as the authentication factor. If the user passes verification, they can proceed to enroll in MFA and then access applications.
5. If the user's verification is rejected, their access is blocked. They can appeal, but your IT and security teams are notified of the failed verification and why it failed.

Example Implementation 2: Using OS Onboarding for Device Login

1. IT creates a shell account for a new employee in your identity provider.
2. IT has a new device shipped to the employee directly from Apple, Microsoft, etc.
3. The new employee goes through the standard MacOS or Windows device setup process, which includes setting a username and password for the device.
4. In order to access applications, the employee authenticates via Cloudflare Access, which uses Nametag identity verification as the authentication factor.
5. If the user passes verification, they can proceed to claim their directory credentials, enroll multi-factor authentication, and then access your networks and applications.
6. If their verification is rejected, the user's access is blocked. They can appeal, but your IT and security teams are notified of the failed verification and why