Overview

Seven practices, applied across the lifecycle

Security is built into each stage of how we design, build, release and operate our products. The practices below work as layers: each one is designed to catch what the previous one might miss.

  • Code
  • Peer review
  • Automated scanning
  • Release
  • WAF & IPS
  • Monitoring
  • Testing
In Detail

Our security practices

01

Automated code and supply-chain scanning

Every line of code is scanned before it is released.

All source code for OneFirewall products is scanned with AquilaX Security, our code and infrastructure assessment partner, before any release reaches production. Scanning is integrated into our build and release pipelines so that it runs on every change, not as a periodic exercise.

Findings are triaged by severity. Critical and high-severity issues must be remediated, or formally risk-accepted with a documented justification, before a release can proceed.

  • Static Application Security Testing (SAST): analysis of first-party source code for injection, authentication, authorisation and data-handling flaws.
  • Software Composition Analysis (SCA): identification of vulnerable or outdated open-source dependencies and licence risks.
  • Secrets detection: prevention of credentials, API keys and private keys being committed to source code.
  • Infrastructure as Code (IaC): review of deployment templates and configuration for insecure defaults and misconfiguration.
  • Container image scanning: detection of known vulnerabilities in base images and packaged components before deployment.

Technology AquilaX Security: SAST, SCA, secrets, IaC and container scanning

02

Peer review of security-critical changes

No security-critical change reaches production without a second pair of eyes.

Changes that affect the security of our products are subject to mandatory peer review by a qualified engineer other than the author before they are merged. Reviewers assess the change for correctness, security impact and adherence to our secure coding standards, and may require further testing or design review.

  • Authentication, session management and access control
  • Cryptography, key management and secrets handling
  • Input validation, parsing and handling of untrusted data
  • Network exposure, firewall rules and infrastructure configuration
  • Processing of customer, member or threat-intelligence data
03

Recurring web application and infrastructure scanning

Our public-facing services are scanned at least monthly, and more often when risk requires it.

All publicly exposed OneFirewall services are subject to recurring web application and infrastructure vulnerability scanning, carried out at least once a month. Additional scans are performed after significant changes, on the disclosure of relevant new vulnerabilities, and whenever our threat intelligence indicates elevated risk.

Scanning covers the external attack surface as an attacker would see it. Identified issues are tracked to resolution and verified by re-scanning.

  • Attack-surface discovery of domains, subdomains, open ports and exposed services
  • Dynamic application security testing (DAST) of web applications and APIs
  • TLS configuration, HTTP security headers, DNS and email security (SPF, DKIM, DMARC)
  • Exposed files, data leakage and misconfiguration checks

Technology Vulnix0, our offensive security platform, built by Velocity Lab with AquilaX Security

04

Manual penetration testing and security assessments

Automated tools are complemented by hands-on, adversary-style testing.

We conduct manual penetration tests and security assessments of our products and infrastructure, periodically and ahead of significant releases or architectural changes. Testing is performed by experienced practitioners who chain together issues that automated scanners alone would not identify.

Findings are risk-rated, assigned an owner and remediated according to severity, then verified by retesting.

  • Web, API, network and cloud penetration testing aligned with OWASP ASVS, the OWASP API Security Top 10, PTES and NIST SP 800-115
  • Threat modelling of new features and architecture using STRIDE
  • Software security maturity assessment against OWASP SAMM
  • Correlation of findings with MITRE ATT&CK techniques observed across the Alliance

Technology OneFirewall Security Assurance programme

05

Web Application Firewall on every public-facing application

We deploy, manage and operate a WAF in front of our public web applications.

Our public-facing web applications are protected by a Web Application Firewall that we deploy, manage and operate ourselves. Traffic is inspected at the edge, and only legitimate requests are forwarded to our application servers, whose origins are not directly exposed.

WAF rules are maintained by our engineering team and adjusted in response to observed attacks and new threat intelligence.

  • Rate limiting of authentication endpoints and resource-intensive pages
  • Blocking of sensitive paths, attack tooling and disallowed HTTP methods
  • Built-in protection against path traversal, request smuggling and IP spoofing
  • Bot management and blocking of known-hostile networks

Technology OneFirewall Web Application Protection (WAP)

06

Security logging, monitoring and incident response

We collect and review logs to detect and respond to security incidents.

Security-relevant logs from our applications, infrastructure and security controls are collected centrally and retained for investigation. Logs are reviewed for indicators of compromise, anomalous behaviour and policy violations, and are enriched with the same threat intelligence we provide to our members.

Suspected incidents are triaged, contained, investigated and resolved under our incident response process, and the lessons learned are fed back into our controls.

  • Centralised collection of application, system, network and WAF logs
  • Correlation of events against the Alliance threat-intelligence feed and Crime Score
  • Defined escalation and incident-response procedures
  • Post-incident review and improvement of detection rules
07

Automated intrusion prevention with our own technology

Our systems are protected by OneFirewall's own automated IPS capabilities.

Our infrastructure is protected by the same automated intrusion prevention capabilities we provide to Alliance members. Indicators of malicious activity, sourced from more than 290 Alliance members and partners and from our own detections, are scored and translated into blocking rules that are enforced automatically at the network edge.

This means that an attacker identified anywhere in the Alliance can be blocked from our services before reaching them, typically within seconds of detection, without waiting for manual action.

  • Real-time enforcement of Alliance threat intelligence (IPs, domains, URLs)
  • Crime Score-based blocking thresholds, with indicators that age as infrastructure changes
  • Automated rule distribution to our firewalls and edge controls
  • Two-way feedback: attacks against OneFirewall are contributed back to the Alliance

Technology OneFirewall Cyber Threat Intelligence, WCF Agent and F3D Agent

Supporting Controls

Governance and assurance

Cyber Essentials certified

OneFirewall Alliance holds Cyber Essentials certification, the UK government-backed scheme covering access management, malware protection, patch management, firewall configuration and secure configuration.

Trust & Security →

Encryption in transit

Communication between our platform, agents and members is encrypted using TLS, with TLS 1.3 used for agent and API channels.

Architecture →

Vulnerability disclosure

We operate a coordinated vulnerability disclosure programme aligned with ISO/IEC 29147, with safe harbour for good-faith research.

Vulnerability Disclosure Policy →

This statement is reviewed at least annually and whenever our practices change materially. It describes our standard practices and does not constitute a contractual commitment; specific obligations are set out in customer agreements.

Have a security or compliance question?

Our team can provide further detail on our practices as part of a security review or questionnaire.