MultiCom Technical Support

[Support]

By default the MultiCom Firewall protects your network with the SecureWall. This blocks incoming packets that are not a response to an outgoing request. If the packet is a response to an outgoing request it is allowed into the network.

There are additional steps that you can take however to better secure your network while using the MultiCom Firewall:

Basic Security

• Have you changed the default username and password to access the firewall?
  
• Have you activated the NAT firewall on the WAN interface? (also known as the SecureWall)
  
• Have you activated the standard filtering protection? (Dos, Spoofing, TCP-Flags)
  
• Did you save your configuration in the boot memory?
  
• Did you make a backup of your active configuration file (AND the security file if you are using IPSec)?
  
• Do you only access the MultiCom firewall itself using HTTPS or SSH telnet?

Medium Security

• Have you disabled unused interfaces?
  
• Have you activated filtering rules to limit the services you want accessible through the firewall?
  
• Have you remapped the firewall's web server, telnet, ftp services with NAT for the LAN and/or WAN? (use a different port than 443 for HTTPS access for example)
  
• Have you limited which IP addresses/ computers are allowed to go through the firewall to access the Internet?
  
• Have you disabled unused services on the firewall?

Maximum Security

• Have you limited which IP addresses can administer the firewall (using filtering rules)?
  have you added a logging rule for each of your filtering rules to know when they are activated?
  
• Have you blocked or limited pings to the firewall?
  
• Have you enabled syslog reports to a particular IP address and are running a syslog software to keep track of activity?
  
• Are you using the latest firmware?
  
• Have you added a filtering rule with logging to see all out going traffic that is attempted but not allowed (for instance traffic not to a webserver)?