VOIP saves money if you can deploy and manage it properly, but there are certain risks that you need to take into account. As you know that VOIP is ip based voice solution and IP network is always vulnerable and point of interest to the intruders.
- If you are using SIP make sure you are using SIPS, or SIP wrapped in a TLS tunnel for the protection of session layer. Therefore, to secure VoIP authentication process, use SIP with SSL/TLS instead of using the standard digest authentication.
- SIP ‘register’ and ‘invite’ request must be authenticated by the SIP user agent. If you find that your SIP user agent is not authenticating INVITE and REGISTER request, your VOIP security can be easily breached.
- If you are using H323, pay attention to the way session setup authentication is being used. To protect session layer, wrap H225 in a TLD tunnel. Avoid using standard H.323 authentication that use MD5 hash and password.
- H225 use time stamp for NTP server to authentication. The duration of this timestamp in NTP server should be less than 15 minutes.
- If you are using IAX instead or H323 or SIP make sure it is using TLS tunnel for session layer protection.
- Never allow concurrent VOIP session with the same username and password. A single username and password should be limited to only one successful authentication.
- Not matter if you are using SIP, H323 or IAX, make sure your session protocols needs authentication in order to unregister a user agent or endpoint device.
- When user agent use LDAP store for authentication, make sure LDAP is used with SSL to protection authentication information.
- Use media layer encryption in order to encrypt the voice communication. Media layer encryption provides adequate privacy to the voice communication.
- When you use SRTP you must use TLS to make sure key exchange traverse the network in encrypted form.
- To prevent TRP injection attack, the RTP entropy should be implemented in such a way that it becomes difficult for attacker to guess values. Make sure you implement full 64-bits of SSRC and timestamp are generated randomly instead of sequentially.
- Avoid using default aliases of E.164. Make sure E.164 is customized and unique.
- Set the gatekeeper’s registration reject policy to reject. Remember that by setting this policy to ‘reject’ you open up the possibility of denial of service attack. So, make sure you take necessary measures to mitigate the DoS attacks before changing the registration reject policy.
- Use only one specific E.164 alias with a given username and password.
- When two endpoints try to register with the same alias name, the endpoints should receive error messages such as secuityDenial or duplicateAlias.
- 1x supported devices should be used in the VOIP network.
- You should remember that VLAN cannot secure a VOIP network. To make sure that only authorized system can be plugged into your VoIP VLAN, you need to use 802.1x technology.
- You should enable ARP monitoring in your VoIP network in order to prevent ARP pollution/poisoning attacks.
- VoIP network and data network should be in their own subnets of VLAN.
- Use out-of-band VOIP device management method from an isolated and secure management network. If you use in-band device management method, your in-band management should be encrypted.
- Use VoIP access filter (IP filter or hostname filter) to make sure only authorized machine can manage VoIP devices.
- Use encryption protocols (SSH, SSL (HTTPS)) for VoIP administration and management.
- Use SNMPv3 instead of SNMPv1
- Make sure data and timestamp are correct. This will ensure the integrity of all log files.
- VoIP management software must log all critical events and log on activities. Logs should be stored and reviewed regularly.
- All VoIP hard phones should use unique PIN that should be at least four digits long.
- Use only https for transfer boot image files from the network to the hard phones.
- Enable server side controls by creating an explicit permission list that tells who can make outbound calls, international calls etc. this will help prevent abuse of phone system and also control toll fraud.
- Turn off auto discover option for all external gatekeepers.
- Devices should use non-self-signed SSLv3/TLSv1 with strong ciphers.
- When an incorrect, expired, or self-signed SSL certificate is used for communication, connection should be dropped immediately.
- Use a dedicated DNS and DHCP server your VOIP network. Do not use the same DNS and DHCP for the voice and data networks.
VOIP security lowers the risk sensitive information leak to a great extent. You should not forget that many business executives share important information on phones and we have a misconception that voice call is private. I hope you will find the above information help in securing your VoIP network. If you have any feedback or suggestion about VoIP security, you can use the comments box below to share your experience.
