Security & trust

Security is the product.
Here is how we run ours.

ThisFirewall reads your most sensitive telemetry, so we hold ourselves to the standard we help you measure. This is how your data is protected, who can reach it, and how we prove it.

Read-only by design

We never change your firewalls. ThisFirewall ingests the syslog you already send and reads through a read-only API user. No agents, no new hardware on the network.

Your data stays yours

Tenant data is isolated at the data-access layer and never pooled across customers. Run on shared infrastructure or a dedicated, single-tenant instance in your region.

Provable, not promised

Every change is audit-logged in a tamper-evident chain, backups are restore-tested, and we map our own controls to ISO 27001 continuously inside the product.

Protecting your data

Defence in depth, secure by default, least privilege everywhere.

  • Encrypted in transit and at rest. All traffic over TLS 1.2 or higher; data encrypted at rest.
  • Credentials sealed. Stored firewall API tokens are encrypted with AES-256-GCM, never logged in clear.
  • Single sign-on and role-based access. Microsoft Entra ID (Azure AD) SSO with role-based access control; sessions are short-lived and revocable.
  • Multi-tenant isolation. Enforced at the data-access layer so one customer can never see another's data.
  • Hardened by default. Rate limiting on every API endpoint, CSRF protection (double-submit cookie), syslog source-IP allowlisting, and datastores firewalled and bound to localhost in production.

Audit trail and integrity

If it happened, there is a record, and that record cannot be quietly altered.

  • Every mutation is logged with the actor, the tenant and a semantic action name.
  • Tamper-evident. The audit log is a SHA-256 hash chain, so any edit or deletion is detectable.
  • Retained. Audit records are kept for two years by default.
  • Continuously self-monitored. A scheduled watcher checks for authentication brute-force, audit-chain breaks and privileged actions, and raises them to the operator.

Resilience and recovery

The platform is built to survive failure and to prove it can recover.

  • Encrypted, offsite backups taken daily.
  • Restore-tested, not just taken. Documented disaster recovery with a recovery-time objective of around 30 minutes and a recovery-point objective of 24 hours.
  • Self-healing operations. Restart policies and health, readiness and liveness checks across the stack.

Compliance posture

We design to the standards our buyers are measured against, and we are transparent about what is certified versus in progress.

  • ISO 27001 control alignment, live. We map our controls to ISO 27001:2022 and run that mapping continuously inside the product, so our posture is evidence, not a slide.
  • Privacy by design. Built to support the New Zealand Privacy Act 2020 and the GDPR; you remain the data controller for your telemetry.
  • Audit-ready. The audit trail, access controls, change control and recovery evidence an external assessor asks for are produced by the platform.
Honest about status: we run to ISO 27001 controls and are built audit-ready. Where a formal certification is in progress rather than complete, we will tell you exactly where it stands. A sub-processor list and a Data Processing Agreement are available on request.

Data ownership and residency

Your telemetry is yours. We do not sell it, mine it across customers, or train shared models on it.

  • You own your data and can export or delete it.
  • Choose where it lives. Shared multi-tenant infrastructure, or a dedicated single-tenant instance in the region you require.
  • Minimal footprint. We process the firewall telemetry needed for detection and analytics, nothing more.

How we build

Security is enforced in the pipeline, not left to good intentions.

  • 1,400+ automated tests gate every release, including security-boundary and tenant-isolation tests.
  • Static analysis and secret scanning (Semgrep SAST, secret detection) plus automated dependency scanning run on every change.
  • Peer review and least-privilege deploys. Changes are reviewed; production credentials are scoped and never embedded in code.

Responsible disclosure

Found something? We want to hear from you, and we will move quickly.

  • Email [email protected] (please do not open a public issue).
  • Acknowledgement within 24 hours, assessment within 72 hours, and resolution of critical issues within 30 days.
  • Machine-readable contact at /.well-known/security.txt.