Iptables Server Security Policy collection

Common ports on Linux servers

Ftp:20 ssh:22 http:80 telnet:23 rsync:873 svn:3690

pop3:110 smtp:25 dns:53 mysql:3306 nfs:111

If your iptables basic knowledge is not yet known, it is recommended to take a look first.

Start configuration

Let's configure a firewall for the filter table.

(1) Check the setting of this institution in Iptables

[Email protected] ~]# iptables-l-N

As you can see, when I installed Linux, I chose a firewall and opened the 22,80,25 port.

If you did not choose to boot the firewall when installing Linux, this is the case

Chain INPUT (Policy ACCEPT)
Target Prot opt source destination

Chain FORWARD (Policy ACCEPT)
Target Prot opt source destination

Chain OUTPUT (Policy ACCEPT)
Target Prot opt source destination

There are no rules.

(2) Clear the original rules.

Whether or not you start a firewall when you install Linux, if you want to configure your own firewall, clear all the rules for the filter now.

[[email protected] ~]# iptables-f clears all rule chain rules in the preset table filter
[[email protected] ~]# iptables-x clear Preset table rules in user-defined chains in filter

We're having a look.

[Email protected] ~]# iptables-l-N
Chain INPUT (Policy ACCEPT)
Target Prot opt source destination

Chain FORWARD (Policy ACCEPT)
Target Prot opt source destination

Chain OUTPUT (Policy ACCEPT)
Target Prot opt source destination

Nothing at all, and we did not start the firewall when installing Linux is the same. (in advance, these configurations are like using commands to configure the IP, the restart will lose its effect), how to save.

[Email protected] ~]#/etc/rc.d/init.d/iptables Save

This will allow you to write to the/etc/sysconfig/iptables file. Remember to re-start the firewall after writing to make it work.

[Email protected] ~]# service iptables restart

Now that the Iptables configuration table does not have any configuration, let's start our configuration.

(3) Set preset rules

[Email protected] ~]# iptables-p INPUT DROP

[[email protected] ~]# iptables-p OUTPUT ACCEPT

[Email protected] ~]# iptables-p FORWARD DROP
The above means that when the two chain rules (Input,forward) in the Iptables filter table are exceeded, the packets that are not in the two rules are handled, and that is the drop (abort). It should be said that this configuration is very safe. We want to control the incoming packets.

And for the output chain, that is, out of the package we do not have to do too much restriction, but to take the accept, that is, not in the rules of the package how to do it, that is through.

It can be seen that the Input,forward two chain uses what packets are allowed to pass through, and the output chain is not allowed by what packets pass.

This setting is quite reasonable, of course, you can also drop three chains, but I think it is not necessary, and to write the rules will increase. But if you only want a few rules that are limited, such as just Web servers. It is recommended that all three chains are drop.

Note: If you are a remote SSH login, you should drop it when you enter the first command. Because you didn't set any rules.

How to do, go to the machine operation Bai!

(4) Add a rule.

First add the input chain, the default rule of the input chain is drop, so we write the need to ACCETP (through) the chain

In order to be able to use remote SSH login, we have to turn on port 22.

[[email protected] ~]# iptables-a input-p TCP--dport 22-j ACCEPT

[[email protected] ~]# iptables-a output-p tcp--sport 22-j ACCEPT (Note: This rule, if you set the OUTPUT to drop it will be written on this part, many people are looking at the writing of this rule resulted in the beginning You can't ssh. In the remote, is not good.

The other port is the same, if the Web server is turned on, output is set to drop, you also add a chain:

[[email protected] ~]# iptables-a output-p TCP--sport 80-j ACCEPT, other similarly.)

If you made a Web server, turn on port 80.

[[email protected] ~]# iptables-a input-p TCP--dport 80-j ACCEPT
If you do a mail server, turn on port 25,110.

[[email protected] ~]# iptables-a input-p TCP--dport 110-j ACCEPT
[[email protected] ~]# iptables-a input-p TCP--dport 25-j ACCEPT
If you do an FTP server, turn on port 21

[[email protected] ~]# iptables-a input-p TCP--dport 21-j ACCEPT

[[email protected] ~]# iptables-a input-p TCP--dport 20-j ACCEPT

If you do a DNS server, turn on port 53

[[email protected] ~]# iptables-a input-p TCP--dport 53-j ACCEPT

If you also do other servers, which port you need to open, just write it.

The main writing above is the input chain, usually not in the above rules, all drop

Allow ICMP packets to pass, that is, to allow pings,

[[email protected] ~]# iptables-a output-p icmp-j ACCEPT (OUTPUT set to drop)

[[email protected] ~]# iptables-a input-p icmp-j ACCEPT (INPUT set to drop)

Allow loopback! (This may cause problems such as DNS not shutting down properly)

Iptables-a input-i lo-p all-j ACCEPT (if INPUT DROP)
Iptables-a output-o lo-p all-j ACCEPT (if OUTPUT DROP)

Write the output chain below, the default rule for the output chain is accept, so we write a chain that needs drop (discard).

Reduce insecure port connections

[[email protected] ~]# iptables-a output-p TCP--sport 31337-j DROP

[[email protected] ~]# iptables-a output-p TCP--dport 31337-j DROP

Some Trojans scan services on ports 31337 through 31340 (that is, the elite ports in the hacker language). Since legitimate services do not use these non-standard ports to communicate, blocking these ports can effectively reduce the chance that your network may be infected by the machine and their remote primary server for independent communication

