// security architecture

Read-Only by Design.

PingTraceSSH uses temporary cross-account AWS access to read the network configuration metadata required for modeling and assurance.

  1. Customer AWS Account
  2. PingTraceSSHReadOnlyRole
  3. AWS STS AssumeRole
  4. Temporary credentials
  5. PingTraceSSH Scanner
  6. Network Change + Assurance Engine
  7. Customer Dashboard
No static customer AWS access keys
Customer-specific External IDs
Minimum read-only network discovery permissions
Temporary STS credentials
Server-side secrets
Customer-scoped connection records

What PingTraceSSH reads

Network configuration metadata—not packet contents or packet captures.

  • VPCs
  • Subnets
  • Route tables
  • Transit Gateways
  • VPN state
  • Security-group configuration
  • Gateway relationships
Access configuration and credentials remain server-side. The browser never receives scanner credentials.