5 terms you need to know before you employ VoIP

1. Network Address Translation
Make sure your network and security infrastructure, including firewalls, IDS, 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 allocated 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. IP PBX
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. VoIP phone
Always properly secure any remote access and configuration capabilities to individual VoIP devices to eliminate any backdoors. VoIP phones as the endpoints are the most common and widest accessible component of a VoIP infrastructure. Default login and administrator passwords on such devices are a very common avenue for attacks. Disable any insecure remote access features, such as FTP and Telnet, and disable local administration and management features.

4. IPsec
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. VLAN
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.

By Gerhard Eschelbeck
20 Dec 2004 | SearchSecurity.com
http://searchenterprisevoice.techtarget.com/originalContent/0,289142,sid66_gci1041738,00.html

Do you have something to add to this definition? Let us know. Send your comments to techterms@whatis.com

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Will VoIP attacks result in more than just spam? Today's enterprises are seeing VoIP installations of every scale. Mike Chapple explains why that means attacks with results far more serious than... Has FFIEC made any VoIP-specific mandates? Mike Rothman discusses the FFIEC risk management program and explains what FFIEC considerations should be made when using VoIP. Enterprise security in 2008: Addressing emerging threats like VoIP and virtualization Network security expert Mike Chapple looks ahead to 2008 and examines virtualization and VoIP, two technologies growing in popularity -- and security...