Comparison Overview

Jrlon, Inc.

VS

Tooling Systems Group, Inc.

Jrlon, Inc.

4344 Fox Rd, Palmyra, 14522, US
Last Update: 2025-11-28
View Profile
Between 750 and 799
http://www.jrlon.com

For many years, Jrlon, Inc. has been recognized as a dependable source and leading supplier of plastic and specialty metal products. We are one of the premier PTFE processors in the United States. Jrlon's expertise also covers a wide range of other performance plastic materials and alloy steels for custom molding, CNC machining, swiss machining, gear manufacturing, technical industrial coatings, welding, full sheet metal fabrication, and assembly. Driven by innovative designers and engineers, Jrlon manufactures unique products vital to a wide variety of industries.

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

Tooling Systems Group, Inc.

555 Plymouth Avenue NE, Grand Rapids, MI, 49505, US
Last Update: 2025-11-28
Between 750 and 799
http://www.toolingsystemsgroup.com

The Tooling Systems Group (TSG) is a family of stamping die, mold tooling, assembly system, steel plate fabrication, machinery sales, and contract machining companies that service OEMs, suppliers and manufacturers around the world. The TSG utilizes the power of the team to bring better timing, quality, and savings to our clients in the automotive, appliance, medical, government, military, and manufacturing industries.

NAICS: None
NAICS Definition: Others
Employees: 96
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/jrlon-inc-.jpeg
Jrlon, Inc.
—
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/tooling-systems-group-inc..jpeg
Tooling Systems Group, Inc.
—
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
Jrlon, Inc.
100%
Compliance Rate
0/4 Standards Verified
Tooling Systems Group, Inc.
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 Jrlon, Inc. in 2025.

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

No incidents recorded for Tooling Systems Group, Inc. in 2025.

Incident History — Jrlon, Inc. (X = Date, Y = Severity)

Jrlon, Inc. cyber incidents detection timeline including parent company and subsidiaries

Incident History — Tooling Systems Group, Inc. (X = Date, Y = Severity)

Tooling Systems Group, Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/jrlon-inc-.jpeg
Jrlon, Inc.
Incidents

No Incident

https://images.rankiteo.com/companyimages/tooling-systems-group-inc..jpeg
Tooling Systems Group, Inc.
Incidents

No Incident

FAQ

Both Jrlon, Inc. company and Tooling Systems Group, Inc. company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Tooling Systems Group, Inc. company has disclosed a higher number of cyber incidents compared to Jrlon, Inc. company.

In the current year, Tooling Systems Group, Inc. company and Jrlon, Inc. company have not reported any cyber incidents.

Neither Tooling Systems Group, Inc. company nor Jrlon, Inc. company has reported experiencing a ransomware attack publicly.

Neither Tooling Systems Group, Inc. company nor Jrlon, Inc. company has reported experiencing a data breach publicly.

Neither Tooling Systems Group, Inc. company nor Jrlon, Inc. company has reported experiencing targeted cyberattacks publicly.

Neither Jrlon, Inc. company nor Tooling Systems Group, Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Jrlon, Inc. nor Tooling Systems Group, Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Jrlon, Inc. company nor Tooling Systems Group, Inc. company has publicly disclosed detailed information about the number of their subsidiaries.

Tooling Systems Group, Inc. company employs more people globally than Jrlon, Inc. company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither Jrlon, Inc. nor Tooling Systems Group, Inc. holds SOC 2 Type 1 certification.

Neither Jrlon, Inc. nor Tooling Systems Group, Inc. holds SOC 2 Type 2 certification.

Neither Jrlon, Inc. nor Tooling Systems Group, Inc. holds ISO 27001 certification.

Neither Jrlon, Inc. nor Tooling Systems Group, Inc. holds PCI DSS certification.

Neither Jrlon, Inc. nor Tooling Systems Group, Inc. holds HIPAA certification.

Neither Jrlon, Inc. nor Tooling Systems Group, Inc. 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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References