Subject: Thread-Index: AQHa07mWxBv4yWdWJEGt7PK8oJtEDQ== Date: Thu, 11 Jul 2024 17:41:40 +0000 Message-ID: Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: X-MS-Exchange-Organization-RecordReviewCfmType: 0 Content-Type: multipart/alternative; boundary="_000_MA0PR01MB98775F59BAA87D6E06BBF138A0A52MA0PR01MB9877INDP_" MIME-Version: 1.0 --_000_MA0PR01MB98775F59BAA87D6E06BBF138A0A52MA0PR01MB9877INDP_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Thanks for reaching out regarding the need for Voice security. This email = explains the context of how our solution works, what to expect. It also ha= s a few business and technical discovery questions, so we understand their = business and expectations. It will be great if we can get on a call with th= e account team / customer to understand more. Context: 1. It is assumed that you use SIP trunks and have SBCs 2. The system operates in 3 logical parts * Remote worker security (to protect your voice network from cyberat= tacks that come through the SBC) * Call screening (to protect your enterprise from scam, robo calls, = TDoS attacks and toll fraud). * Custom workflows to detect and alert on special calls like CMS aud= itor calls 3. The system works by integrating only with your SBC and is oblivious t= o the UC or CC solution that is behind the SBC. It works with all major SB= C vendors and uses standard SIP to interface with the SBC. 4. For call screening, the system only looks at call signaling and is ne= ver in the media path. For remote worker security, the system only looks a= t the logs. 5. The display update requires a header manipulation rule to be applied = on the SBC. Assertion will deploy this as part of the implementation. 6. The system will operate in learning mode i.e. will not block any call= for a minimum duration of 30 days or until it processes a few 100K calls t= o build AI models. 7. The minimum monthly call traffic required for call screening to work = is 100K calls. 8. It is highly recommended to integrate the system with agent / user di= sposition (via email integration, agent widget or via CRM sync) to rate a s= uspicious call. This is essential to continuously train the system and to = reduce its false positives in detecting scam calls. 9. The system is a hybrid solution with the Secure Voice core in AWS and= Scanner and Defender deployed onPrem or in Assertion cloud. Discovery questions: 1. Do you use Avaya SBC to support remote workers? 2. How many remote worker users do you have? 3. Have you ever been breached or attacked via a cyberattack on the SBC? 4. What is the call traffic per month =96 In / Out across the enterprise= ? 5. What percentage of the above traffic flows through SBCs? 6. Do you have an IVR? What percentage of incoming calls flow via the IV= R? 7. Have your employees ever been scammed by a phone call? Are you worri= ed about receiving scam calls? 8. Have your employees complained of having received robo / tele marketi= ng calls? 9. Is there a process where an employee reports a scam or robo call? Wh= at is it? What is done about it? 10. Do you offer callback functionality? Does it allow the caller to ent= er a phone number, or it only calls back a registered number (that is alrea= dy in the database)? 11. Do you have a business reason to call international phone numbers tha= t are not stored as part of your customer database? 12. Do you have a reason to enforce calling restrictions like sanctions b= arring, geo-fencing, DNC? Have you faced any difficulty with that in the pa= st? 13. Do you have a toll-free number? 14. Have you ever wished for a single dashboard to show call traffic and = threat visibility from all over the world? Thanks --_000_MA0PR01MB98775F59BAA87D6E06BBF138A0A52MA0PR01MB9877INDP_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable

Thanks for reaching out regarding the need for Voi= ce security.  This email explains the context of how our solution work= s, what to expect.  It also has a few business and technical discovery questions, so we understand their business and exp= ectations. It will be great if we can get on a call with the account team /= customer to understand more.

 

Context:

  1. It is assumed that you use SIP trunks and = have SBCs
  2. The system operates in 3 logical parts
    1. Remote worker security (to protect your vo= ice network from cyberattacks that come through the SBC)
    2. Call screening (to protect your enterprise= from scam, robo calls, TDoS attacks and toll fraud).
    3. Custom workflows to detect and alert on sp= ecial calls like CMS auditor calls
  3. The system works by integrating only with = your SBC and is oblivious to the UC or CC solution that is behind the SBC.&= nbsp; It works with all major SBC vendors and uses standard SIP to interfac= e with the SBC.
  4. For call screening, the system only looks = at call signaling and is never in the media path.  For remote worker security, the system only looks at the logs. =
  5. The display update requires a header manip= ulation rule to be applied on the SBC.  Assertion will deploy this as = part of the implementation.
  6. The system will operate in learning mode <= span class=3D"GramE"> i.e. will not block any call for a minimum duration of 30 days or un= til it processes a few 100K calls to build AI models.
  7. The minimum monthly call traffic required = for call screening to work is 100K calls.
  8. It is highly recommended to integrate the = system with agent / user disposition (via email integration, agent widget o= r via CRM sync) to rate a suspicious call.  This is essential to conti= nuously train the system and to reduce its false positives in detecting scam calls.
  9. The system is a hybrid solution with the S= ecure Voice core in AWS and Scanner and Defender deployed onPrem or in Assertion cloud.

 

Discovery questions:<= /p>

  1. Do you use Avaya SBC to support remote wor= kers?
  2. How many remote worker users do you have? =
  3. Have you ever been breached or attacked vi= a a cyberattack on the SBC?
  4. What is the call traffic per month =96 In = / Out across the enterprise?
  5. What percentage of the above traffic flows= through SBCs?
  6. Do you have an IVR? What percentage of inc= oming calls flow via the IVR?
  7. Have your employees ever been scammed by a= phone call?  Are you worried about receiving scam calls?
  8. Have your employees complained of having r= eceived robo / tele marketing calls?
  9. Is there a process where an employee repor= ts a scam or robo call?&n= bsp; What is it?  What is done about it?
  10. Do you offer callback functionality? = Does it allow the caller to enter a phone number, or it only calls back a = registered number (that is already in the database)?
    11. =
  11. Do you have a business reason to call inte= rnational phone numbers that are not stored as part of your customer databa= se?
  12. Do you have a reason to enforce calling re= strictions like sanctions barring, geo-fencing, DNC? Have you faced any dif= ficulty with that in the past?
  13. Do you have a toll-free number?
  14. Have you ever wished for a single dashboar= d to show call traffic and threat visibility from all over the world?

 

Thanks

 

 

 

--_000_MA0PR01MB98775F59BAA87D6E06BBF138A0A52MA0PR01MB9877INDP_--