How This Briefing Works
This report opens with key findings, then maps the gaps between what Sitecore 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”
Runtime beacon behavior, CDP data collection scope, and personalization execution not yet observed by BLACKOUT scanner
What This Means For You
What To Do About It
Role-specific actions based on observed behavior
Recommended Actions for Sitecore
- →- Audit the full scope of data sources feeding the Sitecore CDP and ensure each has a documented legal basis and consent mechanism. - Review FXM beacon deployments on non-Sitecore websites and verify tracking scope is disclosed and consented to on each property. - Assess the identity resolution system to understand what cross-channel data is being stitched into unified profiles and whether visitors are informed. - Evaluate the Reference Data service API access and determine which external systems are submitting or retrieving customer data. - Map the complete personalization decision chain to understand how cross-channel behavioral data influences what individual visitors see on your website.
Negotiation Leverage
- →When negotiating with Sitecore, request a complete data architecture diagram showing all data sources feeding the CDP, all external systems with Reference Data service access, and all properties where FXM beacons are deployed. Ask for documentation of the identity resolution methodology, including what data signals are used to stitch cross-channel profiles and what confidence thresholds govern identity merging. Key contractual protections should include comprehensive data portability for unified customer profiles (not just content), restrictions on Sitecore's use of aggregated behavioral data for AI model training or benchmarking, granular data deletion SLAs that cover all channel data (not just web), and audit rights to inspect cross-channel profile construction. Given the platform's scope, negotiate exit provisions that include data migration support and transitional access periods to prevent lock-in from becoming a leverage point at renewal.
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
95 detection signatures across scripts, domains, cookies, and network endpoints