Comparison Overview

IMA Cooling Systems

VS

MAYEKAWA USA INC

IMA Cooling Systems

156 st.Albans Road , St.Albans , Hertfordshire, GB, AL4 9LP
Last Update: 2025-11-27
Between 750 and 799

IMA Cooling Systems was founded in 1989 and specialises in the design and build of cold rooms and refrigerated pack houses. IMA installations can range in size from small restaurant cold rooms of 4 sqm to hyper stores of 20,000 sqm. IMA has particular expertise's in harvested product cooling and offers a range of High Humidity Cooling (HHC) to remove field heat. IMA has installed all over the world with major installation outside the UK, in Kenya, The Gambia, Jordan and Barbados.

NAICS: None
NAICS Definition: Others
Employees: 13
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

MAYEKAWA USA INC

29875 Medline Ln, Katy, TX, 77494, US
Last Update: 2025-11-27

With over 90 years of worldwide experience, Mayekawa is an industry leader in industrial refrigeration equipment. Mayekawa/MYCOM designs refrigeration packages specific to the needs of process cooling and cold storage end users. The MYCOM compressor is the core of our business, available in dual rotary screw and reciprocating designs. Through our commitment to enhance environmentally friendly refrigerant adoption, Mayekawa products use technology to harness the power of the Natural Five (ammonia, carbon dioxide, water, air and hydrocarbons) to help reduce the industry's global warming contributions. To learn more about Mayekawa/MYCOM equipment, visit www.mayekawausa.com.

NAICS: None
NAICS Definition: Others
Employees: 155
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ima-cooling-systems.jpeg
IMA Cooling Systems
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/mayekawa-usa.jpeg
MAYEKAWA USA INC
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
IMA Cooling Systems
100%
Compliance Rate
0/4 Standards Verified
MAYEKAWA USA INC
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mechanical Or Industrial Engineering Industry Average (This Year)

No incidents recorded for IMA Cooling Systems in 2025.

Incidents vs Mechanical Or Industrial Engineering Industry Average (This Year)

No incidents recorded for MAYEKAWA USA INC in 2025.

Incident History — IMA Cooling Systems (X = Date, Y = Severity)

IMA Cooling Systems cyber incidents detection timeline including parent company and subsidiaries

Incident History — MAYEKAWA USA INC (X = Date, Y = Severity)

MAYEKAWA USA INC cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ima-cooling-systems.jpeg
IMA Cooling Systems
Incidents

No Incident

https://images.rankiteo.com/companyimages/mayekawa-usa.jpeg
MAYEKAWA USA INC
Incidents

No Incident

FAQ

Both IMA Cooling Systems company and MAYEKAWA USA INC company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, MAYEKAWA USA INC company has disclosed a higher number of cyber incidents compared to IMA Cooling Systems company.

In the current year, MAYEKAWA USA INC company and IMA Cooling Systems company have not reported any cyber incidents.

Neither MAYEKAWA USA INC company nor IMA Cooling Systems company has reported experiencing a ransomware attack publicly.

Neither MAYEKAWA USA INC company nor IMA Cooling Systems company has reported experiencing a data breach publicly.

Neither MAYEKAWA USA INC company nor IMA Cooling Systems company has reported experiencing targeted cyberattacks publicly.

Neither IMA Cooling Systems company nor MAYEKAWA USA INC company has reported experiencing or disclosing vulnerabilities publicly.

Neither IMA Cooling Systems nor MAYEKAWA USA INC holds any compliance certifications.

Neither company holds any compliance certifications.

Neither IMA Cooling Systems company nor MAYEKAWA USA INC company has publicly disclosed detailed information about the number of their subsidiaries.

MAYEKAWA USA INC company employs more people globally than IMA Cooling Systems company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither IMA Cooling Systems nor MAYEKAWA USA INC holds SOC 2 Type 1 certification.

Neither IMA Cooling Systems nor MAYEKAWA USA INC holds SOC 2 Type 2 certification.

Neither IMA Cooling Systems nor MAYEKAWA USA INC holds ISO 27001 certification.

Neither IMA Cooling Systems nor MAYEKAWA USA INC holds PCI DSS certification.

Neither IMA Cooling Systems nor MAYEKAWA USA INC holds HIPAA certification.

Neither IMA Cooling Systems nor MAYEKAWA USA INC holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.

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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

Risk Information
cvss4
Base: 8.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Integer Overflow vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft ASN.1 structures containing OIDs with oversized arcs. These arcs may be decoded as smaller, trusted OIDs due to 32-bit bitwise truncation, enabling the bypass of downstream OID-based security decisions. This issue has been patched in version 1.3.2.

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: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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. Prior to versions 7.0.13 and 8.0.2, working with large buffers in Lua scripts can lead to a stack overflow. Users of Lua rules and output scripts may be affected when working with large buffers. This includes a rule passing a large buffer to a Lua script. This issue has been patched in versions 7.0.13 and 8.0.2. A workaround for this issue involves disabling Lua rules and output scripts, or making sure limits, such as stream.depth.reassembly and HTTP response body limits (response-body-limit), are set to less than half the stack size.

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

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, a NULL dereference can occur when the entropy keyword is used in conjunction with base64_data. This issue has been patched in version 8.0.2. A workaround involves disabling rules that use entropy in conjunction with base64_data.

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