All Vendors
platform

Aviato

Platform infrastructure vendor. Low liability exposure limited to consent bypass. Minimal revenue impact.

6 IOCs9 detections100% pre-consent9 sites
70
Vendor Risk Score

How This Briefing Works

This report opens with key findings, then maps the gaps between what Aviato 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

Key Findings

9 detections across 9 sites100% pre-consent activity
CRITICAL

Pre-Consent Activity

Aviato was observed loading and executing before user consent was obtained on 100% of sites where it was detected.

GDPRePrivacy
Disclosure Gaps

Claims vs. Observed Behavior

1 gaps

pending

UNKNOWN
They Claim

“Requires claims extraction via CDT”

Observed Behavior

Live website analysis pending

Customer Impact

What This Means For You

For legal: Pre-consent cookie execution creates GDPR liability, though infrastructure necessity arguments may apply to functional cookies. Limited competitive intelligence value due to basic platform monitoring focus.
Recommended Actions

What To Do About It

Role-specific actions based on observed behavior

If You Use Aviato

  • →Require Aviato to separate functional cookies (infrastructure) from analytics cookies (consent required)
  • →Implement cookie consent categorization for non-essential platform tracking
  • →Add platform tracking disclosure to privacy policy

If You're Evaluating Aviato

  • →Review DPA distinguishing infrastructure vs. analytics data processing

Negotiation Leverage

  • →Pre-consent cookie execution violates ePrivacy Directive - require separation of functional (necessary) from analytics (consent required)
  • →Infrastructure necessity arguments do not extend to all platform tracking - demand technical controls for analytics consent
  • →Minimal competitive intelligence value from basic infrastructure monitoring
Runtime Detections

Runtime Detections

1 BTI-C CODES

BLACKOUT observed this vendor's JavaScript executing in a live browser and classified each hostile behavior using our BTI-C (Behavioral Threat Intelligence — Capability) taxonomy. These are not theoretical risks — each code below was triggered by something we watched this vendor's code actually do.

BTI-C09Consent Bypass

Ignoring CMP signals

Impact: Executes platform tracking cookies before consent collection. Violates ePrivacy Directive cookie consent requirements despite infrastructure service role.

IOC Manifest

IOC Manifest

4 INDICATORS

Indicators of compromise across 3 categories. Use for detection rules, CSP policies, or Pi-hole blocklists.

No indicators in this category

Ecosystem

Ecosystem & Supply Chain

Platform infrastructure with minimal third-party integrations. Common co-deployments: SaaS platforms, infrastructure monitoring tools, basic analytics.
Evidence

Evidence Artifacts

Artifacts collected during analysis, available with evidence-tier access.

HAR Capture

Complete network capture with all requests and responses

IOC Manifest

6 detection signatures across scripts, domains, cookies, and network endpoints

Vendor Details