How This Briefing Works
This report opens with key findings, then maps the gaps between what WebEngage discloses and what BLACKOUT observed at runtime. From there: what it means for your organization, what to do about it, and the detection data and evidence underneath.
Key Findings
Analysis pending. Findings will appear here once intelligence collection is complete.
Claims vs. Observed Behavior
Pending Analysis
“Claims extraction pending”
Awaiting scanner verification. Runtime behavioral analysis needed to confirm: (1) exact Anonymous ID creation timing relative to consent events, (2) cookie taxonomy including names, domains, and expiration periods, (3) full list of third-party endpoints contacted by the WebEngage SDK during page load, (4) on-site overlay injection method and DOM manipulation patterns, (5) web push service worker scope and permissions requested, and (6) data payload contents transmitted to WebEngage servers on each tracked event.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for WebEngage
- →- Verify WebEngage Anonymous ID creation timing: confirm no persistent identifiers are set before explicit consent is obtained from visitors - Audit all active WebEngage integrations and data connectors to map the complete data distribution footprint across your marketing stack - Review on-site overlay and survey configurations to ensure no additional personal data is collected through WebEngage-injected widgets without proper disclosure - Request WebEngage's complete sub-processor list and cross-reference against your published privacy notice's third-party disclosure section - Conduct independent HAR capture to document all network calls made by the WebEngage SDK during page load, including payload contents and destination endpoints
Negotiation Leverage
- →WebEngage's primary leverage points are the automatic Anonymous ID system and the breadth of its on-site intervention capabilities. When negotiating: (1) Demand contractual commitment that the Anonymous ID is not created until after explicit consent is obtained -- this is the single highest-risk behavior in their SDK, (2) Require a complete network call manifest documenting every endpoint the WebEngage SDK contacts during page load and ongoing session, (3) Negotiate limits on the on-site overlay and survey injection system -- specifically, require that no WebEngage-controlled content is injected into your web experience without per-campaign approval workflows, (4) Demand data residency commitments given WebEngage's India-based infrastructure -- for organizations subject to EU data protection requirements, confirm whether behavioral data transits through or is stored in jurisdictions without adequacy decisions, and (5) Require that integration marketplace connectors cannot be activated without explicit authorization, preventing new data distribution pathways from being created without your security team's review. WebEngage's ISO 27001 and SOC 2 certifications provide contractual hooks -- demand evidence that these certifications cover the specific data flows touching your customer data, not just their corporate infrastructure.
IOC Manifest
Indicators of compromise across 4 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
419 detection signatures across scripts, domains, cookies, and network endpoints