Jaroslav Novotný, Tomáš Soukal
April 4, 2023

Protecting Your API from App Impersonation: Token Hijacking Guide and Mitigation of JWT Theft

Gone are the days of locally-held data and standalone applications. With the rise of smartphones and portable devices, we are constantly on the go and reliant on network calls for everything from social communication to live updates. As a result, protecting backend servers and API calls has become more crucial than ever.
Gone are the days of locally-held data and standalone applications. With the rise of smartphones and portable devices, we are constantly on the go and reliant on network calls for everything from social communication to live updates. As a result, protecting backend servers and API calls has become more crucial than ever.
You can read more about the concept of RASP (Runtime application self-protection)
here.

You may also like

Cloning and containers: running your app inside someone else's sandbox, and how Talsec detects it
Cloning and containers: running your app inside someone else's sandbox, and how Talsec detects it
Read the full article on our blog.
How Attackers Exploit Play Integrity API and Where AppiCrypt Fits
How Attackers Exploit Play Integrity API and Where AppiCrypt Fits
Play Integrity's real limits: a 10,000-request daily quota, false positives you cannot debug, and seven documented bypasses. Plus where AppiCrypt fits.
Play Integrity Fix: why AppiCrypt is the better attestation anchor
Play Integrity Fix: why AppiCrypt is the better attestation anchor
Play Integrity Fix, the module that makes modified Android devices pass Google's checks: its real scale, its ten-year lineage, and what to anchor on instead.
Read More