Posted on Nov 2nd, 2012 by Michael Hamelin

In my last post I talked about preparing for a firewall audit and all the control points that an auditor will want to check in order to understand if your firewall operations are auditable and repeatable.

Today I want to focus on two parts of the firewall audit: the review of the change process, and the review of the firewall rule base.  In my experience, these two steps are the most important. I'll go over many of the technical details you need to check if you are pre-auditing your firewall before the audit team arrives, or if it is your job to audit the firewall.

Auditing the Change Process

The first technical step in a firewall audit is normally an examination of the firewall change process. The goal of this step is to make sure that requested changes were properly approved, implemented and documented.  You can accomplish this in a few different ways - depending on whether you have a tool to assist you or you are doing it manually.

You will need to pull, at random, around 10 change requests since the last audit. The basic questions you should be asking when you audit a firewall change are:

  • Is the requester documented, and is s/he authorized to make firewall change requests?
  • Is the business reason for the change documented?
  • Are there proper reviewer and approval signatures (electronic or physical)?
  • Were the approvals recorded before the change was implemented?
  • Are the approvers all authorized to approve firewall changes (you will need to ask for a list of authorized individuals)?
  • Are the changes well-documented in the change ticket?
  • Is there documentation of risk analysis for each change?
  • Is there documentation of the change window and/or install date for each change?
  • Is there an expiration date for the change?

If you are doing this manually, the first thing you need to do is match each of the changes up with a firewall device and with a policy. Now match the change requests up with the firewall rule(s) that implemented the requested traffic. Already stumped?  Then you know where you need to improve.  The comment on each rule should have at least 2 pieces of data: the change ID of the request and the initials of the engineer who implemented the change.

There are more automated ways to do this.  For example, Tufin SecureTrack shows you who added the rule and when, as well as if s/he added anything else to the policy at the same time. You can put the change ticket number in the comment field, so that the rule will have a hyperlink back to the change ticket to simplify looking up the audit trail.  You can even run a rule history report over time to see how this rule has changed with other change tickets since it was implemented.  The most complete solution would be to use a security change automation product like SecureChange Workflow which will show the rule request along with audit signoff, risk analysis, and implementation into the rule-base, so that the whole lifecycle from request to implementation is documented and auditable.

Auditing the Firewall Rule Base

The second technical step in an audit is usually a review of the firewall rulebase (also called a policy). The methodology for this step varies widely among auditors because it has traditionally been difficult to do and heavily technology-dependent.

For each of these questions you should have a ranking based on the type of firewall and it's placement in your infrastructure. For example, a firewall not connected to the Internet does not have the same risk as one that is connected to the internet; internal firewalls tend to be more permissive than external firewalls.

The first questions that should be asked about the rulebase are related to basic policy maintenance and good design practices that grant minimal access for each device.  To answer these questions, you need to look at each rule in your rulebase and as well as a year's worth of logs, which will tell you which rules are being used.  This has always been a lengthy manual process until recently, with the arrival of tools like SecureTrack that can be used to answer these questions programmatically and automatically.

  • How many rules does the policy have? How many did it have at last audit? Last year?
  • Are there any uncommented rules?
  • Are there any redundant rules that should be removed?
  • Are there any rules that are no longer used?
  • Are there any services in the rules that are no longer used?
  • Are there any groups or networks in the rules that are no longer used?
  • Are there any firewall rules with ANY in three fields (source, destination, service/protocol) and a permissive action?
  • Are there any rules with ANY in two fields and a permissive action?
  • Are there any rules with ANY in one field and a permissive action?
  • Are there any overly permissive rules: rules with more than 1000 IP addresses allowed in the source or destination? (you might want a number other than 1000, like 10,000, or 500)

The second list of questions that should be asked about a rulebase concern risk and compliance. These rules are more technically challenging to answer.  You must understand the technology of your firewall to understand what traffic is actually passed by each rule, and if there is a group of services called "allowed services," then which ports and protocols actually pass though that rule.  The advantage of a tool like SecureTrack is that it can understand each security policy and automate deep technology questions like these. SecureTrack can answer all of these questions with the Security Risk Report and Customized Compliance Checks:

  • Are there any rules that violate our corporate security policy?
  • Are there any rules that allow risky services inbound from the Internet?  While you may have a different list of what is considered "risky" for your company, most start with protocols that pass login credentials in the clear like telnet, ftp, pop, imap, http, netbios, etc.
  • Are there any rules that allow risky services outbound to the internet?
  • Are there any rules that allow direct traffic from the Internet to the Internal network (not the DMZ)?
  • Are there any rules that allow traffic from the Internet to sensitive servers, networks, devices or databases?

There you have it, my top two steps for a firewall audit.  If you take the time to master these two processes you will find that it is much easier to pass firewall audits.  These questions are much easier to answer with the help of automation technology. And having responded to hundreds of firewall audits, I'm quite passionate about making sure SecureTrack has the knowledge to help administrators answer difficult audit questions quickly.

Michael

Recommended: How to Clean Up a Firewall Rulebase – Tufin Firewall Expert Tip #6