Governance
Automation a risk committee can approve
The scanning tools are the same ones the whole industry uses. The difference is in how their use is controlled: nothing runs without signed rules, nothing is exploited without approval, and every action is logged.
governance · online bankingRoE v1.2 in force
Exploitation approval
sqlmap ·
/api/clientes?id=ApproveRejectzap · active
scan · portalApproveRejectWaiting for the ReviewerWithout approval, the flow stops.
Audit log
Admin signed RoE v1.2 · sqlmap and zap enabled
Out-of-scope target rejected
Reviewer approved exploitation · sqlmap
User revoked · history kept
The three principles
Control before, during, and after every test
The platform does not depend on each person respecting the scope. The rules live in its four layers: the web platform, the orchestration that rejects any execution without a valid RoE, the AI agents, and the tools in an isolated sandbox. What does not comply, does not run.
No valid RoE, no scan
The rules of engagement are the configuration that enables each tool. If they expire, new tests cannot be started.
Exploitation only with approval
The Reviewer role reviews and approves before any attempt to exploit a vulnerability. Without that approval, the flow stops.
Complete chain of custody
Every action by a person or by the automation is logged. If a user is revoked, their history is kept.
The RoE sets the limits of each tool
Every scan starts with Nuclei and adds a second tool, only if the RoE enables it. These are the 6 available combinations and the limits signed for each one.
| Combination | What it tests | What the RoE sets |
|---|---|---|
| Crawl and active scan of the web application: XSS, headers, configuration. | ||
| Certificate, ciphers, and security headers. Passive. | ||
| SQL injection on the authorized parameters. | ||
| Exposed directories and files. | ||
| HTTP load test on the authorized paths. | ||
| Dependencies and images with known vulnerabilities. |
The one who runs is not the one who approves
Three roles with separate permissions. Each user joins by invitation and 2FA, and sees only what their role allows.

Sees everything, manages users, and reviews the audit. Invites by single-use link and revokes access without deleting history.

Runs the engagements, launches the scans, and manages the findings within what the RoE allows.

Read-only, plus approval of every exploitation and validation of findings. Can be someone from the client.
Controlled cycle
Each state has a condition to move forward
To move from draft to ready you need a valid RoE and at least one target within scope. While it scans, you see the progress of each tool in real time, and the kill switch stops everything at any moment.
Evidence for audit
What you hand to your auditor or regulator
All the evidence comes out of the same platform, ready to download and without assembling folders by hand.
Regulatory annexoptional service
USD 1,500per report
The findings and evidence, mapped to the framework your regulator asks for.
- PCI DSS
- ISO 27001
- Agreement 6-2011 of the Superintendency of Banks of Panama
