Authorised assessment
Toll-Fraud Risk Assessment
Toll fraud turns a compromised phone system into a bill. This assessment finds the specific weaknesses that make it possible (exposed services, weak accounts and permissive dialling) before the charges land.
This is active, authorised testing. We confirm scope and written authorisation before any active work begins, including a hosted provider's consent where required.
The problem
The business usually pays for the fraud
Standard telephony contracts leave the customer liable for fraudulent call charges. Providers sell fraud caps because the risk sits with you. But caps trigger after fraud starts and cover outbound spend, not the compromise itself. Closing the exposure is the only thing that prevents the charges.
What we commonly find
- Extensions and SIP accounts an attacker can compromise
- Outbound dialling permissions wider than the business needs
- International and premium-rate routes left enabled by default
- No alerting on unusual calling patterns
- Management access that lets an attacker change routing
The approach
Target the fraud exposure directly
GoldAgent assesses the specific paths that lead to fraudulent call spend and shows you how to shut them down (tightened dial plans, stronger authentication, restricted routes and alerting), prioritised by how exploitable each one is.
- Assessment focused on the fraud attack path end to end
- Dial-plan and routing permissiveness examined in detail
- Authentication and account hygiene reviewed
- Clear, prioritised controls to reduce fraud exposure
Methodology
How the engagement runs
- 1
Define scope
Agree the systems, trunks and routes in and out of scope.
- 2
Confirm authorisation
Written confirmation of ownership or right-to-test.
- 3
Discover exposure
Map the accounts, services and routes an attacker could reach.
- 4
Analyse posture
Assess dial-plan permissiveness, routing, authentication and alerting.
- 5
Validate findings
Confirm each fraud path is real, without generating billable calls.
- 6
Prioritise risk
Rank by exploitability and potential financial impact.
- 7
Deliver the report
Management summary plus technical findings and controls.
- 8
Retest
Confirm remediated findings and update status.
What you receive
- Executive summary framing the financial exposure
- Fraud attack-path findings with evidence
- Dial-plan and routing assessment
- Prioritised fraud-reduction controls
- An illustrative exposure scenario, clearly labelled as illustrative, not a forecast or observed loss
- Retest status
Who it suits
- Businesses with high international or out-of-hours call risk
- Organisations that have suffered, or narrowly avoided, fraud
- Contact centres and multi-site operations
- Anyone relying on a provider fraud cap as their only control
Risks it addresses
Direct financial loss
Fraudulent call spend can accumulate quickly, often out of hours, before anyone notices.
Contractual liability
The business is typically liable for the charges under standard telephony terms.
FAQ
Toll-Fraud Risk Assessment: questions
Doesn't our provider's fraud cap already cover this?
A cap limits and reacts to spend once fraud is under way; it does not prevent the compromise or cover interception and configuration exposure. This assessment closes the underlying weaknesses.
Do you place real fraudulent calls to prove risk?
No. Exposure is demonstrated in a controlled, non-billable way. Any higher-impact proof is only run with your explicit agreement.
Will you give us a guaranteed loss figure?
No. Any exposure figure is an illustrative scenario, clearly labelled as such, not a forecast or an observed loss.
Related services
Explore related assessments
PBX Security Assessment
An authorised, end-to-end assessment of the PBX systems your business runs on.
Read moreSIP Security Audit
A focused review of SIP trunks, registration and authentication.
Read moreContinuous Assurance
Scheduled, automated reassessment with historical change tracking that keeps your exposure picture current between assessments.
Read more
Request a Toll-Fraud Risk Assessment
We confirm scope and authorisation first, then show you exactly what is exposed and what to fix.
Testing is only performed against systems you own or are explicitly authorised to test.