Comparison Overview

Ferguson

VS

METRO/MAKRO

Ferguson

751 Lakefront Commons, Newport News, Virginia, 23606, US
Last Update: 2025-11-26
Between 750 and 799

Since 1953, Ferguson has been a leading source of quality supplies for a variety of industries. We are proud to provide world-class products and services to a customer base that is as vast and varied as our inventory. The professionals we serve help transform the world we live in, and we are their trusted partners with the scale, expertise and solutions to provide peace of mind. Ferguson is part of Ferguson Enterprises Inc., which has approximately 36,000 associates across 1,700 locations and serves customers in all 50 states, Canada, Puerto Rico, Mexico and the Caribbean. We are Ferguson, and Together We Build Better.

NAICS: 42
NAICS Definition: Wholesale Trade
Employees: 19,826
Subsidiaries: 11
12-month incidents
0
Known data breaches
1
Attack type number
1

METRO/MAKRO

Metro-Str. 1, Duesseldorf, undefined, 40235, DE
Last Update: 2025-11-26
Between 750 and 799

METRO is a leading international wholesale company with food and non-food assortments that specialises in serving the needs of hotels, restaurants and caterers (HoReCa) as well as independent traders. Around the world, METRO has 15 million customers who can choose whether to shop in one of the large-format stores, order online and collect their purchases at the store or have them delivered. METRO also supports the competitiveness of entrepreneurs and independent businesses with digital solutions and thereby contributes to cultural diversity in trade and the hospitality industry. The company operates in more than 30 countries and employs more than 85,000 people worldwide. In financial year 2022/23, METRO generated a group revenue of €31 billion. More information: https://careers.metroag.de Imprint: https://careers.metroag.de/imprint Data Privacy: https://careers.metroag.de/privacy-policy

NAICS: 424
NAICS Definition:
Employees: 26,312
Subsidiaries: 22
12-month incidents
0
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/ferguson-enterprises.jpeg
Ferguson
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/metro-makro.jpeg
METRO/MAKRO
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
Ferguson
100%
Compliance Rate
0/4 Standards Verified
METRO/MAKRO
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Wholesale Industry Average (This Year)

No incidents recorded for Ferguson in 2025.

Incidents vs Wholesale Industry Average (This Year)

No incidents recorded for METRO/MAKRO in 2025.

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

Ferguson cyber incidents detection timeline including parent company and subsidiaries

Incident History — METRO/MAKRO (X = Date, Y = Severity)

METRO/MAKRO cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ferguson-enterprises.jpeg
Ferguson
Incidents

Date Detected: 4/2017
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog
https://images.rankiteo.com/companyimages/metro-makro.jpeg
METRO/MAKRO
Incidents

Date Detected: 10/2022
Type:Cyber Attack
Blog: Blog

FAQ

METRO/MAKRO company demonstrates a stronger AI Cybersecurity Score compared to Ferguson company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Ferguson and METRO/MAKRO have experienced a similar number of publicly disclosed cyber incidents.

In the current year, METRO/MAKRO company and Ferguson company have not reported any cyber incidents.

Neither METRO/MAKRO company nor Ferguson company has reported experiencing a ransomware attack publicly.

Ferguson company has disclosed at least one data breach, while the other METRO/MAKRO company has not reported such incidents publicly.

METRO/MAKRO company has reported targeted cyberattacks, while Ferguson company has not reported such incidents publicly.

Neither Ferguson company nor METRO/MAKRO company has reported experiencing or disclosing vulnerabilities publicly.

Neither Ferguson nor METRO/MAKRO holds any compliance certifications.

Neither company holds any compliance certifications.

METRO/MAKRO company has more subsidiaries worldwide compared to Ferguson company.

METRO/MAKRO company employs more people globally than Ferguson company, reflecting its scale as a Wholesale.

Neither Ferguson nor METRO/MAKRO holds SOC 2 Type 1 certification.

Neither Ferguson nor METRO/MAKRO holds SOC 2 Type 2 certification.

Neither Ferguson nor METRO/MAKRO holds ISO 27001 certification.

Neither Ferguson nor METRO/MAKRO holds PCI DSS certification.

Neither Ferguson nor METRO/MAKRO holds HIPAA certification.

Neither Ferguson nor METRO/MAKRO 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