ipfilter resource
Use the ipfilter
Chef InSpec audit resource to test rules defined for ipfilter
. The ipfstat
utility is used to report on packet filter statistics and filter list. ipfstat -io
is used to view the active filtering rule set for the input and the output side of the kernel IP processing. The rule match is done against the output rules of ipfstat -io
.
Availability
Installation
This resource is distributed with Chef InSpec and is automatically available for use.
Syntax
An ipfilter
resource block declares tests for rules defined for IP Filter:
describe ipfilter do
it { should have_rule("RULE") }
end
where
have_rule('RULE')
tests the active rule for ipfilter. This must match the entire line taken from'ipfstat -io'
.
Examples
The following examples show how to use this Chef InSpec audit resource.
Test if there are no restrictions on a loopback interface
describe ipfilter do
it { should have_rule("pass in quick on lo0 all") }
it { should have_rule("pass out quick on lo0 all") }
end
Test if there are no restrictions on inside LAN interface named xl0 for private network
describe ipfilter do
it { should have_rule("pass in quick on xl0 all") }
it { should have_rule("pass out quick on xl0 all") }
end
Test if there is a rule allowing FTP traffic on the public interface named dc0
describe ipfilter do
it { should have_rule("pass out quick on dc0 proto tcp from any to any port = ftp flags S/FSRPAU keep state") }
end
Test if there is a rule allowing SSH on the public interface named dc0
describe ipfilter do
it { should have_rule("pass out quick on dc0 proto tcp from any to any port = ssh flags S/FSRPAU keep state") }
end
Note that the rule specification must exactly match what is in the output of 'ipfstat -io'
, which depends on how you have built your rules.
Matchers
For a full list of available matchers, please visit our matchers page.
have_rule
The have_rule
matcher tests the named rule against the information in the output rule of 'ipftstat -io'
:
it { should have_rule("RULE") }
Was this page helpful?