See also FreePBX Firewall

Using symbols in these next two passwords may not be supported and they must match.

vi /etc/asterisk/manager.conf

[admin]
secret = yournewpassword

vi /etc/amportal.conf

AMPMGRPASS=yournewpassword

Admin → Administrators → admin → Change Password

Settings → Advance Settings → Asterisk Manager Password → Change Password

Settings → Advance Settings → User Portal Admin Password → Change Password

SELinux generally gets in the way, so it is often disabled:

setenforce 0

vi /etc/selinux/config

SELINUX=disabled

Only open the required ports and no more to minimize your 'attack surface'.

See also Vitelity for Vitelity-specific firewall rules.

Some or all of the following ports may need to be opened:

Two firewall options are Arno's Firewall or the built-in IPtables.

Arno's Firewall is a light weight and comprehensive firewall based on iptables which is also used in the ASTLinux PBX.

See also Arno's Firewall

If you plan to use TFTP or FTP on the PBX itself, load a couple of kernel modules and make them survive reboots:

modprobe ip_conntrack_tftp
modprobe ip_conntrack_ftp
depmod -a

Now we modify the default firewall rules in a way that survives reboots.

Add these lines right after the 'accept ssh' (port 22) line:

vi /etc/sysconfig/iptables

-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
-A INPUT -m state --state NEW -m tcp -p tcp --dport 443 -j ACCEPT
-A INPUT -m state --state NEW -m udp -p udp --dport 69 -j ACCEPT
-A INPUT -m state --state NEW -m udp -p udp --dport 4569 -j ACCEPT
-A INPUT -m state --state NEW -m udp -p udp --dport 5060:5061 -j ACCEPT
-A INPUT -m state --state NEW -m udp -p udp --dport 10000:20000 -j ACCEPT

service iptables reload

iptables -nL

It is recommended to leave SSH on the standard port 22 and use a different port on your external firewall forwarded in to port 22 on the PBX. This keeps the FreePBX status page 'green'.

Edit /etc/ssh/sshd_config, uncomment the Port setting changing it to 2222, then restart the sshd service:

vi /etc/ssh/sshd_config

Port 2222

service sshd restart

Fix the FreePBX Status listing (this may also be in Advanced Settings):

vi /etc/amportal.conf

SSHPORT=2222

amportal restart

Make sure the httpd.conf option AllowOverride All is in effect. If it is not, the .htaccess file will not be actuated.

Create an .htaccess file in your document root then restart Apache:

vi /var/www/html/.htaccess

# Force SSL
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

service httpd restart

mysqladmin -u root password newpassword

or

mysqladmin -u root -p 'oldpassword' password 'newpassword'

Fail2Ban is a superior tool that monitors various log files looking for brute force attacks. Once an attack has been identified, the attacker is blocked from further attempts for a preconfigured period of time.

See Fail2Ban.

For a base CentOS 6 box, after installing Fail2Ban via the EPEL repo, you can just copy and paste the following in one go to get a basic Fail2Ban installation set up for your PBX:

cat << EOF >> /etc/fail2ban/fail2ban.local
# Fail2Ban local configuration file
#
# This file overrides the fail2ban.conf file

[Definition]
logtarget = /var/log/fail2ban.log

EOF

cat << EOF >> /etc/fail2ban/jail.local
# Fail2Ban local configuration file
#
# This file overrides the jail.conf file

[DEFAULT]
ignoreip = 127.0.0.1 209.193.64.0/24 70.176.57.141
bantime  = 600
findtime  = 600
maxretry = 3
backend = auto


[asterisk-iptables]
enabled  = true
filter   = asterisk
action   = iptables-allports[name=SIP, protocol=all]
#           sendmail-whois[name=SIP, dest=none@yourpbx.com, sender=none@yourpbx.com]
logpath  = /var/log/asterisk/fail2ban
maxretry = 5
bantime = 600

[ssh-iptables]
enabled  = true
filter   = sshd
action   = iptables[name=SSH, port=ssh, protocol=tcp]
#           sendmail-whois[name=SSH, dest=none@yourpbx.com, sender=none@yourpbx.com]
logpath  = /var/log/secure
maxretry = 3

[apache-tcpwrapper]
enabled  = true
filter   = apache-auth
action   = iptables-allports[name=PBX-GUI, port=http, protocol=tcp]
#           sendmail-whois[name=PBX-GUI, dest=none@yourpbx.com, sender=none@yourpbx.com]
logpath  = /var/log/httpd/error_log
maxretry = 3

