Your SlideShare is downloading. ×
Print 9580 Wireless Overview whitepaper
Print 9580 Wireless Overview whitepaper
Print 9580 Wireless Overview whitepaper
Print 9580 Wireless Overview whitepaper
Print 9580 Wireless Overview whitepaper
Print 9580 Wireless Overview whitepaper
Print 9580 Wireless Overview whitepaper
Print 9580 Wireless Overview whitepaper
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Print 9580 Wireless Overview whitepaper

555

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
555
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. White Paper VoIP Security and Privacy VoIP Security and Privacy Making PC Platforms and Networks Highly Secure
  • 2. Introduction Voice over Internet Protocol (VoIP) offers many operational benefits over traditional PSTN calls, but with this technology comes additional concerns about security and privacy. Careful system design can address these issues and, in fact, make VoIP more secure and private than PSTN. Potential benefits of VoIP include higher fidelity (wideband) audio, video, presence information, lower cost and improved manageability, all of which are made possible because VoIP travels over a flexible data network rather than the more confined circuit-switched network. However, the flexibility of this data network and its potential shared usage with other applications also adds levels of vulnerability. To address security and privacy concerns, the traffic not only needs to be encrypted effectively, but the distribution and storage of keys needs to be managed and the integrity of platforms verified. Ensuring network availability and quality of service are also important issues, but are beyond the scope of this paper. When a PC hosts the VoIP client (sometimes called a software-phone or softphone), there are additional benefits from the integration, as well as additional threats. Benefits include use of the PC’s resources and screen for video, file and document sharing, and rich integration with other applications, such as initiating a call from a calendar appointment. New vulnerabilities associated with the ability to interact with other applications include viruses, worms and spyware. In fact, it is because VoIP clients are implemented on powerful platforms that more technology is available to provide robust security and privacy. Properly implemented, VoIP systems can be made more secure than the PSTN due to the availability of both communications security technology and platform security technology. This paper describes solutions for addressing security and privacy issues for VoIP networks and how to effectively address network vulnerabilities while maintaining platform integrity and performance. 2
  • 3. Contents Introduction .........................................................................2 IPSEC is a more general layer 3 security protocol in that it can be used for many IP applications including VoIP. SRTP was VoIP Network Security..........................................................3 designed specifically to protect VoIP (RTP) traffic and is more Data Security ................................................................3 technically appropriate for the application than IPSEC. Infrastructure Security ...................................................3 Proper implementation of the security subsystem and protocols is Client Platform Security ........................................................4 more important than which particular security standard is chosen. Client Platform Integrity .................................................4 (Assuming that the protocol and cryptographic algorithms that Client Attestation ..........................................................6 are chosen are based on well-established standards such as User Authentication.......................................................6 IPSEC or SRTP that have survived extensive peer review). Proper Key Management and Sealed Storage...........................7 implementation dictates that security system issues, such as Summary.............................................................................7 implementing a good randomizer and protecting the security system firmware from malicious or accidental modification, are comprehended, included in the design, and thoroughly tested. Proprietary security protocols are most likely more risky to use VoIP Network Security due to the fact that they do not have as much peer review and are therefore more likely to have undiscovered flaws. VoIP network security can be divided into two general categories: VoIP data security and VoIP infrastructure security. Securely encrypting the signaling and the media is one of the VoIP data security provides for privacy and integrity protection ways that VoIP can be made more secure than PSTN. PSTN of VoIP media transmissions and includes end-user authenti- signaling and media are generally not encrypted, and most of cation of the remote party. VoIP infrastructure security the deployed phones and network equipment are incapable of encompasses protection of the network elements used to encryption. PSTN predominately relies on physical security of carry the VoIP traffic and protection of the signaling and the dedicated networks, but in many ways is vulnerable to network management traffic. eavesdropping or other attacks. End-user authentication/traffic authentication is an end-to- Data Security end security service required to ensure that received VoIP End-to-end cryptographic protection of VoIP traffic over traffic was sent by the expected party and to prevent mas- the public network provides privacy and integrity to VoIP querading. End-to-end authentication service is provided in conversations. There are a number of security protocols key exchange protocols like ISAKMP and MIKEY or can be used for protection of VoIP data traffic. The most popular of provided as a native part of the SIP6 signaling as discussed these are Secure Real Time Protocol (SRTP)1 and the IPSEC in the following section. 2 Encapsulating Security Payload (ESP). Both of these proto- cols require cryptographic keys to be set up either dynamically Infrastructure Security through a separate key management protocol or manually. The Multimedia Internet KEYing (MIKEY)3 protocol is often Infrastructure security protects the VoIP network infrastructure used to exchange keys for use by SRTP, but it has not been from attack. VoIP network infrastructure consists of the network universally adopted. For example, the draft Session equipment used to signal, route, and provide management for Description Protocol Security Descriptions is sometimes 4 VoIP services. Protection of the signaling and management used to exchange keying material and other elements of the communications also falls under the umbrella of infrastructure cryptographic context. The IPSEC suite has its own native security. key exchange protocol called Internet Security Association and Key Management Protocol (ISAKMP).5 3
  • 4. Infrastructure Platform Security Identity and Trust Model Network infrastructure platform security is required to protect A trust infrastructure provides a level of confidence to the against cyber attacks and ensure the integrity of the network. VoIP network interactions. The central part of a VoIP trust It is important that the infrastructure equipment that imple- model is to provide a reasonable level of identity authentication ments the VoIP security functions is built upon platforms that and integrity for the network users. The trust infrastructure are trusted and maintain software integrity. Recent news provides the facilities needed to assign and manage the stories have disclosed vulnerabilities in network equipment identities of VoIP users and is part of the trust model. that could be exploited to crash or remotely run malicious The trust model dictates how identity certification services to code. Such incidents highlight the need for platform assur- VoIP network users and network providers are implemented. ance mechanisms such as those found in a technology that The trust infrastructure contains a Certification Authority (CA) Intel has developed, code-named LaGrande.7 The subject of that can issue cryptographically signed identity certificates or platform security and integrity is discussed further below. credentials to the users of the network. The digital signature of the CA can be verified by the network users who “trust” Protection of Network Signaling that the signed information issued by the CA is correct. These The use of common layer 3, 4 or application layer security certificates are typically formatted in a digital certificate encapsulation protocols such as IPSEC, TLS8(SSL) and according to the ITU X.50911 certificate standard. The trust S/MIME9 is the standard approach to protecting SIP signaling. model also defines what type of “proof of identity” information Secure MIME (S/MIME) is a technology used to sign and must be provided in order to get a certificate. encrypt standalone messages and allow recipients to verify and decrypt them. It was originally developed for protecting Another significant aspect of a trust model is management email but is also used to protect other types of messages, of platform trust, i.e., managing the assurance level of the such as session descriptions, presence documents, and devices that process VoIP traffic. Platform trust is distinct from other data in the body of SIP message. user identity trust, although they share similar mechanisms, such as Certificate Authorities. For example, a CA could issue TLS, IPSEC and S/MIME protocols provide confidentiality both user-identity certificates and device-identity certificates. and integrity protection of the signaling data. However, they Some type of standardized rating system to specify platform do not provide end-to-end (client-to-client) protection of the trust level could be developed so that a device CA has criteria signaling or internal signaling information elements. These to issue device credentials with. encapsulating security protocols are terminated at each hop in the SIP network. Therefore the trust model for signaling is Trust models can have different levels of identity granularity. transitive hop-by-hop which is not as robust as an end-to- For example, the identity information may only indicate the end trust model. organization and department that the users (and platforms) are part of. Work is being performed within the IETF SIP working group to specify end-to-end security mechanisms for the signaling Platform trust and integrity are discussed in greater detail in of authenticable SIP identities. The draft Enhancements for Figure 1. Authenticated Identity Management in the Session Initiation Protocol (SIP)10 is an example of end-to-end security mecha- Client Platform Security nisms embedded in the signaling protocol. Extending this type of approach to other portions of the VoIP signaling layer will enhance the security of the network. Client Platform Integrity A concern for VoIP users is VoIP client platform security The Enhancements for Authenticated Identity work also and integrity. A basic PSTN phone is a simple, single-purpose points to the need for a trust infrastructure that can issue device, incapable of being remotely managed or upgraded, authenticable credentials to VoIP end users (or to proxies and therefore the device is not susceptible to network- trusted to vouch for their identities). based attacks. 4
  • 5. Figure 1. Elements of platform trust and integrity. Encryption: ensures privacy and integrity of transmitted media and signaling Network Sealed storage: protects the integrity of sensitive security parameters Platform attestation: conveys the client platform’s integrity to remote party User authentication: robustly identifies the person calling to the remote party A VoIP phone is a computer, whether an embedded, dedicated LT features comprise capabilities in the microprocessor, phone device or a general-purpose PC platform with VoIP chipset, I/O subsystems, and other platform components that software. These sophisticated, network-connected devices are used to enforce the integrity of the platform, including: can, in most cases, be remotely managed and/or upgraded through the network. This provides powerful cost and time- Protected execution mechanisms for building protected software partitions saving advantages for both users and network managers, but it also means these devices may be vulnerable to malicious • These are used to provide a virtual firewall within the computer code that, for example, might install itself in the client platform platform. Software contained in a protected partition cannot to eavesdrop, record or log information about the calls made. be maliciously modified or compromised by other software on the platform. A VoIP softphone that is configured in a These platform security concerns are being addressed by protected partition is protected from other malicious software forums such as the Trusted Computing Group and Intel has on the system. A secure virtualized platform can have a created technology, such as LaGrande Technology, to securely secure partition dedicated to the VoIP software and a sepa- and efficiently realize these solutions. The goals of these rate partition that contains a commodity web browser and activities are to harden the platform and prevent malicious other untrusted software. This way, the platform user can software from being able to attack the software and get surf the web while not compromising the VoIP software. access to sensitive data. In fact, many of the following funda- mental issues and solutions are not specific to VoIP, but are Sealed storage function also relevant for protecting other data and applications as well. • This is used to protect sensitive parameters with hardware- Platform integrity prevents unauthorized software from eaves- based encryption and hardware key storage. A Trusted dropping on and/or compromising other software processes Platform Module (TPM) is a hardware device designed to executing on the system. Platform security services can be securely store cryptographic key material used in platform used to protect the VoIP software running on a commodity authentication and other cryptographic functions. A TPM PC or application specific VoIP platform from common implements cryptographic keys used for digital signatures Internet-based attacks such as viruses and spyware. Key and key wrapping in hardware. LT makes use of a TPM technology being developed by Intel for providing platform- for platform attestation (discussed on page 6). A TPM can level security is LaGrande Technology (LT). The goal of LT be used to securely store key material that protects VoIP is to protect the PC from software-based attacks. communications. 5
  • 6. Figure 2 depicts the basic platform security components of a The remote party’s platform integrity level would be displayed trusted VoIP Softphone discussed in this paper. These com- in some fashion as part of call establishment so that a decision ponents include a secure execution environment; a high-as- could be made about whether to accept or reject the call or surance hardware-based cryptographic module, and a restrict what is communicated based upon the level. This Trusted Platform Module. integrity level information could be thought of in the same manner as the security level (128 bit, 64 bit) of the security Client Attestation protocol and key size that is negotiated during call setup. It is these two pieces of information and the key management Proof of platform integrity is a security service that allows a system that really define how secure the end-to-end link is. remote system to verify the integrity level of a system that it There would have to be standardized criteria and minimal connects to. This service and the associated protocols are essential requirements for each integrity level. Businesses being defined in the Trusted Computing Group’s Trusted could establish employee policies that state which integrity Network Connect Working Group. Remote platform integrity level is required to discuss certain types of information. verification is accomplished using a mechanism called attes- Consumers could make their own choices based on how tation whereby the remote platform provides an electronically they perceive the threat of communicating with a low signed digest of its operating environment or the description integrity VoIP phone. of platform characteristics that affect the integrity of the plat- form. As discussed earlier, TLS is one of the security protocols In addition to authenticating the remote party’s platform, used in VoIP systems to provide security to the SIP signaling user-authentication can identify the remote party. for VoIP sessions. TLS Extensions for Attestation12 is used to exchange platform integrity and authentication information as User Authentication part of the security exchange between VoIP entities. A PSTN phone relies on physical security for caller identification. Proof of platform integrity could be used by communicating Anyone who is within reach of the phone, or can physically VoIP platforms to verify the robustness of the remote party’s access the network, can masquerade and answer or place a platform. It is conceivable that the users would restrict the call. In contrast, VoIP phones can be designed with additional information they share based upon the integrity level of the security measures to authenticate the user, which may include remote VoIP phone. passwords, biometric input, or combinations. Furthermore, Figure 2. The basic platform security components of a trusted VoIP Softphone. These components include a secure execution environment, a high-as- surance hardware-based cryptographic module, and a Trusted Platform Module. Trusted VoIP Softphone Platform Hardware-Based Cryptographic Module Standard Partition Protected Partition Protected Partition (Secure key storage) Secure VoIP Other Standard Other Protected Softphone Trusted Platform Module Applications Applications Applications (Secure key and parameter storage) LaGrande Technology - Protection Execution Environment 6
  • 7. this identity can then be sent securely through the network to level 3 and higher certified cryptographic modules or devices the other party using digital signature techniques described in such as the Trusted Platform Module that provide hardware- the “Enhancements for Authenticated Identity” draft. based key storage provide the type of key protection required to prevent key extraction type attacks. At the Intel Developer The proper use of these platform-attestation and user-auth- Forum in March 2005, Intel demonstrated a secure system entication technologies will enable the design of secure VoIP that used TPM to store keys for SRTP. platforms that provide many more security services than are provided in their PSTN counterpart. Summary Key Management and Sealed Storage The sophistication of VoIP clients and network components allow IP-based telephony systems to offer many features that The various encryption protocols mentioned previously require are not economically feasible with PSTN-based systems. This key management: the generation, storage, protection, and sophistication brings additional vulnerabilities that must be destruction of cryptographic keying material. Proper key addressed. Properly applied security measures can make VoIP management is essential in the design of any cryptographic communications more secure and private than PSTN com- security system. Key management is critical in applications munications. Whereas PSTN relies on the physical security such as VoIP where any-to-any communications can be of the network, VoIP can encrypt signaling and media end-to- established on the fly. end. Mechanisms for securing the client platform and for Secure key storage is essential because adversaries will attestation of the client’s integrity also enhance VoIP security. typically not try to break a strong cryptographic algorithm, In addition, VoIP also provides a means of user authentica- 13 14 such as 3DES or AES. Rather, they will try to exploit tion, whereas PSTN relies predominantly on physical access vulnerability in the security implementation, such as gaining to the phone. access to the cryptographic key material that is used to There are many aspects of VoIP security, and well-known authenticate and protect the VoIP sessions. Spyware attacks ways to robustly implement each of them. Properly applied, that search for key material on a client device can compromise VoIP can provide richer and more secure communication all of the VoIP sessions made on the system. Hardware-based than PSTN. key storage, as well as protection of key material throughout its lifetime, is an essential security requirement. FIPS-140-2 1 Baugher, M., McGrew, D., Naslund, M., Carrara, E., and Norrman, K., “The Secure Real-time Transport Protocol (SRTP),” RFC 3711, March 2004. 2 Kent, S. and Atkinson, R., “IP Encapsulating Security Payload (ESP)”, RFC 2406, November 1998. 3 Arkko, J., Carrara, E., Lindholm, F., Naslund, M. and Norman, K., “MIKEY: Multimedia Internet KEYing”, RFC 3830, August 2004. 4 Andreasen, F., Baugher, M. and Wing, D., “Session Description Protocol Security Descriptions for Media Streams”, draft-ietf-mmusic-sdescriptions-12, September, 2005. 5 Maughan, D., Schertler, M., Schneider, M. and Turner, J., “Internet Security Association and Key Management Protocol (ISAKMP)”, RFC 2408, November 1998. 6 Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M. and Schooler, E., “SIP: Session Initiation Protocol”, RFC 3261, June 2002. 7 Intel Corporation, “LaGrande Technology Architectural Overview”, 252491-001, avail. at http://www.intel.com/technology/security/, September 2003. 8 Dierks, T. and Allen, C., “The TLS Protocol Version 1.0”, RFC 2246, January 1999. 9 Ramsdell, B., “Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification”, RFC 3851, July 2004. 10 Peterson, J and Jennings, C., “Enhancements for Authenticated Identity Management in the Session Initiation Protocol (SIP)”, Internet-Draft draft-ietf-sip-identity-06, October 2005. 11 International Telecommunications Union, “Information technology - Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks”, ITU-T Recommendation X.509, ISO Standard 9594-8, March 2000. 12 Trusted Computing Group, TLS Extensions for Attestation, Specification Version 1.0, Revision 0.8, July 2004, Work in Progress. 13 National Institute of Standards and Technology, “Data Encryption Standard,” FIPS PUB 46-2, December 1993. 14 National Institute of Standards and Technology, “Advanced Encryption Standard (AES),” FIPS PUB 197, November 2001. 7
  • 8. Copyright © 2005 Intel Corporation. All rights reserved. Intel and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Information in this document is provided in connection with Intel® products. Except as provided in Intel’s terms and conditions of sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty relating to sale and/or use of intel products, including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright, or other intellectual property right. Intel may make changes to specifications, product descriptions, and plans at any time, without notice. Intel Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. Intel products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications. The Intel® Pentium® M processor and the Intel® Celeron® M processor may contain design defects or errors known as errata,which may cause the product to deviate from published specifications. Current characterized errata are available upon request. Printed in USA/1105/PMS/LKY/PP/150 Order Number: 310431-001US

×