14

South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4 IPv6 • NAT traversal Service assurance

  • Upload
    others

  • View
    4

  • Download
    0

Embed Size (px)

Citation preview

Page 1: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance
Page 2: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

November 27-29, 2012

South San Francisco Conference Center

Panel - Edges and Security

Jason Uberti

Software Engineer

Google

November 29, 2012

Page 3: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

Panel Participants

• Patrick McNeil

– Sr. Security Engineer

– Acme Packet

• Mohan Palat

– Product marketing

– Sonus

• Jerry Ryner

– CTO

– Sansay

Page 4: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

November 27-29, 2012

South San Francisco Conference Center

ACME PACKET

Patrick McNeil, CISSP

Senior Security Engineer

Page 5: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

Old challenges are new again … These may sound familiar if you experienced the first round of VoIP • Mixing developers with Bob the telephone guy when he just got comfortable

with the networking team • Web developer understanding and use of security mechanisms in HTML5 and

WS (failing since ‘93) • Identity, authentication, authorization, and the notion of trust (IdP only part) • Asset preservation while developing new revenue streams

and

New ‘access network’ … … same session delivery challenges

Assuring Security, Service Reach, Service Assurance, and Regulatory Compliance – which are usually left until last!

Page 6: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

The challenges to address…

Security • CORS enforcement • Limit protocols (ex: SIPoWS, REST,

ROAP, XMPP) • HTTPS / WSS • DoS / dynamic blacklisting • Dynamic port management • IdP token / session management

Service reach • Interwork to SIP • Media – differing suppt. for ICE,

STUN/TURN, transcoding • IPv4 <-> IPv6 • NAT traversal

Service assurance • HA & load balancing • QoS, QoE

Regulatory compliance • Direction to media recorders • Call details, logging, etc at

boundaries

Note: Enterprise example shown – service provider back end and path to subscribers would be different…

sound suspiciously like gateway or SBC territory.

Page 7: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

November 27-29, 2012

South San Francisco Conference Center

SONUS

Mohan Palat

Senior Product Marketing Manager

Page 8: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

Overlaying with WebRTC Deployment Areas…

Mobile Operator

Wholesale Provider

IAD

IP Phones

Mobile 3G

IMS Wireless

Peering Network

IP Phones

IP PBX

SIP H.323 4G/LTE

WiMAX

MSC BICC SIP-I

BICC SIP-I

SIP/SIP-I

SIP

SIP

SIP-I

Service Provider

SIP

Other Mobile,

Fixed Network

Other IMS

SIP/SIP-I

TISPAN/

PacketCable

BGF

IPX Proxy IPX Proxy

IPX Proxy

I-BCF/I-BGF

I-BCF/I-BGF

SBC

P-CSCF

SBC

A-SBC

SBC SBC

Enterprise

Home

Public Internet

Page 9: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

SBC in WebRTC – Use Cases

Web (WebRTC) Server

Session Manager

HTTP Javascript

Browser

VoIP Phone

SIP Server

PSTN Phone TDM

IP

TDM

SBC

DTLS/SRTP RTP IPv4

Lawful Intercept

1

2

SBC

3

IPv6

4

5

Page 10: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

November 27-29, 2012

South San Francisco Conference Center

SANSAY

Jerry Ryner

CTO

Page 11: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

WebRTC with SBCs

Browser A

Firewall / NAT

Website Server

SBC

• Private Network • IP PBX • Application Servers • VoLTE and PSTN

Firewall / NAT

Browser B

HTTPS

SRTP / STUN

HTTPS / SIPS

Page 12: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

WebRTC Security and Protection

Theft of Service Solution

• Eavesdropping - HTTPS and SRTP

• Unauthorized Access - Login Credentials and Certificates

Denial of Service Solution

• Website DOS/DDOS - TCP/HTTPS Rate Limiting and IP Tracking

• SBC DOS/DDOS - Strict ACLs for HTTPS/SIPS Interface

- STUN Authentication for SRTP Interface

SBC vs. TURN

• TURN uses long term credentials and must accept client authentication requests

• TURN uses same interface for control and media and requires client media encapsulation

• SBC has strict control interfaces and does not require long term client authentication

• SBC media relay ports are not locked to any one interface and require no media encapsulation

• SBC has knowledge of media type, bandwidth, priority, and application treatment

Page 13: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

Panel Questions

• What are the top 3 security vulnerabilities in WebRTC, and what are their implications?

• Does the SBC address all the WebRTC security needs? Or, do we need other security WebRTC elements/functions?

• What are the additional features that an SBC should have to support WebRTC?

• Is the SBC critical in securing WebRTC? Can WebRTC operate securely without an SBC?

• If I put a WebRTC server in the DMZ do I need an SBC?

• Do I need and SBC for client support in the enterprise, especially if it is designed to work in the open internet?

• Do SBC functions and media server functions need to come together for WebRTC?

Page 14: South San Francisco Conference Center...• Interwork to SIP • Media – differing suppt. for ICE, STUN/TURN, transcoding • IPv4  IPv6 • NAT traversal Service assurance

November 27-29, 2012

South San Francisco Conference Center

Thank You

Jason Uberti

Software Engineer

Google