securing your voice and voice over network assets lesson 08

56
Securing Your Voice and Voice over Network Assets Lesson 08

Upload: philippa-lloyd

Post on 25-Dec-2015

217 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Securing Your Voice and Voice over Network Assets Lesson 08

Securing Your Voice and Voice over Network AssetsSecuring Your Voice and Voice over Network Assets

Lesson 08

Page 2: Securing Your Voice and Voice over Network Assets Lesson 08

Wiretapping and EavesdroppingWiretapping and Eavesdropping

WiretappingLegal perspective (individual and gov)Techniques– Tape recorder– Lineman handset– Small RF transmitter in handset

PBX soft wiretap Telephones as listening devices Eavesdropping

Cordless (1.6-1.8MHz, 43.7-49.97MHz, 900MHz)Cellular– Conversation not the good stuff, the ‘serial’ number is -- cloning

Page 3: Securing Your Voice and Voice over Network Assets Lesson 08

Telecommunications FraudTelecommunications FraudBlue Boxes

blue box n. 1. obs. Once upon a time, before all-digital switches made it possible for the phone companies to move them out of band, one could actually hear the switching tones used to route long-distance calls. Early phreakers built devices called `blue boxes' that could reproduce these tones, which could be used to commandeer portions of the phone network. (This was not as hard as it may sound; one early phreak acquired the sobriquet `Captain Crunch' after he proved that he could generate switching tones with a plastic whistle pulled out of a box of Captain Crunch cereal!) There were other colors of box with more specialized phreaking uses; red boxes, black boxes, silver boxes, etc. 2. n. An IBM machine, especially a large (non-PC) one. (from Jargon File)

Page 4: Securing Your Voice and Voice over Network Assets Lesson 08

Telecommunications FraudTelecommunications Fraud PBX Fraud

Common– A university with $200K bill– A computer manufacturer with $300K– “call sell” operation with $1.4M tag

Risk of being caught generally lowNo special equipment neededThere is money to be made in it!Commonly exploited through dial-up connection directly to the PBX– Discover number through war-dialing or social engineering– Once you have number, now you have to get past the password

Page 5: Securing Your Voice and Voice over Network Assets Lesson 08

Octel Voice Network LoginOctel Voice Network Login System Manager password is a # By default, set to 9999

From “Hacking Exposed”

Copyright (C) 1994-1998 Octel Communications Corporation. All Rights Reserved

Please Enter System Manager Password:Number must be enteredEnter the password of either System Manager mailbox, then press “Return.”9999

Page 6: Securing Your Voice and Voice over Network Assets Lesson 08

Williams PBXWilliams PBX

Type login Will be followed with prompt to enter user

number.Requires four-digit numeric access code.– (how long will it take to guess one?)

Page 7: Securing Your Voice and Voice over Network Assets Lesson 08

Meridian LinksMeridian Links

Looks similar in response to a Unix-based box userid: maint Password: maint will get you into

management console userid: mluser Password: mluser will do the same will put you into a restricted unix shell

Page 8: Securing Your Voice and Voice over Network Assets Lesson 08

ROLM PhoneMailROLM PhoneMail

Default Accounts:LOGIN: sysadmin PASSWORD: sysadminLOGIN: tech PASSWORD: techLOGIN: poll PASSWORD: tech

Page 9: Securing Your Voice and Voice over Network Assets Lesson 08

ATT Definity G/System 75ATT Definity G/System 75

Lots of possibilities here

ATT UNIX S75Login:Password:

enquiry/enquirypw init/intpw browse/lookermaint/rwmaint locate/locatepw tech/fieldrcust/rcustpw cust/custpw inads/inadssupport/supportpw bcms/bcms blue/bluepwkraft/kraftpw craft/craftpw field/support

Page 10: Securing Your Voice and Voice over Network Assets Lesson 08

Threats to PBXsThreats to PBXs

Theft of service – I.e., toll fraud, probably the most common of motives for attackers. Disclosure of information – data disclosed without authorization, either by deliberate

action or by accident. Examples include both eavesdropping on conversations or unauthorized access to routing and address data.

Data modification – data altered in some meaningful way by reordering, deleting or modifying it. For example, an intruder may change billing information, or modify system tables to gain additional services.

Unauthorized access – actions that permit an unauthorized user to gain access to system resources or privileges

Denial of service – actions that prevent the system from functioning in accordance with its intended purpose. A piece of equipment may be rendered inoperable or forced to operate in a degraded state.

Traffic analysis – a form of passive attack in which an intruder observes information about calls and makes inferences from things such as the source and destination numbers, or the length or frequency of the calls.

