Comparison Overview

Rourkela steel plant

VS

Nippon Steel Corporation

Rourkela steel plant

Last Update: 2025-12-09
Between 750 and 799

There is a little bit of steel in Everybody's life Show more Show less

NAICS: 333
NAICS Definition:
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Nippon Steel Corporation

2-6-1 Marunouchi, Chiyoda-ku, Tokyo 100-8071, Japan, None, Tokyo, 2-6-1 Marunouchi, Chiyoda-ku, Tokyo 100-8071, Japan, JP, 〒100-8071
Last Update: 2025-12-09
Between 750 and 799

<Nippon Steel Corporation does not recognize this account as OFFICIAL, but it is open for LinkedIn subscribers.> On April 1, 2019, we renamed ourselves as “Nippon Steel Corporation” (from Nippon Steel and Sumitomo Metal Corporation), to keep in pace with our advance as a growing global steelmaker with origins in Japan.

NAICS: 333
NAICS Definition: Machinery Manufacturing
Employees: 618
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/rourkela-steel-plant.jpeg
Rourkela steel plant
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/日本製鉄.jpeg
Nippon Steel Corporation
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
Rourkela steel plant
100%
Compliance Rate
0/4 Standards Verified
Nippon Steel Corporation
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Machinery Manufacturing Industry Average (This Year)

No incidents recorded for Rourkela steel plant in 2025.

Incidents vs Machinery Manufacturing Industry Average (This Year)

No incidents recorded for Nippon Steel Corporation in 2025.

Incident History — Rourkela steel plant (X = Date, Y = Severity)

Rourkela steel plant cyber incidents detection timeline including parent company and subsidiaries

Incident History — Nippon Steel Corporation (X = Date, Y = Severity)

Nippon Steel Corporation cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/rourkela-steel-plant.jpeg
Rourkela steel plant
Incidents

No Incident

https://images.rankiteo.com/companyimages/日本製鉄.jpeg
Nippon Steel Corporation
Incidents

No Incident

FAQ

Nippon Steel Corporation company demonstrates a stronger AI Cybersecurity Score compared to Rourkela steel plant company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Nippon Steel Corporation company has disclosed a higher number of cyber incidents compared to Rourkela steel plant company.

In the current year, Nippon Steel Corporation company and Rourkela steel plant company have not reported any cyber incidents.

Neither Nippon Steel Corporation company nor Rourkela steel plant company has reported experiencing a ransomware attack publicly.

Neither Nippon Steel Corporation company nor Rourkela steel plant company has reported experiencing a data breach publicly.

Neither Nippon Steel Corporation company nor Rourkela steel plant company has reported experiencing targeted cyberattacks publicly.

Neither Rourkela steel plant company nor Nippon Steel Corporation company has reported experiencing or disclosing vulnerabilities publicly.

Neither Rourkela steel plant nor Nippon Steel Corporation holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Rourkela steel plant company nor Nippon Steel Corporation company has publicly disclosed detailed information about the number of their subsidiaries.

Rourkela steel plant company employs more people globally than Nippon Steel Corporation company, reflecting its scale as a Machinery Manufacturing.

Neither Rourkela steel plant nor Nippon Steel Corporation holds SOC 2 Type 1 certification.

Neither Rourkela steel plant nor Nippon Steel Corporation holds SOC 2 Type 2 certification.

Neither Rourkela steel plant nor Nippon Steel Corporation holds ISO 27001 certification.

Neither Rourkela steel plant nor Nippon Steel Corporation holds PCI DSS certification.

Neither Rourkela steel plant nor Nippon Steel Corporation holds HIPAA certification.

Neither Rourkela steel plant nor Nippon Steel Corporation 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