Firewalld Configuration

Firewalld Configuration

Learn how to manage host firewall behavior with firewalld, including zones, services, ports, rich rules, port forwarding, and panic mode. This course introduces the practical firewall administration skills needed to control network exposure on Linux systems without editing raw packet-filter rules directly.

Why It Matters

Network exposure is one of the clearest parts of a system's attack surface. Operators need to know which services are reachable, which should remain internal, and how to express those decisions safely in a host firewall. firewalld provides a structured way to manage that exposure, especially on Red Hat-style systems.

What You Will Learn

• Understand firewalld basics and how zones group trust levels and interface behavior.
• Open and manage services and ports deliberately.
• Use rich rules for more specific traffic-control logic.
• Configure port forwarding for redirected service access.
• Use panic mode as an emergency containment option.
• Apply these controls in a hardened web server challenge.

Course Roadmap

The course begins with firewalld basics and zones so you can understand how the firewall organizes trust and network policy. It then moves to managing services and ports, which covers the most common day-to-day exposure changes.

Next, the course introduces rich rules for more flexible matching and control, followed by port forwarding so traffic can be redirected to the right service destination. After that, you learn panic mode, which is useful for immediate containment in high-risk situations.

The course ends with the Hardened Web Server challenge, where zone selection, port exposure, richer rule logic, and emergency thinking all contribute to a more realistic firewall configuration task.

Who This Course Is For

This course is for Linux learners and administrators who need to manage host-level network access safely on systems that use firewalld.

Outcomes

By the end of this course, you will be able to configure firewalld with more confidence, expose only the services that should be reachable, apply more specific policy when needed, and reason more clearly about host-level network security.