4.4
IG1 IG2 IG3

Implement and Manage a Firewall on Servers

Asset Type: Devices
Security Function: Protect

Description

Implement and manage a firewall on servers, where supported. Example implementations include a virtual firewall, operating system firewall, or a third-party firewall agent.

Implementation Checklist

1
Assess current protection controls in place
2
Configure and deploy required security controls
3
Test control effectiveness in non-production environment
4
Deploy to production and verify functionality
5
Document configuration and operational procedures
6
Review and document current firewall rule sets
7
Define required firewall rules based on business needs
8
Implement and test firewall rules
9
Schedule periodic rule review and cleanup
10
Inventory all third-party service providers
11
Classify third parties by risk level
12
Conduct security assessments of critical vendors
13
Include security requirements in contracts

Threats & Vulnerabilities (CIS RAM)

Threat Scenarios

Lateral Movement Through Unprotected Server Ports

Confidentiality

Attackers who compromise one server move laterally to others through open ports and services that a host-based firewall would have blocked, escalating the breach scope.

Remote Exploitation of Unnecessary Server Services

Integrity

Servers without host-based firewalls expose all running services to the network, allowing attackers to exploit vulnerable services that should have been restricted to local or specific source access.

Server-to-Server Worm Propagation

Availability

Without host-based firewalls enforcing least-privilege network access, worms and automated attacks propagate rapidly between servers on the same network segment.

Vulnerabilities (When Safeguard Absent)

No Host-Based Firewall on Servers

Without server firewalls, all network-accessible services on the server are exposed to any device that can route to it, relying entirely on perimeter controls.

Servers Accessible on All Ports from Internal Network

Absence of host-based firewalls means internal network compromise provides unrestricted access to all server services, negating defense-in-depth strategies.

Evidence Requirements

Type Evidence Item Collection Frequency
Technical Configuration screenshots or exports showing protection controls enabled Captured quarterly
Document Procedure documentation for protection measures Reviewed annually
Technical Firewall rule set export and review documentation Reviewed quarterly
Record Firewall change request and approval records Per change
Record Third-party risk assessment reports and scorecards Annually per vendor
Document Vendor contracts with security requirements Per contract cycle
Document Governing policy document (current, approved, communicated) Reviewed annually