Mapping reachable gateways
Probes can show which voice, carrier, and management services answer at a network edge.
Industry blocklist
Telecommunications blocklist
Give voice and network teams one current source list for the exposed services they manage across separate systems.
The coverage
What our sensors observed
Our sensors saw probes against voice systems, carrier management, routing, and subscriber services. The coverage spans call handling as well as the network interfaces used to run those services.
Why use this feed
Call handling, network management, and subscriber services often have different owners and different logs. A shared source list lets those teams review observed scanners at the gateways they already manage, without passing around manual IP blocks. Check the rule against trusted peers and partner connections before enforcing it. Those access decisions still belong to the people operating each service.
The challenges
Scanning can reveal a reachable service before an exploit attempt, whether a flaw is known or still undisclosed. Our sensors record sources doing that probing. A firewall rule using the feed can deny a listed source before its next connection reaches your service, without needing to recognize the exploit itself.
The next request matters
A reachable call or management gateway gives later exploit traffic a place to land if a weakness exists.
Before the local log
A team need not wait for the same source to appear in its gateway log if our sensors have already recorded it.
Edge enforcement
Defend your edge
The feed loads matching rules into your firewall. Listed sources are intercepted before crossing the edge; traffic with no match continues to your services.
Where this feed fits
Use the observed source list where your existing edge controls meet these reachable services.
Review scanner sources in the firewall rules around call handling gateways. Check any block against the traffic those gateways need to accept.
Apply the list to a reachable voice administration interface. Keep administrator access restricted by its own rules.
Use the same source list across exposed network device management interfaces instead of pulling addresses from each device log.
Review the list at gateways serving subscriber services. Confirm the required outside connections before adding a deny rule.
Use the feed as one input when reviewing rules for reachable routing interfaces. Route policy and trusted peers still need separate controls.
Apply the list where an externally reachable messaging service crosses the network edge. Review the sources against normal partner connections.
Industry blocklist
Start blocking observed scanner sources.
Choose this industry, connect the feed to your firewall, and review access with the people who run each service.