Skip to main content

 

AD_4nXdpx0bI_dG9ekbXEYqWCIFmhBkB1NlfibTsLCzB7g9fePggur522dnNEuUkWoepTV9LeFVsD56JSvxAZmMEA9D4siYewH1rEeTmYOPsvI5Jmcq-YIlxFXkEEROZSo6dGiDp2ocOCg9jIUd4BXOgh1FdkfJ8?key=HIgO_bNCUh_PB6wu9ev3dw

Netskope Global Technical Success (GTS)

Use Case - Implementing Steering bypass for WhatsApp's native agent traffic on the Android platform

 

Netskope Cloud Version - 117

 

Objective

Create a Certificate Pinned Application for WhatsApp Android Native Agent and add it into the Netskope client steering configuration

 

Prerequisite

Netskope CASB Inline/SWG license is required

 

Context

How can WhatsApp traffic from Android devices be excluded from routing through Netskope?

 

Details

WhatsApp, being a certificate-pinned app, can be excluded or bypassed from the steering configuration on Android devices.

 

Lab Recreate

Step 1 - Click over new certificate pinned app

Path: Netskope Tenant UI >>> Settings >>> Security Cloud Platform >>> App Definition

 AD_4nXfKVgYz9B6TKGwuo79KbVkujRu446GjxJBwuPxuv8WD1y6fqp_EnyY1Mg4Bw_rLkVI7i37bJehSzPmC5V5MW6pIpyWAuG4v3FFv7DrkwTMWEOY-K-5M9Wswn9sL6QRUqREupYKmihKbdnVaRKqOQ_Ej64ND?key=HIgO_bNCUh_PB6wu9ev3dw

 

Step 2 - Add the required details

Name - 1WhatsApp]

Platform - Android

Definition - com.whatsapp, com.whatsapp.w4b

 

Note - The process names for WhatsApp on the Android platform are com.whatsapp &  com.whatsapp.w4b

 

AD_4nXfTdtuu5hbp92ORwZnUQO0w3GUz4MumTX6DezXbI6ciYErICWBQQJKGIbUoNtd1DrGbCW99VKIEaZNad_hXHPQplUJoFc75bjLT-ALxGzjZqXkll_oiK9RgQoA8HC8paCWXFCsnFzHo8f13_3gKeRSdRApC?key=HIgO_bNCUh_PB6wu9ev3dw

 

Step 3 - Add Certificate Pinned Application steering exception

Path: Netskope Tenant UI >>> Settings >>> Security Cloud Platform >>> Steering Configuration >>> Exceptions >>> Certificate Pinned Application

AD_4nXfstkAzvclD_P5MKh1hG8xGe_SJrvknCJCnJrfEtjHax-Ckzta5DcqjYxs2cVS3FGCP_XIY--VJLam5mwvY7OsnPGtxRCWVCwqOwu-ufnT8iB-tTxxTCchZCJ3noLYWSvMK1QqmusirWl6WVry4SOrLchiu?key=HIgO_bNCUh_PB6wu9ev3dw

 

Step 4 - Add the required details

Certificate Pinned Application - lWhatsApp]

Custom App Domains - There are 2 options -

Option A - You can find all the list of all the domains the process - com.whatsapp &  com.whatsapp.w4b, trying to connect

Option B - Or add an * entry

Select - Bypass

AD_4nXevETUTlJz9V4l7PU2-sR0m86JUiwAE9owiHmrbq3P1wnGfCCvDvLQm1bMj1wL27TwaD01u-FhCH_W6tW04fUN32In0k-BAjIwRpjSwnGrscwoXLpgprWIMof5aawVLHBejs72-FPJZt89RxLQFRlYpQO4?key=HIgO_bNCUh_PB6wu9ev3dw

 

Question - How can I determine all the domains that the processes com.whatsapp and com.whatsapp.w4b are attempting to connect to?

Answer

Netskope Client logs

File name - nsdebuglog.log

 

Sample

AD_4nXedtNHDAhDSYjXPnXIeYftilMDRrSm7x80-tLnm5bqkwXyxge325HnA36a4myihDuqLla-Oryyh6jT4DUNkw2L8X_UHLW1MRAeUO0xSjR2HEMY2TxZVIHVY6aXM-fS0V4jHnSlRilxi5GRrIkw6HFzZkhpb?key=HIgO_bNCUh_PB6wu9ev3dw

 

Based on my research, I've identified the following domains related to com.whatsapp and com.whatsapp.w4b. However, please note that this list may not be complete, so you might consider ‘Option B’

whatsapp.com, whatsapp.net, wa.me, mmg.whatsapp.net, static.whatsapp.net, media-gig4-1.cdn.whatsapp.net, media-gru1-2.cdn.whatsapp.net, dit.whatsapp.net, c.whatsapp.net, media-lim1-1.cdn.whatsapp.net, mmg.whatsapp.net, graph.whatsapp.com, g.whatsapp.net, g-fallback.whatsapp.net, mmx-ds.cdn.whatsapp.net, media-mia3-1.cdn.whatsapp.net, media.feoh1-1.fna.whatsapp.net, media-bog2-1.cdn.whatsapp.net, media-gru1-1.cdn.whatsapp.net, scontent.whatsapp.net

 

Step 5 - Please ensure that the Netskope Client on your Android device retrieves any pending Netskope Client agent updates before starting any testing

 

Terms and Conditions

  • All documented information undergoes testing and verification to ensure accuracy.
  • Netskope Engineering is continuously working on product enhancements. In the future, additional controls may become available to address some of the limitations mentioned earlier. If any such changes are brought to our attention, we will promptly update the documentation to reflect them.

 

Notes

  • This article is authored by Netskope Global Technical Success (GTS).
  • For any further inquiries related to this article, please contact Netskope GTS by submitting a support case with 'Case Type – How To Questions'.