Data handling & retention¶
This page explains what SheerSight collects, how it's protected, and how long it's kept. For the underlying trust model, see Security & trust.
What SheerSight collects¶
SheerSight collects read-only audit and security-finding data from the sources you connect — for example sign-in and admin activity, cloud control-plane events, and endpoint/EDR findings. It uses the least-privilege, read-only credentials you create (see Connecting sources); it never has write access to your systems and never needs inbound access to your network.
How it's protected¶
- Your own instance. Your raw data and alert details live on your own dedicated instance, never shared with other customers. The console is shared infrastructure that holds short summaries, kept separate by customer and checked on every request.
- Encrypted credentials. The credentials you connect are encrypted in your browser and decrypted only on your instance — SheerSight relays ciphertext only.
- Least privilege & minimization. Access is scoped to the minimum needed, and monitoring data is minimized or de-identified where it doesn't need to carry identifying detail.
What reaches the console¶
Your raw events and full alert details stay on your dedicated instance. The console receives short summaries so it can draw charts and counts: alert and incident IDs, rule names, the entity involved (a user, host or IP address), times, dispositions, daily triage counts and source health. Anything that looks like a secret is removed before it is sent. The console keeps these summaries for 90 days. See How SheerSight works.
Who can see your data¶
Members of your organization, and SheerSight analysts running the service for you. No other customer can see it. Every action taken on your instance is logged in the console's tamper-evident Audit log. See Signing in, team and roles.
How long data is kept¶
| Data | Retention |
|---|---|
| Alerts, detections, and incidents | 15 months |
| Raw source data (the underlying logs and events collected from your tools) | 30 days |
Keeping detections and incidents for 15 months preserves the security record you'd want for investigation and reporting, while raw source data is held for a shorter 30-day window for triage and lookback.
Where your data runs¶
Your dedicated instance runs in a region agreed with you during onboarding.
Offboarding¶
If you stop using SheerSight, contact your SheerSight team to arrange handling of your data. See Support.