Account
Account Security
Everything that hardens your VulnRadar account and controls what it keeps about you: two-step verification, the devices and sessions that can sign in, which social logins are attached, the emails you get, and how to pull your data out or delete the account entirely. All of it lives under Profile, this page is the map.
- 2FA methods
- 2
- Backup codes
- 8
- Trusted-device window
- 30 days
Overview
Your password is the floor, not the ceiling. On its own it means a single leaked or reused credential is enough to sign in as you. Everything below sits on top of it: a second factor so a stolen password is not enough, a session list so you can see and cut off anything you do not recognise, and privacy controls over what a scan leaves behind and what VulnRadar stores.
Every control here is under Profile, split across four tabs: Security (password, two-step verification, sessions), Connections (social logins), Notifications (which emails you get), and Privacy (data export, scan visibility, account deletion). Changing anything sensitive asks for your current password again, so a hijacked session alone cannot quietly rewire your security.
Two-step verification
Two-step verification (2FA) asks for a second code after your password at sign-in. VulnRadar offers two methods and you run one at a time: a rotating code from an authenticator app, or a code emailed to you. Turning either one on, off, or switching between them asks for your current password first. To switch, turn the active method off, then turn the other on.
Authenticator app (TOTP)
Works with Google Authenticator, Authy, 1Password, or any other TOTP app. In Profile > Security, under Two-step verification, choose Set up authenticator app and follow the two steps:
- Scan. Point your app at the QR code, or type the shown key in by hand if you cannot scan. The app starts showing a 6-digit code for VulnRadar that changes every 30 seconds.
- Verify. Enter the current 6-digit code plus your account password. The password step is what stops someone with only a borrowed session from enrolling their own device. Get it right and 2FA is on, and your backup codes appear once.
The secret that seeds those codes is stored encrypted at rest (AES-256-GCM), and the server refuses to set up app 2FA at all unless that encryption key is configured, so a database read never yields a usable seed. If a code is rejected, it is almost always because the 30-second window rolled over: use the one showing right now. Turning the app method off later also asks for your password and deletes both the enrolled secret and every backup code.
Email codes
Simpler to set up and nothing to install. In Profile > Security, choose Turn on email codes and confirm your password. After that, every sign-in sends a fresh 6-digit code to your account email, which you enter to finish signing in. There are no backup codes for this method, because access to your inbox is already the recovery path. Turning it off asks for your password again.
Backup codes
When you turn on the authenticator-app method, VulnRadar issues eight single-use backup codes. Each one signs you in exactly once if you lose your phone, so they are the difference between a lost device and a lost account. They are shown a single time. Copy or download them then, and keep them somewhere that is not the phone running the authenticator.
- Each code is 80 bits of randomness as 20 uppercase hex characters, grouped in fives:
3F9A1-0C7E2-BD48F-16A05. There are no letters past F. Each one works exactly once; using it consumes it. - VulnRadar stores only a hash of each code, never the code itself, so nobody, staff included, can read them back to you. Lose them and your only route back in is the authenticator app.
- The Security tab shows how many are left (for example
3 of 8 left). When you are running low, useNew codesand confirm your password to issue a fresh set. Generating a new set immediately invalidates the old one. - Backup codes exist only for the authenticator-app method. The email method does not use them.
Sessions and trusted devices
A session is one signed-in browser or device. A trusted device is one that has already cleared 2FA and is allowed to skip the second-factor prompt for a while. Both are listed and revocable in Profile > Security, and they are the fastest way to answer "is anyone else in my account".
Active sessions
The Active sessions list shows every device currently signed in: a summary of the browser and OS, the IP address, and when it signed in. The one you are on is tagged This device. Anything you do not recognise, sign it out with one click.
- IPv4 for IPv6 logins: when your connection came in over IPv6, the list also shows a usable IPv4 address for that session where it could be captured, so the address is something you can actually recognise rather than a long IPv6 string.
- You cannot single-out your current session: signing out the device you are on is what "Sign out everywhere" is for. Every other session can be revoked individually, and doing so ends it immediately.
- Nothing replayable is exposed: the list never contains the real session token. Revoking works through an opaque identifier that only resolves to your own sessions, so the list cannot be used to touch anyone else's.
Trusted devices
At the 2FA prompt you can tick remember this device. That device then skips the second-factor code on future sign-ins for 30 days (the default), after which it has to pass 2FA again. Do this only on hardware you control, never on a shared or public machine.
Every remembered device shows up under Trusted devices with its name, IP, and when it was last used. Remove one and its next sign-in has to clear 2FA from scratch. The token that marks a device as trusted is held in a locked-down cookie and is never shown in the list, so the page can flag which row is "this device" without ever handing out a credential that skips your second factor.
Sign out everywhere
The danger-zone button at the bottom of the Security tab ends every session on every device, including the one you are using. Reach for it if you think someone else has access: it drops you back at the sign-in page and forces your password (and 2FA) again everywhere. If Session Alerts are on, you also get an email confirming it happened.
Sign in with Google, GitHub, Discord
You can sign in with Google, GitHub, or Discord instead of, or alongside, a password. On a first sign-in through a provider, VulnRadar creates an account for you automatically. Which buttons appear depends on the deployment: a provider only shows up once the operator has configured it, so a self-hosted instance may offer fewer than the hosted one.
- Link a provider to an account you already have from Profile > Connections. Linking Google or GitHub lets you use that button next time in addition to your password. Discord has its own connect flow on the same tab.
- Unlink a provider from the same place when you no longer want it attached. If a provider is the only way into your account, set a password first so you do not lock yourself out.
- No password yet? An account created purely through a provider has no password on file. The Security tab lets you add one, which is worth doing so a provider outage never becomes a lockout.
Notifications and posture digest
VulnRadar talks to you in two places: the in-app bell (the notification centre, for things like team invites and announcements) and email. Which emails you get is entirely up to you, set in Profile > Notifications. The security-related categories are the ones worth leaving on.
| Category | What it tells you | Default |
|---|---|---|
| Security Alerts | Unusual activity and account-compromise warnings. This is how you find out about access you did not grant, so it stays on regardless. | Always on |
| Login Alerts | A sign-in from a new device or location. | On |
| Password Changes | Your password was changed or a reset was requested. | On |
| 2FA Changes | Two-step verification was turned on, off, or its backup codes were regenerated. | On |
| Session Alerts | Sessions were revoked, including a sign-out-everywhere. | On |
| Posture Digest | A periodic summary across every site you have scanned. Opt-in, see below. | Off |
The weekly posture digest
The posture digest is the one email that looks across your whole account instead of a single scan. Once a week it rolls up every site you have scanned into one message: new critical and high findings since last time, and whether your open-issue count is trending up or down. It is off by default and never turns itself on, flip the Posture Digest toggle under Notifications to start receiving it. Findings you have marked as false positives are left out, so the trend line reflects real work.
Your data and privacy
VulnRadar encrypts your data at rest and in transit and handles it under GDPR and other applicable data-protection law. The controls for seeing, restricting, and removing that data are in Profile > Privacy. For the full policy, see the Privacy Policy.
Export your data
Export your data on the Privacy tab downloads a single JSON file with everything tied to your account: profile, sessions, trusted devices, API keys and their usage logs, scan history and findings, tags, webhooks, teams, billing history, notifications, and more. It is the fastest and most complete answer to "what do you actually hold about me".
- A 30-day cooldown applies between fresh exports (the operator can change this on a self-hosted instance). The tab shows when the next one is available.
- Your last export stays available to re-download with no cooldown, so you never have to burn a fresh request just to grab the file again.
- Secrets are left out by design. Password hash, the 2FA seed, backup codes, and any encrypted provider or API tokens are never included in the export.
Profile > Privacy > Export your data > Download now
-> vulnradar-data-export-YYYY-MM-DD.jsonScan and share privacy
Two independent defaults on the Privacy tab control how visible your scanning is. Both have per-scan and per-share overrides, so a default never traps you.
- Scan visibility. By default a completed scan writes a snapshot to a public page at
/host/<hostname>. Turn offScans are public by defaultto keep new scans private unless you say otherwise, either per scan on the scan form or from a scan's own menu afterwards. - Public Scans directory. Separately, when you share a scan, the share link can be listed in the public Public Scans directory. Turn off
List new shares in Public Scans by defaultto keep new share links off that directory. The link still works for anyone you send it to, it just is not browsable by strangers.
Delete your account
The danger zone at the bottom of the Privacy tab permanently deletes your account and everything attached: API keys, scan history, exports, and the rest. To confirm you type DELETE and re-enter your password (an account with no password, created through a provider, skips the password step). The purge runs as one transaction, and there is no recovery afterwards.