Project in development · Policy management on OPNsense

NGFW BitArmor

In developmentLab validation

BitArmor’s NGFW project starts from a simple idea: you should see a firewall rule before you apply it and verify it afterwards. On OPNsense, it makes the policies within its remit verifiable: a preview of the expected outcome, controlled application, comparison with the actual state, an explanation of the blocks those policies cause, and controlled rollback to the approved version.

In development A project undergoing lab validation, not yet intended for customer devices. Its commercial name has not yet been decided.

01The problem

Rules applied, but never verified

Changes pile up on a firewall: rules added in an emergency, forgotten exceptions, changes made outside the usual procedure. When something gets blocked, working out why takes time.

BitArmor’s NGFW project treats the policies it manages as a process: you see the expected outcome first, apply it in a controlled way, compare it with the real state and, within the qualified scope, roll back to the approved version.

02How it works

From policy to actual state

Five steps, with verification after every change.

  1. Policy

    The policies managed by the project are described explicitly and kept for review.

  2. Preview

    Before applying a change, you see its expected outcome based on the available data.

  3. Controlled application

    Changes follow a controlled workflow, with separate roles and a log of every operation.

  4. Actual state

    The state of the managed policies is compared with what was approved; detectable differences surface even after changes made outside the workflow.

  5. Explanation and rollback

    Blocks caused by the managed policies can be explained and, within the qualified scope, the approved version can be restored.

Illustrative diagram; no real data. The managed policies are compared with the actual state; any difference found is flagged and can be returned, in a controlled way, to the approved version.

03Features

What the NGFW project does

Built for people who need to be able to explain what the managed policies do, and why.

  • Change preview

    The expected outcome of a change is visible before it is applied.

  • Controlled application

    Separate roles and an operations log for every policy change.

  • Verifiable actual state

    The live configuration of the managed policies is compared with the approved one.

  • External changes detected

    Detectable differences introduced outside the workflow come to light instead of staying hidden.

  • Blocks explained

    For blocks caused by the managed policies, you can trace back to the rule responsible.

  • Controlled rollback

    Within the qualified scope, you can return to the approved version of a policy in a controlled way.

The project manages its own policies and the qualified DNS and IDS/IPS paths, not the firewall’s entire configuration, and is undergoing lab validation on OPNsense. To protect your perimeter today, there is BitWall.

04Where it fits

Three tools, three different roles

  • BitWall

    An NGFW firewall managed by BitArmor: the offering for protecting your perimeter today, with ongoing policy management.

    Discover BitWall

  • NGFW BitArmor

    In development

    A software project for verifiable management of the security policies within its remit on OPNsense, currently undergoing lab validation.

  • BitShield

    In development

    A separate project for organising, reviewing and publishing DNS lists.

    BitShield project

Want to know more about the NGFW project?

In development

Tell us how you manage your firewall policies today. We’ll explain where the project stands.

Prefer email? Write to [email protected].