Skip to content

Security Overview

MyOwnProxy separates product administration from application proxy traffic. The control plane manages configuration, access, status, health, and MyOwnProxy software lifecycle. The data plane carries proxy traffic through the Gateway and Node infrastructure controlled by the Customer; it does not route that traffic through the control plane.

Security depends on both MyOwnProxy controls and Customer operations:

  • Customer resources and supported operations are scoped to the signed-in user's Customer and role. See Customer Isolation and Access Control.
  • The control plane retains operational information but is not the proxy traffic path. Connection diagnostics stored locally on the Customer-controlled Gateway remain outside MyOwnProxy access unless the Customer chooses to share them with MyOwnProxy Support. See Data Plane Privacy.
  • MyOwnProxy and the Customer have different responsibilities for software, operating systems, infrastructure, access, and secrets. See Shared Responsibility Model.
  • Supported hardware, operating systems, network prerequisites, and stable product constraints are documented in Supported Environments and Platform Limits.

Proxy Credential passwords and temporary SSH access material require careful handling. Use an approved secret manager for Proxy Credential passwords, keep SSH private keys under Customer control, grant ADMIN access only when required, and rotate or revoke persistent credentials when exposure is suspected.