Comparison Overview

Sur-Seal, LLC.

VS

Fives Filling & Sealing

Sur-Seal, LLC.

6156 Wesselman Rd, Cincinnati, Ohio, 45248, US
Last Update: 2025-11-27
Between 750 and 799

Sur-Seal goes the extra mile to solve the toughest challenges around the world of sealing. You may not know our products, but you certainly know the products that ours go in such as home heating systems, hospital beds, roadside lighting, and more. From initial design concepts to prototyping to small batches to full scale production, Sur-Seal provides end-to-end engineering and manufacturing services to our customers.

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

Fives Filling & Sealing

Parc d'Activités de la Forêt, 17 rue de la Communauté , LE BIGNON, 44140, FR
Last Update: 2025-11-28

For more than 50 years, Fives Filling | Sealing offer ultimate engineering solution to their customers in the Automotive, Trucks, Heavy machinery and 2-wheelers, HVAC and Energy industries. Dedicated to OEM and TIER1, the Fives product range includes Fluid filling machines, Leak detection solutions, and Sealing application systems. Our manufacturing facilities are located in France, USA, China, and Japan. With the strong support of a network of agents and local offices, and more than 5,000 installations in 40 countries, Fives Filling | Sealing is a recognized provider of outstanding solutions at the heart of the customers’ performance.

NAICS: None
NAICS Definition: Others
Employees: 94
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/sur-seal-corporation.jpeg
Sur-Seal, LLC.
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/fives-filling-sealing.jpeg
Fives Filling & Sealing
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
Sur-Seal, LLC.
100%
Compliance Rate
0/4 Standards Verified
Fives Filling & Sealing
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 Sur-Seal, LLC. in 2025.

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

No incidents recorded for Fives Filling & Sealing in 2025.

Incident History — Sur-Seal, LLC. (X = Date, Y = Severity)

Sur-Seal, LLC. cyber incidents detection timeline including parent company and subsidiaries

Incident History — Fives Filling & Sealing (X = Date, Y = Severity)

Fives Filling & Sealing cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/sur-seal-corporation.jpeg
Sur-Seal, LLC.
Incidents

No Incident

https://images.rankiteo.com/companyimages/fives-filling-sealing.jpeg
Fives Filling & Sealing
Incidents

No Incident

FAQ

Both Sur-Seal, LLC. company and Fives Filling & Sealing company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Fives Filling & Sealing company has disclosed a higher number of cyber incidents compared to Sur-Seal, LLC. company.

In the current year, Fives Filling & Sealing company and Sur-Seal, LLC. company have not reported any cyber incidents.

Neither Fives Filling & Sealing company nor Sur-Seal, LLC. company has reported experiencing a ransomware attack publicly.

Neither Fives Filling & Sealing company nor Sur-Seal, LLC. company has reported experiencing a data breach publicly.

Neither Fives Filling & Sealing company nor Sur-Seal, LLC. company has reported experiencing targeted cyberattacks publicly.

Neither Sur-Seal, LLC. company nor Fives Filling & Sealing company has reported experiencing or disclosing vulnerabilities publicly.

Neither Sur-Seal, LLC. nor Fives Filling & Sealing holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Sur-Seal, LLC. company nor Fives Filling & Sealing company has publicly disclosed detailed information about the number of their subsidiaries.

Sur-Seal, LLC. company employs more people globally than Fives Filling & Sealing company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither Sur-Seal, LLC. nor Fives Filling & Sealing holds SOC 2 Type 1 certification.

Neither Sur-Seal, LLC. nor Fives Filling & Sealing holds SOC 2 Type 2 certification.

Neither Sur-Seal, LLC. nor Fives Filling & Sealing holds ISO 27001 certification.

Neither Sur-Seal, LLC. nor Fives Filling & Sealing holds PCI DSS certification.

Neither Sur-Seal, LLC. nor Fives Filling & Sealing holds HIPAA certification.

Neither Sur-Seal, LLC. nor Fives Filling & Sealing 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