Comparison Overview

Metzner

VS

Tysse Mekaniske Verksted AS

Metzner

Messerschmittstr. 30, Neu-Ulm, 89231, DE
Last Update: 2025-11-27
Between 750 and 799

For over 30 years, we have been developing machines and systems for cable, corrugated tube, rubber and plastics processing as well as complete automation solutions. Metzner machines process, among other things, high-voltage cables (Metzner E-Mobility), medical articles such as catheter and respiratory tubes, sports articles as well as profiles and hoses for the automotive industry. Our most important asset here is our unique staff. They design and build the machines with the greatest passion in our halls in Neu-Ulm. It is only through their creativity, commitment and know-how that competent solutions are created for our international customers. Become part of this team - we are always looking for trainees, students, young professionals and experienced professionals.  More information here: www.metzner.com And to find out more about our subsidiary E-Mobility, click here: www.metzner-emobility.com

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

Tysse Mekaniske Verksted AS

5284, NO
Last Update: 2025-11-22
Between 750 and 799

Tilhenger, Båthenger, Biltilhenger, Lift En tilhenger kan brukes til så mangt. Derfor produserer vi mange ulike typer av dem. Innenfor alle kategorier har vi et stort utvalg av ekstrautstyr, og muligheter for endring i spesifikasjoner, og vi kan innrede skaphengere og lage spesialløsninger hvis du har spesielle behov. Hele tiden driver Tysse utviklingen videre. Vi satser mye på bredde, og mest på kvalitet.

NAICS: None
NAICS Definition: Others
Employees: 34
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/metzner-maschinenbau-gmbh.jpeg
Metzner
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/tysse-mekaniske-verksted-as.jpeg
Tysse Mekaniske Verksted AS
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
Metzner
100%
Compliance Rate
0/4 Standards Verified
Tysse Mekaniske Verksted AS
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 Metzner in 2025.

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

No incidents recorded for Tysse Mekaniske Verksted AS in 2025.

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

Metzner cyber incidents detection timeline including parent company and subsidiaries

Incident History — Tysse Mekaniske Verksted AS (X = Date, Y = Severity)

Tysse Mekaniske Verksted AS cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/metzner-maschinenbau-gmbh.jpeg
Metzner
Incidents

No Incident

https://images.rankiteo.com/companyimages/tysse-mekaniske-verksted-as.jpeg
Tysse Mekaniske Verksted AS
Incidents

No Incident

FAQ

Metzner company demonstrates a stronger AI Cybersecurity Score compared to Tysse Mekaniske Verksted AS company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Tysse Mekaniske Verksted AS company has disclosed a higher number of cyber incidents compared to Metzner company.

In the current year, Tysse Mekaniske Verksted AS company and Metzner company have not reported any cyber incidents.

Neither Tysse Mekaniske Verksted AS company nor Metzner company has reported experiencing a ransomware attack publicly.

Neither Tysse Mekaniske Verksted AS company nor Metzner company has reported experiencing a data breach publicly.

Neither Tysse Mekaniske Verksted AS company nor Metzner company has reported experiencing targeted cyberattacks publicly.

Neither Metzner company nor Tysse Mekaniske Verksted AS company has reported experiencing or disclosing vulnerabilities publicly.

Neither Metzner nor Tysse Mekaniske Verksted AS holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Metzner company nor Tysse Mekaniske Verksted AS company has publicly disclosed detailed information about the number of their subsidiaries.

Metzner company employs more people globally than Tysse Mekaniske Verksted AS company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither Metzner nor Tysse Mekaniske Verksted AS holds SOC 2 Type 1 certification.

Neither Metzner nor Tysse Mekaniske Verksted AS holds SOC 2 Type 2 certification.

Neither Metzner nor Tysse Mekaniske Verksted AS holds ISO 27001 certification.

Neither Metzner nor Tysse Mekaniske Verksted AS holds PCI DSS certification.

Neither Metzner nor Tysse Mekaniske Verksted AS holds HIPAA certification.

Neither Metzner nor Tysse Mekaniske Verksted AS 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