loading
Loading content
loading
Attack Surface Management
Identify CMS, CDN, and WAF on live web servers. Technology detection names server software, runtimes, and frameworks with version status.
Technology detection answers what a live web server actually runs. After liveness, the next question is the stack: the CMS, the CDN, the WAF, the server software, the runtimes, and the frameworks, with a version status when the check is supported. This module writes that taxonomy as a typed record the next scan nests on.
You feed live web server URLs. This module names the CMS, CDN, WAF, server
software, runtimes, and frameworks on each one. When a version check is
supported, it writes version, latest_version, and version_status
(outdated, up_to_date, or unknown), plus technology-specific locations
such as login panels. The artifact is a typed web-technologies JSONL file
for the next scan. This is the fingerprint step of the ASM web tail:
hosts -> probe-web -> web FP -> tech-specific.
Pipeline guidance
hosts -> probe-web -> web FP -> tech-specific
web-servers. That is what you
nest on. Do not feed raw hosts.web-technologies. Generate Scan Report
can take the same file.port-details from Scan for Open Ports.
Do not cross-wire this node onto the network tail
(hosts -> open-ports -> network FP -> (misconfig | weak-creds)).Nest this after Probe for Web Servers
has produced web-servers, and before any technology-specific vulnerability
scan. The input contract is live HTTP(S) URLs. Probe owns liveness. This
module owns the CMS, CDN, and WAF taxonomy on that live list.
web-servers (FILE). Live web server URLs, one per line. Probe for web
header (STRING). Header(s) to include in HTTP requests. There is no
web-technologies (FILE). JSONL rows. Published fields: asset,
The tables this module produces. Sample rows are illustrative.
CMS, CDN, WAF, server software, runtimes, and frameworks detected on each live web server URL.
urlurl | technologytext | categoriesjson | versiontext | hostnametext | |
|---|---|---|---|---|---|
| 1 | https://blog.example.com | WordPress | Array[2] | 6.5.3 | blog.example.com |
| 2 | https://app.example.com | Cloudflare | Array[2] | app.example.com | |
| 3 | https://git.example.com | GitLab | Array[1] | 16.11.4 | git.example.com |
Fingerprint Web Technologies
Artifact class it owns
CMS, CDN, WAF, versions
Upstream it needs
web-servers (after probe)
Artifact class it owns
Stack CVEs on the ten named products
Upstream it needs
web-technologies
Fuzz Web Applications for Vulnerabilities is adjacent crawl-then-payload DAST on a URL list. It does not sit in this table and does not consume web-technologies.
questions
optional `header`
live-probe instrument; this page owns the taxonomy job
WAF-only flags; this module covers WAF plus CMS, CDN, server software, runtimes, and frameworks
Drop this module into a Trickest workflow and connect it to your upstream and downstream nodes. The face contract above is the wiring.
Get a personalized demo
A 30-minute walkthrough. We map the platform to your stack and answer pricing and deployment questions for your environment.