Technology Detection¶

Escape ASM automatically identifies the technologies running on your assets: frameworks, libraries, web servers, databases, and CMS platforms. Each detected technology is linked back to the asset it was found on, giving you an inventory of detected technologies across your discovered assets.

Why it matters: knowing exactly which technologies are deployed, and at which version, is the first step to identifying vulnerable dependencies and outdated software before attackers do.

Where Technologies Are Detected¶

Technologies are identified from multiple asset types using different detection techniques:

Every detected technology is linked to its parent asset, so you always know where a given technology is running and can trace findings back to the asset that introduced them.

Detection Techniques¶

Escape combines several complementary approaches to maximize detection coverage:

• HTTP Fingerprinting: Analyzes HTTP response headers, body content, and script references to identify deployed technologies.
• Source Map Analysis: When source maps are exposed, Escape extracts dependency information directly from the bundled application code.
• Stack Trace Analysis: Error responses and stack traces are analyzed to reveal underlying frameworks and runtime environments.
• Low-Level Fingerprints: Protocol-level signals such as TLS banners, server behavior patterns, and byte signatures provide additional identification signals.
• Dependency Manifest Analysis: For connected code repositories, Escape parses package manifests and lock files to enumerate every declared dependency.

All detection is non-intrusive and agent-less: no software is installed on your infrastructure.

Packages and Software¶

Detected technologies are classified into two categories:

This classification helps you understand both your application-level dependencies (packages) and your infrastructure footprint (software) in a single inventory.

Versions and Versionless Technologies¶

When Escape detects a technology, it attempts to determine the specific version in use.

• Versioned technologies: The exact version is identified (for example, from HTTP headers, script filenames, or dependency manifests). This enables precise CVE matching against known affected version ranges.
• Versionless technologies: Escape identifies the technology by name when the available signals don't include a specific version, such as HTTP responses without version information. These technologies contribute to your stack inventory. A selection of potential CVEs is grouped into one issue per technology with reduced severity because the affected version hasn't been confirmed. Verify the version in use before treating the finding as confirmed. See CVE Scanning.

In the platform, versioned technologies are displayed as technology@version while versionless technologies show the technology name alone.

Technology Enrichment¶

After initial detection, each technology is enriched with additional metadata:

• Description: A human-readable summary of what the technology is
• Reference URL: A link to the technology's official page or repository
• Standard Identifiers: Industry-standard product identifiers (CPE) that feed into CVE Scanning

This enrichment enables accurate vulnerability matching and helps security teams quickly understand what each technology does without leaving the platform.

Related Documentation¶

• CVE Scanning
• Asset Management
• Security Tests Reference