Comparison Overview
Storebrand

Storebrand
Professor Kohts vei 9, Lysaker, 1327, NO
Last Update: 04/12/2025
Storebrand er et nordisk finanskonsern som tilbyr tjenester innen pensjon, sparing, bank og forsikring. Vi ønsker å tilby bærekraftige løsninger og motivere våre kunder til å ta gode økonomiske valg for fremtiden: sammen skaper vi en fremtid å glede seg til. Med en for...

Goldman Sachs
200 West Street, New York, 10282, US
Last Update: 21/06/2026
We aspire to be the world’s most exceptional financial institution, united by our shared values of partnership, client service, integrity, and excellence. Operating at the center of capital markets, we act as one firm, mobilizing our people, capital, and ideas to deli...
Compliance Ranges Comparison

Storebrand







Goldman Sachs






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

Storebrand

Goldman Sachs
FAQ
Latest Global CVEs
Improper access control in Microsoft Edge for Android allows an unauthorized attacker to bypass a security feature over a network.
A security vulnerability has been detected in NousResearch hermes-agent up to 2026.4.30. Affected is the function GatewayStreamConsumer._filter_and_accumulate of the file gateway/stream_consumer.py of the component Streaming Reasoning Tag Filter. The manipulation leads to improper handling of case sensitivity. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitability is told to be difficult. The exploit has been disclosed publicly and may be used. The project decided to not implement a dedicated fix: "[T]he analysis and the fix are both sound. It just lands below the bar for the maintenance cost of a duplicated scrub path."
- https://gist.github.com/YLChen-007/2229e5505bcbb3e15a7ae8fba4c4be37
- https://github.com/NousResearch/hermes-agent/
- https://github.com/NousResearch/hermes-agent/issues/27288
- https://github.com/NousResearch/hermes-agent/pull/28631#issuecomment-4622188016
- https://vuldb.com/cve/CVE-2026-14617
- https://vuldb.com/submit/844654
- https://vuldb.com/vuln/376134
- https://vuldb.com/vuln/376134/cti
Insufficient ui warning of dangerous operations in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Relative path traversal in Microsoft Edge for Android allows an unauthorized attacker to disclose information locally.