Comparison Overview

Lee Kum Kee (China) Trading Limited

VS

Cargill

Lee Kum Kee (China) Trading Limited

徐汇区南宁路970号李锦记大厦22F、23F、25F, 上海市, CN
Last Update: 2025-11-27
Between 750 and 799

Established in 1888 , Lee Kum Kee is an international household name in authentic Asian sauces and condiments , as well as "a symbol of quality and trust". As a globally renowned Chinese multinational corporation , Lee Kum Kee now offers over 200 types of sauce and condiment to over 100 countries and regions.

NAICS: 311
NAICS Definition: Food Manufacturing
Employees: 10,557
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Cargill

15407 McGinty Rd W, Wayzata, Minnesota, 55391, US
Last Update: 2025-11-25
Between 800 and 849

Cargill is a family company committed to nourishing the world in a safe, responsible and sustainable way. With over 158 years of experience, we sit at the heart of the supply chain, partnering with producers and customers to source, make and deliver products that are vital for living. Whether it’s making alternative proteins for food manufacturers or helping farmers raise healthier animals with AI, we put as much care into how things are sourced as what we provide. We put people first. We do the right thing—today and for generations to come.

NAICS: 311
NAICS Definition: Food Manufacturing
Employees: 69,828
Subsidiaries: 10
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/李锦记(中国)销售有限公司.jpeg
Lee Kum Kee (China) Trading Limited
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/cargill.jpeg
Cargill
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
Lee Kum Kee (China) Trading Limited
100%
Compliance Rate
0/4 Standards Verified
Cargill
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Food and Beverage Manufacturing Industry Average (This Year)

No incidents recorded for Lee Kum Kee (China) Trading Limited in 2025.

Incidents vs Food and Beverage Manufacturing Industry Average (This Year)

No incidents recorded for Cargill in 2025.

Incident History — Lee Kum Kee (China) Trading Limited (X = Date, Y = Severity)

Lee Kum Kee (China) Trading Limited cyber incidents detection timeline including parent company and subsidiaries

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

Cargill cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/李锦记(中国)销售有限公司.jpeg
Lee Kum Kee (China) Trading Limited
Incidents

No Incident

https://images.rankiteo.com/companyimages/cargill.jpeg
Cargill
Incidents

No Incident

FAQ

Cargill company demonstrates a stronger AI Cybersecurity Score compared to Lee Kum Kee (China) Trading Limited company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Cargill company has disclosed a higher number of cyber incidents compared to Lee Kum Kee (China) Trading Limited company.

In the current year, Cargill company and Lee Kum Kee (China) Trading Limited company have not reported any cyber incidents.

Neither Cargill company nor Lee Kum Kee (China) Trading Limited company has reported experiencing a ransomware attack publicly.

Neither Cargill company nor Lee Kum Kee (China) Trading Limited company has reported experiencing a data breach publicly.

Neither Cargill company nor Lee Kum Kee (China) Trading Limited company has reported experiencing targeted cyberattacks publicly.

Neither Lee Kum Kee (China) Trading Limited company nor Cargill company has reported experiencing or disclosing vulnerabilities publicly.

Neither Lee Kum Kee (China) Trading Limited nor Cargill holds any compliance certifications.

Neither company holds any compliance certifications.

Cargill company has more subsidiaries worldwide compared to Lee Kum Kee (China) Trading Limited company.

Cargill company employs more people globally than Lee Kum Kee (China) Trading Limited company, reflecting its scale as a Food and Beverage Manufacturing.

Neither Lee Kum Kee (China) Trading Limited nor Cargill holds SOC 2 Type 1 certification.

Neither Lee Kum Kee (China) Trading Limited nor Cargill holds SOC 2 Type 2 certification.

Neither Lee Kum Kee (China) Trading Limited nor Cargill holds ISO 27001 certification.

Neither Lee Kum Kee (China) Trading Limited nor Cargill holds PCI DSS certification.

Neither Lee Kum Kee (China) Trading Limited nor Cargill holds HIPAA certification.

Neither Lee Kum Kee (China) Trading Limited nor Cargill 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