Page 11: Securing Your Voice and Voice over Network Assets Lesson 08

PBX security –vs- OS securityPBX security –vs- OS security

PBXs are sophisticated computer systems, and many of the threats and vulnerabilities associated with OS’s are shared by PBXs. There are, however, two important distinctions:

External access/control – Like larger telephone switches, PBXs typically require remote maintenance by the vendor. Instead of relying on local administrators to make operating system updates and patches, organizations normally have updates installed remotely by the switch manufacturer. This of course requires remote maintenance ports.Feature richness – The wide variety of features available on PBXs, particularly administrative features and conference functions, provide the possibility of unexpected attacks. A feature may be used by an attacker in a manner that was not intended by its designers. Features may also interact in unpredictable ways causing security problems. Even though the features may be fairly standard, the implementation between vendors is different, thus the reason instruments can often not be interchanged between PBXs.

Page 12: Securing Your Voice and Voice over Network Assets Lesson 08

PBX susceptibility to tappingPBX susceptibility to tapping

A PBX’s susceptibility to tapping depends on the methods used for communication between the PBX and its instruments. This may include voice, data, and signaling information.

Signaling information is typically commands to the instrument (turn on indicators, microphones, speakers, etc.) and status from the instrument (hook status, keys pressed, etc.).Three general communication methods exist– Analog Voice with separate Control Signals– Analog Voice with inclusive Control Signals– Digital Voice with Inclusive Control Signals

Page 13: Securing Your Voice and Voice over Network Assets Lesson 08

Analog Voice with separate Control SignalsAnalog Voice with separate Control Signals

Simplest method. Analog voice is passed between the PBX and the instrument on either a single pair of wires or two pairs (one for transmit and one for receive). If there is any additional signaling communication (other than the hook switch) between the PBX and the instrument, it is done on wires that are separate from the voice pair(s).

Voice information is transmitted essentially as it is picked up by the microphone. It is in a form that can be directly reproduced by a speaker.

The voice line can be easily tapped by connecting an amplifier to the pair of voice wires. The amplified voice signal can then be heard directly with a speaker or headphones or be recorded.

Page 14: Securing Your Voice and Voice over Network Assets Lesson 08

Analog Voice with inclusive Control SignalsAnalog Voice with inclusive Control Signals

Analog voice and control signaling is passed between the PBX and the instrument on either a single pair of wires or two pairs. This can be done if the signal path is of high enough bandwidth to pass voice information (less than 4KHz) plus additional data information. For example, voice information can be combined with data information modulated onto a carrier tone that is centered outside of the voice band.

Vulnerable to tapping by connecting an amplifier to the pair and passing signal through filters to separate the voice and data information. Data information can be recovered by demodulating the carrier tone.

Page 15: Securing Your Voice and Voice over Network Assets Lesson 08

Digital Voice with Inclusive Control SignalsDigital Voice with Inclusive Control Signals

Voice and control signaling data are passed across the same pair of wires. There may be two pairs of wires, one for each direction, or both directions could be combined onto one pair of wires using echo cancellation. Conventional tapping techniques won’t work against most types of digital lines. The format and type of digital signals that pass between the PBX and its instruments vary widely between vendors.

If separate pairs are used for transmit and receive, each pair could be tapped to provide access to the bit streams but the format needs to be determined.

Page 16: Securing Your Voice and Voice over Network Assets Lesson 08

Echo CancellationEcho Cancellation If both transmit and receive are combined on one pair using

echo cancellation, the previously described methods would not be useful for tapping.

Each transmit end of the link can only determine what is being received by subtracting out what it is transmitting from the total signal.

An outside observer tapping the line somewhere between the two ends would only have access to the total signal and would therefore find it very difficult to reproduce either end. An attack would depend on a known original condition on an end.

Page 17: Securing Your Voice and Voice over Network Assets Lesson 08

Maintenance Feature VulnerabilitiesMaintenance Feature Vulnerabilities Maintenance-out-of-service (MOS) – this feature allows maintenance

personnel to place a line out of service for maintenance. If a line is placed MOS while it is in operation, the PBX may terminate its signaling communication with the instrument and leave the instrument’s voice channel connection active even after the instrument is placed on-hook.

Line Testing Capabilities – the ability to connect two lines together in order to transmit data from one line to the other and verify whether or not the second line receives the data properly. This feature would allow someone with maintenance access to connect a user’s instrument to an instrument at another location in order to eavesdrop on the area surrounding the user’s instrument without the user’s knowledge.

Page 18: Securing Your Voice and Voice over Network Assets Lesson 08

Securing Voice over NetworksSecuring Voice over Networks

Page 19: Securing Your Voice and Voice over Network Assets Lesson 08

