Comparison Overview

IRICO

VS

Loram South America

IRICO

No. 91, Tehran, 4111-4897-4133, IR
Last Update: 2025-11-27
Between 700 and 749

Iranian Golden Goal Group (IGGG) with long-lasting experience and service as a general contractor with the aim of implementing constructional projects in the fields of: oil, gas , petrochemical industries, steel manufacturing, railway transportation, construction and installing plants. IGGG top managers, decided to buy 100% stocks of IRICO and become one of the affiliated companies of Group. IRICO is a pioneer of design and manufacture different types of passenger coaches (such as regional passenger train, mass transit system, Light Rail Vehicle and Elevated Light Rail Transit) and freight wagons in Iran with production capacity of almost 200 units passenger cars and 500 Freight wagons per year. Some of the IRICO's productions are : Regional DMU in contract with Hyundai Rotem, Metro cars and diffrent typpes of Freight wagons .

NAICS: 3365
NAICS Definition: Railroad Rolling Stock Manufacturing
Employees: 135
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Loram South America

Rua Dr. Alexandre Gutierrez 826, Curitiba, 80240-130, BR
Last Update: 2025-11-27
Between 700 and 749

A Loram South America é uma subsidiária ligada a Loram Maintenance of Way, empresa ferroviária especializada em prestação de serviço e fabricação de máquinas de manutenção de Via Permanente, localizada nos EUA. Líder no fornecimento de serviços e equipamentos de manutenção de via da América do Norte, atendemos ferrovias Classe I, além shortlines e transporte de passageiros. Estamos há mais de 60 anos no mercado e hoje possuímos uma das maiores frotas de equipamentos de via permanente na América do Norte, mais de 250 máquinas e de 1.500 colaboradores distribuídos pelo mundo.

NAICS: 3365
NAICS Definition: Railroad Rolling Stock Manufacturing
Employees: 113
Subsidiaries: 2
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/irico.jpeg
IRICO
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/loramsouthamerica.jpeg
Loram South America
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
IRICO
100%
Compliance Rate
0/4 Standards Verified
Loram South America
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Railroad Equipment Manufacturing Industry Average (This Year)

No incidents recorded for IRICO in 2025.

Incidents vs Railroad Equipment Manufacturing Industry Average (This Year)

No incidents recorded for Loram South America in 2025.

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

IRICO cyber incidents detection timeline including parent company and subsidiaries

Incident History — Loram South America (X = Date, Y = Severity)

Loram South America cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/irico.jpeg
IRICO
Incidents

No Incident

https://images.rankiteo.com/companyimages/loramsouthamerica.jpeg
Loram South America
Incidents

No Incident

FAQ

IRICO company demonstrates a stronger AI Cybersecurity Score compared to Loram South America company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Loram South America company has disclosed a higher number of cyber incidents compared to IRICO company.

In the current year, Loram South America company and IRICO company have not reported any cyber incidents.

Neither Loram South America company nor IRICO company has reported experiencing a ransomware attack publicly.

Neither Loram South America company nor IRICO company has reported experiencing a data breach publicly.

Neither Loram South America company nor IRICO company has reported experiencing targeted cyberattacks publicly.

Neither IRICO company nor Loram South America company has reported experiencing or disclosing vulnerabilities publicly.

Neither IRICO nor Loram South America holds any compliance certifications.

Neither company holds any compliance certifications.

Loram South America company has more subsidiaries worldwide compared to IRICO company.

IRICO company employs more people globally than Loram South America company, reflecting its scale as a Railroad Equipment Manufacturing.

Neither IRICO nor Loram South America holds SOC 2 Type 1 certification.

Neither IRICO nor Loram South America holds SOC 2 Type 2 certification.

Neither IRICO nor Loram South America holds ISO 27001 certification.

Neither IRICO nor Loram South America holds PCI DSS certification.

Neither IRICO nor Loram South America holds HIPAA certification.

Neither IRICO nor Loram South America 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