Firewall
Network security component that filters traffic by defined rules to protect systems and networks from unauthorized access.
Classification
- ComplexityMedium
- Impact areaTechnical
- Decision typeArchitectural
- Organizational maturityIntermediate
Technical context
Principles & goals
Use cases & scenarios
Compromises
- Faulty rules may block legitimate business operations.
- Rule or configuration drift without controls.
- Overreliance on perimeter firewalls instead of defense in depth.
- Apply 'deny by default' for rules.
- Version and peer-review rule changes.
- Combine monitoring and alerts with proactive testing.
I/O & resources
- Network and zone architecture
- Security and access policies
- Monitoring and logging infrastructure
- Rule sets and configuration backups
- Alerts, logs and audit reports
- Segmentation and access controls
Description
A firewall is a network security component that protects a system or network segments from unauthorized access by filtering inbound and outbound traffic according to defined rules. It can operate at packet, stateful, or application layer levels and is key for perimeter, host, and cloud security architectures.
✔Benefits
- Reduces attack surface by filtering traffic.
- Enables segmentation and enforcement of security zones.
- Supports compliance via auditable rules.
✖Limitations
- Not a complete protection against compromised legitimate connections.
- Complex rules can lead to misconfigurations.
- Performance bottlenecks possible with deep packet inspection.
Trade-offs
Metrics
- Number of blocked connections
Counts connection attempts denied by firewall rules to indicate trends and potential attacks.
- False positive rate
Percentage of legitimate connections erroneously blocked to assess rule quality.
- Average latency introduced by firewall
Additional latency introduced by inspection and processing, measured in milliseconds.
Examples & implementations
Cisco ASA at enterprise gateway
Use of a hardware firewall to secure the internet gateway of large sites.
pfSense for branch offices
Open-source appliance for flexible rule management and VPN integration in branches.
Cloud-native managed firewall
Use of provider firewall services for segmentation and as part of cloud security architecture.
Implementation steps
Plan: define assets, zones and policies.
Design: draft rule sets and evaluate impacts.
Deploy: roll out rules incrementally and test.
Operate: set up monitoring, maintenance and periodic reviews.
⚠️ Technical debt & bottlenecks
Technical debt
- Old redundant rules without owners or documentation.
- On-prem hardware with outdated firmware and lacking support.
- Missing automation for rule lifecycle and testing.
Known bottlenecks
Misuse examples
- Opening all ports for a service upgrade instead of targeted exceptions.
- Static rules that ignore dynamic cloud IPs.
- Disabling logging for perceived performance gains.
Typical traps
- Placing rules in wrong order causing priority errors.
- Defining trusted networks too generously.
- Applying untested rule changes to production.
Required skills
Architectural drivers
Constraints
- • Hardware resources and bandwidth limits.
- • Compatibility with existing network topologies.
- • Compliance with legal and sector-specific requirements.