Comparison Overview

H&M

VS

Coles Group

H&M

Vasagatan 7, Stockholm, Stockholm County, SE, 111 20
Last Update: 2025-11-20
Between 800 and 849

At H&M, we welcome you to be yourself and feel like you truly belong. Help us reimagine the future of an entire industry by making everyone look, feel, and do good. We take pride in our history of making fashion accessible to everyone and led by our values we strive to build a more welcoming, inclusive, and sustainable industry. We are privileged to have more than 120,000 colleagues, in over 75 countries across the world. That’s 120 000 individuals with unique experiences, skills, and passions. At H&M, we believe everyone can make an impact, we believe in giving people responsibility and a strong sense of ownership. Our business is your business, and when you grow, we grow.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 67,647
Subsidiaries: 11
12-month incidents
0
Known data breaches
0
Attack type number
0

Coles Group

800-838 Toorak Rd, Melbourne, VIC, 3123, AU
Last Update: 2025-11-21
Between 750 and 799

Coles Group is home to some of Australia’s iconic and most trusted brands and is one of the biggest employers with more than 1115,000 team members in every state and territory. Our workforce is diverse including groceries and liquor retail operations, online, manufacturing, cleaning and trolley services, drivers, supply chain, and commercial and corporate services. Our vision is to become the most trusted retailer in Australia and grow long-term shareholder value. Our purpose is Helping Australians eat and live better every day. Our priority is to provide leading food, drink, and home solutions that are delicious, sustainable, and healthy for our customers every day, both in-store and online. At Coles Group you’ll belong to an inclusive culture that’s as diverse as the communities we’re a trusted part of. You’ll also get to see the impacts of your work in those communities. We’re a team that grows together, and we always make sure we’re doing the best for Australians – now and into the future. Your ideas, your enthusiasm, and your passion – we’re looking for people like you to join the team, sustainably feed Australians, and help them eat and live better every day.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 11,767
Subsidiaries: 5
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/h&m.jpeg
H&M
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/coles.jpeg
Coles Group
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
H&M
100%
Compliance Rate
0/4 Standards Verified
Coles Group
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Industry Average (This Year)

No incidents recorded for H&M in 2025.

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Coles Group in 2025.

Incident History — H&M (X = Date, Y = Severity)

H&M cyber incidents detection timeline including parent company and subsidiaries

Incident History — Coles Group (X = Date, Y = Severity)

Coles Group cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/h&m.jpeg
H&M
Incidents

No Incident

https://images.rankiteo.com/companyimages/coles.jpeg
Coles Group
Incidents

No Incident

FAQ

H&M company demonstrates a stronger AI Cybersecurity Score compared to Coles Group company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Coles Group company has disclosed a higher number of cyber incidents compared to H&M company.

In the current year, Coles Group company and H&M company have not reported any cyber incidents.

Neither Coles Group company nor H&M company has reported experiencing a ransomware attack publicly.

Neither Coles Group company nor H&M company has reported experiencing a data breach publicly.

Neither Coles Group company nor H&M company has reported experiencing targeted cyberattacks publicly.

Neither H&M company nor Coles Group company has reported experiencing or disclosing vulnerabilities publicly.

Neither H&M nor Coles Group holds any compliance certifications.

Neither company holds any compliance certifications.

H&M company has more subsidiaries worldwide compared to Coles Group company.

H&M company employs more people globally than Coles Group company, reflecting its scale as a Retail.

Neither H&M nor Coles Group holds SOC 2 Type 1 certification.

Neither H&M nor Coles Group holds SOC 2 Type 2 certification.

Neither H&M nor Coles Group holds ISO 27001 certification.

Neither H&M nor Coles Group holds PCI DSS certification.

Neither H&M nor Coles Group holds HIPAA certification.

Neither H&M nor Coles Group 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