Comparison Overview

Industrial Controls SAC

VS

JDRM Engineering

Industrial Controls SAC

None
Last Update: 2025-11-28
Between 800 and 849

Industrial Controls es una compañía peruana con 22 años de experiencia en el sector industrial, que ha desarrollado sus operaciones de manera integral en el campo de la automatización, instrumentación, control de procesos, automatismos, electricidad, neumática y servicios especializados atendiendo sectores industriales tales como: Minería, Siderúrgia,Pesca, Agroindustria, Energía, Petróleo & Gas, Qumica,Manufactura, Alimentos, Farmacéuticos, Tratamiento de aguas, entre otros, acorde a nuestros valores y principios desde 1994.

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

JDRM Engineering

5604 N. Main Street, Sylvania, 43560, US
Last Update: 2025-11-27
Between 750 and 799

JDRM Engineering is a professional mechanical, electrical, plumbing, technology and safety engineering firm. We provide comprehensive engineering, consulting, and design services. JDRM specializes in six distinct markets: industrial, healthcare, commercial, recreational, educational and government. Our clients include architectural firms, facility owners, and contractors. JDRM Engineering is licensed in 30 States. The current staff of 48 employees includes: 21 engineers, 8 of whom are registered Professional Engineers; 5 Registered Communication Distribution Designers; 1 ESS Designer; 1 CTS Certified Technology Specialist, 1 CESCP Certified Electrical Safety Compliance; 1 NICET level III and 4 LEED Accredited Professionals. Located at 5604 N. Main Street in Sylvania, Ohio (a suburb of Toledo, Ohio), JDRM Engineering is ideally positioned to serve your facility engineering needs in Ohio and Michigan. But we don't stop there -- our reach extends through much of the Midwest with professional registrations in 30 states. In 1995 JDRM Engineering, Inc. was formed with the merger of principals, staff, and business interests of separate mechanical and electrical firms. The firms had a close history of collaborating on projects and the four founding principles had worked together since 1976. The partners’ combined design experience of over 225 years contributes a solid base of knowledge to support a staff organized to furnish complete and quality design engineering for your construction needs.

NAICS: None
NAICS Definition: Others
Employees: 57
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/industrial-controls-sac.jpeg
Industrial Controls SAC
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/jdrm-engineering.jpeg
JDRM Engineering
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
Industrial Controls SAC
100%
Compliance Rate
0/4 Standards Verified
JDRM Engineering
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 Industrial Controls SAC in 2025.

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

No incidents recorded for JDRM Engineering in 2025.

Incident History — Industrial Controls SAC (X = Date, Y = Severity)

Industrial Controls SAC cyber incidents detection timeline including parent company and subsidiaries

Incident History — JDRM Engineering (X = Date, Y = Severity)

JDRM Engineering cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/industrial-controls-sac.jpeg
Industrial Controls SAC
Incidents

No Incident

https://images.rankiteo.com/companyimages/jdrm-engineering.jpeg
JDRM Engineering
Incidents

No Incident

FAQ

Industrial Controls SAC company demonstrates a stronger AI Cybersecurity Score compared to JDRM Engineering company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, JDRM Engineering company has disclosed a higher number of cyber incidents compared to Industrial Controls SAC company.

In the current year, JDRM Engineering company and Industrial Controls SAC company have not reported any cyber incidents.

Neither JDRM Engineering company nor Industrial Controls SAC company has reported experiencing a ransomware attack publicly.

Neither JDRM Engineering company nor Industrial Controls SAC company has reported experiencing a data breach publicly.

Neither JDRM Engineering company nor Industrial Controls SAC company has reported experiencing targeted cyberattacks publicly.

Neither Industrial Controls SAC company nor JDRM Engineering company has reported experiencing or disclosing vulnerabilities publicly.

Neither Industrial Controls SAC nor JDRM Engineering holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Industrial Controls SAC company nor JDRM Engineering company has publicly disclosed detailed information about the number of their subsidiaries.

Industrial Controls SAC company employs more people globally than JDRM Engineering company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither Industrial Controls SAC nor JDRM Engineering holds SOC 2 Type 1 certification.

Neither Industrial Controls SAC nor JDRM Engineering holds SOC 2 Type 2 certification.

Neither Industrial Controls SAC nor JDRM Engineering holds ISO 27001 certification.

Neither Industrial Controls SAC nor JDRM Engineering holds PCI DSS certification.

Neither Industrial Controls SAC nor JDRM Engineering holds HIPAA certification.

Neither Industrial Controls SAC nor JDRM Engineering 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