VoIP Security Threats Every Business Should Know
A business phone system that is reachable from the internet is probed constantly, usually by automated tools looking for weak passwords and open dial plans. This article lists the threats that matter most for a typical business PBX or hosted phone service, and the practical defences against each.
1. Toll fraud through stolen or guessed SIP accounts
This is the most common and most expensive problem. Attackers scan for SIP servers, try common extension numbers and passwords, and once they can register, use the account to place large numbers of calls to premium-rate or international numbers, often over a weekend. The business pays the bill.
- Use long, random SIP passwords, never the extension number or a dictionary word.
- Block repeated failed registrations automatically, for example with fail2ban or the PBX’s own security features.
- Restrict international and premium-rate destinations in the dial plan, and set spending limits with your SIP provider.
- Where possible, allow registrations only from known networks or through a VPN or proxy.
The Siperb knowledge base (published by the team behind SoftPage) explains why its service generates long random SIP credentials for this reason.
2. Eavesdropping on unencrypted calls
Standard SIP and RTP are not encrypted. Anyone able to capture traffic on the path can read signalling and replay audio. Encrypt signalling with TLS, as defined in RFC 3261, and media with SRTP (RFC 3711), especially for remote workers and SIP trunks that cross the internet. Our article on encrypted VoIP for remote teams explains what each kind of encryption protects.
3. Attacks on the PBX itself
Unpatched PBX software and web administration panels exposed to the internet are regular targets. Keep the PBX, its operating system and any modules up to date, put the admin interface behind a VPN or an IP allow-list, and do not expose services you do not use.
4. Caller ID spoofing and social engineering
Caller ID can be forged, so a call that appears to come from a bank or a colleague may not. Train staff to verify requests for payments or passwords through a second channel. In the US and Canada, carriers sign and verify caller ID with STIR/SHAKEN; see our article on STIR/SHAKEN for SIP calls.
5. Denial of service
Floods of SIP requests can overload a PBX or fill an internet link so that calls fail. Rate-limit SIP traffic at the edge, use a session border controller or SIP proxy in front of the PBX for larger systems, and ask your provider what protection they offer.
Checklist
- Random SIP passwords and automatic blocking of repeated failures
- International and premium-rate calls restricted; spending limits set
- TLS for signalling and SRTP for media on remote devices and trunks
- PBX and admin interfaces patched and not openly exposed
- SIP traffic monitored for unusual registration attempts and call patterns
For SIP trunks specifically, see our guide to SIP trunking security.
Related: how secure WebRTC browser calls are.
Related: How STIR/SHAKEN verifies caller ID on SIP calls.
Corrected 18 November 2026: the earlier version opened with a paid advertising link carrying tracking parameters, cited CSO Online and Cloudflare for statements their pages do not make, recommended “end-to-end encryption” against man-in-the-middle attacks without explaining that business calls are normally encrypted hop by hop, and did not cover toll fraud, the most common VoIP attack. Tracking parameters and decorative emoji have been removed.