Comparison Overview

Jarrett Engineering

VS

TRP Sealing Systems Ltd

Jarrett Engineering

1011 N. Pennsylvania St., Indianapolis, Indiana, 46204, US
Last Update: 2025-11-28
Between 750 and 799

Welcome to Jarrett Engineering. We are a Midwest Tool and Machine design house in business since 1962. With an onsite staff of 16 we can handle all of your tool, gauging, machine, and manufacturing design needs. We operate in downtown Indianapolis or what is better known as the heart of the Crossroads of America. We are a fully ISO 9001:2015 certified design shop. We have clients in many different industries. Ranging from academic facilities to aerospace, automotive, consumer products, and pharmaceutical. From prototyping to the final design, from hand held tools to fully automated assembly lines, we do it all. With abilities to use different software packages to cater to each clients need, we run on Siemens NX, Unigraphics, SolidWorks, Inventor, Solidedge, and AutoCAD. We are able to handle all types of mechanical designs and get them into the factory working for you or into production. While we specialize in design only and don't build our designs in house, we have project management and a large range of suppliers to be able to manage your design and build process from start to finish.

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

TRP Sealing Systems Ltd

None
Last Update: 2025-11-27
Between 750 and 799

TRP are a large, established and growing manufacturer who specialise in supplying seals, gaskets and mouldings for demanding environments and advanced applications. The company has over 500 people based in manufacturing locations across the world to serve our long standing global customer base. In addition to experienced people and a quality ethos, the business has advanced labs and manufacturing facilities to ensure that customer needs can be thoroughly addressed. TRP has a strong engineering and advanced materials focus, and our knowledge of sealing products and rubber mouldings is based on over 30 years experience in providing innovative design solutions enhanced by our own custom developed polymers.

NAICS: None
NAICS Definition: Others
Employees: 72
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/jarrettengineering.jpeg
Jarrett 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
https://images.rankiteo.com/companyimages/trp-sealing-systems-ltd.jpeg
TRP Sealing Systems 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
Compliance Summary
Jarrett Engineering
100%
Compliance Rate
0/4 Standards Verified
TRP Sealing Systems Ltd
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 Jarrett Engineering in 2025.

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

No incidents recorded for TRP Sealing Systems Ltd in 2025.

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

Jarrett Engineering cyber incidents detection timeline including parent company and subsidiaries

Incident History — TRP Sealing Systems Ltd (X = Date, Y = Severity)

TRP Sealing Systems Ltd cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/jarrettengineering.jpeg
Jarrett Engineering
Incidents

No Incident

https://images.rankiteo.com/companyimages/trp-sealing-systems-ltd.jpeg
TRP Sealing Systems Ltd
Incidents

No Incident

FAQ

Both Jarrett Engineering company and TRP Sealing Systems Ltd company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, TRP Sealing Systems Ltd company has disclosed a higher number of cyber incidents compared to Jarrett Engineering company.

In the current year, TRP Sealing Systems Ltd company and Jarrett Engineering company have not reported any cyber incidents.

Neither TRP Sealing Systems Ltd company nor Jarrett Engineering company has reported experiencing a ransomware attack publicly.

Neither TRP Sealing Systems Ltd company nor Jarrett Engineering company has reported experiencing a data breach publicly.

Neither TRP Sealing Systems Ltd company nor Jarrett Engineering company has reported experiencing targeted cyberattacks publicly.

Neither Jarrett Engineering company nor TRP Sealing Systems Ltd company has reported experiencing or disclosing vulnerabilities publicly.

Neither Jarrett Engineering nor TRP Sealing Systems Ltd holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Jarrett Engineering company nor TRP Sealing Systems Ltd company has publicly disclosed detailed information about the number of their subsidiaries.

TRP Sealing Systems Ltd company employs more people globally than Jarrett Engineering company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither Jarrett Engineering nor TRP Sealing Systems Ltd holds SOC 2 Type 1 certification.

Neither Jarrett Engineering nor TRP Sealing Systems Ltd holds SOC 2 Type 2 certification.

Neither Jarrett Engineering nor TRP Sealing Systems Ltd holds ISO 27001 certification.

Neither Jarrett Engineering nor TRP Sealing Systems Ltd holds PCI DSS certification.

Neither Jarrett Engineering nor TRP Sealing Systems Ltd holds HIPAA certification.

Neither Jarrett Engineering nor TRP Sealing Systems Ltd 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