Comparison Overview
DNV Cyber

DNV Cyber
Veritasveien, Oslo, 1363, NO
Last Update: 06/03/2026
DNV Cyber is a leading cybersecurity services provider. We empower businesses with complex needs to become safer and more resilient with tailored solutions. Our global team of more than 500 experts brings over 30 years of IT and industrial control system security experi...

Sweco
Gjörwellsgatan 22, Stockholm, 112 60, SE
Last Update: 02/04/2026
Sweco is at the heart of the green transition - planning and designing the sustainable communities and cities of the future. Together with our clients and the collective knowledge of our 23,000 architects, engineers and other specialists, we co-create solutions to addre...
Compliance Ranges Comparison

DNV Cyber







Sweco






Benchmark & Cyber Underwriting Signals
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for DNV Cyber in 2026.
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for Sweco in 2026.
Incident History - DNV Cyber (X = Date, Y = Severity)
DNV Cyber cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sweco (X = Date, Y = Severity)
Sweco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

DNV Cyber

Sweco
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.