How it works
Agents we build in your environment read, a partner reviews while we're engaged, and you approve. At the end, we hand the agents to your team. Every service follows the same five stages, and two of them belong to you.
The five stages
Stage 1: You create read-only keys and roles
You
Stage 2: Agents we build in your environment run the checks
Agents
Stage 3: A partner reviews every finding
Partner, during the engagement and with ongoing support
Stage 4: Report, evidence, and fix tickets
Agents and partner
Stage 5: You approve any change
You
Ongoing support (optional): After handover, we keep the agents tuned as your environment changes, and a partner keeps reviewing their findings. Any change still needs your approval.
Stages with a brass border are yours: nothing starts without your keys, and nothing changes without your approval.
What the agents do
- Read configurations
- Compare them against your controls
- Draft findings
What a partner does
- Judge the risk of every finding
- Remove false positives
- Recommend fixes
What you do
- Create the read-only keys and roles
- Approve any change
The limits behind every stage, from the roles we ask for to where agents run, are on the security and trust page.
Start with a two‑week Security Program Assessment.
We review identity, cloud, and your key SaaS apps, take a snapshot of shadow IT and AI tools, and hand you prioritized findings with a plan. Fixed scope and fixed fee, agreed in writing before we start.