Comparison Overview

Hitachi

VS

Ingram Micro

Hitachi

1-6-6, Marunouchi, Chiyoda-ku, Tokyo, Japan, JP, 100-8280
Last Update: 2026-03-28
Between 800 and 849

For over 100 years, Hitachi has been committed to developing innovations that improve lives. Today, this means creating superior technology and products that balance environment, well-being, and economic growth. We integrate IT, operational technology (OT), and products to transform critical infrastructure and industrial systems. Through Hitachi’s process for creating value from data, which we call Lumada, we combine rich industry insight and infrastructure expertise to create measurable, positive change. We operate across four global sectors – Digital Systems & Services, Energy, Mobility, and Connective Industries – plus a Strategic Social Innovation Business Unit developing next-generation solutions. With over 280,000 employees across 618 consolidated subsidiaries in over 140 countries, we partner with our customers to create a harmonized society and build what’s next for people and planet.

NAICS: 5415
NAICS Definition: Computer Systems Design and Related Services
Employees: 37,613
Subsidiaries: 16
12-month incidents
0
Known data breaches
0
Attack type number
2

Ingram Micro

3351 Michelson Drive, Suite 100, Irvine, CA, US, 92612
Last Update: 2026-03-28

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 manufacturers and cloud providers to a highly diversified base of business-to-business technology experts. Through Ingram Micro Xvantage™, our AI-powered digital platform, we offer what we believe to be the industry’s first comprehensive business-to-consumer-like experience, integrating hardware and cloud subscriptions, personalized recommendations, instant pricing, order tracking, and billing automation. We also provide a broad range of technology services, including financing, specialized marketing, and lifecycle management, as well as technical pre- and post-sales professional support. Learn more at www.ingrammicro.com.

NAICS: 5415
NAICS Definition: Computer Systems Design and Related Services
Employees: 28,560
Subsidiaries: 13
12-month incidents
1
Known data breaches
3
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/hitachi.jpeg
Hitachi
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/ingram-micro.jpeg
Ingram Micro
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Hitachi
100%
Compliance Rate
0/4 Standards Verified
Ingram Micro
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs IT Services and IT Consulting Industry Average (This Year)

No incidents recorded for Hitachi in 2026.

Incidents vs IT Services and IT Consulting Industry Average (This Year)

Ingram Micro has 40.12% fewer incidents than the average of same-industry companies with at least one recorded incident.

Incident History — Hitachi (X = Date, Y = Severity)

Hitachi 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

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/hitachi.jpeg
Hitachi
Incidents

Date Detected: 8/2025
Type:Ransomware
Attack Vector: Stolen credentials, Vulnerability exploitation, Phishing
Motivation: Financial gain
Blog: Blog

Date Detected: 7/2025
Type:Vulnerability
Attack Vector: Radio Frequency (RF) communications
Motivation: Disruption of operations, brake system failures
Blog: Blog

Date Detected: 4/2025
Type:Ransomware
Motivation: Financial Gain
Blog: Blog
https://images.rankiteo.com/companyimages/ingram-micro.jpeg
Ingram Micro
Incidents

Date Detected: 1/2026
Type:Breach
Blog: Blog

Date Detected: 7/2025
Type:Ransomware
Blog: Blog

Date Detected: 7/2025
Type:Ransomware
Motivation: financial extortion (presumed)
Blog: Blog

FAQ

Hitachi company demonstrates a stronger AI Cybersecurity Score compared to Ingram Micro company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Ingram Micro company has faced a higher number of disclosed cyber incidents historically compared to Hitachi company.

In the current year, Ingram Micro company has reported more cyber incidents than Hitachi company.

Both Ingram Micro company and Hitachi company have confirmed experiencing at least one ransomware attack.

Ingram Micro company has disclosed at least one data breach, while Hitachi company has not reported such incidents publicly.

Neither Ingram Micro company nor Hitachi company has reported experiencing targeted cyberattacks publicly.

Both Hitachi company and Ingram Micro company have disclosed vulnerabilities.

Neither Hitachi nor Ingram Micro holds any compliance certifications.

Neither company holds any compliance certifications.

Hitachi company has more subsidiaries worldwide compared to Ingram Micro company.

Hitachi company employs more people globally than Ingram Micro company, reflecting its scale as a IT Services and IT Consulting.

Neither Hitachi nor Ingram Micro holds SOC 2 Type 1 certification.

Neither Hitachi nor Ingram Micro holds SOC 2 Type 2 certification.

Neither Hitachi nor Ingram Micro holds ISO 27001 certification.

Neither Hitachi nor Ingram Micro holds PCI DSS certification.

Neither Hitachi nor Ingram Micro holds HIPAA certification.

Neither Hitachi nor Ingram Micro holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

A flaw has been found in wandb OpenUI up to 1.0. This affects the function create_share/get_share of the file backend/openui/server.py of the component HTMLAnnotator Component. Executing a manipulation of the argument ID can lead to HTML injection. The attack may be performed from remote. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

A vulnerability was detected in QDOCS Smart School Management System up to 7.2. The impacted element is an unknown function of the file /admin/enquiry of the component Admission Enquiry Module. Performing a manipulation of the argument Note results in cross site scripting. The attack is possible to be carried out remotely.

Risk Information
cvss2
Base: 4.0
Severity: LOW
AV:N/AC:L/Au:S/C:N/I:P/A:N
cvss3
Base: 3.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.1
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

The Ultimate Member plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.11.2. This is due to the '{usermeta:password_reset_link}' template tag being processed within post content via the '[um_loggedin]' shortcode, which generates a valid password reset token for the currently logged-in user viewing the page. This makes it possible for authenticated attackers, with Contributor-level access and above, to craft a malicious pending post that, when previewed by an Administrator, generates a password reset token for the Administrator and exfiltrates it to an attacker-controlled server, leading to full account takeover.

Risk Information
cvss3
Base: 8.0
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Description

LibJWT is a C JSON Web Token Library. Starting in version 3.0.0 and prior to version 3.3.0, the JWK parsing for RSA-PSS did not protect against a NULL value when expecting to parse JSON string values. A specially crafted JWK file could exploit this behavior by using integers in places where the code expected a string. This was fixed in v3.3.0. A workaround is available. Users importing keys through a JWK file should not do so from untrusted sources. Use the `jwk2key` tool to check for validity of a JWK file. Likewise, if possible, do not use JWK files with RSA-PSS keys.

Risk Information
cvss4
Base: 5.8
Severity: HIGH
CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:A/VC:L/VI:L/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Description

Locutus brings stdlibs of other programming languages to JavaScript for educational purposes. Starting in version 2.0.39 and prior to version 3.0.25, a prototype pollution vulnerability exists in the `parse_str` function of the npm package locutus. An attacker can pollute `Object.prototype` by overriding `RegExp.prototype.test` and then passing a crafted query string to `parse_str`, bypassing the prototype pollution guard. This vulnerability stems from an incomplete fix for CVE-2026-25521. The CVE-2026-25521 patch replaced the `String.prototype.includes()`-based guard with a `RegExp.prototype.test()`-based guard. However, `RegExp.prototype.test` is itself a writable prototype method that can be overridden, making the new guard bypassable in the same way as the original — trading one hijackable built-in for another. Version 3.0.25 contains an updated fix.

Risk Information
cvss4
Base: 6.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X