Network interception detection

Network conditions can provide context about an application’s exposure. Pulse identifies relevant signals without treating VPN or proxy use as proof of an attack.

PlatformsAndroidiOS

What it is

Intercepting the network means getting in the middle of the conversation between your app and your servers. There are three common ways to do it:

  • A proxy. The phone sends its traffic to an intermediate machine that can log or modify it. If a custom certificate is also installed on the phone, that machine can decrypt the encrypted traffic.
  • A VPN. It routes all of the phone’s traffic through a tunnel to another point on the network. It almost always has legitimate uses, but it can also be used to route traffic to an analysis tool.
  • Server impersonation. Someone poses as your server so the app talks to them instead.

Why it matters

For anyone analyzing an app, the network is a gold mine. Intercepting the traffic lets them:

  • discover your APIs: routes, parameters, formats and tokens;
  • replay legitimate requests or craft new ones from outside the app;
  • modify responses, for example to enable features or change prices on screen;
  • on hostile networks, capture the credentials of users who do not know someone is listening.

Encrypting traffic protects against passive eavesdroppers. But if the attacker controls the phone and makes it trust their own certificate, encryption stops being a barrier. That is why it matters to know, from inside the app, whether the network environment is the one you expect.

There is a less visible consequence too. With the requests in plain sight, an attacker can write a program that talks directly to your server without going through the app. From that moment on, no protection on the phone can see it. That is why on-device detection works hand in hand with attestation: your APIs can require proof that a request comes from your real app.

What Pulse does

Pulse provides signals about network conditions that warrant assessment, such as proxy or VPN use. Available information depends on the platform. These conditions can serve legitimate needs, including enterprise networks and privacy services.

Received reports allow teams to review context alongside other signals. Pulse does not inspect application traffic content or replace communication security controls.

How it responds

The policy can record the signal, notify the application or trigger termination, where the response is applicable. Actions such as requesting additional verification, restricting an operation or protecting content require implementation in your application.

Local detection and response can work offline. Pending reports are sent when connectivity returns; the console shows the data it receives. History should not be interpreted as a guaranteed record of all device activity.

Before applying restrictions in production, assess detections on the devices and versions used by your organization. Observation mode supports investigating signals and potential false positives without enabling their restrictive response. Define separate policies for development, testing and production.

Scope and limitations

  • Traffic content. Pulse does not read or modify your application’s communications with its services.
  • Service protection. Communication security and backend authorization require their own controls.
  • Legitimate networks. VPNs, proxies or corporate configurations do not confirm malicious interception.
  • Limited visibility. Detection of activity outside the device or identification of a connection’s operator is not guaranteed.

Evaluate Pulse for your application

Discuss coverage, integration requirements and deployment options with our team.

Request an evaluation