Comparison Overview
CIRO / OCRI

CIRO / OCRI
Toronto, CA
Last Update: 04/04/2026
L’Organisme canadien de réglementation des investissements (OCRI) est déterminé à protéger les investisseurs, à assurer une réglementation efficace et uniforme et à renforcer la confiance des Canadiens dans la réglementation financière et les personnes qui s’occupent de...

Aegon
Schiphol Boulevard 223, Schiphol, 1118 BH, NL
Last Update: 01/04/2026
People are living longer, and we are excited about the possibilities this brings. We see longevity, aging, and changing life patterns as an opportunity for our customers, our employees, and society as a whole. And we want to support everyone in building the financial me...
Compliance Ranges Comparison

CIRO / OCRI







Aegon






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
CIRO / OCRI has 42.86% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Aegon in 2026.
Incident History - CIRO / OCRI (X = Date, Y = Severity)
CIRO / OCRI cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aegon (X = Date, Y = Severity)
Aegon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CIRO / OCRI

Aegon
FAQ
Latest Global CVEs
Use after free in Aura in Google Chrome prior to 150.0.7871.128 allowed a local attacker to potentially exploit heap corruption via a malicious file. (Chromium security severity: High)
Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.128 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Out of bounds read and write in V8 in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Cast in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Network in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)