Comparison Overview

Asahi Kasei

VS

BASF

Asahi Kasei

1-1-2 Yurakucho, Chiyoda-ku, Tokyo, Tokyo, JP, 100-0006
Last Update: 2025-12-09
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

BASF

Carl-Bosch-Str. 38, Ludwigshafen, undefined, 67056, DE
Last Update: 2025-12-09
Between 800 and 849

At BASF, we create chemistry for a sustainable future. Our ambition: We want to be the preferred chemical company to enable our customers’ green transformation. We combine economic success with environmental protection and social responsibility. Around 112,000 employees in the BASF Group contribute to the success of our customers in nearly all sectors and almost every country in the world. Our portfolio comprises, as core businesses, the segments Chemicals, Materials, Industrial Solutions, and Nutrition & Care; our standalone businesses are bundled in the segments Surface Technologies and Agricultural Solutions. BASF generated sales of €65.3 billion in 2024. BASF shares are traded on the stock exchange in Frankfurt (BAS) and as American Depositary Receipts (BASFY) in the United States. Credits: https://www.basf.com/global/en/legal/credits Data protection information: https://www.basf.com/global/en/legal/data-protection-at-basf.html

NAICS: 325
NAICS Definition: Chemical Manufacturing
Employees: 66,966
Subsidiaries: 43
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/basf.jpeg
BASF
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
BASF
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 BASF in 2025.

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

Asahi Kasei cyber incidents detection timeline including parent company and subsidiaries

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

BASF 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/basf.jpeg
BASF
Incidents

No Incident

FAQ

BASF 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 BASF company has not reported any.

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

Neither BASF 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 BASF company has not reported such incidents publicly.

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

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

Neither Asahi Kasei nor BASF holds any compliance certifications.

Neither company holds any compliance certifications.

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

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

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

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

Neither Asahi Kasei nor BASF holds ISO 27001 certification.

Neither Asahi Kasei nor BASF holds PCI DSS certification.

Neither Asahi Kasei nor BASF holds HIPAA certification.

Neither Asahi Kasei nor BASF holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N