Skip to content

Connecting your sources

A source is a place detections come from: a cloud provider, a SaaS control plane, an endpoint tool, or a network sensor. This page explains how SheerSight connects to each one. Each source then has its own step-by-step page under Integrations.

The golden rule throughout: you only ever create a read-only credential, and it is encrypted in your browser before it leaves your screen. SheerSight relays ciphertext only. Nobody in the middle, including us, can read it. See Security for the full trust model.

Two sources have no credential at all: AWS uses a read-only role you create and can delete, and the on-box sensors (Suricata, Wazuh) run on your own instance. Their pages say so.

How connecting works

Every source follows the same shape:

  1. In the vendor (GitHub, AWS, Cloudflare, ...)
     create a READ-ONLY credential, one scope, no write access.
        |
  2. Paste it into the SheerSight console (Integrate -> Sources).
     It is encrypted IN YOUR BROWSER to your instance's key.
        | (only ciphertext is relayed, we never see the secret)
        v
  3. Your dedicated instance decrypts it locally and starts
     collecting, OUTBOUND ONLY. No inbound ports on the vendor
     or on your instance.
        |
        v
  4. Detections begin appearing in the console.

In the console, open Integrate -> Sources, click the source you want, fill in its fields, and press Connect (or Update credentials, see below). The value is wrapped to your dedicated instance's public key in the browser tab, and only the resulting ciphertext is sent. Your instance applies it shortly after, and the form tells you what happened.

Why it's safe to paste a token here

The console holds no long-lived secrets. The value you type is encrypted in the browser tab before any network request, delivered to your dedicated instance as ciphertext, and decrypted only there. The relayed credentials panel shows each one as pending, then applied once your instance picks it up.

Connect or update

Each source's form opens in one of two modes. The console picks the mode from whether that source has ever reported from your instance. You can switch with the link under the fields; switching keeps anything you've typed.

Connect is for a source your instance hasn't collected from yet. Every field is required. If one is empty, the form names it, for example "Fill in every field to connect: Delegated admin email.", and sends nothing.

Update credentials is for changing a value on a source that's already running, such as a rotated token. Fill in only the values you're changing. Blank fields keep their current value on your instance. If every field is blank, the form says "Enter at least one value to change."

The console can't see which values your instance holds. A source that reported once may have been disconnected since. If you're not sure, use Connect and enter every value.

Only operators and your team's admins see these forms. Analysts and viewers see each source's status without the form. See Signing in, team and roles.

What the form tells you

After you press Connect or Update credentials, the form waits for your instance and checks back every few seconds for up to two minutes. While the console is re-checking your instance's key, the button is briefly unavailable and the form says "Checking your instance…". Values you typed stay in the form only until you leave the page; the console never stores them.

Words in italics below are filled in by the form: the source's name, the names of the fields you changed, or the button you pressed.

Message What it means What to do
Waiting for your instance… The values were sent and your instance hasn't picked them up or restarted the source yet. Nothing. It usually takes under a minute.
Connected. Your instance applied the values and the source is running. Your instance stored every value and restarted the source. Nothing. The status badge updates in a moment.
Your instance applied the new field names and the source is running. Other values were kept. The update worked. Only the values you filled in changed. Nothing.
Your instance refused these values, so nothing changed. Reason. The source keeps running on its previous values. Your instance checked the values and turned them down before storing anything. The Reason sentence, one of the four listed below, is shown only when your instance reported one. The last sentence appears only after Update credentials. Fix what the reason names and press the button again. Your values are still in the form.
Your instance restarted source, but couldn't confirm the new values were applied. Check this source's status below. The source restarted, but application of the new values is unconfirmed. Check the source's status and verify the new credential is in use; a live status alone does not confirm that.
Your instance hit an error while applying these values, so it can't confirm they took effect. Check this source's status below before trying again. Something failed on your instance while it stored the values. Check the source's status before trying again. If it isn't live, contact us.
Your instance doesn't have field name. Enter every value to connect. You updated a source, but your instance has never been given that value. The form switches to Connect and marks the field. Fill in every field and press Connect.
The source was started, but setting up detections failed. Contact Sheer Safe and check this source's status below. The source's containers were started, but their detections were not set up. Check the card's health and contact support to finish setting up detections.
Your instance couldn't start source. Check this source's status below. The values were stored, but the source didn't start. Usually a scope or an ID is wrong on the vendor side. Read the status and the error help on the card, fix it on the vendor side, then update the value.
Your instance didn't get to this request in time. Your instance was busy or offline, and the request to start the source expired. The credential relay resolved, but application can still be unconfirmed. Press Retry starting this source. Don't paste the values again.
Your instance couldn't run this request. Contact Sheer Safe. Your instance turned the request down, or sent an answer the console can't make sense of. Only we can fix this. Contact support.
Your instance didn't pick up these values. Make sure it's running, then press Connect or Update credentials again. Your instance didn't collect the values before the waiting job expired or the relay was dropped. A late credential may still reach the instance; check the source's status before retrying. Make sure your instance is running, then press the button again. Your values are still in the form.
Your instance received this request, but couldn't confirm the new values were applied or whether the source restarted. Don't send them again; check this source's status below in a few minutes. Application and restart are unconfirmed after two minutes. Check status and contact support before resending.
Your instance has the new values, but hasn't reported whether the source restarted. Don't send them again; check this source's status below in a few minutes. Your instance has the values and was asked to restart the source, but hasn't answered within two minutes. Don't send the values again. Check the source's status in a few minutes.
Still waiting on your instance. Check this source's status below in a few minutes. No answer within two minutes. Check the source's status in a few minutes. If the relayed credential stays pending, see Troubleshooting.

