Skip to content

Compliance (coming soon)

Not available yet

Compliance is in development. Nothing on this page is in the console yet, and details may change before launch. We'll add step-by-step guides here as each part ships. Want early access? Email support@sheersafe.com.

SheerSight Compliance will help you get and stay audit-ready, using the same tools you've already connected for security monitoring. No second set of integrations, no second vendor, and the same sign-in.

Frameworks

At launch:

  • ISO 27001
  • SOC 2
  • HIPAA
  • GDPR
  • DPDPA (India's Digital Personal Data Protection Act)

Each framework gets its own page showing:

  • a readiness score: the share of applicable controls that are passing,
  • progress bars for controls, automated tests, policies and documents,
  • a breakdown by section of the framework (for example SOC 2's trust services criteria or ISO 27001's Annex A themes), so you can see where the gaps are,
  • once there are two weeks of history, an estimate of when you'll be audit-ready at your current pace.

One control can count towards several frameworks, so work you do once shows up everywhere it applies.

Controls: what's failing and how to fix it

Controls are listed with the ones that need you most at the top: failing first, ordered by how critical they are and by their fix-by date.

  • Fix-by dates. When a control starts failing it gets a deadline based on how critical it is. Your admin can adjust these targets.
  • How to fix. Open any control to see exactly which resources are failing (for example the users without MFA, or the storage bucket without encryption) and step-by-step instructions for each way you might fix it: the vendor's web console, its command-line tool, or infrastructure-as-code. Commands come pre-filled with the failing resources and a copy button. SheerSight never runs them for you.
  • About this control. A plain explanation of what's checked, the exact pass/fail rule, which integration and read-only permission it uses, how often it runs, and whether the evidence is live. Your auditor can see this too, so they know how each piece of evidence was collected.

Automated tests

Your dedicated instance checks how your connected tools are configured, on a schedule (hourly by default), and feeds the results into the matching controls. The first tests at launch cover:

  • Microsoft Entra ID: multi-factor authentication enforced for every user.
  • AWS: storage and databases encrypted.
  • GitHub: branch protection on your important repositories.
  • Google Workspace: 2-step verification enforced.

More tests follow after launch. Admins can also re-run a test on demand.

As with security monitoring, the tests run on your dedicated instance with the read-only credentials it already holds. Only pass/fail results and the IDs of affected resources reach the console. Never your credentials, never raw data.

Security monitoring as evidence

Your SheerSight alerts, incidents and response history count as evidence for monitoring and incident-response controls, automatically.

Policies

  • Templates written for each framework, to start from instead of a blank page.
  • Edit in the console, send for approval, and publish. An approver can't approve their own draft unless an admin allows it.
  • Versions. Every published version is kept. When you publish a new one, you write a short note saying what changed.
  • Yearly reviews. Reminders when a policy is due for its yearly review.

Employee policy acceptance

  • Employees get an email with a sign-in link to a simple page where they read and accept the policies assigned to them. They don't need a console account.
  • When a policy changes, people who accepted an earlier version see the "what changed" note at the top before accepting again.
  • Policies can be re-accepted every year, as most frameworks expect.
  • Every acceptance records who accepted, which version, when, and how they signed in, and is kept as audit evidence.
  • Reminders go out by email, with a summary in your Slack channel.
  • A tracker shows who has accepted and who still needs to.

People

Your employee list syncs from Google Workspace, Microsoft Entra ID or JumpCloud, with checks for onboarding and offboarding (for example, that a leaver's accounts were disabled).

Audits and auditors

  • Set up an audit for a framework and an observation period.
  • Invite your auditor by email. They get read-only access to that audit only: its frameworks, controls, evidence and policies, for a limited time.
  • Export the evidence for an audit as one package that comes with a way to check nothing in it was changed after export. Only admins (with their authenticator code) and the invited auditor can export.

Who can do what

Compliance uses the same team roles as the rest of SheerSight:

  • Admins enable frameworks, publish policies, invite auditors and export evidence. Sensitive actions ask for an authenticator code.
  • Analysts work on controls and evidence and draft policies.
  • Viewers can see everything but change nothing.
  • Auditors see only the audit they were invited to, read-only.
  • Employees only see the policies they've been asked to accept.

Every change is recorded in your tamper-evident activity log.

How long compliance records are kept

Planned retention, so your evidence covers the periods auditors look at:

Record Kept for
Automated test results About 400 days
Readiness history 3 years
Policy acceptances 7 years

Uploaded documents are stored encrypted, separately for each customer.

Planned after launch

  • A risk register, so you can record and treat risks (needed for ISO 27001).
  • Creating Jira or Linear tickets from a failing control.
  • Access reviews across your connected apps.
  • A one-page monthly summary of security and compliance for your board.
  • UK Cyber Essentials and Australia's Essential Eight.
  • Later: a public Trust Center page for your customers, and a fuller auditor workspace.