third-party-detector

Third-party detection identifies external vendors embedded in a website by analyzing signals like script URLs, JavaScript globals, DNS TXT records, and CSP domains. It maps these signals to known SaaS services across categories like payments, analytics, and authentication.

Vendor discovery uses JavaScript globals, HTML snippets, DNS TXT records, CSP domains, and job-posting text as detection signals. These signals are matched to known third-party vendors to build an inventory for compliance and security assessments.

To compile an integration inventory, you analyze raw signals from the web app including JavaScript globals, HTML, and HTTP CSP domains. The detector matches these signals to known vendors, producing a categorized list with evidence attribution for audit validation.

Yes, CSP analysis identifies external SaaS categories by extracting approved domains from HTTP headers and matching them to known vendors. This maps external services across functional areas like analytics, authentication, payments, and customer support.

Detection confidence for compliance review is ranked using weighted scoring across diverse signal types. Each detected vendor receives evidence attribution based on the specific signals found, such as script URLs or DNS records, enabling audit-style validation.

Yes, third-party detection works across diverse SaaS categories including monitoring, CRM, payments, and support. It maps detection signals from JavaScript, HTML, and DNS to known vendors, providing category-level coverage for security and compliance audits.