Comparison Overview

EHR.Network

VS

Ingram Micro

EHR.Network

No.39, 2nd Floor, NGEF Lane, Bangalore, 560038, IN
Last Update: 2026-01-23
Between 700 and 749

EHR.Network is a data-first platform powered by openEHR for various stakeholders of the healthcare ecosystem. EHR.Network unlocks data value by making it accessible and inter-operable for companies and individuals to generate insights, securely within and across organizations. Value creation is linked to data access and use. Value is generated by the insights resulting from asking better questions of data - whether it belongs to companies themselves or to others with whom they can partner. We are an open standards based Healthcare Information Platform. It is aligned to EHR standards and is designed to accept data from any source, normalize them and present them as an integrated, comprehensive EHR data of a person. This person centric EHR data is intended to be freely shareable with any person authorized to view it. The platform provides open APIs and SDKs to enable third parties to develop healthcare related applications that leverage the EHR data on the platform to provide enhanced services.

NAICS: 5415
NAICS Definition: Computer Systems Design and Related Services
Employees: 9
Subsidiaries: 0
12-month incidents
0
Known data breaches
1
Attack type number
1

Ingram Micro

3351 Michelson Drive, Suite 100, Irvine, CA, US, 92612
Last Update: 2026-01-22

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
2
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ehrnetwork.jpeg
EHR.Network
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
EHR.Network
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 EHR.Network in 2026.

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

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

Incident History — EHR.Network (X = Date, Y = Severity)

EHR.Network 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/ehrnetwork.jpeg
EHR.Network
Incidents

Date Detected: 1/2024
Type:Breach
Attack Vector: Third-Party Vendor Compromise
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
Motivation: financial extortion (presumed)
Blog: Blog

Date Detected: 3/2025
Type:Vulnerability
Attack Vector: Unauthorized Cloud Storage, Phishing, Ransomware, DDoS, Malicious Git Repositories
Motivation: Political, Financial Gain, Espionage, Hacktivism
Blog: Blog

FAQ

EHR.Network 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 EHR.Network company.

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

Ingram Micro company has confirmed experiencing a ransomware attack, while EHR.Network company has not reported such incidents publicly.

Both Ingram Micro company and EHR.Network company have disclosed experiencing at least one data breach.

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

Ingram Micro company has disclosed at least one vulnerability, while EHR.Network company has not reported such incidents publicly.

Neither EHR.Network nor Ingram Micro holds any compliance certifications.

Neither company holds any compliance certifications.

Ingram Micro company has more subsidiaries worldwide compared to EHR.Network company.

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

Neither EHR.Network nor Ingram Micro holds SOC 2 Type 1 certification.

Neither EHR.Network nor Ingram Micro holds SOC 2 Type 2 certification.

Neither EHR.Network nor Ingram Micro holds ISO 27001 certification.

Neither EHR.Network nor Ingram Micro holds PCI DSS certification.

Neither EHR.Network nor Ingram Micro holds HIPAA certification.

Neither EHR.Network nor Ingram Micro holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Improper validation of specified type of input in M365 Copilot allows an unauthorized attacker to disclose information over a network.

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

Improper access control in Azure Front Door (AFD) allows an unauthorized attacker to elevate privileges over a network.

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

Azure Entra ID Elevation of Privilege Vulnerability

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

Moonraker is a Python web server providing API access to Klipper 3D printing firmware. In versions 0.9.3 and below, instances configured with the "ldap" component enabled are vulnerable to LDAP search filter injection techniques via the login endpoint. The 401 error response message can be used to determine whether or not a search was successful, allowing for brute force methods to discover LDAP entries on the server such as user IDs and user attributes. This issue has been fixed in version 0.10.0.

Risk Information
cvss4
Base: 2.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U/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

Runtipi is a Docker-based, personal homeserver orchestrator that facilitates multiple services on a single server. Versions 3.7.0 and above allow an authenticated user to execute arbitrary system commands on the host server by injecting shell metacharacters into backup filenames. The BackupManager fails to sanitize the filenames of uploaded backups. The system persists user-uploaded files directly to the host filesystem using the raw originalname provided in the request. This allows an attacker to stage a file containing shell metacharacters (e.g., $(id).tar.gz) at a predictable path, which is later referenced during the restore process. The successful storage of the file is what allows the subsequent restore command to reference and execute it. This issue has been fixed in version 4.7.0.

Risk Information
cvss3
Base: 8.0
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H