Security Considerations

Security Considerations

Security Considerations

Relock replaces token-based session trust with device-bound, continuously rotating cryptographic verification with high-frequency key rotation

Relock replaces token-based session trust with device-bound, continuously rotating cryptographic verification with high-frequency key rotation

Modern web authentication systems rely heavily on transferable artifacts: passwords, bearer tokens, session tokens, refresh tokens, and static client secrets. Once issued, these artifacts often function as reusable proof of identity. As a result, theft of authenticated sessions has become one of the dominant causes of account takeover, unauthorized access, and data breaches.

Relock addresses this problem by replacing token-based session trust with device-bound, continuously rotating cryptographic verification with high-frequency key rotation. At the core of this high-assurance relationship is an encrypted key, rotated with high-frequency, referred to as the Tesseract. For every request to a protected application, the in-browser CryptoTag derives a one-time integrity token from the current Tesseract state.

Relock is not a replacement for primary authentication mechanisms such as passwords, passkeys, or federated SSO. Instead, it acts as a specialized continuous trust layer for session integrity across applications, identities, and devices. It strengthens existing identity systems by ensuring that authenticated sessions cannot be reused, replayed, smuggled, or cloned outside the legitimate browser environment.

Modern web authentication systems rely heavily on transferable artifacts: passwords, bearer tokens, session tokens, refresh tokens, and static client secrets. Once issued, these artifacts often function as reusable proof of identity. As a result, theft of authenticated sessions has become one of the dominant causes of account takeover, unauthorized access, and data breaches.

Relock addresses this problem by replacing token-based session trust with device-bound, continuously rotating cryptographic verification with high-frequency key rotation. At the core of this high-assurance relationship is an encrypted key, rotated with high-frequency, referred to as the Tesseract. For every request to a protected application, the in-browser CryptoTag derives a one-time integrity token from the current Tesseract state.

Relock is not a replacement for primary authentication mechanisms such as passwords, passkeys, or federated SSO. Instead, it acts as a specialized continuous trust layer for session integrity across applications, identities, and devices. It strengthens existing identity systems by ensuring that authenticated sessions cannot be reused, replayed, smuggled, or cloned outside the legitimate browser environment.

Read full report

Explore the full report

Explore the full report

Check more resources

Check more resources

Check more resources

END

  • TOKEN THEFT

  • SESSION HIJACKING

  • ACCOUNT TAKEOVER

  • MFA BYPASS

© 2026 Relock, Inc. | 701 Brazos St., STE 150 | 78701 Austin, TX

END

  • TOKEN THEFT

  • SESSION HIJACKING

  • ACCOUNT TAKEOVER

  • MFA BYPASS

© 2026 Relock, Inc. | 701 Brazos St., STE 150 | 78701 Austin, TX