Skip to main content
Back to security

CTEM — Continuous Threat Exposure Management

Continuously discover, prioritize, validate and reduce exposures against an authorized inventory and evidence.

Operating cycle

  1. Define authorized scope and criticality
  2. Discover assets and exposures
  3. Prioritize risk and attack paths
  4. Validate observations and false positives
  5. Remediate, measure and verify again

Tools and responsibilities

OASM

External attack surface discovery and inventory (isolated proof of concept).

Prowler

Cloud, Kubernetes and Microsoft 365 posture and compliance for authorized providers.

Cartography

Asset relationships and attack-path analysis in Neo4j.

Nuclei

HTTP misconfiguration and exposure detection requiring validation.

Nmap

Bounded network inventory of authorized ports.

testssl.sh

Certificates, protocols and ciphers; independent SSL Labs checks.

checkdmarc

SPF, DKIM, DMARC, MX, MTA-STS and TLS-RPT; provider-confirmed selectors.

Backstage

Canonical inventory and declared exposure policy.

DefectDojo

Triage, deduplication and remediation tracking.

FastAPI Sample

Aggregate indicators and evidence provenance without revealing private details.

Exposure policy

Secrets, technical files, administrative interfaces and metrics are private by default. LiteLLM and Ollama are LAN-only. Scanners operate within authorized scope.

Evidence status

This page describes a target architecture, not a security attestation or verified deployment. Missing, expired or incomplete reports never prove zero vulnerabilities. Detailed findings remain private.