scan-fase-10

To discover third-party services and API keys, scan frontend JS bundles and network traffic to extract DSNs and configuration fragments. This adaptive analysis surfaces patterns from SaaS integrations like Stripe and Sentry to generate risk-aware reports.

Adaptive pattern discovery identifies known and unknown third-party configurations in web applications. By extracting data from JS bundles and network traffic, it documents unfamiliar patterns and classifies findings by risk context to guide remediation.

Yes, SaaS integrations like Stripe, Sentry, and PostHog can be detected from network traffic. The scan extracts API keys, DSNs, and endpoints from frontend requests to map external service dependencies and surface exposed configurations.

Extract DSNs and configuration fragments by invoking a scan against the target URL after initial detections. The scan parses JavaScript bundles and network traffic to enumerate external configurations, classify findings, and generate risk-aware reports.

No dependencies are required for this third-party discovery approach. However, it should be invoked after initial FASE 0-1 detections are completed on the target URL, ensuring the web application has been mapped before extracting JS bundles and network traffic.

The best way to classify exposed API keys by risk context is through authenticated validation. By validating discovered keys and DSNs against their SaaS providers, the scan generates risk-aware reports that prioritize remediation for sensitive data exposure.