The Promise of IP TelephonyThe Promise of IP Telephony

World moving toward “converged” networks Benefits usually cited for implementing VoIP

Long-Distance toll savingsIncreased number of calls with less bandwidthAdditional and enhanced servicesMost efficient use of IP assetsCombined network/telecom infrastructure

Page 20: Securing Your Voice and Voice over Network Assets Lesson 08

Additional IssuesAdditional Issues

Related VoIP IssuesInternational callsTelemarketingCall CentersFacsimile

Page 21: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony ProtocolsIP Telephony Protocols

H.323ITU -- 1996, 1998, 1999

SIP – Session Initiation ProtocolIETF -- 1999

MGCP – Media Gateway Control Protocol (Megaco/H.248)

IETF/ITU -- 1999

Page 22: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony OverviewIP Telephony Overview

MCU

H.323 Terminal

Router

Gatekeeper

Ethernet Phone

Gateway

Packet-switchedIP Network

intranet, Internet, VPNs

PBXPBX-std. Phone

Gatekeeper

H.323 Terminal

Ethernet Phone

Router

Circuit-switchedNetworks

PSTN, ISDN, wireless

Gateway

PBX

H.323 Architecture

From: “Security Requirements and Constraints of VoIP” by Mika Marjalaakso

Standard Phone

Page 23: Securing Your Voice and Voice over Network Assets Lesson 08

H.323 ComponentsH.323 Components Terminal – a terminal, or a client, is an endpoint where H.323

data streams and signaling originate and terminate. It may be a multimedia PC with a H.323 compliant stack or a standalone device such as a USB (universal serial bus) IP telephone. A terminal must support audio communication; video and data communication support is optional.

Gateway – a gateway is an optional component in a H.323-enabled network. When communication is required between different networks a gateway is needed at the interface. It provides data format translation, control signaling translation, audio and video codec translation, and call setup and termination functionality on both sides of the network.

Page 24: Securing Your Voice and Voice over Network Assets Lesson 08

H.323 Components (cont.)H.323 Components (cont.) Gatekeeper – a gatekeeper is a very useful, but

optional, component of an H.323-enabled network. Gatekeepers are needed to ensure reliable, commercially feasible communications. When a gatekeeper exists all endpoints (terminals, gateways, and MCUs) must be registered with it.

A gatekeeper provides several services to all endpoints in its zone. These services include:– Address translation– Admission and access control of endpoints – Bandwidth management – Routing capability

Page 25: Securing Your Voice and Voice over Network Assets Lesson 08

H.323 Components (cont.)H.323 Components (cont.) MCU – a multipoint control unit (MCU) enables

conferencing between three or more endpoints. Although the MCU is a separate logical unit it may be combined into a terminal, gateway, or gatekeeper. The MCU is an optional component of an H.323-enabled network.

The multipoint controller provides a centralized location for multipoint call setup. Call and control signaling are routed through the MC so that endpoints capabilities can be determined and communication parameters negotiated.

Page 26: Securing Your Voice and Voice over Network Assets Lesson 08

Standards for IP Telephony H.323 for IP Telephony

From: IP Telephony, by Goralski & Kolon

Video Audio Control Data

Unreliable Transport (UDP) Reliable Transport (TCP)

H.261H.263(videoCoding)

G.711G.722G.723G.728G.729

RTP RTCPRTP RTCP

H.225

Terminal togatekeepersignaling

H.225

Callsignaling

H.245 T.120(Multipointdata transfer)

Page 27: Securing Your Voice and Voice over Network Assets Lesson 08

H.225 and H.245H.225 and H.245 H.225 performs the signaling for call control

uses H.245 to establish and terminate individual logical channels for communication

Five phases of signaling processCall setupInitial communications and capability exchangeEstablishment of audiovisual communicationCall servicesCall termination

Page 28: Securing Your Voice and Voice over Network Assets Lesson 08

Encoding techniquesEncoding techniques

0

10

20

30

40

50

60

70

G.711 G.722 G.726 G.728 G.729 G.723

Data RateDelay (ms)Quality (MOS)

From: IP Telephony, by Goralski & Kolon

Page 29: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony OverviewIP Telephony Overview

Redirect Server

SIP Terminal

Router

Proxy Server

SIP Phone

Packet-switchedIP Network

intranet, Internet, VPNs

Proxy Server

SIP TerminalSIP Phone

Router

Location Server

Session Initiation Protocol (SIP) Architecture

From: “Security Requirements and Constraints of VoIP” by Mika Marjalaakso

Page 30: Securing Your Voice and Voice over Network Assets Lesson 08

Media GatewayController

