Comparison Overview

Abtech Ltd

VS

HANNECARD

Abtech Ltd

199 Newhall Road, Sheffield, South Yorkshire, S9 2QJ, GB
Last Update: 2025-11-27
Between 750 and 799

Hazardous area enclosures, high voltage Ex-junction boxes, LED & HID lighting and cable connection products.... With over 40 years of experience in designing, manufacturing and supplying high quality electrical connection solutions, Abtech is an ideal partner for all your hazardous area solutions. Abtech have been manufacturing quality industrial and hazardous area junction boxes since the early 1970’s. Our range has now expand to include market leading HV and fire rated solutions, local control stations and the latest in Ex-rated LED lighting technology. Our goal is to be the first choice supplier of quality electrical connection products worldwide. This, we believe is achieved through innovation, market leading design, rigorous testing and adherence to quality. With our head office based in Sheffield, UK and locations in Houston, Texas; Bünde, Germany; Busan, Korea and Singapore combined with our network of agents covering over 40 counties world-wide, Abtech have the coverage to handle any project, no matter how large or diverse of location.

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

HANNECARD

Ninoofsesteenweg 589, Ronse, undefined, 9660, BE
Last Update: 2025-11-27
Between 750 and 799

With over 120 years of expertise, the Hannecard Group stands as a worldwide leader in industrial roller coverings and coatings, delivering cutting-edge solutions in rubber, polyurethane, composite, and carbide to diverse industries. With a strong global presence, Hannecard offers a comprehensive range of services, including roller maintenance, roller repair, and roller optimization, ensuring unparalleled support to customers across the world. Our mission is to boost business performance with durable solutions, exceptional roller coverings and services, and advanced smart monitoring tools.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/abtech-ltd.jpeg
Abtech 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/hannecard-nv.jpeg
HANNECARD
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
Abtech Ltd
100%
Compliance Rate
0/4 Standards Verified
HANNECARD
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 Abtech Ltd in 2025.

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

No incidents recorded for HANNECARD in 2025.

Incident History — Abtech Ltd (X = Date, Y = Severity)

Abtech Ltd cyber incidents detection timeline including parent company and subsidiaries

Incident History — HANNECARD (X = Date, Y = Severity)

HANNECARD cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/abtech-ltd.jpeg
Abtech Ltd
Incidents

No Incident

https://images.rankiteo.com/companyimages/hannecard-nv.jpeg
HANNECARD
Incidents

No Incident

FAQ

HANNECARD company demonstrates a stronger AI Cybersecurity Score compared to Abtech Ltd company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, HANNECARD company has disclosed a higher number of cyber incidents compared to Abtech Ltd company.

In the current year, HANNECARD company and Abtech Ltd company have not reported any cyber incidents.

Neither HANNECARD company nor Abtech Ltd company has reported experiencing a ransomware attack publicly.

Neither HANNECARD company nor Abtech Ltd company has reported experiencing a data breach publicly.

Neither HANNECARD company nor Abtech Ltd company has reported experiencing targeted cyberattacks publicly.

Neither Abtech Ltd company nor HANNECARD company has reported experiencing or disclosing vulnerabilities publicly.

Neither Abtech Ltd nor HANNECARD holds any compliance certifications.

Neither company holds any compliance certifications.

HANNECARD company has more subsidiaries worldwide compared to Abtech Ltd company.

HANNECARD company employs more people globally than Abtech Ltd company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither Abtech Ltd nor HANNECARD holds SOC 2 Type 1 certification.

Neither Abtech Ltd nor HANNECARD holds SOC 2 Type 2 certification.

Neither Abtech Ltd nor HANNECARD holds ISO 27001 certification.

Neither Abtech Ltd nor HANNECARD holds PCI DSS certification.

Neither Abtech Ltd nor HANNECARD holds HIPAA certification.

Neither Abtech Ltd nor HANNECARD 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