STIR/SHAKEN overview

Your guide to everything STIR and SHAKEN

STIR (Secure Telephony Identity Revisited) and SHAKEN (Secure Handling of Asserted information using toKENs) are the frameworks that promise to prevent the completion of illegally spoofed calls.

Overview

STIR/SHAKEN uses digital certificates, based on common public key cryptography techniques, to ensure the calling number of a telephone call is secure. Each telephone service provider obtains their digital certificate from a certificate authority who is a trusted authority. The certificate technology enables the called party to verify that the calling number is accurate and has not been spoofed.

STIR/SHAKEN work flow

How STIR/SHAKEN work in a network
  1. A SIP INVITE is received by the originating telephone service provider.
  2. The originating telephone service provider checks the call source and calling number to determine how to attest for the validity of the calling number.
    • Full Attestation. The service provider has authenticated the calling party and attest that they are authorized to the use the calling number. An example of this case is a subscriber registered with the originating telephone service provider’s softswitch.
    • Partial Attestation. The service provider has authenticated the call origination but cannot verify the call source is authorized to use the calling number. An example of this use case is a telephone number behind an enterprise PBX.
    • Gateway Attestation. The service provider has authenticated from where it received the call but cannot authenticate the call source. An example of this case would be a call received from an international gateway.
  3. The originating telephone service provider uses the authentication service to create a SIP Identity header. The authentication service could be a third party service hosted in the cloud, or a software application integrated with the telephone service provider’s Session Border Controller (SBC) or a softswitch. The SIP Identity header contains the following encrypted data:
    • Calling number
    • Called number
    • Date and time
    • Attestation
    • Unique originating identifier
  4. The SIP INVITE with the SIP Identity header is sent to the terminating telephone service provider. In addition, the Identity token may be sent across the internet, out-of-band, to the terminating provider’s Call Placement Service
  5. The SIP INVITE with Identity header is passed to the verification service.
  6. The verification service obtains the digital certificate of the originating telephone service provider from the public certificate repository. The two step process of verification commences. Verification is a two-step process. First, the SIP Identity header is base-64 decoded and the details are compared to the SIP INVITE message. If they match, the next step is to use the public key of the certificate to verify the SIP identity header signature. If both verification steps are successful, then the calling number has not been spoofed.
  7. The verification service returns the results to the terminating service provider’s softswitch or SBC.
  8. The call is completed to the called party.

For more information on STIR/SHAKEN, see our STIR/SHAKEN software solution overview.

Contact us today to learn more about STIR/SHAKEN.

Request info about our products and services

* required

This information will only be used to respond to your inquiry. TransNexus will not share your data with any third parties. We will retain your information for as long as needed to retain a record of your inquiry. For more information about how we use personal data, please see our privacy statement.


More on TransNexus.com

June 29, 2020

FCC issues staff report on robocall blocking tools

June 25, 2020

Open source Call Placement Service advances SHAKEN call authentication for all

May 27, 2020

USTelecom files letter of intent to apply for the Traceback Consortium role

April 7, 2020

Who may authenticate calls for STIR/SHAKEN

April 1, 2020

FCC issues STIR/SHAKEN mandate

March 6, 2020

FCC Chairman Pai announces proposed mandate for STIR/SHAKEN

January 20, 2020

NTCA discusses barriers to SHAKEN faced by rural carriers

January 2, 2020

STIR/SHAKEN mandate signed into U. S. law

October 1, 2019

California enacts law to mandate STIR/SHAKEN

October 1, 2019

FCC filings calling for Out-of-Band STIR

August 15, 2019

ClearIP now supports Rich Call Data in STIR/SHAKEN

April 29, 2019

ClearIP now supports out-of-band STIR/SHAKEN