Comparison Overview
SWISS STEEL USA, Inc.
SWISS STEEL USA, Inc.
Schmolz+Bickenbach USA, Inc., Carol Stream, US
Last Update: 04/03/2026
Since the late 1970’s Swiss Steel USA has been active in the distribution for the US market. The activities of the company are focused on providing the highest quality tool steels, stainless steels, and engineering steels from our own mills: Deutsche Edelstahlwerke, Ugi...
Norsk Hydro
Drammensveien 264, Oslo, Oslo, NO, 0283
Last Update: 01/04/2026
Hydro is a leading industrial company that builds businesses and partnerships for a more sustainable future. We develop industries that matter to people and society. Since 1905, Hydro has turned natural resources into valuable products for people and businesses, creati...
Compliance Ranges Comparison
SWISS STEEL USA, Inc.
Norsk Hydro
Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for SWISS STEEL USA, Inc. in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Norsk Hydro in 2026.
Incident History - SWISS STEEL USA, Inc. (X = Date, Y = Severity)
SWISS STEEL USA, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Norsk Hydro (X = Date, Y = Severity)
Norsk Hydro cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SWISS STEEL USA, Inc.
Norsk Hydro
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.