Comparison Overview

Asahi Kasei

VS

Givaudan

Asahi Kasei

1-1-2 Yurakucho, Chiyoda-ku, Tokyo, Tokyo, JP, 100-0006
Last Update: 2025-11-27
Between 750 and 799

The Asahi Kasei Group contributes to life and living for people around the world. Since its foundation in 1922 with ammonia and cellulose fiber business, Asahi Kasei has consistently grown through the proactive transformation of its business portfolio to meet the evolving needs of every age. With more than 48,000 employees around the world, the company contributes to sustainable society by providing solutions to the world’s challenges through its three business sectors of Material, Homes, and Health Care.

NAICS: 325
NAICS Definition: Chemical Manufacturing
Employees: 10,499
Subsidiaries: 28
12-month incidents
0
Known data breaches
4
Attack type number
2

Givaudan

Givaudan International SA, 5, Chemin de la Parfumerie, Vernier, Geneva, CH, 1214
Last Update: 2025-11-26
Between 800 and 849

Givaudan is a global leader in Fragrance & Beauty and Taste & Wellbeing. We celebrate the beauty of human experience by creating for happier, healthier lives with love for nature. Together with our customers we deliver food experiences, craft inspired fragrances, and develop beauty and wellbeing solutions that make people look and feel good. With over 163 locations in 52 countries and over 78 production sites, of which 31 are located in Europe, 22 in North America, 17 in Latin America, 8 in Asia-Pacific, and 1 across South Asia, the Middle East, and Africa, we are committed to driving purpose-led growth that makes a positive impact. Givaudan: Human by nature. www.givaudan.com

NAICS: 325
NAICS Definition: Chemical Manufacturing
Employees: 13,029
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/asahi-kasei.jpeg
Asahi Kasei
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/givaudan.jpeg
Givaudan
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
Asahi Kasei
100%
Compliance Rate
0/4 Standards Verified
Givaudan
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Chemical Manufacturing Industry Average (This Year)

No incidents recorded for Asahi Kasei in 2025.

Incidents vs Chemical Manufacturing Industry Average (This Year)

No incidents recorded for Givaudan in 2025.

Incident History — Asahi Kasei (X = Date, Y = Severity)

Asahi Kasei cyber incidents detection timeline including parent company and subsidiaries

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

Givaudan cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/asahi-kasei.jpeg
Asahi Kasei
Incidents

Date Detected: 11/2023
Type:Breach
Attack Vector: Phishing
Blog: Blog

Date Detected: 8/2023
Type:Breach
Attack Vector: Phishing
Blog: Blog

Date Detected: 1/2023
Type:Breach
Attack Vector: External System Hack
Blog: Blog
https://images.rankiteo.com/companyimages/givaudan.jpeg
Givaudan
Incidents

No Incident

FAQ

Givaudan company demonstrates a stronger AI Cybersecurity Score compared to Asahi Kasei company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Asahi Kasei company has historically faced a number of disclosed cyber incidents, whereas Givaudan company has not reported any.

In the current year, Givaudan company and Asahi Kasei company have not reported any cyber incidents.

Neither Givaudan company nor Asahi Kasei company has reported experiencing a ransomware attack publicly.

Asahi Kasei company has disclosed at least one data breach, while the other Givaudan company has not reported such incidents publicly.

Neither Givaudan company nor Asahi Kasei company has reported experiencing targeted cyberattacks publicly.

Neither Asahi Kasei company nor Givaudan company has reported experiencing or disclosing vulnerabilities publicly.

Neither Asahi Kasei nor Givaudan holds any compliance certifications.

Neither company holds any compliance certifications.

Asahi Kasei company has more subsidiaries worldwide compared to Givaudan company.

Givaudan company employs more people globally than Asahi Kasei company, reflecting its scale as a Chemical Manufacturing.

Neither Asahi Kasei nor Givaudan holds SOC 2 Type 1 certification.

Neither Asahi Kasei nor Givaudan holds SOC 2 Type 2 certification.

Neither Asahi Kasei nor Givaudan holds ISO 27001 certification.

Neither Asahi Kasei nor Givaudan holds PCI DSS certification.

Neither Asahi Kasei nor Givaudan holds HIPAA certification.

Neither Asahi Kasei nor Givaudan 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