Comparison Overview

Acosta

VS

Walmart Canada

Acosta

6600 Corporate Center Parkway, Jacksonville, FL, 32216, US
Last Update: 2025-11-21
Between 750 and 799

Acosta brings simplicity to retail sales. We act as a catalyst to boldly connect brands, retailers and consumers, fueling growth and building long-term value throughout North America and Europe. We are deeply embedded in every corner of the retail industry, strengthening the local, regional and national relationships between brands and retailers.​ Our team of experts uses deep industry insight, cutting-edge analytics and integrated partnerships to help our clients move ahead with confidence.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 12,991
Subsidiaries: 26
12-month incidents
0
Known data breaches
1
Attack type number
1

Walmart Canada

1940 Argentia Rd, Mississauga, ON, CA, L5N 1P9
Last Update: 2025-11-27
Between 800 and 849

Walmart Canada operates a chain of more than 400 stores nationwide serving 1.5 million customers each day. Walmart Canada's flagship online store, Walmart.ca is visited by more than 1.5 million customers daily. With more than 100,000 associates, Walmart Canada is one of Canada's largest employers and is ranked one of the country's top 10 most influential brands. Walmart Canada's extensive philanthropy program is focused on supporting Canadian families in need, and since 1994 Walmart Canada has raised and donated more than $750 million to Canadian charities. Additional information can be found at walmartcanada.ca and on Walmart Canada’s social media pages – Facebook, X, Instagram and LinkedIn.

NAICS: 43
NAICS Definition: Retail Trade
Employees: 18,946
Subsidiaries: 26
12-month incidents
0
Known data breaches
7
Attack type number
2

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/acosta.jpeg
Acosta
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/wal-mart-canada.jpeg
Walmart Canada
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
Acosta
100%
Compliance Rate
0/4 Standards Verified
Walmart Canada
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Acosta in 2025.

Incidents vs Retail Industry Average (This Year)

No incidents recorded for Walmart Canada in 2025.

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

Acosta cyber incidents detection timeline including parent company and subsidiaries

Incident History — Walmart Canada (X = Date, Y = Severity)

Walmart Canada cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/acosta.jpeg
Acosta
Incidents

Date Detected: 3/2024
Type:Breach
Attack Vector: Inadvertent Disclosure
Blog: Blog
https://images.rankiteo.com/companyimages/wal-mart-canada.jpeg
Walmart Canada
Incidents

Date Detected: 4/2025
Type:Ransomware
Attack Vector: Zero-day vulnerabilities in MOVEit and Cleo file transfer software
Motivation: Data extortion
Blog: Blog

Date Detected: 1/2024
Type:Breach
Attack Vector: Hacking
Blog: Blog

Date Detected: 12/2023
Type:Breach
Attack Vector: External System Breach (Hacking)
Blog: Blog

FAQ

Walmart Canada company demonstrates a stronger AI Cybersecurity Score compared to Acosta company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Walmart Canada company has faced a higher number of disclosed cyber incidents historically compared to Acosta company.

In the current year, Walmart Canada company has reported more cyber incidents than Acosta company.

Walmart Canada company has confirmed experiencing a ransomware attack, while Acosta company has not reported such incidents publicly.

Both Walmart Canada company and Acosta company have disclosed experiencing at least one data breach.

Neither Walmart Canada company nor Acosta company has reported experiencing targeted cyberattacks publicly.

Neither Acosta company nor Walmart Canada company has reported experiencing or disclosing vulnerabilities publicly.

Neither Acosta nor Walmart Canada holds any compliance certifications.

Neither company holds any compliance certifications.

Both Walmart Canada company and Acosta company have a similar number of subsidiaries worldwide.

Walmart Canada company employs more people globally than Acosta company, reflecting its scale as a Retail.

Neither Acosta nor Walmart Canada holds SOC 2 Type 1 certification.

Neither Acosta nor Walmart Canada holds SOC 2 Type 2 certification.

Neither Acosta nor Walmart Canada holds ISO 27001 certification.

Neither Acosta nor Walmart Canada holds PCI DSS certification.

Neither Acosta nor Walmart Canada holds HIPAA certification.

Neither Acosta nor Walmart Canada 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