A sandbox build role can assume its way into production
HighCWE-269Build-agent session → Customer event data
01ENTERPRISE
Nobody can drawthe estate anymore.
Trident maps every account and cloud into one graph, validates the paths that cross them, and opens the fix.
Read-only connection. No agents deployed.
Standing trust into production
Federated workload identity
02THE PATH
The path crossesthe cloud boundary.
At enterprise scale the hard problem is attribution, not detection. Trident consolidates by path and ranks remediation by routes removed.
Cross-account path
Reach proven, nothing read.01 · EntryBuild agent, sandbox account
Every link is standing trust. Naming one principal breaks it.
02 · HopStanding trust into production
03 · HopFederated workload identity
04 · TargetCustomer analytics store
01 · EntryBuild agent, sandbox account
Every link is standing trust. Naming one principal breaks it.
02 · HopStanding trust into production
03 · HopFederated workload identity
04 · TargetCustomer analytics store
03ENGAGEMENT
How an estateengagement runs.
- 01
Recon
Read-only roles attach across accounts, clouds, and subsidiaries.
- 02
Path mapping
Trust and federation edges resolve into ranked cross-account paths.
- 03
Exploit validation
Each assumption is exercised, then dropped. Reach proven, nothing read.
- 04
Draft PR + report
The severing policy change opens as a draft pull request.
04THE PACK
The packprocurement asks for.
The whole estate in one document, shaped for procurement and the security review behind it.
In the pack
- One scoped, read-only role per account, nothing shared
- Trust map drawn from live policy, not interviews
- Findings name the account, principal and the policy that admits it
- Methodology document ships beside the report
SOC 2 report
Audited by Sensiba LLP
05COVERAGE
What multi-cloud, multi-teamcoverage requires.
The constraint is rarely the testing. It is routing the result to whoever can actually fix it.
- 01
Cross-account paths
Routes that begin in one account or provider and end in another, including the federation no single provider console displays.
- 02
Ownership routing
Each finding goes to the team that owns the resource, so nothing waits in central triage.
- Tags
- Account structure
- Repo ownership
- 03
Deduplication by root cause
One misapplied policy template across forty accounts is one defect, not forty findings competing for the same engineer.
40 instances → 1 defect - 04
Business-unit segmentation
Whether isolation between units, subsidiaries and acquired environments actually holds. Post-acquisition integration most often leaves a permanent bridge.
- 05
Programme-level metrics
Whether the programme works, not how busy it is.
- Evidence age by critical path
- Change-to-test latency
- Fix-to-retest latency
06DATA RULES
Read-only access.Authorized in writing.
- Read-only roles per account or organizational unit
- Every account in scope authorized in writing first
01
Read-only cloud access
The graph is built from read-only access to configuration and metadata.
- No agents
- No resource changes
- 02
SOC 2 report
Issued by the independent audit firm Sensiba LLP.
- Controls monitored continuously in Vanta
07TALK TO THE TEAM
Talk to the teamthat builds Trident.
Bring the accounts, clouds and subsidiaries you want mapped. Read-only roles are scoped per account or business unit.
- Cloud exposure
- Web & API pentest
- Identity paths
- Sensitive data
Talk to the team
Read-only connection. No agents deployed.
Read-only roles are provisioned per account or per organizational unit, so scope, authorization and reporting segment by account structure or business unit. Units with different regulatory obligations stay separately authorized.
Validation exercises a route to prove it resolves; it does not alter or destroy data. Anything destructive is demonstrated in a non-production account, and every account in scope is authorized in writing first.
The scanner says what conditions exist; the graph says which combine into something reachable. Most enterprises keep broad scanning for hygiene obligations and use path analysis to decide what to act on first.
Those are usually the highest-value scope. Acquired estates carry unreviewed trust relationships to the parent, and because a different team configured them, cross-unit isolation most often turns out to be theoretical there.
[09]GET STARTED+
Draw the estateagain.
Connect read-only roles and see the verified paths between accounts.
acme · all accounts
READ-ONLY
Recon
roles attached
done
Path mapping
cross-account
done
Validating
exercised, dropped
Reach proven
nothing read
proven
- SOC 2 audited by Sensiba LLP
- Read-only cloud access