Comparison Overview

AT SCHWEISSTECHNIK GmbH

VS

Polymaster

AT SCHWEISSTECHNIK GmbH

Bad Marienberg, DE
Last Update: 2025-11-27

AT SCHWEISSTECHNIK GmbH ist seit über zehn Jahren kompetenter Partner auf dem Gebiet der Schweißtechnik im Verschleißschutz und der Instandhaltung und Reparatur für Recycling- und Schredder-Anlagen, Kies- und Sandgruben, Steinbruch- und Bergbaubetriebe, Asphaltmischwerke, Stahl- und Eisenwerke, Fertigbeton- und Zementanlagen sowie Wärme- und Biomassekraftwerke und Verbrennungsanlagen. Unser Motto: BEST PROTECTION FOR A LONG LIFETIME. Nutzen Sie unsere Erfahrung. Wir bieten Ihnen von der Anlageninstandhaltung mit originalen und optimierten Verschleißteilen über die Inbetriebnahme bis zu dem richtigen Verschleißschutz alles aus einer Hand.

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

Polymaster

161 Karinie St, Swan Hill, 3585, AU
Last Update: 2025-11-27

We are a thriving Australian-owned and operated company based in regional Victoria, with our head office based in regional Victoria and offices/facilities represented in all states. We've been in business since 1994 manufacturing a diverse range of Australian-made storage products for industries, including agriculture, mining, food and beverage, chemical, and water authorities. We deliver excellence in liquid storage through innovative designs, quality product and superior customer service. In everything we do, we aim to be ‘the standard’ and choice for liquid storage.

NAICS: None
NAICS Definition: Others
Employees: 54
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/at-schweisstechnik-gmbh.jpeg
AT SCHWEISSTECHNIK GmbH
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/polymaster-group.jpeg
Polymaster
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
AT SCHWEISSTECHNIK GmbH
100%
Compliance Rate
0/4 Standards Verified
Polymaster
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 AT SCHWEISSTECHNIK GmbH in 2025.

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

No incidents recorded for Polymaster in 2025.

Incident History — AT SCHWEISSTECHNIK GmbH (X = Date, Y = Severity)

AT SCHWEISSTECHNIK GmbH cyber incidents detection timeline including parent company and subsidiaries

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

Polymaster cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/at-schweisstechnik-gmbh.jpeg
AT SCHWEISSTECHNIK GmbH
Incidents

No Incident

https://images.rankiteo.com/companyimages/polymaster-group.jpeg
Polymaster
Incidents

No Incident

FAQ

AT SCHWEISSTECHNIK GmbH company demonstrates a stronger AI Cybersecurity Score compared to Polymaster company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Polymaster company has disclosed a higher number of cyber incidents compared to AT SCHWEISSTECHNIK GmbH company.

In the current year, Polymaster company and AT SCHWEISSTECHNIK GmbH company have not reported any cyber incidents.

Neither Polymaster company nor AT SCHWEISSTECHNIK GmbH company has reported experiencing a ransomware attack publicly.

Neither Polymaster company nor AT SCHWEISSTECHNIK GmbH company has reported experiencing a data breach publicly.

Neither Polymaster company nor AT SCHWEISSTECHNIK GmbH company has reported experiencing targeted cyberattacks publicly.

Neither AT SCHWEISSTECHNIK GmbH company nor Polymaster company has reported experiencing or disclosing vulnerabilities publicly.

Neither AT SCHWEISSTECHNIK GmbH nor Polymaster holds any compliance certifications.

Neither company holds any compliance certifications.

Neither AT SCHWEISSTECHNIK GmbH company nor Polymaster company has publicly disclosed detailed information about the number of their subsidiaries.

Polymaster company employs more people globally than AT SCHWEISSTECHNIK GmbH company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither AT SCHWEISSTECHNIK GmbH nor Polymaster holds SOC 2 Type 1 certification.

Neither AT SCHWEISSTECHNIK GmbH nor Polymaster holds SOC 2 Type 2 certification.

Neither AT SCHWEISSTECHNIK GmbH nor Polymaster holds ISO 27001 certification.

Neither AT SCHWEISSTECHNIK GmbH nor Polymaster holds PCI DSS certification.

Neither AT SCHWEISSTECHNIK GmbH nor Polymaster holds HIPAA certification.

Neither AT SCHWEISSTECHNIK GmbH nor Polymaster 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