What is PolicyGuru?
The PolicyGuru® meta-policy controller provides security-policy-based call control and monitoring for large enterprise SIP deployments, including centralized SIP, without the need for another device inline on the voice network. The PolicyGuru System interfaces with SBCs that support the ENUM protocol with the Kaplan extension. The solution is not inline, but rather receives the important call data (source, destination, and direction) from the ENUM request and then returns the security policy decision for routing the call to the SBC—allow as dialed, redirect to an alternate destination, or terminate prior to call setup.
Deployment
The PolicyGuru System is typically deployed with the SecureLogix® Call Secure™ Managed Service, which provides many additional features and benefits in addition to those described below. If a customer chooses not to use the managed service, the following features and benefits are available.
PolicyGuru® + Call Authentication
The SecureLogix® Orchestra One™ call authentication service is a separate cloud-based offering that provides call authentication / verification to identify trusted vs. untrusted callers before the call is answered. The PolicyGuru System integrates with the Call Authentication Service via a RESTful API to query the service for an authentication score for calls and return that score to an external customer REST endpoint system that the customer has configured to receive it.
Granular Control of International Calling
Centrally managed Voice Firewall security policy rules are distributed across the network to enforce in real time whether calls are allowed, redirected to a different destination, or terminated prior to call setup. You can whitelist known allowed calls, blacklist known malicious, fraudulent, or otherwise unauthorized calls, redirect suspicious calls, or watch and alert for potentially suspect calls to determine whether they represent misuse / abuse or potential attack activity.
Harassing Caller Mitigation
Every organization receives unwanted calls from harassing, malicious, or abusive callers. Use the PolicyGuru System to block such callers when they are identified by adding the calling number to a blacklist in the Firewall policy.
Nuisance Caller Mitigation
Nuisance calls such as robocalls and scam callers sap productivity and tie up trunk resources with no- value or negative-value calls. Add the calling number for such calls to a blacklist used in the PolicyGuru Firewall policy to block these callers when they are identified.
Countries of Interest Management
Many organizations have concerns about calls to or from specific countries. Add countries of interest to blacklists and use them in Firewall rules to monitor, alert, or block calls to or from specific countries of interest.
Real-Time Policy-Based Call Control and Alerting
Centrally managed Voice Firewall security policy rules are distributed across the network to enforce in real time whether calls are allowed, redirected to a different destination, or terminated prior to call setup. You can whitelist known allowed calls, blacklist known malicious, fraudulent, or otherwise unauthorized calls, redirect suspicious calls, or watch and alert for potentially suspect calls to determine whether they represent misuse / abuse or potential attack activity.
Enterprise-Wide Visibility, Logging, and Alerting
The solution provides a real-time, drill-down call detail analytics dashboard in the GUI. Up to 12 months of call and policy processing data for monitored SIP trunks is stored in a centralized database for offline analysis and reporting via third party tools. A real-time dashboard displays system events such as user logins and a graph of current calls per second (CPS).,Configurable real-time alerting provides immediate notification via syslog, SNMP, or email when security and monitoring policy rules fire.
Web-Based GUI
The PolicyGuru Controller provides a web-based GUI from which you define and install Voice Firewall security and monitoring policy rules.
Capacity
The PolicyGuru System supports up to 3000 concurrent calls / 150 CPS when running the call control policy, with up to 5 million discrete phone numbers used in policy. Policy processing adds less than 250ms latency to a call.