Comparison Overview

Kuala Lumpur Kepong Berhad

VS

Yara International

Kuala Lumpur Kepong Berhad

Wisma Taiko No. 1 Jalan S.P. Seenivasagam Ipoh, Perak Darul Ridzuan 30000, MY
Last Update: 2025-11-26
Between 750 and 799

Kuala Lumpur Kepong Berhad (”KLK”) started as a plantation company in 1906 and until today, the development of oil palm and rubber remains the Group’s core business. KLK presently has about 300,000 hectares of planted area (97% oil palm). Our land bank is spread across Malaysia (Peninsular and Sabah), Indonesia (Belitung Island, Sumatra, as well as Kalimantan), and Liberia. In order to optimise value across the supply chain, KLK diversified into resource-based manufacturing (refinery and oleochemical), and vertically integrated its upstream, midstream and downstream businesses. The Group has since expanded its manufacturing operations resulting in an international oleochemicals operations in Malaysia, Indonesia, China, Switzerland, Germany, the Netherlands, Belgium and Italy. In 1990, KLK started capitalising on the strategic location of its land bank in Peninsular Malaysia by branching into property development under KLK Land. Our first foray into property development was Sierramas in Sungai Buloh, a joint venture with Tan & Tan Developments Berhad, a wholly owned subsidiary of IGB Berhad. It is currently focused on Bandar Seri Coalfields, a 1,001-acre township in Sungai Buloh and Caledonia in Ijok, Selangor.

NAICS: 111
NAICS Definition: Crop Production
Employees: 10,001
Subsidiaries: 3
12-month incidents
0
Known data breaches
0
Attack type number
0

Yara International

Drammensveien 131, Oslo, undefined, N-0277, NO
Last Update: 2025-11-26
Between 750 and 799

Yara's mission is to responsibly feed the world and protect the planet. We pursue a strategy of sustainable value growth through reducing emissions from crop nutrition production and developing low-emission energy solutions. Yara’s ambition is focused on Growing a Nature-Positive Food Future that creates value for our customers, shareholders and society at large and delivers a more sustainable food value chain. To drive the green shift in fertilizer production, shipping, and other energy intensive industries, Yara will produce ammonia with significantly lower emissions. We provide digital tools for precision farming and work closely with partners at all levels of the food value chain to share knowledge and promote more efficient and sustainable solutions. Founded in 1905 to solve the emerging famine in Europe, Yara has established a unique position as the industry’s only global crop nutrition company. With 18,000 employees and operations in more than 60 countries, sustainability is an integral part of our business model. In 2023, Yara reported revenues of USD 15.5 billion.

NAICS: 111
NAICS Definition: Crop Production
Employees: 14,651
Subsidiaries: 9
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/klkberhad.jpeg
Kuala Lumpur Kepong Berhad
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/yara.jpeg
Yara International
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
Kuala Lumpur Kepong Berhad
100%
Compliance Rate
0/4 Standards Verified
Yara International
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Farming Industry Average (This Year)

No incidents recorded for Kuala Lumpur Kepong Berhad in 2025.

Incidents vs Farming Industry Average (This Year)

No incidents recorded for Yara International in 2025.

Incident History — Kuala Lumpur Kepong Berhad (X = Date, Y = Severity)

Kuala Lumpur Kepong Berhad cyber incidents detection timeline including parent company and subsidiaries

Incident History — Yara International (X = Date, Y = Severity)

Yara International cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/klkberhad.jpeg
Kuala Lumpur Kepong Berhad
Incidents

No Incident

https://images.rankiteo.com/companyimages/yara.jpeg
Yara International
Incidents

No Incident

FAQ

Yara International company demonstrates a stronger AI Cybersecurity Score compared to Kuala Lumpur Kepong Berhad company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Yara International company has disclosed a higher number of cyber incidents compared to Kuala Lumpur Kepong Berhad company.

In the current year, Yara International company and Kuala Lumpur Kepong Berhad company have not reported any cyber incidents.

Neither Yara International company nor Kuala Lumpur Kepong Berhad company has reported experiencing a ransomware attack publicly.

Neither Yara International company nor Kuala Lumpur Kepong Berhad company has reported experiencing a data breach publicly.

Neither Yara International company nor Kuala Lumpur Kepong Berhad company has reported experiencing targeted cyberattacks publicly.

Neither Kuala Lumpur Kepong Berhad company nor Yara International company has reported experiencing or disclosing vulnerabilities publicly.

Neither Kuala Lumpur Kepong Berhad nor Yara International holds any compliance certifications.

Neither company holds any compliance certifications.

Yara International company has more subsidiaries worldwide compared to Kuala Lumpur Kepong Berhad company.

Yara International company employs more people globally than Kuala Lumpur Kepong Berhad company, reflecting its scale as a Farming.

Neither Kuala Lumpur Kepong Berhad nor Yara International holds SOC 2 Type 1 certification.

Neither Kuala Lumpur Kepong Berhad nor Yara International holds SOC 2 Type 2 certification.

Neither Kuala Lumpur Kepong Berhad nor Yara International holds ISO 27001 certification.

Neither Kuala Lumpur Kepong Berhad nor Yara International holds PCI DSS certification.

Neither Kuala Lumpur Kepong Berhad nor Yara International holds HIPAA certification.

Neither Kuala Lumpur Kepong Berhad nor Yara International holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

ThingsBoard in versions prior to v4.2.1 allows an authenticated user to upload malicious SVG images via the "Image Gallery", leading to a Stored Cross-Site Scripting (XSS) vulnerability. The exploit can be triggered when any user accesses the public API endpoint of the malicious SVG images, or if the malicious images are embedded in an `iframe` element, during a widget creation, deployed to any page of the platform (e.g., dashboards), and accessed during normal operations. The vulnerability resides in the `ImageController`, which fails to restrict the execution of JavaScript code when an image is loaded by the user's browser. This vulnerability can lead to the execution of malicious code in the context of other users' sessions, potentially compromising their accounts and allowing unauthorized actions.

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that the token used during the code exchange originates from the same authentication flow, which allows an authenticated user to perform account takeover via a specially crafted email address used when switching authentication methods and sending a request to the /users/login/sso/code-exchange endpoint. The vulnerability requires ExperimentalEnableAuthenticationTransfer to be enabled (default: enabled) and RequireEmailVerification to be disabled (default: disabled).

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

Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to sanitize team email addresses to be visible only to Team Admins, which allows any authenticated user to view team email addresses via the GET /api/v4/channels/{channel_id}/common_teams endpoint

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

Exposure of email service credentials to users without administrative rights in Devolutions Server.This issue affects Devolutions Server: before 2025.2.21, before 2025.3.9.

Description

Exposure of credentials in unintended requests in Devolutions Server.This issue affects Server: through 2025.2.20, through 2025.3.8.