Skip To Content

Security

Your Signals,Handled With Care

Vantor reads the most sensitive telemetry your team has. Here is exactly how we encrypt it, where it lives, who can reach it and how long we keep it.

Settings › Security

Region: Europe

Audit Log

Checkout Platform Workspace

Recording
  1. 14:13:05

    A. Kaur Signed In: Single Sign On, Portwell Office

  2. 14:12:28

    Support Access Approved: Ticket 5512 For 2 Hours, By J. Reyes

  3. 14:11:51

    T. Sato Exported Signals: Ledger API, Last 24 Hours

  4. 14:11:14

    Vantor Opened Incident: Incident 2291, Severity Two

  5. 14:10:37

    J. Reyes Changed Role: A. Kaur To Responder

  6. 14:10:00

    M. Okafor Ran Runbook Step: Roll Back Deploy 4127

Entries cannot be edited or deleted.

Export Log

Access Controls

Roles In This Workspace

Single Sign On
OwnerResponderViewer
Read Signals
Join Incident Rooms
Run Runbook Steps
Export Data
Change Roles And Settings

Staff Access

Off, Until You Grant It

2 Approvers

At A Glance

Encryption For Every Signal At Rest, With Keys You Can Rotate
256 Bit
To Choose From At Setup, With Data Kept In That Region
3 Regions
Default Retention On Team And Scale, Shorter On Request
13 Months
Needed To Approve Any Staff Access To Production Data
2 People

Describes the planned setup for the private beta.

How Data Is Handled

Plain Answers, No Fine Print

Six things every security review asks about, written the way we would want them explained to us.

  1. 01Encryption

    Encrypted In Transit And At Rest

    Signals are encrypted by the collector before they leave your host and stay encrypted in our store. Scale plans can bring their own keys and rotate them on their own schedule.

    • TLS 1.3 Between Every Hop
    • 256 Bit Encryption At Rest
    • Customer Managed Keys On Scale
  2. 02Regions

    Your Data Stays Where You Put It

    Choose North America, Europe or Asia Pacific when you create a workspace. Raw signals, incidents and backups stay in that region. Support staff outside it see only what you share in a ticket.

    • Three Regions At Launch
    • Backups Kept In Region
    • Region Locked Per Workspace
  3. 03Retention

    Kept As Long As You Need, No Longer

    Raw signals are kept for 14 days on Starter and 13 months on Team. Scale workspaces set their own retention per source. When data ages out it is deleted from the store and from backups within 30 days.

    • Retention Set Per Source
    • Deletion From Backups In 30 Days
    • Full Export At Any Time
  4. 04Access Controls

    The Right People, The Right Rooms

    Roles decide who can read signals, run runbook steps or change settings. Single sign on and automatic account removal keep your directory in charge of who gets in.

    • Owner, Responder And Viewer Roles
    • Single Sign On On Scale
    • Sessions Expire After 12 Hours
  5. 05Audit Log

    Every Action, Written Down

    Sign ins, role changes, runbook steps, exports and settings changes are written to an audit log that nobody can edit, including us. Filter it, export it, or stream it to your own store.

    • Tamper Evident Entries
    • 30 Days On Team, Unlimited On Scale
    • Export Or Stream Anytime
  6. 06Private Network Deploy

    Run Ingest Inside Your Network

    On Scale, the ingest edge can run inside your own private network. Raw logs never leave it. Only the summaries the correlation engine needs travel out, over a single outbound connection you control.

    • No Inbound Ports To Open
    • Raw Logs Stay In Your Network
    • One Outbound Connection

Security Program

What We Do Now, And What Comes Next

Vantor holds no security certifications today. This list is what is in place for the private beta and what we plan before and after general release.

  1. 01

    Least Privilege Access

    Staff reach production data only through a logged, time limited request that a second engineer approves.

    In Place
  2. 02

    Encrypted, Tested Backups

    Backups are encrypted, kept in region and restored into a clean environment every month to prove they work.

    In Place
  3. 03

    Dependency And Code Scanning

    Every change is scanned for known vulnerable packages and leaked secrets before it can merge.

    In Place
  4. 04

    Incident Response Plan

    A written plan with named owners, rehearsed every quarter. Affected customers hear from us within 72 hours of a confirmed breach.

    In Place
  5. 05

    Security Training

    Every engineer completes secure coding training when they join and again every year.

    In Place
  6. 06

    Independent Penetration Test

    We plan to commission an outside penetration test before general release and share a summary with customers on request.

    Planned
  7. 07

    Formal Security Audit

    We intend to begin a formal third party audit after general release. We will only describe it as complete once a report has been issued.

    Planned
  8. 08

    Public Trust Page

    A live page listing our subprocessors, regions and open security items, planned for general release.

    Planned

Responsible Disclosure

Found Something? Tell Us First

If you believe you have found a security issue in Vantor, write to us privately before sharing it anywhere else. We read every report and we will keep you posted until it is fixed.

  • 01

    A Reply In Two Business Days

    A named engineer confirms your report and tells you what happens next.

  • 02

    Good Faith Is Welcome

    We will not pursue research done in good faith that avoids customer data and service disruption.

  • 03

    Credit If You Want It

    With your permission, we thank you by name in the changelog once the fix ships.

Write To

security@vantor.example

What To Include

  • The Affected Page, Endpoint Or Collector
  • Steps To Reproduce, Plus What You Expected
  • Any Proof You Have, Without Real Customer Data
  • How You Would Like To Be Credited

Please do not test against workspaces you do not own, and give us a reasonable window to fix an issue before you publish it.

Questions

Asked In Every Security Review

Use the arrow keys to move between questions, and Enter or Space to open one.

Email The Security Team

Not today. Vantor is in private beta and we would rather tell you plainly than imply otherwise. The Security Program list above shows what is in place now and what we plan to do before and after general release.

Only when you open a support ticket and grant access, and only for the time you choose. Every staff session needs a second engineer to approve it and is written to your audit log.

No. Baselines and root cause rankings are learned per workspace and never shared between customers. Your signals are not used to train anything outside your own workspace.

Export everything at any time in open formats. When you close a workspace, we delete its data from the store within 7 days and from backups within 30 days, then confirm by email.

Yes. Beta teams can request our security overview and a call with the engineer who leads our security program. Write to the security team and we will set it up within a week.