Contact Open demo
Security Graph

See every path to sensitive data

Follow authority from every agent and non-human identity through roles and credentials to your crown jewels, and cut the one route that matters.

Trace authority to the data that matters

Follow every authority path from an agent through roles and credentials to a crown-jewel secret. Every step is an observed relationship, not a guess.

Authority paths
ExploreSaved queriesHistory⌕⚙▥

Security Graph

Find agents, identities and data stores and the access paths between them in the latest scan
FINDAgent×WHEREOwner does not exist +
THATUses Identity×+
THATHas access to Data store×+
Can assumeBreakpoint · Read3partner-syncLambda function3partner-integration-roleIAM role6prod/payments/stripe-keySecrets Manager secret
Find · agents without an owner
Follow · what they can reach
Observed relationship
Crown jewel

One graph for every platform

nerl0 connects AWS, Azure, Salesforce, GitHub, Slack, OpenAI and MCP servers, and turns what it finds into authority paths.

Cloud & CRM
Code, chat & AI
aws
azure
salesforce
github
slack
openai
mcp
awsAWS · Lambda function

partner-sync can assume partner-integration-role, which other accounts can assume.

prod/payments/stripe-keyCROWN JEWEL
Security Graph · Authority path

partner-sync can read production crown-jewel prod/payments/stripe-key through partner-integration-role.

Medium1 crown jewelProven

Cut the path. The next scan verifies.

nerl0 recommends the breakpoint that interrupts the most routes. You apply the change yourself, the next scan confirms the route is gone.

Recommended breakpointYou apply the changeVerified by the next scanEvery step observed
New4···  +
NRL-48

partner-sync can read production crown-jewel prod/payments/stripe-key through partner-integration-role, which other accounts can assume

MediumAWS
NRL-47

Principals in other accounts can read production crown-jewel prod/payments/stripe-key through partner-integration-role

HighAWS
NRL-44

claude-code installation token can read 7 repositories

MediumGitHub
NRL-41

ops-automation-agent wrote to northstar-build-artifacts

LowAWS
Assigned3···  +
NRL-46

ops-automation-agent can administer prod/payments/stripe-key through ops-admin

HighAWS
NRL-43

remediator-admin can administer prod/payments/stripe-key

MediumAWS
NRL-39

Unowned agent found in connected platforms

Medium
Verified2···  +
NRL-38

partner-integration-role no longer reads prod/payments/stripe-key

ClosedAWS
NRL-36

Share of identities older than 365 days dropped below target

Closed
ExploreSaved queriesHistory⌕⚙▥
Can readCan readCan readCan readCan readUses credential1claude-codeGitHub Appclaude-code installationtokenApp installation tokennorthstar-tech/platformRepository1northstar-tech/payments-serviceRepository1northstar-tech/internal-toolsRepository1northstar-tech/infraRepository2northstar-tech/docsRepository+ 2 MORE REPOSITORIES

Follow credentials into every repository

One installation token can read far more than the agent that holds it. See the whole fan-out at once.

NewMedium
partner-sync can read production crown-jewel prod/payments/stripe-key through partner-integration-role, which other accounts can assume
OwnerOHOmar Haddad SeverityMedium Impact1 crown jewel value 12, target ≤ 5 Authority paths1 authority path EvidenceProvenEvery step is an observed relationship: configured authority. 2 scans · reproduced
Recommended breakpoint
partner-integration-role→prod/payments/stripe-keyRead
✓No known route remains · Routes interrupted 1 of 1
RemediateAssignCreate a ticket

Every path becomes an issue with an owner

Severity, impact, evidence and the recommended breakpoint in one place, so nobody has to rebuild the story from logs.

  • SeverityMedium, High, with the reason.
  • EvidenceProven, with how often it was reproduced.
  • OwnerAssigned, tracked, verified by the next scan.

Activity

Every event on this issue's paths, one lane per entity · newest first
ops-automation-agentDecisionDev Patel assigned an issue on ops-automation-agent
ops-automation-agentDecisionDev Patel opened an issue on ops-automation-agent
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent read prod/payments/stripe-key
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
nerl0Reproduced
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts
ops-automation-agentops-automation-agent wrote to northstar-build-artifacts

Every event on the path, newest first

Reads, writes, decisions and re-checks sit on one timeline per entity, so you can show who knew what and when.

  • DecisionsWho opened, assigned or closed an issue.
  • ActivityEvery read and write on the paths.
  • ReproducedEach path is re-checked on every scan.

Find the agents nobody registered

Shadow agent detection lists every agent and MCP server found in your connected platforms, with privilege, data reach and risk, so unowned agents cannot hide.

Shadow agent detection
41Agents and MCP servers
5Sanctioned
33In review
1Unowned
2Rejected

See exposure by platform and access

Data access leads your exposure. See where read, write and admin access sit across your platforms, then open the Security Graph from any cell.

Exposure
11 Sep20 Sep29 Sep08 Oct17 Oct26 Oct09 Nov
Exposure over timeSum of countable questions · 11 Sep to 09 Nov

The question is never only who has access. It is which path leads to the data you cannot lose.

Security Graphnerl0 · See every path to sensitive data

Non-human.
Non-negotiable.

See how nerl0 worksView docs →

See the access path behind it.