When your instance reported why it refused the values, the Reason is exactly one of these (if it didn't, the message has no reason sentence):

  • One of the values has characters your instance won't accept (quotes, $, backslashes, or spaces at the ends).
  • The form sent a field your instance doesn't expect. Reload the page and try again.
  • Your instance couldn't verify this request. Try again; if it repeats, contact Sheer Safe.
  • Your instance isn't set up to receive credentials right now. Contact Sheer Safe.

Before you start

  • Your instance is ready. The Sources panel needs your dedicated instance's public key. If the console shows it isn't enrolled yet, provisioning is still finishing. See Your dedicated instance.
  • Console access. You can sign in and reach Integrate -> Sources.
  • Admin on the vendor. Creating a read-only token or role usually requires an org owner or account admin on that vendor. That is the only thing you need from them: one read-only grant, no standing access for us.

Least privilege, always

Every credential is read-only and scoped to just the audit or findings data SheerSight monitors. None of them can change, delete, or take action on anything in your environment.

What you can connect today

Not every source is self-serve yet. There are three cases, and each integration page says at the top which one it is in:

Status What it means How it starts
Available now Live in the console. You create the read-only credential and connect it yourself on the source's card.
Already on your instance An on-box sensor, not an API integration. Nothing to create and nothing to paste. We enable and tune it for you.
Available on request Built and running in our lab, but not switchable from the console yet. Ask through Integrate -> Request an integration and we enable it on your instance.

Find your integration

Each page shows what SheerSight reads, how to create the read-only credential with its exact scope, what to paste into the console, how to verify, and how to troubleshoot.

Source Category Status
Google Workspace Identity & SaaS audit logs Available now
GitHub Identity & SaaS audit logs Available now, GitHub Enterprise Cloud required
GitLab Identity & SaaS audit logs Available now
Cloudflare Identity & SaaS audit logs Available now
Microsoft 365 Identity & SaaS audit logs Available now
AWS Cloud platforms Available now
Suricata IDS Network & host sensors Already on your instance
Wazuh Network & host sensors Already on your instance
Microsoft Entra ID Identity & SaaS audit logs Available on request
Atlassian (Jira & Confluence) Identity & SaaS audit logs Available on request
Azure Cloud platforms Available on request
GCP Cloud platforms Available now
Linear Evidence & policy documents Available now
Notion Evidence & policy documents Available now
CrowdStrike Endpoint detection & response Available on request
SentinelOne Endpoint detection & response Available on request
Kandji Device management Available on request
JumpCloud Device management Available on request

The Integrations nav on the left is grouped the same three ways, so you can see at a glance which sources you can switch on yourself.

Asking for a source that is not self-serve yet

The credential steps on an available on request page are accurate today - the collector and detections exist, they just are not wired to the console's connect button. Create the credential, ask us through Integrate -> Request an integration, and we enable the source on your dedicated instance.

Verifying a connection

The form reports the outcome itself (see What the form tells you). To double-check after you press Connect or Update credentials:

  1. The relayed credentials panel shows the entry as pending, then applied once your instance decrypts and loads it (usually within a minute or two).
  2. The source's status badge in the Sources list moves from not connected to live once data is flowing.
  3. Detections and telemetry for that source begin appearing in the console.

If the form says "credential relayed, but ..."

Your credential was encrypted and delivered safely, but the step that starts the source didn't run, or the console couldn't confirm it. Don't paste it again. If the form offers Retry starting this source, press it: it starts the source without sending the credential a second time. Otherwise check the source's status in a few minutes, and if it doesn't start, contact support.

Steps 2 and 3 are the same for every source. Step 1 only applies to sources that relay a credential, so AWS and the on-box sensors have no entry in that panel - see their pages for what to check instead.

First real backfill

On the first live poll for audit sources (GitHub, Google Workspace, Cloudflare, and the like), it's worth spot-checking the event count and time range against the vendor's own audit-log view for the same window, to confirm everything lines up before you rely on steady-state output.

Troubleshooting

  • Stuck on pending. Confirm your instance is online and has outbound internet access. It has to dial out to fetch the ciphertext and to poll the vendor.
  • Badge stays not connected. Re-check the credential's scope on the vendor side (it must include the read permission listed on the source's page) and that any IDs (org, account, group, subscription, project) are correct.
  • Authorized but no data (Google Workspace). Give domain-wide delegation a few minutes to propagate before troubleshooting further.
  • Something else. See the FAQ, or email security@sheersafe.com for anything security-related.

Slack alert delivery

Slack is an optional alert destination, separate from source collection. Its app posts messages and receives emoji reactions, so it uses different permissions from the read-only source credentials above. See Slack triage setup for the app manifest, tokens, channel, admin and operator console steps and verification. Customer admins can manage Slack or request help through Integrate → Request an integration.