Built for financial services.
Evidence by default
Each action records the permission in force, the approval used and the verification result in a hash-chained log you can export.
Operational resilience
Out-of-band design: Guardian is never in the data path, so its failure can’t take services down. Containment is fast, reversible and logged.
Segregation of duties
Guardian can’t raise its own permissions, edit its own audit trail or disable its monitors. Approvals are single-use and tied to exact settings.
Data residency
On-premise AI, an on-site vault and an on-site audit trail. An air-gapped option is planned for the most sensitive estates.
Try an incident yourself.
Run a lockout loop, a DHCP failure or a VPN attack in the browser demo, and decide what Guardian may do.
Common questions.
Can the audit trail be sent to our SIEM?
Yes. Copies of the activity log can be forwarded to your own log platform, and checkpoint copies make truncation detectable.
Who is accountable for an automated change?
The named manager who granted the permission or approved the change. The record shows which, for every action.