Media Gateway

Packet-switchedIP Network

PSTN

IP Telephony OverviewIP Telephony Overview

MGCP, H.248/Megaco Architecture

PSTN

Media Gateway

SignalingGateway

SignalingGateway

SS7

Media GatewayController

TDM

PSTN SignalingSS7, ISDN, Q.Sig

Signaling ConversionSigtran

IP SignalingH323, SIP, ISUP

Media GW ControlMGCP,

Megaco/H.248

MediaRTP/RTCP

TDM

SS7

PSTN SignalingSS7, ISDN, Q.Sig

Signaling ConversionSigtran

From: “Security Requirements and Constraints of VoIP” by Mika Marjalaakso

Page 31: Securing Your Voice and Voice over Network Assets Lesson 08

MediaGateway ControlSignaling

IP Telephony OverviewIP Telephony Overview

IP

UDPTCP

SIPH.248

MegacoRTP RTCP RTSP

H.450.x H.235

H.245 RAS SGCP IPDCH.225.0 (Q.931)

MGCP Codecs (A/V)

H.323

The Protocol Stack

From: “Security Requirements and Constraints of VoIP” by Mika Marjalaakso

Page 32: Securing Your Voice and Voice over Network Assets Lesson 08

Approaches to IP TelephonyApproaches to IP Telephony

T1

ISDN

ANALOG

PBXPrivate Branch Exchange

Phones

Strategy One (PBX Vendors)

Page 33: Securing Your Voice and Voice over Network Assets Lesson 08

Approaches to IP TelephonyApproaches to IP Telephony

T1

ISDN

ANALOG

PBXPrivate Branch Exchange

Phones

Strategy One-a (PBX Vendors)

Page 34: Securing Your Voice and Voice over Network Assets Lesson 08

Strategy Two (Networking Vendors)

Approaches to IP Telephony Approaches to IP Telephony

PBXPrivate Branch Exchange

Data Switch

IP Phones

Page 35: Securing Your Voice and Voice over Network Assets Lesson 08

Approaches to IP TelephonyApproaches to IP Telephony

Strategy Three (Telecom Firewall)

Least cost Routing

Security – PSTN & Internet

Leverage Existing Infrastructure

PBXPrivate Branch Exchange

T1

ISDN

ANALOG

Page 36: Securing Your Voice and Voice over Network Assets Lesson 08

Quality of Service IssuesQuality of Service Issues “Perhaps the most vexing problem in voice-

over-IP, in general, has been the issue of quality of service (QoS). The delay in conversation that many VoIP users encounter is caused by the jitter and latency of packet delivery within the Internet itself”

[J. Rosenberg, Computer Telephony: The SIP Protocol. June 2000]

Page 37: Securing Your Voice and Voice over Network Assets Lesson 08

Quality of Service IssuesQuality of Service Issues Bandwidth (minimum) Latency (maximum) Jitter (delay variation) Packet loss (network congestion or errors) Availability (individual) Reliability (network)

Page 38: Securing Your Voice and Voice over Network Assets Lesson 08

Network ReliabilityNetwork Reliability

Reliability Total yearly Downtime99% 3.65 days99.5% 1.825 days99.9% 8.76 hours99.95% 4.38 hours99.99% 52.56 minutes99.995% 26.28 minutes99.999% 5.25 minutes

From: IP Telephony, by Goralski & Kolon

Page 39: Securing Your Voice and Voice over Network Assets Lesson 08

Quality of Service IssuesQuality of Service Issues

Prevailing IP Telephony thinking:security reduces QoS to unacceptable levelssecurity or QoS - but not bothlet’s fix QoS then worry about securitysecurity and QoS are competing requirementssecurity isn’t necessary over well-managed IP networks (e.g. “I’m not using the Internet, so why worry.”)

Page 40: Securing Your Voice and Voice over Network Assets Lesson 08

Quality of Service IssuesQuality of Service Issues

Scheduled downtime is not a term used in the telephony world.

Security is not usually thought of as a QoS issue -- but it should be!

Page 41: Securing Your Voice and Voice over Network Assets Lesson 08
Page 42: Securing Your Voice and Voice over Network Assets Lesson 08

VoIP SecurityVoIP Security

“It may seem painfully obvious, but it’s importantto remember that a VoIP network is an IP network. Any VoIP device is an IP device, and it’s thereforevulnerable to the same types of attacks as any otherIP device. In addition, a VoIP network will almostalways have non-VoIP devices attached to it and beconnected to other mission-critical networks.”

Dr. Andrew Molitor, Aravox Technologies

Page 43: Securing Your Voice and Voice over Network Assets Lesson 08

