Comparison Overview

Laxyo Energy Ltd.

VS

Midwest Pacific Rail Net & Logistics

Laxyo Energy Ltd.

Laxyo House, Plot No. 02, County Park, Ring Road, Indore, 452010, IN
Last Update: 2025-11-27
Between 700 and 749

LAXYO, an Engineering Company established in mid 2007, with amalgamation of sister concerns, is meeting the Niche of industrial houses. With the Commitment; We, the energy people…., LAXYO is offering excellent value added professional services in multiple engineering fields to industrial houses. A combination of well planned outsourcing of relevant services to LAXYO and gainful utilization of available in-house resources, can reduce operational cost of the industrial houses and they can be free from day to day worries, concentrate on formulation of plans to achieve corporate goals and contribute significantly to fulfil `VISION 2020` conceived and projected by our honorable Ex President Mr. A. P. J. Abdul Kalam

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

Midwest Pacific Rail Net & Logistics

None
Last Update: 2025-11-27
Between 700 and 749

ECONOMIC IMPACT... Customers of all shapes and sizes rely on rail, and MPR&L plays a vital role as a regional shortline carrier in that supply chain. We enable our local customers to participate in a wide range of markets in North America and around the world. We work hard to listen and respond to customer needs, maintain trust and provide an ease of doing business. Our goal is simple, to provide consistent, reliable service that meets our customers' needs today as well as those in the future. We consistently monitor our rail network to insure we work safely and efficiently providing a platform for success today and for the years to come. MPR&L is committed to working hard, working smart, to insure both our employees and our customers the reliability and efficiency they can count on.

NAICS: 336
NAICS Definition:
Employees: 5
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/defaultcompany.jpeg
Laxyo Energy Ltd.
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/midwest-pacific-rail-net-&-logistics.jpeg
Midwest Pacific Rail Net & Logistics
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
Laxyo Energy Ltd.
100%
Compliance Rate
0/4 Standards Verified
Midwest Pacific Rail Net & Logistics
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Railroad Equipment Manufacturing Industry Average (This Year)

No incidents recorded for Laxyo Energy Ltd. in 2025.

Incidents vs Railroad Equipment Manufacturing Industry Average (This Year)

No incidents recorded for Midwest Pacific Rail Net & Logistics in 2025.

Incident History — Laxyo Energy Ltd. (X = Date, Y = Severity)

Laxyo Energy Ltd. cyber incidents detection timeline including parent company and subsidiaries

Incident History — Midwest Pacific Rail Net & Logistics (X = Date, Y = Severity)

Midwest Pacific Rail Net & Logistics cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Laxyo Energy Ltd.
Incidents

No Incident

https://images.rankiteo.com/companyimages/midwest-pacific-rail-net-&-logistics.jpeg
Midwest Pacific Rail Net & Logistics
Incidents

No Incident

FAQ

Laxyo Energy Ltd. company demonstrates a stronger AI Cybersecurity Score compared to Midwest Pacific Rail Net & Logistics company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Midwest Pacific Rail Net & Logistics company has disclosed a higher number of cyber incidents compared to Laxyo Energy Ltd. company.

In the current year, Midwest Pacific Rail Net & Logistics company and Laxyo Energy Ltd. company have not reported any cyber incidents.

Neither Midwest Pacific Rail Net & Logistics company nor Laxyo Energy Ltd. company has reported experiencing a ransomware attack publicly.

Neither Midwest Pacific Rail Net & Logistics company nor Laxyo Energy Ltd. company has reported experiencing a data breach publicly.

Neither Midwest Pacific Rail Net & Logistics company nor Laxyo Energy Ltd. company has reported experiencing targeted cyberattacks publicly.

Neither Laxyo Energy Ltd. company nor Midwest Pacific Rail Net & Logistics company has reported experiencing or disclosing vulnerabilities publicly.

Neither Laxyo Energy Ltd. nor Midwest Pacific Rail Net & Logistics holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Laxyo Energy Ltd. company nor Midwest Pacific Rail Net & Logistics company has publicly disclosed detailed information about the number of their subsidiaries.

Laxyo Energy Ltd. company employs more people globally than Midwest Pacific Rail Net & Logistics company, reflecting its scale as a Railroad Equipment Manufacturing.

Neither Laxyo Energy Ltd. nor Midwest Pacific Rail Net & Logistics holds SOC 2 Type 1 certification.

Neither Laxyo Energy Ltd. nor Midwest Pacific Rail Net & Logistics holds SOC 2 Type 2 certification.

Neither Laxyo Energy Ltd. nor Midwest Pacific Rail Net & Logistics holds ISO 27001 certification.

Neither Laxyo Energy Ltd. nor Midwest Pacific Rail Net & Logistics holds PCI DSS certification.

Neither Laxyo Energy Ltd. nor Midwest Pacific Rail Net & Logistics holds HIPAA certification.

Neither Laxyo Energy Ltd. nor Midwest Pacific Rail Net & Logistics 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