Comparison Overview
Yara Birkeland AS
Yara Birkeland AS
Drammensveien 131, Oslo, Oslo, 0277, NO
Last Update: 20/11/2025
Setting precedent as a catalyst and creator for zero emission transportation offerings. Partnering with best in class providers across industries we are connecting autonomous transportation assets to enable a continuous and efficient flow of goods.
Ingram Micro
3351 Michelson Drive, Suite 100, Irvine, CA, US, 92612
Last Update: 05/04/2026
Ingram Micro is a leading technology company for the global information technology ecosystem. With the ability to reach nearly 90% of the global population, we play a vital role in the worldwide IT sales channel, bringing products and services from technology manufactur...
Compliance Ranges Comparison
Yara Birkeland AS
Ingram Micro
Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Yara Birkeland AS in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
Ingram Micro has 3.85% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Yara Birkeland AS (X = Date, Y = Severity)
Yara Birkeland AS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ingram Micro (X = Date, Y = Severity)
Ingram Micro cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Yara Birkeland AS
Ingram Micro
FAQ
Latest Global CVEs
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an inadequate encryption strength vulnerability which could allow an attacker to steal admin credentials via weak hash or a pass-the-hash attack.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could allow for asset discovery by unauthenticated users.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an unintended proxy or intermediary vulnerability which could allow an attacker to use an active proxy, which would bypass OT segmentation.
Pronetiqs IntraVUE Versions 3.2.1a14 and prior have a plaintext storage of a password vulnerability that could expose cleartext credentials through the API.
Pronetiqs IntraVUE versions 3.2.1a14 and prior have an exposure of sensitive system information to an unauthorized control sphere vulnerability which could expose the underlying host/share filesystem.