How This Briefing Works
This report opens with key findings, then maps the gaps between what Iubenda 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”
No runtime behavioral analysis completed. CDT browser forensics needed to verify: (1) cookie blocking completeness before consent, (2) TCF string accuracy and distribution, (3) pre-consent network requests by Iubenda's own JavaScript, (4) consent database data sharing practices, (5) whether Iubenda's scripts set any tracking identifiers of their own.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
If You Use Iubenda
- →Verify Iubenda's cookie blocking completeness with independent scanner analysis
- →Audit TCF string generation for accuracy against actual consent choices
- →Review Iubenda's own network requests for pre-consent data collection
- →Confirm consent database records match actual visitor interactions
If You're Evaluating Iubenda
- →Independent CMP audit to verify consent signal integrity
- →Compare Iubenda's blocked vendor list against actual network requests
- →Assess whether consent database integrations (Zapier) create unintended data flows
Negotiation Leverage
- →CMP integrity is foundational — if Iubenda fails, every vendor on the page fires without valid consent and the site operator bears liability
- →150,000+ organization install base means consent pattern data has aggregate intelligence value
- →SMB focus means most customers cannot independently verify CMP behavior
- →Consent database integrations (Zapier, CRM syncs) may create data flows beyond stated privacy purposes
- →Request independent verification of cookie blocking completeness before renewal
IOC Manifest
Indicators of compromise across 5 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
74 detection signatures across scripts, domains, cookies, and network endpoints