TY - GEN
T1 - Multiple design patterns for Voice over IP (VoIP) security
AU - Anwar, Zahid
AU - Yurcik, William
AU - Johnson, Ralph E.
AU - Hafiz, Munawar
AU - Campbell, Roy H.
PY - 2006
Y1 - 2006
N2 - Design patterns capture software solutions to specific problems that have evolved over time and reflect many iterations of work. Documenting such patterns promotes proven design and software reuse. There has been a growing amount of work documenting design patterns for security, however, little work specific to VoIP security. In 2005 NIST released a report on recommendations and best practices for securing VoEP, however it lacks the structure, terminology, and ease-of-understanding needed for both technical and non-technical audiences that is an inherent feature of design patterns. In this paper we document three design patterns for VoIP implementations related to specific security problems: (1) secure traversal of firewalls and NATs; (2) detecting and mitigating DDoS attacks; and (3) securing against eavesdropping. With many VoIP vendors rushing products to market with overlapping functionality and requirements for interoperability, documenting design patterns is poised to become an important part of secure programming processes for VoIP.
AB - Design patterns capture software solutions to specific problems that have evolved over time and reflect many iterations of work. Documenting such patterns promotes proven design and software reuse. There has been a growing amount of work documenting design patterns for security, however, little work specific to VoIP security. In 2005 NIST released a report on recommendations and best practices for securing VoEP, however it lacks the structure, terminology, and ease-of-understanding needed for both technical and non-technical audiences that is an inherent feature of design patterns. In this paper we document three design patterns for VoIP implementations related to specific security problems: (1) secure traversal of firewalls and NATs; (2) detecting and mitigating DDoS attacks; and (3) securing against eavesdropping. With many VoIP vendors rushing products to market with overlapping functionality and requirements for interoperability, documenting design patterns is poised to become an important part of secure programming processes for VoIP.
KW - Internet telephony
KW - Secure traversal of firewalls and NATs
KW - Security design patterns
KW - Threat modeling
KW - VoIP security
UR - http://www.scopus.com/inward/record.url?scp=33751052258&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=33751052258&partnerID=8YFLogxK
U2 - 10.1109/.2006.1629443
DO - 10.1109/.2006.1629443
M3 - Conference contribution
AN - SCOPUS:33751052258
SN - 1424401976
SN - 9781424401970
T3 - Conference Proceedings of the IEEE International Performance, Computing, and Communications Conference
SP - 485
EP - 492
BT - 25th IEEE International Performance, Computing, and Communications Conference, 2006, IPCCC 2006
T2 - 25th IEEE International Performance, Computing, and Communications Conference, 2006, IPCCC 2006
Y2 - 10 April 2006 through 12 April 2006
ER -