[vsftpd-iptables]
enabled  = true
filter   = vsftpd
action   = iptables[name=FTP, port=ftp, protocol=tcp]
#           sendmail-whois[name=FTP, dest=none@yourpbx.com, sender=none@yourpbx.com]
logpath  = /var/log/vsftpd.log
maxretry = 3
bantime  = 600

[apache-badbots]
enabled  = true
filter   = apache-badbots
action   = iptables-multiport[name=BadBots, port="http,https"]
#           sendmail-whois[name=PBX GUI, dest=none@yourpbx.com, sender=none@yourpbx.com]
logpath  = /var/log/httpd/*access_log
bantime  = 600
maxretry = 1

EOF

cat << EOF >> /etc/fail2ban/filter.d/asterisk.conf
# Fail2Ban configuration file
#
# Asterisk Filter - /etc/fail2ban/filter.d/asterisk.conf

[INCLUDES]

# Read common prefixes. If any customizations available -- read them from
# common.local
#before = common.conf

[Definition]

#_daemon = asterisk

# Option:  failregex
# Notes.:  regex to match the password failures messages in the logfile. The
#          host must be matched by a group named "host". The tag "<HOST>" can
#          be used for standard IP/hostname matching and is only an alias for
#          (?:::f{4,6}:)?(?P<host>\S+)
# Values:  TEXT
#

failregex = Registration from '.*' failed for '<HOST>(:[0-9]{1,5})?' - Wrong password
	    Registration from '.*' failed for '<HOST>(:[0-9]{1,5})?' - No matching peer found
	    Registration from '.*' failed for '<HOST>(:[0-9]{1,5})?' - Device does not match ACL
	    Registration from '.*' failed for '<HOST>(:[0-9]{1,5})?' - Username/auth name mismatch
	    Registration from '.*' failed for '<HOST>(:[0-9]{1,5})?' - Peer is not supposed to register
	    NOTICE.* <HOST> failed to authenticate as '.*'$
	    NOTICE.* .*: No registration for peer '.*' (from <HOST>)
	    NOTICE.* .*: Host <HOST> failed MD5 authentication for '.*' (.*)
	    VERBOSE.* logger.c: -- .*IP/<HOST>-.* Playing 'ss-noservice' (language '.*')

# Option:  ignoreregex
# Notes.:  regex to ignore. If this regex matches, the line is ignored.
# Values:  TEXT
#
ignoreregex =

EOF

service fail2ban restart

Seven Easy Steps to Better SIP Security on Asterisk:

1. Don’t accept SIP authentication requests from all IP addresses. Use the permit= and deny= lines in sip.conf to only allow a reasonable subset of IP addresess to reach each listed extension/user in your sip.conf file. Even if you accept inbound calls from “anywhere” (via [default]) don’t let those users reach authenticated elements!
2. Set alwaysauthreject=yes in your sip.conf file. This option has been around for a while (since 1.2?) but the default is no, which allows extension information leakage. Setting this to yes will reject bad authentication requests on valid usernames with the same rejection information as with invalid usernames, denying remote attackers the ability to detect existing extensions with brute-force guessing attacks.
3. Use STRONG passwords for SIP entities. This is probably the most important step you can take. Don’t just concatenate two words together and suffix it with “1”. If you’ve seen how sophisticated the tools are that guess passwords, you’d understand that trivial obfuscation like that is a minor hindrance to a modern CPU. Use symbols, numbers, and a mix of upper and lowercase letters at least 12 digits long.
4. Block your AMI manager ports. Use permit= and deny= lines in manager.conf to reduce inbound connections to known hosts only. Use strong passwords here, again at least 12 characters with a complex mix of symbols, numbers, and letters.
5. Allow only one or two calls at a time per SIP entity, where possible. At the worst, limiting your exposure to toll fraud is a wise thing to do. This also limits your exposure when legitimate password holders on your system lose control of their pass-phrase, writing it on the bottom of the SIP phone, for instance, which I’ve seen.
6. Make your SIP usernames different than your extensions. While it is convenient to have extension “1234” map to SIP entry “1234” which is also SIP user “1234”, this is an easy target for attackers to guess SIP authentication names. Use the MAC address of the device, or some sort of combination of a common phrase + extension MD5 hash (example: from a shell prompt, try “md5 -s ThePassword5000″)
7. Ensure your [default] context is secure. Don’t allow unauthenticated callers to reach any contexts that allow toll calls. Permit only a limited number of active calls through your default context (use the “GROUP” function as a counter.) Prohibit unauthenticated calls entirely (if you don’t want them) by setting allowguest=no in the [general] part of sip.conf.
8. See more at: http://blogs.digium.com/2009/03/28/sip-security/#sthash.swNSlCKz.dpuf