Trust and data handling
Your data does not go anywhere.
Senua Cyber runs inside your perimeter, on hardware you own. There is no vendor cloud in the request path and no telemetry channel out. This page shows exactly what that means, component by component.
Where your data goes
Shield sits inline. Nothing leaves.
A request arrives, your reverse proxy asks Shield for a verdict, and the request either continues to your application or is refused. Every box below runs on your infrastructure. There is no arrow leaving it, because there is nothing to draw.
Compare this with a SaaS bot-defence product, where the first hop is the vendor's edge network and your production traffic is decrypted outside your control. That is the architectural difference, not a policy promise. The ~0.09 ms verdict in the diagram is the per-request figure measured on CSIC 2010, a published academic HTTP request corpus.
What is logged
Logging and audit.
Every verdict is recorded with the evidence that produced it, on your disk, under your retention policy. A block you cannot explain is a block you cannot defend to the customer it affected.
| Record | Contents | Where it lives | Retention |
|---|---|---|---|
| Verdict log | Source id, verdict, this request's departure, the source's running mean, requests seen | Your disk | You set it |
| Audit log | Licence installs, policy changes, mode changes, operator and timestamp | Your disk | You set it |
| Learnt baseline | Causal patterns learnt from your own normal traffic | Your disk | Until you rebuild it |
| Request bodies | Not retained | Nowhere | Not kept |
| Telemetry to Senua | None. There is no channel. | Nowhere | Not kept |
What you get for your authorisation pack
Built for an Australian security review.
Self-hosted software sits inside your own system boundary, which is the shortest path through a security review there is. Here is what we hand your team for it.
| Item | Status | Detail |
|---|---|---|
| Australian owned and built | Yes | Australian entity, developed in Australia |
| Runs entirely on your infrastructure | Yes | No vendor cloud in the request path |
| Air-gapped operation | Supported | Offline licence file; no activation call required |
| Vulnerability disclosure | Published | Named contact, acknowledged within two business days |
| Evidence you can check | Published | Results on public datasets, with the harness, so your team can re-run them |
| ISM control responsibility matrix | Available on request | For your own system authorisation |
Speed and safety
Measured, with the conditions named.
Figures without their test conditions are decoration. These are Shield's, measured on the CSIC 2010 corpus at engine level, and the boundary is stated with them.
added per request, verdict path
CSIC 2010 run, single core
of attacking sources blocked by their third request
CSIC 2010
of 6,000 genuine sources wrongly blocked
same setting, same run
if the process stops, traffic passes
default; fail-closed is opt-in
These are per-source results: Shield watches a source's own requests until they agree, which is the shape credential stuffing, scraping and API abuse take. Source identity is configurable in the connector, so a fingerprint can be the subject rather than an address where your traffic calls for it.