Connected to your stack, one scope at a time.
Forty-two connectors across nine kinds of tool, each holding the narrowest scopes its job needs. Which ones you connect depends on your estate, and where a tool is missing, NEBU brings its own.
Book a callNine kinds of tool.
Environments7
Where your workloads and identities live. Read to surface and analyze, written to only to remediate.
- Amazon Web Services
- Microsoft Azure
- Google Cloud
- Kubernetes
- Red Hat OpenShift
- Oracle Cloud Infrastructure
- VMware vSphere
Identity3
Who and what can sign in, and with which roles.
- Okta
- Microsoft Entra ID
- Google Workspace
Secrets4
Keys, tokens and credentials, read for their age and use, rotated when a fix calls for it.
- HashiCorp Vault
- AWS Secrets Manager
- Azure Key Vault
- CyberArk
Scanners6
Findings from the scanners you already run, read-only.
- Prowler
- Wiz
- Orca
- AWS Security Hub
- Tenable
- NEBU Self-Scan
Change approval7
Where approval requests reach the people who decide.
- Slack
- Microsoft Teams
- Jira
- ServiceNow
- ClickUp
- Email (SMTP)
- NEBU Console Approvals
Tasks4
Where the work is documented and closed.
- ClickUp
- Jira
- ServiceNow
- NEBU Tasks
Code and IaC3
Fixes delivered as code: pull requests, merge requests and runs.
- GitHub
- GitLab
- Terraform Cloud
Telemetry3
Metrics and logs that show whether a fix held, read-only.
- Datadog
- Prometheus
- Amazon CloudWatch
Evidence5
Where the record lands: your SIEM and your compliance platform.
- Splunk
- Microsoft Sentinel
- Vanta
- Drata
- NEBU Evidence Ledger
What a connector is allowed to do.
Each connector lists its read and write scopes and the loop steps it serves. Scanners and telemetry stay read-only, most evidence tools only receive, and nothing holds more than its step needs.
Pick any of the 42 to see exactly what it holds.
Zero trust, connector by connector.
Every connector starts read-only. Write scopes are added only where a fix needs them, each call is authenticated for that one action, and the identity behind it is yours to review or revoke.
When a tool is missing.
Not every estate runs every kind of tool. We can recommend a leading product or an open-source option, for telemetry for example, or NEBU can fill the gap with its own connectors: self-scan, console approvals, tasks and an evidence ledger.
They work with NEBU’s specialized agents directly inside your boundary, so they need more permissions than a third-party connector. They too start read-only and grow only as far as least privilege allows.
Not on the list?
Tell us what you run. Connectors are added as customers need them.
Questions
Do we need to connect all of them?
No. You connect what your estate runs. A pilot can start with one environment, your identity provider and the place your approvals already happen.
Do connectors send our data outside?
No. Every connector runs inside your boundary. What reaches a third-party tool, such as an approval request or a record, is only what you chose to send there.
Map your stack to the connectors.
On a call, we go through what you run and which scopes each connector would need.