Comparison Overview

Smith Engineering Inc.

VS

MECAWA

Smith Engineering Inc.

4040 Norex Dr, Chaska, Minnesota, 55318, US
Last Update: 2025-11-27

Smith Engineering manufactures custom high purity water treatment equipment, supports all water treatment equipment with a fleet of field service technicians, and distributes products utilized in high purity process environments. Our manufacturing arm designs and builds treatment equipment with the precise requirements of our customer in mind. We offer no standard product line; our finished products are the result of process and purity requirements determined by our customer and our extensive knowledge of water purity requirements particular to given applications/industries. Medical Device, Biomedical and Microelectronics are key markets. Our service division is made up of veteran field technicians that average over 15 years of employment with the company. We offer on call and contracted service and are available to support your maintenance/repair requirements 24 hours a day, 7 days per week. Additionally, our route DI service represents a substantial portion of our service capability. Our in house regeneration plant allows us to quickly respond to all service requirements and provide ½ day service in most cases. Distributed Products have become a strength for Smith Engineering. Process Filtration and Piping, Instrumentation, Flow Control and Instrumentation, as well as Ultraviolet Technology make up only a portion of our distributed product offering. Most products are stocked in our Chaska, MN warehouse and available for same day shipping.

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

MECAWA

Rue Mandenne, Momignies, Région wallonne, BE, 6590
Last Update: 2025-11-27
Between 750 and 799

MECAWA est une entreprise familiale belge spécialisée dans la conception, la production et l'installation d'ensembles et sous-ensembles mécanosoudés pour divers secteurs d'activités. De dimension humaine, nous vous offrons une relation personnalisée pour assurer une souplesse d'action et une rapidité d'adaptation. Actifs depuis de nombreuses années dans divers secteurs industriels, tels que le ferroviaire, l'énergie, l'agroalimentaire, l'industrie, la construction,...nous nous spécialisons et positionnons, en réponse aux besoins de nos partenaires, sur des projets et produits spécifiques, sur mesure, à valeur ajoutée. ✔Un de nos principaux atouts se situe dans la prise en main complète de votre projet : • 1 interlocuteur fixe pour la relation commerciale • 1 chef de projet dédié à l'étude, la conception et la validation des plans avant mise en production • 1 interlocuteur pour les aspects de fabrication, qualité, logistique, pose sur chantier Pas, ou peu de sous-traitance, le processus est entièrement géré en interne, en notre pôle de production ✔Nos certificats forment la garantie de notre travail, de la qualité de votre projet. • Le système de management de la qualité de MECAWA a été audité et certifié selon les exigences de la norme ISO 9001: Version 2015 • MECAWA est certifié EN15085 classe 2 "Applications ferroviaires - soudage des véhicules et composants ferroviaire" • Par extension nous possédons également la certification EN1090 MECAWA collabore étroitement avec des organismes, auditeurs et techniciens pour la validation et certification de projets spécifiques.

NAICS: None
NAICS Definition: Others
Employees: 6
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/smith-engineering-inc-.jpeg
Smith Engineering Inc.
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/mecawa.jpeg
MECAWA
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
Smith Engineering Inc.
100%
Compliance Rate
0/4 Standards Verified
MECAWA
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 Smith Engineering Inc. in 2025.

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

No incidents recorded for MECAWA in 2025.

Incident History — Smith Engineering Inc. (X = Date, Y = Severity)

Smith Engineering Inc. cyber incidents detection timeline including parent company and subsidiaries

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

MECAWA cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/smith-engineering-inc-.jpeg
Smith Engineering Inc.
Incidents

No Incident

https://images.rankiteo.com/companyimages/mecawa.jpeg
MECAWA
Incidents

No Incident

FAQ

Both Smith Engineering Inc. company and MECAWA company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, MECAWA company has disclosed a higher number of cyber incidents compared to Smith Engineering Inc. company.

In the current year, MECAWA company and Smith Engineering Inc. company have not reported any cyber incidents.

Neither MECAWA company nor Smith Engineering Inc. company has reported experiencing a ransomware attack publicly.

Neither MECAWA company nor Smith Engineering Inc. company has reported experiencing a data breach publicly.

Neither MECAWA company nor Smith Engineering Inc. company has reported experiencing targeted cyberattacks publicly.

Neither Smith Engineering Inc. company nor MECAWA company has reported experiencing or disclosing vulnerabilities publicly.

Neither Smith Engineering Inc. nor MECAWA holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Smith Engineering Inc. company nor MECAWA company has publicly disclosed detailed information about the number of their subsidiaries.

Smith Engineering Inc. company employs more people globally than MECAWA company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither Smith Engineering Inc. nor MECAWA holds SOC 2 Type 1 certification.

Neither Smith Engineering Inc. nor MECAWA holds SOC 2 Type 2 certification.

Neither Smith Engineering Inc. nor MECAWA holds ISO 27001 certification.

Neither Smith Engineering Inc. nor MECAWA holds PCI DSS certification.

Neither Smith Engineering Inc. nor MECAWA holds HIPAA certification.

Neither Smith Engineering Inc. nor MECAWA 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