Comparison Overview

Oy Tamware AB

VS

Master Packing & Rubber Company

Oy Tamware AB

Yrittäjänkulma 5, Tampere, FI-33710, FI
Last Update: 2025-11-27
Between 700 and 749

Decades of experience in product development with customers have placed the company in the top drawer globally. Since 2008, our main focus has been on designing, developing and producing electronic door systems. Our goal is to provide our customers with a comprehensive partnership, working with them from design to maintenance. We look after our clients, even after delivery. We aim to develop long-term cooperation. Our headquarters and production site are located in Tampere, Finland.

NAICS: 3365
NAICS Definition: Railroad Rolling Stock Manufacturing
Employees: 19
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Master Packing & Rubber Company

6430 4th Street SW, Cedar Rapids, 52404, US
Last Update: 2025-11-27
Between 700 and 749

In today’s marketplace, when buyers need to find someone to supply them with pump and valve packings, gasket and specialty seals, they will find many companies from which to choose. Mechanical packings and gaskets have, after all, slowly evolved into “commodity type” products that are almost generic in nature. Many of the suppliers of these items will come with good credentials; records of cost savings for customers, quality products and good service. Like these competitors, Master Packing & Rubber Company also has a fine record of accomplishments and testimonials. But there is something else that we bring to the marketplace – commitment to our customers. We want our customers to know that we take their needs and problems seriously. That is why we are in business. We make no apologies. We are in business to be faithful and successful and we believe that it takes a day to day dedication to make it happen. This is a technical business and we believe we have a thorough knowledge of it. But that is not good enough. We know that we must constantly earn the right to serve you. People will come back to do business if the price is fair, the quality high, and the service is what you have a right to expect. We are committed to this way of doing business. We hope that there may be an opportunity to serve you in the near future.

NAICS: 3365
NAICS Definition: Railroad Rolling Stock Manufacturing
Employees: 18
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/oy-tamware-ab.jpeg
Oy Tamware AB
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/master-packing-&-rubber-company.jpeg
Master Packing & Rubber Company
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
Oy Tamware AB
100%
Compliance Rate
0/4 Standards Verified
Master Packing & Rubber Company
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Railroad Equipment Manufacturing Industry Average (This Year)

No incidents recorded for Oy Tamware AB in 2025.

Incidents vs Railroad Equipment Manufacturing Industry Average (This Year)

No incidents recorded for Master Packing & Rubber Company in 2025.

Incident History — Oy Tamware AB (X = Date, Y = Severity)

Oy Tamware AB cyber incidents detection timeline including parent company and subsidiaries

Incident History — Master Packing & Rubber Company (X = Date, Y = Severity)

Master Packing & Rubber Company cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/oy-tamware-ab.jpeg
Oy Tamware AB
Incidents

No Incident

https://images.rankiteo.com/companyimages/master-packing-&-rubber-company.jpeg
Master Packing & Rubber Company
Incidents

No Incident

FAQ

Both Oy Tamware AB company and Master Packing & Rubber Company company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Master Packing & Rubber Company company has disclosed a higher number of cyber incidents compared to Oy Tamware AB company.

In the current year, Master Packing & Rubber Company company and Oy Tamware AB company have not reported any cyber incidents.

Neither Master Packing & Rubber Company company nor Oy Tamware AB company has reported experiencing a ransomware attack publicly.

Neither Master Packing & Rubber Company company nor Oy Tamware AB company has reported experiencing a data breach publicly.

Neither Master Packing & Rubber Company company nor Oy Tamware AB company has reported experiencing targeted cyberattacks publicly.

Neither Oy Tamware AB company nor Master Packing & Rubber Company company has reported experiencing or disclosing vulnerabilities publicly.

Neither Oy Tamware AB nor Master Packing & Rubber Company holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Oy Tamware AB company nor Master Packing & Rubber Company company has publicly disclosed detailed information about the number of their subsidiaries.

Oy Tamware AB company employs more people globally than Master Packing & Rubber Company company, reflecting its scale as a Railroad Equipment Manufacturing.

Neither Oy Tamware AB nor Master Packing & Rubber Company holds SOC 2 Type 1 certification.

Neither Oy Tamware AB nor Master Packing & Rubber Company holds SOC 2 Type 2 certification.

Neither Oy Tamware AB nor Master Packing & Rubber Company holds ISO 27001 certification.

Neither Oy Tamware AB nor Master Packing & Rubber Company holds PCI DSS certification.

Neither Oy Tamware AB nor Master Packing & Rubber Company holds HIPAA certification.

Neither Oy Tamware AB nor Master Packing & Rubber Company 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