Comparison Overview

OCEAN CORPORATION

VS

Metalurgica Rio Grande

OCEAN CORPORATION

Block C Gulshan e Jamal Khi, Karachi, Headquarters, PK
Last Update: 2025-11-27
Between 750 and 799

Ocean Corporation (OC), as a group of professional engineers providing Integrated Quality Solutions to Industrial & Commercial sectors of Pakistan by putting together Application Engineering Expertise; Supply Chain Support; Project Integration Capabilities to work for them up to their utmost satisfactions. Industrial Technology Solutions for Oil & Gas, Petrochemical & Power Sectors (Includes Process & Utility Equipment; Mechanical & Control Valves, ESD & BDV valves) Water & Wastewater Treatment Solution (Including Treatment Plants & Packages, Consultancy & Contracting Services, Blower, Pumps & Equipment, Treatment Chemicals) Fire Protection Products & Services Contracting & Consultancy for Industrial Utility & Water/WWT plants projects For inquiries contact: 0092 321 8498136 email us: [email protected]; [email protected] www.oceancorpn.com #reducereuserecycle #watertreatment #mechanical #petrochemical #oilandgasindustry #power

NAICS: None
NAICS Definition: Others
Employees: 3
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Metalurgica Rio Grande

R André Francisco de Andrade Arantes, 235, Igarapava, SP, 14540000, BR
Last Update: 2025-11-27

From an initiative of the employees who have joined together and founded on September 21, 1999 the Cooperative of Producers of Article Industrial Boilers. It started its activities on November 5, 1999 with 4.154,04m² of built area. On January 4, 2008 changed its name to CCRG Industrial Equipment LTD and passed his Cooper's fancy name for Metallurgical boiler Rio Grande Rio Grande that now has a building area of ​10,000 square meters and a total area of ​100,000m². A company fully prepared to provide equipment for the sugar-energy sector, Distilleries, Fuel Terminals, Fertilizers and Paper and Pulp.

NAICS: None
NAICS Definition:
Employees: 126
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/ocean-corporation.jpeg
OCEAN 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
https://images.rankiteo.com/companyimages/metalurgica-rio-grande.jpeg
Metalurgica Rio Grande
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
OCEAN CORPORATION
100%
Compliance Rate
0/4 Standards Verified
Metalurgica Rio Grande
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Mechanical Or Industrial Engineering Industry Average (This Year)

No incidents recorded for OCEAN CORPORATION in 2025.

Incidents vs Mechanical Or Industrial Engineering Industry Average (This Year)

No incidents recorded for Metalurgica Rio Grande in 2025.

Incident History — OCEAN CORPORATION (X = Date, Y = Severity)

OCEAN CORPORATION cyber incidents detection timeline including parent company and subsidiaries

Incident History — Metalurgica Rio Grande (X = Date, Y = Severity)

Metalurgica Rio Grande cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/ocean-corporation.jpeg
OCEAN CORPORATION
Incidents

No Incident

https://images.rankiteo.com/companyimages/metalurgica-rio-grande.jpeg
Metalurgica Rio Grande
Incidents

No Incident

FAQ

Metalurgica Rio Grande company demonstrates a stronger AI Cybersecurity Score compared to OCEAN CORPORATION company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Metalurgica Rio Grande company has disclosed a higher number of cyber incidents compared to OCEAN CORPORATION company.

In the current year, Metalurgica Rio Grande company and OCEAN CORPORATION company have not reported any cyber incidents.

Neither Metalurgica Rio Grande company nor OCEAN CORPORATION company has reported experiencing a ransomware attack publicly.

Neither Metalurgica Rio Grande company nor OCEAN CORPORATION company has reported experiencing a data breach publicly.

Neither Metalurgica Rio Grande company nor OCEAN CORPORATION company has reported experiencing targeted cyberattacks publicly.

Neither OCEAN CORPORATION company nor Metalurgica Rio Grande company has reported experiencing or disclosing vulnerabilities publicly.

Neither OCEAN CORPORATION nor Metalurgica Rio Grande holds any compliance certifications.

Neither company holds any compliance certifications.

Neither OCEAN CORPORATION company nor Metalurgica Rio Grande company has publicly disclosed detailed information about the number of their subsidiaries.

Metalurgica Rio Grande company employs more people globally than OCEAN CORPORATION company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither OCEAN CORPORATION nor Metalurgica Rio Grande holds SOC 2 Type 1 certification.

Neither OCEAN CORPORATION nor Metalurgica Rio Grande holds SOC 2 Type 2 certification.

Neither OCEAN CORPORATION nor Metalurgica Rio Grande holds ISO 27001 certification.

Neither OCEAN CORPORATION nor Metalurgica Rio Grande holds PCI DSS certification.

Neither OCEAN CORPORATION nor Metalurgica Rio Grande holds HIPAA certification.

Neither OCEAN CORPORATION nor Metalurgica Rio Grande 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