Datasheets
The detail your security team will ask for.
Deployment architecture, what each product writes to disk, measured results with their test conditions, and the control responsibilities you will need for your own system authorisation.
What you can request
Four documents, one form.
Each is a PDF written for a technical evaluator, not a brochure. Tell us where to send them and we send them the same day.
Shield deployment and architecture
Where Shield sits in the request path, the connector options, resource footprint, failure behaviour, and what it does and does not see.
Benchmark method and results
Both public-dataset runs in full: dataset revision, split, metric definitions, every figure, and how to re-run it yourself.
Data handling and logging reference
Every record written, where it lives, who controls retention, and the fields that are never captured. Written to be pasted into a security questionnaire.
ISM control responsibility matrix
Which controls the product satisfies, which remain yours, and which are shared -- for an Australian system authorisation.
Every dataset we have measured has a one-page datasheet: the dataset, the unit measured, the pass mark fixed before the run, the results, the conditions and the limits. They need no form and sit beside the results they describe, on the benchmarking page.
Request the documents
Where should we send them?
We use this to send the documents and to follow up once. Not a newsletter, not sold, not shared.