How This Briefing Works
This report opens with key findings, then maps the gaps between what Oracle CX 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
“Awaiting scanner verification”
Oracle CX deploys multiple JavaScript libraries, tracking pixels, and email beacons requiring runtime analysis to determine actual data collection scope, cookie behavior, and third-party data sharing patterns.
data_flow
“Post-advertising data isolation unverified”
Oracle claims advertising and CX data are separate, but no independent verification confirms BlueKai/AddThis data assets are fully segregated from remaining CX infrastructure.
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Oracle CX
- →- Audit all Oracle CX JavaScript deployments for pre-consent firing and undisclosed data collection behaviors using runtime observation tools - Demand contractual isolation guarantees ensuring CX customer data is never aggregated with Oracle's broader enterprise data assets or remnant advertising data - Verify CX Unity's cross-channel identity resolution operates strictly within consented data boundaries and document all data flows between Eloqua, Responsys, and Unity - Review Oracle's data processing agreements for post-advertising-exit changes to data retention, sharing, and processing terms - Establish independent measurement capabilities to validate Oracle's attribution and scoring outputs rather than relying solely on Oracle-reported campaign performance
Negotiation Leverage
- →Oracle's 2024 exit from the advertising business is the most significant leverage point in any CX negotiation. The forced shutdown of a multi-billion-dollar business unit due to privacy compliance failures demonstrates systemic data governance issues at the organizational level. Negotiators should use this history to demand: (1) contractual data isolation guarantees with audit rights, (2) enhanced data processing agreements that explicitly prohibit cross-product data aggregation, (3) price protection clauses given Oracle's track record of aggressive enterprise license auditing, and (4) data portability provisions that reduce lock-in. Oracle's CX division needs to demonstrate it has learned from the advertising debacle — make them prove it contractually, not just verbally.
IOC Manifest
Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.
No indicators in this category
Ecosystem & Supply Chain
Evidence Artifacts
Artifacts collected during analysis, available with evidence-tier access.
Complete network capture with all requests and responses
8 detection signatures across scripts, domains, cookies, and network endpoints