NIST Offers Guidelines for Securing VOIP

May 6th, 2004 | Industry News

Voice over IP (VOIP) technology offers potential cost savings and increased functionality, but it also may introduce new security headaches for systems administrators, the National Institute of Standards and Technology has warned.

VOIP adds a number of complications to existing network technology, and these problems are magnified by security considerations, the agency said in a draft version of security guidelines released today for public comment.

Firewalls can delay or block call setups, and encryption can introduce unacceptable latency. Putting voice on data networks opens new potential avenues for attacks to the data network, and Network Address Translation complicates the process.

VOIP is still an emerging technology, NIST said, and agencies considering it should carefully assess their understanding of the technology and the associated risks, and the maturity of both their IT and physical security. Because anyone with physical access to the LAN could potentially monitor voice traffic, access control to network elements is critical.

NIST recommends:

Separating voice and data traffic on logically different networks Denying access to the voice gateway from the data network Using firewalls designed for VOIP traffic Using IPsec or Secure Shell as well as strong authentication for remote management and auditing Encrypting voice traffic at the router or gateway if performance is a problem. Newer IP phones are able to handle Advanced Encryption Standard algorithms. Federal Information Processing Standard 140-2 certification is required for federal use.

Agencies also should consider how Enhanced 911 service, which provides the location of the caller to emergency dispatchers, will be provided. Although most VOIP vendors have workable solutions for E-911 service, government regulators and vendors are still working out standards, NIST said.

Reported By GCN Daily Updates,
Copyright 2004 Post-Newsweek Business Information, Inc.