Comparison Overview

Breezy Med

VS

Bürkert Türkiye

Breezy Med

317 Commercial St NE, Suite 102, Albuquerque, New Mexico, US, 87102
Last Update: 2025-11-21
Between 750 and 799

Breezy Med delivers smart, science-backed automation for hospital infection prevention. Our flagship Breezy Blue system uses EPA-registered aerosolized hydrogen peroxide (aHP) to achieve whole-room disinfection with push-button simplicity—no manual labor, no missed spots, and no UV limitations. Designed for terminal cleaning and high-risk areas, Breezy Blue outperforms legacy UV systems in efficacy, usability, and cost—at a fraction of the price. Our Breezy Cloud platform gives infection preventionists, EVS leaders, and executives real-time data for compliance, tracking, and continuous improvement. Hospitals choose Breezy Med to reduce healthcare-associated infections (HAIs), protect patients and staff, and modernize disinfection with technology that works as hard as they do.

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

Bürkert Türkiye

Halkapınar Mahallesi 1082 Sokak No:5-S , İzmir , 35170, TR
Last Update: 2025-11-26
Between 750 and 799

Akışkan kontrol ve ölçüm sistem çözümlerinde önde gelen firma olan Bürkert. 60 yılı aşan deneyimiyle sıvıların ve gazların kontrolünü sağlamaktadır. Ölçüm ve kontrol alanında akan her şey bizi büyülemekte ve hiç şüphesiz, bu büyülenme bizim Akışkan Kontrol alanında dünya lideri olmamızı mümkün kılmaktadır. Aynı zamanda, güçlü değerlerine bağlılığını kaybetmeden kendini yenilemekte, partnerlerine yakınlığı sayesinde her gün gelişen esnek bir organizasyon yaratmaktadır. Bürkert olarak, tüm segmentlerde proseslerimizin sürekli optimizasyonu eşliğinde giderek genişleyen küresel ağımız, deneyimimizi doğrudan paylaşmamızı ve ortak çözümlerimizi daha hızlı ve etkin biçimde geliştirmemizi mümkün kılmaktadır. Sistem çözümleri, aynı zamanda belirli sektörlerin kısıtlı alanlarının ötesine geçmek ve alışık olunmayan problemlere seçkin çözümler sunmak için bizi motive etmektedir. Sanayi ihtiyaçlarının segmentasyonu, Bürkert’in standartlardan sapma yolundaki özel cesaretinin bir başka örneğidir. Bu durum; ürün-bazlı çözümlere bakış açımızı kaybetmeksizin, partnerlerimize sağladığımız özel çözümler ile maksimum avantaj sunmamızı mümkün kılmaktadır. Bürkert dünyasına hoş geldiniz!

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/breezy-bwr.jpeg
Breezy Med
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/burkertturkiye.jpeg
Bürkert Türkiye
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
Breezy Med
100%
Compliance Rate
0/4 Standards Verified
Bürkert Türkiye
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Breezy Med in 2025.

Incidents vs Industrial Automation Industry Average (This Year)

No incidents recorded for Bürkert Türkiye in 2025.

Incident History — Breezy Med (X = Date, Y = Severity)

Breezy Med cyber incidents detection timeline including parent company and subsidiaries

Incident History — Bürkert Türkiye (X = Date, Y = Severity)

Bürkert Türkiye cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/breezy-bwr.jpeg
Breezy Med
Incidents

No Incident

https://images.rankiteo.com/companyimages/burkertturkiye.jpeg
Bürkert Türkiye
Incidents

No Incident

FAQ

Both Breezy Med company and Bürkert Türkiye company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Bürkert Türkiye company has disclosed a higher number of cyber incidents compared to Breezy Med company.

In the current year, Bürkert Türkiye company and Breezy Med company have not reported any cyber incidents.

Neither Bürkert Türkiye company nor Breezy Med company has reported experiencing a ransomware attack publicly.

Neither Bürkert Türkiye company nor Breezy Med company has reported experiencing a data breach publicly.

Neither Bürkert Türkiye company nor Breezy Med company has reported experiencing targeted cyberattacks publicly.

Neither Breezy Med company nor Bürkert Türkiye company has reported experiencing or disclosing vulnerabilities publicly.

Neither Breezy Med nor Bürkert Türkiye holds any compliance certifications.

Neither company holds any compliance certifications.

Bürkert Türkiye company has more subsidiaries worldwide compared to Breezy Med company.

Breezy Med company employs more people globally than Bürkert Türkiye company, reflecting its scale as a Industrial Automation.

Neither Breezy Med nor Bürkert Türkiye holds SOC 2 Type 1 certification.

Neither Breezy Med nor Bürkert Türkiye holds SOC 2 Type 2 certification.

Neither Breezy Med nor Bürkert Türkiye holds ISO 27001 certification.

Neither Breezy Med nor Bürkert Türkiye holds PCI DSS certification.

Neither Breezy Med nor Bürkert Türkiye holds HIPAA certification.

Neither Breezy Med nor Bürkert Türkiye 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