All Fortect Key models meet an IP67 rating—safe from accidental spills and dust.
<button onclick="startLogin()">Log in with Fortect Key</button> The code works with any FIDO2‑compatible token—including Fortect Key—without any vendor‑specific libraries. | Practice | Recommended Action | |----------|---------------------| | Device Inventory | Keep a real‑time list of all issued Fortect Keys in the Management Console. | | Policy Enforcement | Require biometric unlock for privileged accounts. | | Lost Device Procedure | Revoke the compromised key instantly from the console; issue a replacement. | | Firmware Updates | Enable automatic secure‑boot firmware checks (Fortect Key pushes updates over the air). | | Physical Security | Store unused keys in a tamper‑evident container. | | Audit Logging | Enable detailed logging of authentication attempts for SOC‑2 and ISO‑27001 compliance. | 9. Pricing & Availability | Tier | Devices Included | Management Console | Support | |------|------------------|--------------------|---------| | Starter | Up to 25 keys | Basic portal (user‑level) | Email support (24 h) | | Professional | 26 – 250 keys | Advanced portal + API access | Phone & email (8 h) | | Enterprise | 251 + keys | Unlimited keys, SSO integration, custom RBAC | 24/7 dedicated account manager | fortect key
Simply de‑provision the user in your IdP; the key is automatically revoked in the console, rendering it unusable. All Fortect Key models meet an IP67 rating—safe
// 3. Call the browser API – the Fortect Key will be presented as an option const assertion = await navigator.credentials.get( publicKey ); | | Policy Enforcement | Require biometric unlock