How It's Done

METHODOLOGY

The principles and process behind every network security build. Good security isn't a product — it's a discipline applied consistently.

The Process
01

Capture First, Build Second

Before writing a single firewall rule for any device, traffic is captured and analyzed. The exact ports, protocols, and destinations each device actually uses are identified. Rules are built from evidence, not assumptions.

02

Minimum Necessary Permission

Allow rules are the exception, not the default. Every rule permits exactly one thing and no more. If a device only needs outbound HTTPS, that's all it gets — nothing else is permitted, regardless of how benign it looks.

03

Verify at the Kernel

Configuration UIs can lie. Every firewall rule change is verified by directly inspecting the kernel's active rule table via command line. If a rule isn't visible there, it doesn't exist — regardless of what the dashboard shows. Some UniFi features (GeoIP country blocking, for one) never appear in iptables; those are verified in the configuration the controller actually pushed to the gateway — the lowest layer the feature exposes.

04

Document the Intent

Every rule has a description. Every zone has a defined trust level. Every exception has a justification. A network no one can explain is a network no one can maintain or audit.

05

Eliminate Bypass Paths

Controls only work if they can't be circumvented. DNS, NTP, and other critical services are redirected at the network level so device-level configuration overrides are silently intercepted. The network enforces policy, not trust.

06

Observable by Design

Monitoring and alerting are not optional extras — they're part of the architecture. Service failures, authentication anomalies, and policy violations are detected and reported within seconds, not discovered during an incident.

What You Get
›
Firewall rule documentation
Every rule named, described, and organized by zone pair
›
Network diagram
Accurate topology showing all segments and trust relationships
›
Findings report
Prioritized list of issues found, with severity and remediation steps
›
Verification evidence
Kernel-level proof that implemented rules are actually active
›
Runbook
Step-by-step procedures for common maintenance tasks
›
Change log
Record of every configuration change made, with rollback notes
Reference Standards