Your raw security data stays on your dedicated instance. The shared console receives selected summaries and passes encrypted credentials to the instance.
A dedicated instance, a shared console
Your organization has its own security instance for collection, detection, raw events and full alert records. The console is shared infrastructure, with customer-scoped access checks on every request.
Sheer Safe operates your instance and can access it for maintenance and support. Members of your organization use the console within their assigned roles.
Credentials encrypted before relay
When a source requires a secret, your browser encrypts it for the instance before sending it. The console relays ciphertext, and decryption happens on the dedicated instance.
AWS follows a different path: a read-only role authorizes collection without a long-lived access key to relay.
API collection and sensor permissions
API source grants are limited to the audit activity or security findings being monitored. Host sensors and agents require a separate deployment with permissions documented before installation. Any response or remediation authorization follows your engagement scope.
Collection connects outbound to supported APIs. Any deployment-specific management access is documented during setup.
How the instance checks operational instructions
Operational instructions sent to the instance are signed and checked before execution. The agent runs a defined set of operations such as starting a supported source or applying an approved upgrade.
Access and accountability
Console access is checked against your organization’s membership and role. Sensitive administrative actions use additional authenticator verification. Service actions and customer activity are recorded for review.
The audit record uses a hash chain to help detect changes. It provides evidence of tampering, but cannot guarantee that records are impossible to alter.
What reaches the console
Selected alert and incident summaries, rule and entity fields, timestamps, dispositions, daily counts and source health. Raw source events and full alert bodies remain on your instance. Summary fields can still identify a user, host or IP address.
Published retention
These periods refer to different records. They should not be read as one retention period for all data. Confirm the agreed configuration during onboarding.
Raw source events: 30 days on your dedicated instance.
Alerts, detections and incidents: 15 months on your dedicated instance.
Console summaries and daily counts: 90 days in the shared console.
Hosting and service providers
The dedicated-instance region is agreed during onboarding. Published infrastructure providers include AWS for customer instances and Cloudflare for the console and web infrastructure.
Revoking source access
Ask your engagement contact to confirm the disconnect and vendor-side revocation steps for your source. Stopping collection and revoking the vendor grant are separate operations. Follow the current source documentation before removing a grant or role.
Security questions
For security architecture or vulnerability reports, contact security@sheersafe.com. For account or setup help, contact support@sheersafe.com.
SheerSight by Sheer Safe Pvt Ltd
Included at no extra platform charge with every Sheer Safe engagement.