Janus
Guards the doorway. Triages what the Secure Web and Email Gateway caught, phishing, risky SaaS, blocked downloads, and tells you in one sentence whether it mattered. You never talk to Janus; he reports to Lucy.
Answers the only question that matters: did it matter?
Janus, the god of doors, looks in and out at once. That is a gateway: web and email, both directions, nothing unchecked.
Your gateways catch things all day: a blocked download here, a quarantined attachment there, a SaaS app someone tried to use. Each catch raises the same question, was that just noise, or did we just dodge something real? Janus is the specialist that answers it. He triages everything the Secure Web and Email Gateway caught and separates the routine from the incident.
The result is a one-sentence verdict instead of a log entry: "That attachment was blocked. It was a real BEC attempt." Or just as valuable: "Routine. Nothing to do."
One sentence
Did it matter? Answered, not just added to a log.
No noise
The one real attempt, surfaced from a day of routine blocks.
Evidence, one click
Straight to the caught email or session in the portal.
What Janus learns.
- Decades of triaged gateway events: which catches mattered, which were noise
- Your tenant's web and email traffic patterns, policies and users
- Live threat context: phishing campaigns, BEC tradecraft, risky SaaS behaviour
Triage in one sentence, evidence one click away.
- Triages every Secure Web and Email Gateway catch, phishing, risky SaaS, blocked downloads
- Tells you in one sentence whether it mattered, and why
- Surfaces the real attempt hiding in a day of routine blocks
- Links straight to the evidence in the portal, no console-diving
From a log entry to a verdict.
Janus reads everything the Secure Web and email gateways caught, and separates the routine from the incident.
1 - Collect the catches
Pulls Secure Web Gateway and email security events: blocked downloads, quarantined mail, risky SaaS, denied URLs.
2 - Enrich each one
Resolves sender, URL, file hash and destination against threat intel and the current campaign landscape.
3 - Score real versus noise
Weighs it against decades of triaged catches: a genuine attempt in your context, or routine noise?
4 - Answer in one sentence
States whether it mattered and why, with a link to the evidence. Routine catches stay silent.
A day of blocks, one that mattered.
Representative output. Every line links to the underlying records in the portal.
What the gateways see.
| Web gateway | Secure Web Gateway verdicts: blocked downloads, denied URLs, risky SaaS use. |
|---|---|
| Email security | Phishing, BEC, malware and quarantine events, with headers and attachments. |
| Threat context | Live campaign intel, sender reputation, file and URL reputation. |
| Tenant policy | Your allow and block lists and the users involved, for context. |
Reports to Lucy. You talk to her.
You never address Janus directly. Ask Lucy "was that blocked attachment dangerous?" and she consults him behind the curtain, then answers in one voice, with Janus named as the source. He works alongside the rest of the team:
Autonomous, not autonomous-washing.
Grounded
Verdicts cite the real gateway logs and the 35-year baseline, not free-form generation.
Bounded autonomy
Janus triages and explains; any action still runs through propose, approve, act.
Human accountability
Level-3 engineers own every critical call. No L1, no L2.
Sovereign by design
Scoped to your tenant, region-pinned, with the evidence to prove it.
Go deeper.
Maturity: Live. Janus ships with Lucy: no extra tool, no separate console, no additional contract. The gateway simply gets a voice inside the conversation you already have.
See the operators run your SASE.
Watch the agents diagnose, decide and act, with Level-3 engineers owning every critical call.
Book a demo →