How it works
From finding a flaw to blocking it, with proof kept along the way.
The flow
-
1. Find
AegisForgeAegisForge finds a business-logic flaw.
-
2. Prove
AegisForgeIt proves the flaw and seals the evidence in a proof pack that anyone can verify offline.
-
3. Suggest a rule
A rule is proposed to stop that flaw.
-
4. Test it first
The rule is replayed against the attack it was written for, plus normal requests, to make sure it works and doesn't hurt real customers.
-
5. Human approves
HumanA named person switches it on. Until then, the rule only watches and does not block.
-
6. Block with a reason
AegisWallAegisWall blocks the bad requests and explains why, while attack bots can get fake success.
-
7. Proof for every decision
Every block or allow is saved as evidence, and any change to it can be detected.
A normal firewall vs AEGIS
Someone asks for a 900 SAR refund on a 300 SAR order.
A normal firewall
Checks how the request looks: it looks clean.
Looks clean, allowed
The refund goes through.
AEGIS
Checks what the request means: the refund is more than was paid.
Blocked
Blocked: the refund is more than what was paid.
A still illustration with pre-written text.