1. Make sure your network and security infrastructure, including firewalls, IDSes, VPNs, etc., are voice-optimized and capable of supporting the advanced security requirements for VoIP. Traditional static policy rules are not adequate for VoIP traffic control. The protocols involved dynamically allocate ports during call setup, requiring opening and closing of ports at the security gateway on demand. Inspection of VoIP traffic not only at the network layer, but also at the application level is necessary to deal with the challenges of VoIP protocols in Network Address Translation (NAT) environments. Finally, bandwidth, latency and quality of service become critical requirements for network and security infrastructure, when processing multiple simultaneous voice streams.
2. Critical security vulnerabilities are being identified on a regular basis, leaving systems vulnerable for denial of service and even more severe buffer overflow attacks. As your IP PBX is at the core of your VoIP infrastructure, ensure that the base operating system of your IP PBX, as well as network infrastructure, are always updated and patched for the latest security vulnerabilities. Regular security assessments of your VoIP infrastructure provide identification and remediation of such security flaws to avoid attacks and prevent outages.
3. Always properly secure any remote access and
4. If your VoIP traffic goes over unsecured channels, such as the Internet, use encryption technologies like IPsec tunnels to secure the VoIP traffic. While many of the VoIP protocols include capabilities for encryption and authentication, most of them are optional. It is essential to establish secure tunnels for carrying the VoIP information streams (call signaling, call control and media) between sites and over untrusted networks.
5. Structure your network and leverage VLANs to separate voice and data devices and traffic. While this may have limited impact on security, deploying VoIP devices on separate VLANs permits isolating data traffic from voice and signaling traffic, as well as utilizing Quality of Service (QoS) capabilities.
Gerhard Eschelbeck, CTO and vice president of engineering, Qualys Inc.
This article originally appeared on SearchSecurity.com.
This was first published in January 2006