Risk category | Risk tag | Description |
Device risk (Native SDK) |
| Indicates that the device may be rooted or jailbroken. |
| Indicates that a hook framework may be active on the device. | |
| Indicates that the device may be connected through a VPN. | |
| Indicates that the application may be running on an emulator. | |
| Indicates that a system-level app cloning feature is in use. Important Android only. | |
| Indicates that a third-party app cloning tool is in use. Important Android only. | |
| Indicates that developer mode is enabled on the device. Important Android only. | |
| Indicates that debug mode is enabled. | |
| Indicates that the device has no SIM card installed. | |
| Indicates that a virtual video tool is installed on the device. | |
| Indicates that a virtual video tool is currently in use. | |
| Indicates that screen mirroring or recording is active. Important iOS only. | |
| Indicates that the device is running a high-risk custom ROM. Important Android only. | |
| Indicates that the device is running a non-standard ROM. Important Android only. | |
| Indicates automated operations, such as scripting or auto-clicking. | |
| Indicates that high-risk tools are installed on the device. | |
| Indicates that the application may be running on a cloud phone. Important Android only. | |
| Indicates that the device's bootloader is unlocked. Important Android only. | |
| Indicates the device has a low boot count, suggesting it is new or temporary. Important Android only. | |
| Indicates that the screen remains on while the device is charging. Important Android only. | |
| Indicates that the device has no screen lock enabled while charging. Important Android only. | |
| Indicates that the device is currently charging via USB. Important Android only. | |
| Indicates device spoofing, such as tampering with the device model or other characteristics. | |
| Indicates that anomalous ports are open or in use on the device. Important Android only. | |
Device risk (Web SDK) Important
Due to browser sandbox restrictions, the detection capabilities of the Web SDK are limited to the browser layer. It cannot access low-level information such as hardware sources or drivers, which creates bottlenecks in detecting injection techniques. Therefore, it is recommended to combine server-side image liveness detection and business risk control measures to build a multi-layered defense-in-depth system, rather than relying solely on the Web-side Device Guard for decision-making. |
| Indicates that the session may originate from a virtualized or automated browser environment. |
| Indicates that a virtual camera may be installed. | |
| Indicates that a virtual camera may be in use. | |
| Indicates the use of automation tools. | |
| Indicates that browser parameters may have been tampered with. | |
| Indicates that the page's JavaScript (JS) is being debugged. | |
| Indicates that the session may originate from a cloud phone environment. | |
| Indicates activity associated with a malicious crawler or scripted protocol abuse. | |
| Indicates that cookies are disabled in the browser. | |
| Indicates that the browser is in incognito mode. | |
| Indicates that the browser's media stream API is being hooked. | |
| Indicates that the verification page was accessed without a referrer. Note This risk tag requires integration with ID Verification and is not available in standalone Device Guard deployments. | |
| Indicates a mismatch between the verification page URL and the device. Note This risk tag requires integration with ID Verification and is not available in standalone Device Guard deployments. | |
Device token risk |
| Indicates that the |
| Indicates that the | |
| Indicates that the | |
| Indicates that the | |
General |
| Indicates a mismatch between the Note If this risk tag appears frequently, check for inconsistencies between the |
| Indicates that Device Guard failed to initialize due to a poor network condition. Note If this risk tag appears frequently, review the client-side integration. This issue often occurs when the client initialization and the | |
| Indicates that Device Guard failed to report some collected data. Note If this risk tag appears frequently, review the client-side integration. This issue often occurs when the client initialization and the | |
Customer scenarios |
| Indicates a medium-risk environment associated with fraudulent activities. This is a composite assessment. Note This composite risk tag combines multiple indicators based on extensive analysis of online threats and attacks. |
| Indicates a device the customer has added to an allowlist. By default, its | |
| Indicates a device the customer has blocklisted for repeated malicious activity. By default, its | |
Large model detections Note These risk tags are only available in the |
| Indicates that the large model has identified a high-risk environment during the verification process. Note This composite risk tag results from a multi-factor analysis that uses large model inference and threat intelligence. |
| Indicates that the large model has identified a high-risk environment associated with fraudulent activities. Note This composite risk tag is derived from a multi-factor analysis of accumulated threat intelligence and attack patterns. | |
| Indicates a match with the large model's knowledge base of known risks. Note This risk tag results from a multi-factor analysis that uses the large model to detect fraud rings. | |
| Indicates high-risk behavior identified by the large model. Note This risk tag results from the large model's multi-factor analysis of behavioral patterns. | |
Others |
| Indicates a low-risk device. This tag is returned when no other risks are detected. |
| Indicates that no data was returned. The system returns this tag if it cannot retrieve risk data due to an error in ID Verification. |