Exposure Management - Snapsec Suite

Exposure Management moves beyond passive inventory to pinpoint active, high-risk security flaws across your perimeter.

Exposure Rule Engine

Snapsec uses a YAML-driven rule engine to evaluate asset state and trigger exposure alerts:

rule:
  id: "exp-001"
  name: "Exposed Database on Public Subnet"
  severity: "Critical"
  match:
    ports: [3306, 5432, 27017, 6379]
    exposure: "internet-facing"
  action:
    generate_exposure: true
    notify: "slack:#security-incidents"

Top Common Exposures Detected

Directly Exposed Admin Consoles: Publicly accessible Jenkins or Kubernetes dashboards without SSO.
Exposed Version Control & Env Files: Public access to /.git/, /.env, or id_rsa private keys.
Internal IP Disclosure: HTTP response headers leaking private RFC 1918 internal IP addresses.
Insecure CORS Policies: Wildcard Access-Control-Allow-Origin: * paired with credentials.