Special VoIP Security ConsiderationsSpecial VoIP Security Considerations

Availability requirements for VoIP are extremely critical, higher than normal network operations.

VoIP applications are badly behaved IP applications.Tend to use dynamically negotiated ports.Makes security job harder since we don’t know in advance which port numbers represent legitimate communication.

VoIP applications are more sensitive to delays and other performance issues

IP designed to work over slow, noisy networks. Current IP security devices designed to meet the needs of a

data-oriented network.

Page 44: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony Security IssuesIP Telephony Security Issues

Security in IP Telephonyachieved using built-in mechanisms of protocolsachieved using external application or network layer protocols (e.g. IPSEC)

Page 45: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony Security IssuesIP Telephony Security Issues

Benefits of Security in IP TelephonyConfidentialityIntegrityAvailabilityAuthenticationNon-repudiation

Page 46: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony Security IssuesIP Telephony Security Issues

Basic Threats to Traditional TelephonyPhone disturbancePrank callsFree calls using someone else’s phone numberMasquerading as someone elseDenial-of-Service attacks aimed at phone systemAttacks aimed at telephony equipment– Voicemail attacks– PBX configuration port attacks

Page 47: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony Security IssuesIP Telephony Security Issues Basic Threats to IP Telephony

Data network access through VoIP ports (tunneling)Free long distance calls over PSTN (spoofing)Eavesdrop on conversations (packet sniffing)Record conversations without authorizationModify, delete, or replace fax/voice packetsForward incoming phone calls to somewhere elseDenial-of-Service attack on business phone systemDenial-of-Service attack on business data networkExpose private conversations on InternetHijack conversationsBlock calls of targeted individuals Log all calls through an organization

Page 48: Securing Your Voice and Voice over Network Assets Lesson 08

The Threats to VoIPThe Threats to VoIP

Attack Category Likelihood Impact Risk FactorDenial of Service 3 3 9Eavesdropping 2-3 1-3 7Unauthorized Access 2-3 2-3 7Spoofing 2 3 6Information Loss 1-2 3 5Repudiation 1-2 3 5Information Corruption 1 3 3

DTR/TIPHON-08002 V0.1.8 (2000-12-07)Telecommunications and Internet Protocol Harmonization over Networks (TIPHON)

Page 49: Securing Your Voice and Voice over Network Assets Lesson 08

Eavesdropping on VoIPEavesdropping on VoIP

Page 50: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony Security IssuesIP Telephony Security Issues

Security Constraints – the reason why security in IP Telephony is practically non-existent

adds latency to the voice packetincreases computational load of network devicesdoesn’t work well with data-centric VPNsdoesn’t work well with data-centric firewallsincreases bandwidth requirementspublic-key infrastructure not globally availabledoesn’t work well with NAT-enabled routers/firewalls

Page 51: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony Security IssuesIP Telephony Security Issues

PSTN

The Ideal - the Firewall allows VoIP packets across

Internet

10/100

PBX

Router

GW

IP Firewall

Example 1: VoIP Gateway with IP Firewall

Page 52: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony Security IssuesIP Telephony Security Issues

PSTN Internet

10/100

PBX

Router

GW

Reality - the Firewall blocks VoIP packets

IP Firewall

Example 1: VoIP Gateway with IP Firewall

Page 53: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony Security IssuesIP Telephony Security Issues

PSTN Internet

10/100

PBX

Router

GW

Danger – opened VoIP ports can be attackedSome firewall ports are left open to allow VoIP packets.

IP Firewall

Example 1: VoIP Gateway with IP Firewall

Page 54: Securing Your Voice and Voice over Network Assets Lesson 08

VoIP - Capable FirewallsVoIP - Capable Firewalls

Firewalls have to support IP telephony to allow use of VoIPor

IP telephony has to support firewalls to allow use of VoIP

A VoIP Capable Firewall should:Allow a host to send packets to another through dynamically assigned ports, Allow signaling devices to “control” the firewall.

Page 55: Securing Your Voice and Voice over Network Assets Lesson 08

IP Telephony Security IssuesIP Telephony Security Issues

Traditional Responses to Security ThreatsIP Firewalls – must prioritize to not delay critical packets such as VoIP– must handle multiple dynamic UDP port assignments– must be able to handle or else not use NAT

VPNs– must prioritize VoIP packets– must handle numerous smaller packets– must not add too much latency

Encryption– needs to be FAST– PKI issues need to be addressed

Page 56: Securing Your Voice and Voice over Network Assets Lesson 08

SummarySummary

What is the Importance and Significance of this material?

How does this topic fit into the subject of “Voice and Data Security”?