Skip to content

Prerequisites for Private Locations

Infrastructure Workflow

  1. The locally deployed Private Location connects to the Escape platform.
  2. When a scan is initiated, Escape sends requests to the Private Location service rather than directly to your servers.
  3. The Private Location forwards the requests to your internal applications.
  4. Scan results are then returned to Escape for reporting and analysis.

Diagram of Private Location Infrastructure:

Escape Private Locations

Resource Requirements

The resource requirements depend on expected traffic; a 1 vCPU instance with 2GB RAM is typically sufficient to start, with usage monitored and scaled as necessary. The more integrations you connect through the Private Location, the more resources you need.