Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Security & privacy

Security & privacy

How are sign-in sessions secured?

Quick answer

Cyberlop sign-in sessions use short-lived access tokens plus rotating refresh tokens, held in HttpOnly, SameSite and Secure cookies. Refresh tokens rotate each time, and reusing an old one revokes all sessions. The app stores session and API tokens only as hashes.

The short version

Your session has two parts. A short-lived access token proves who you are for a few minutes at a time, and a refresh token quietly renews it. Both live in cookies that scripts on the page cannot read.

FeatureWhat it does
Short-lived access tokenLimits how long a stolen token works
Rotating refresh tokenGives a new token on every refresh
Reuse detectionRevokes all sessions if an old refresh token appears again
HttpOnly, SameSite, Secure cookiesKeep tokens away from page scripts and plain HTTP
Hashed storageCyberlop stores only hashes of session and API tokens

How it works in Cyberlop

Each time the app refreshes your session, it rotates the refresh token and issues a new one. The API reference describes the call as one that rotates the refresh token and issues a new session. An old token stops working as soon as the new one exists.

If someone presents an old refresh token again, Cyberlop treats it as a sign of theft and revokes all sessions for that account. The real owner signs in again, and the thief is out.

The cookie flags do separate jobs. HttpOnly hides the cookie from page scripts. SameSite limits when other sites can trigger requests with it. Secure keeps it off plain HTTP. Signing out revokes the session and clears the cookies.

API tokens work differently. Cyberlop shows the raw secret once when you create it and keeps only a hash afterwards, so a lost token needs replacing and cannot be recovered.

What to do next

Questions? Use /contact.

Full tutorial

Cyberlop API tokens and permissions: how to issue and limit them

Step-by-step, with annotated screenshots.

Updated · Back to the help centre

Security question we did not answer?

Our team will answer it directly, or walk through it on a call with your security lead.