There are other ports as well, like: 31335, 27444, 27665, 20034 NetBus, 9704, 137-139 (SMB), 2049 (NFS) port should also be banned, I write in this is not all, interested friends should go to check the relevant information.

Of course, it's safer to go in and out. You can also set the output chain to drop, then you add more rules, like the above added

Allow SSH to log in as well. Just write it.

The following is a more detailed rule, that is, to restrict to a machine

For example: We only allow SSH connection for 192.168.0.3 machines.

[[email protected] ~]# iptables-a input-s 192.168.0.3-p tcp--dport 22-j ACCEPT

If you want to allow or restrict a certain IP address, you can use 192.168.0.0/24 to represent all IPs on the 192.168.0.1-255 side.

24 indicates the number of subnet masks. But remember to delete the line in the/etc/sysconfig/iptables.

-A input-p tcp-m TCP--dport 22-j ACCEPT because it means all addresses can be logged in.

or using the command mode:

[[email protected] ~]# iptables-d input-p TCP--dport 22-j ACCEPT

And then save, I say one side, the reverse is the way of the command, only at the time of entry into force, if you want to restart the role, it should be saved. Write to the/etc/sysconfig/iptables file.

[Email protected] ~]#/etc/rc.d/init.d/iptables Save

This write!192.168.0.3 indicates that the IP address except the 192.168.0.3

Other regular connections are set up as well.

In the following is the forward chain, the default rule of the forward chain is drop, so we write the need to ACCETP (through) the chain, the monitoring of the forwarding chain.

Turn on forwarding, (when doing NAT, forward default rule is drop, must be done)

[Email protected] ~]# iptables-a forward-i eth0-o eth1-m State--state related,established-j ACCEPT

[Email protected] ~]# iptables-a forward-i eth1-o eh0-j ACCEPT

Discard Bad TCP packets

[[Email protected] ~] #iptables-A forward-p TCP! --syn-m State--state New-j DROP

Handle the number of IP fragments, prevent attacks, allow 100 per second

[[Email protected] ~] #iptables-A forward-f-M limit--limit 100/s--limit-burst 100-j ACCEPT

Set ICMP packet filtering to allow 1 packets per second, limiting the trigger condition to 10 packets.

[[Email protected] ~] #iptables-A forward-p icmp-m limit--limit 1/s--limit-burst 10-j ACCEPT

I'm in front only so allow ICMP packets to pass because I have restrictions here.

Two, configure a NAT table to fire the wall

1. View the settings of this agency on NAT

[Email protected] rc.d]# iptables-t nat-l
Chain prerouting (Policy ACCEPT)
Target Prot opt source destination

Chain postrouting (Policy ACCEPT)
Target Prot opt source destination
SNAT All-192.168.0.0/24 anywhere to:211.101.46.235

Chain OUTPUT (Policy ACCEPT)
Target Prot opt source destination

My NAT has been configured (just to provide the simplest proxy Internet access, and no firewall rules have been added). about how to configure NAT, refer to my other article

Of course you don't have to clear the rules if you haven't configured NAT, because Nat doesn't have anything by default.

If you want to clear, the command is

[[email protected] ~]# iptables-f-t NAT

[[email protected] ~]# Iptables-x-t NAT

[[email protected] ~]# Iptables-z-t NAT

2, adding rules

Add basic NAT Address translation (see my other article on how to configure NAT),

To add a rule, we only add the drop chain. Because the default chain is all accept.

Prevention of intranet IP spoofing for external network

[Email protected] sysconfig]# iptables-t nat-a prerouting-i eth0-s 10.0.0.0/8-j DROP
[Email protected] sysconfig]# iptables-t nat-a prerouting-i eth0-s 172.16.0.0/12-j DROP
[Email protected] sysconfig]# iptables-t nat-a prerouting-i eth0-s 192.168.0.0/16-j DROP
If we want to, for example, stop MSN,QQ,BT and so on, need to find the port or IP they use, (personally think not too much necessary)

Cases:

Prohibit all connections to the 211.101.46.253

[Email protected] ~]# iptables-t nat-a prerouting-d 211.101.46.253-j DROP

Disabling the FTP (21) port

[[email protected] ~]# iptables-t nat-a prerouting-p tcp--dport 21-j DROP

The scope of the writing is so large that we can define it more precisely.

[[email protected] ~]# iptables-t nat-a prerouting-p tcp--dport 21-d 211.101.46.253-j DROP

This disables only FTP connections for 211.101.46.253 addresses, and other connections are available. such as Web (80 port) connections.

As I wrote, you just have to find the IP address of other software such as QQ,MSN, and the port, and based on what protocol, just write it.

At last:

drop illegal connection
[[email  Protected] ~]# iptables-a input    -M State--state invalid-j drop
[[email protected] ~]# iptables-a output   -M State--state invalid-j DROP
[[email protected] ~]# iptables-a forward-m State--state invalid-j drop
allow all established and related connections
[[email protected] ~]# Iptables-A Input-m State--state established,related-j accept
[[email  protected] ~]# iptables-a output-m State--state established,related-j accept

[Email protected] ~]#/etc/rc.d/init.d/iptables Save

This will allow you to write to the/etc/sysconfig/iptables file. Remember to re-start the firewall after writing to make it work.

[Email protected] ~]# service iptables restart

Do not forget to save, do not write a save once. You can save, experiment and see if it meets your requirements.

I've tried all the rules above, no problem. Ccc

This article is from the "Blacksmith operation and Maintenance Network" blog, please be sure to keep this source http://blacksmith.blog.51cto.com/7087635/1586155

Iptables Server Security Policy collection