Aptori Proxy

Aptori Proxy – Secure HTTP CONNECT Proxy for Cross-Network Testing

Description:
Aptori Proxy is a new module that enables secure, cross-network application testing by acting as an HTTP CONNECT proxy. It allows traffic from the Aptori Sift engine, running inside a private or restricted network, to appear as though it's originating from a public IP address or alternate vantage point. This is ideal for validating externally deployed applications from outside the firewall while reporting results to an Aptori Platform inside the internal network.

Aptori Proxy is built for secure tunneling and optimized for API security testing across hybrid or segmented environments. It gives teams more flexibility in how and where they run tests without compromising security.

Primary Benefits:

• Test public endpoints from secure, internal environments.
• Maintain centralized configuration, control, and audit logging.
• Simulate real-world access patterns while preserving private network integrity.

Example Use Case

When Sift runs within a private network, but testing a public deployment requires requests to appear as though they originate from a public IP address, Aptori Proxy makes it possible. Test traffic is routed through a proxy hosted on a public IP, while results are securely transmitted back to the Aptori Platform inside the private network. This approach safeguards internal security while providing an accurate view of the application’s behavior under real-world conditions.

Key Features:

• Secure HTTP CONNECT tunneling to destination servers
• Token-based access control using JWTs issued by the Aptori Platform
• One-time token enforcement to prevent replay attacks
• TLS encryption using configurable certificate and key files
• Customizable port (default: 8443), fully configurable via CLI

Why It Matters:
Aptori Proxy enables secure, controlled testing of public deployments from inside your private network, ensuring centralized control, full visibility, and unified reporting.

By acting as a secure bridge, it closes the gap between isolated internal testing environments and real-world application behavior.