Security at Varaxon
Your clients' scan data, and exactly where it goes.
Scan Hub holds vulnerability data about the systems you look after. Here is how it moves, who can see it, how long we keep it, and what we can and can't prove to you yet.
In your scan exportExample Nessus row
- host
- fs02.northside-clinic.local
- ip
- 10.20.4.15
- mac
- 00:1A:2B:3C:4D:5E
- contact
- j.martin@northside-clinic.com
- port
- 22/tcp
- finding
- CVE-2024-6387 OpenSSH regreSSHion
What Anthropic's AI models receive
- host
- HOST-0001
- ip
- IP-0001
- mac
- MAC-0001
- contact
- EMAIL-0001
- port
- 22/tcp
- finding
- CVE-2024-6387 OpenSSH regreSSHion
Where we stand today
CSA STAR Registry
SOC 2
No report yet
ISO 27001
Not certified yet
Breach notice
Within 24 hours of confirming
Data stored in
The United States
Our STAR entry is CSA's questionnaire (CAIQ v4.1), answered by us and published on CSA's public registry since October 25, 2026. It is not an audit or a certification. We don't hold a CMMC assessment or FedRAMP authorization either. Our written security policies are mapped to SOC 2 and ISO 27001 controls, and we'll complete your security questionnaire.
The path a scan takes
Five stops, from the moment you upload to the moment it's gone. All customer data is stored in the United States.
You upload a scan or connect a tool
Scan exports, PDF reports, upload API files, or a Microsoft Defender or ConnectSecure pull. Everything travels over HTTPS, from users who have all passed MFA.
- Where
- Supabase private storage, US East
- Kept
- Raw file deleted within 7 days
Our workers read it
Report workers on our own server turn the raw file into findings. Nothing in the file is executed, and unsafe XML is refused.
- Where
- OVHcloud server, United States
- Kept
- Processing only
Anthropic's AI models see placeholders
The model gets the placeholder version shown above. The key that turns HOST-0001 back into a real name stays with us, and Anthropic's terms prohibit training on the data.
- Where
- Anthropic, under its commercial terms
- Kept
- Deleted by Anthropic within 30 days, subject to its legal exceptions
Findings and reports stay walled off
Row-level security in the database limits each organization's data to its own members. Owners and admins can export everything, or delete a client, a scan or the whole organization, at any time.
- Where
- Supabase, US East, encrypted at rest
- Kept
- Until you delete it or close the account
Backups expire on their own
The database is backed up daily and every backup is encrypted. Raw uploads and raw connection pulls are never kept past 7 days.
- Where
- Supabase, encrypted
- Kept
- Each daily backup expires after 7 days
What protects it
Who can get in
MFA for every user
Including Microsoft and Google sign-in. The database refuses customer data to any session without the second factor.
Walled-off organizations
Row-level security on every table. Invite links expire after an hour.
An activity log you can read
Security-relevant actions are logged and visible to your owners and admins, and customers can't edit or delete them.
How it's kept
Encrypted in transit and at rest
HTTPS only, with HSTS. Supabase encrypts the database, storage and backups.
Files behind 60-second links
Private storage, reached only through signed links that expire after a minute.
Read-only connections
Microsoft Defender access is read-only and per tenant, and your admin can revoke it in Entra ID. Connection secrets sit in an encrypted vault.
What leaves, and when
People approve tickets
Nothing reaches HaloPSA or ConnectWise PSA until someone on your team reviews and approves it.
Upload API keys you control
Stored only as one-way hashes, with optional expiry, IP allow lists and instant revocation.
Dependencies audited weekly
Every Python and JavaScript library is checked against public vulnerability databases.
Who else touches it
Our subprocessors, and whether each one ever sees scan data. The Data Processing Addendum is the full, binding list, and we give 30 days' notice before adding one.
| Provider | What it does | Sees scan data? |
|---|---|---|
| Supabase | Database, sign-in, file storage, vault and backups (US East) | Yes |
| OVHcloud (OVH US) | Servers running the app and report workers (US) | Yes, while processing |
| Anthropic | AI models for reading files, enrichment, reports and ticket drafts | With placeholders, as DPA section 4 describes |
| Resend | Service email | Client names and finding titles only |
| Stripe | Payments and billing | No |
| Cloudflare | Bot check on sign-in and sign-up pages | No |
| Sentry | Error monitoring, with identifiers removed | No |
| Namecheap (Private Email) | Our business email | Only what you email us |
Microsoft, ConnectSecure, HaloPSA and ConnectWise are your own providers, not our subprocessors. We exchange data with them only when you set up a connection.
Security documents
Public now
On request
- A countersigned DPA (request it)
- Your security questionnaire, completed (your own, SIG Lite or CAIQ)
- Software bill of materials (CycloneDX)
Check us yourself
- Qualys SSL LabsA+ for the app and this site when we checked on 25 October 2026.
- Mozilla ObservatoryA+ for the app when we checked on 25 October 2026.
Report a security issue
Email support@varaxontech.com with "Security" in the subject. We acknowledge reports within 3 business days, and our disclosure policy gives good-faith researchers safe harbor.
For defense contractors and their MSPs
Vulnerability scan results are normally treated as Security Protection Data under the CMMC program rule, not as CUI. A tool that holds only that data is reviewed inside your own assessment scope as an external service provider. Scan Hub is not a place to store CUI, classified or export-controlled information, and our Terms say so. Confirm the details with your assessor or RPO.
