Proxy Usage Detection
| Plan | Platforms | MASVS |
|---|---|---|
| Team | Android, iOS | MASVS-NETWORK-1 |
Overview
Proxy Usage Detection identifies when a device appears to be using an HTTP, HTTPS, SOCKS, or auto-configured proxy. Proxies are sometimes legitimate in enterprise environments, but they can also be used to intercept traffic, bypass location or network policy, inspect sensitive requests, or support fraud workflows.
When proxy usage is detected, AppTego applies your configured response. Teams commonly start with logging, then warn or restrict sensitive flows once expected enterprise behavior is understood.
When To Use It
Use this control when:
- Your app handles credentials, payment data, account changes, health data, or regulated information.
- Network trust, certificate pinning, or fraud decisions depend on avoiding unknown intermediaries.
- Your compliance policy restricts use of user-configured proxies.
- You want proxy usage as an input to server-side risk scoring.
How It Works
The protected app evaluates platform network configuration and connectivity signals for evidence that traffic may be routed through a proxy. Detection behavior is platform-aware and designed to catch common proxy states without exposing the exact signal list or inspection order in public documentation.
Proxy detection is a risk signal. It does not remove a proxy from the device and it does not replace certificate pinning, TLS hardening, or server-side fraud controls.
How to Enable the Control
Navigate to Detection & Response from the AppTego portal, and expand the Network And Location Detection section. Under this section you will find the Proxy Usage Detection control. Click Enable Configuration, choose the response action, and save the configuration for the next build or for it to be applied with a live push (if enabled).
API Configuration Example
{
"ProxyUsageDetectionResponse": {
"detection": true,
"action": "alert",
"title": "Proxy Detected",
"message": "Your device appears to be using a network proxy. Please disable it before continuing.",
"buttons": ["OK"],
"actions": ["close"],
"redirects": [""]
}
}
| Field | Purpose |
|---|---|
detection | Enables or disables proxy detection. |
action | Selects the response style, such as alert, close, log, or warn. |
title / message | User-facing text shown when a response is displayed. |
buttons / actions / redirects | Defines the available response buttons and their outcomes. |
Compatibility Notes
- Corporate networks and managed devices may require proxies for legitimate access. Use logging first if your app serves enterprise users.
- Some VPN products also configure proxy behavior. Use VPN Detection alongside this control when you need to distinguish network tunnel risk from proxy risk.
- Proxy detection should be treated as one signal in a broader network-trust model. Pair it with certificate pinning and TLS policy controls.