Incoming and outgoing traffic flow rules are the traffic flows used by your applications and operating system. You should document their source, destination, ports and any other useful characteristics about them. Lay them out in tables or in a spreadsheet to allow you to better visual and keep track of them. You should also try to "lock" down your rules. If it is possible to limit the source or destination of traffic flow, then do so. For example, if you only need to access two DNS servers then you can write rules to ensure traffic on port 53 can only go to those DNS servers.
Defensive rules consist of rules designed to counter known network-based attacks, scanning and other forms of malicious traffic. There are a variety of these available to you. Many of them are documented in various iptables scripts or sites online. These include rules to counteract network and port scans, SYN/ACK attacks, SYN flooding and other types of malicious traffic. These change on a regular basis so you need to keep up with current attacks and counters. You also need to extensively test these sorts of rules. In the past, badly coded applications have occasionally behaved like attack or scanning tools and had their traffic blocked by these types of rules.
Dig Deeper on Linux system security best practices
Related Q&A from James Turnbull
A user wants to implement OSSEC on a Windows server because he has no server side Linux operating system.continue reading
Solaris 10 Trusted Extensions and SELinux are best suited to different system requirements and administrator skill sets. Our security expert explains...continue reading
Configuring spam filters Spamassassin and dspam together in the email server Postfix is easy with the resources listed by our security expert.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.