Comparison Overview

Environmental and Engineering Services Inc.

VS

BZKU

Environmental and Engineering Services Inc.

917 NW Grant Avenue, Corvallis, OR, 97330, US
Last Update: 2025-11-27

Founded in 1979, EESI provides cost-effective mechanical, electrical, and control engineering services, with a special emphasis in assessments, building systems remodel or renovation design, commissioning, and energy upgrades. Our team has the expertise required to provide efficient, low maintenance building system designs which provide safe and comfortable environments. With our main office centrally located in Corvallis and branch offices in Portland and Helix, we serve clients large and small throughout the Pacific Northwest. EESI is personalized enough for small projects, yet structured to handle large design and construction management projects.

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

BZKU

None
Last Update: 2025-11-27
Between 750 and 799

Наше предприятие – ОДО "Броварской завод коммунального оборудования" (БЗКО) – имеет 85-тилетнюю историю и на сегодняшний день является производителем отопительного оборудования под ТМ Ardenz. Продукция БЗКО изготавливается с использованием иностранных технологий и отвечает современным требованиям к энергосбережению, отличается простотой в монтаже и обслуживании. Сформировано специальное ценовое предложение для предприятий и учреждений на котлы ТМ Ardenz. Мы уверены, что наша продукция удовлетворит все Ваши требования к функциональности и надежности отопительного оборудования и оправдает ожидания по его стоимости, а в лице нашего предприятия Вы найдете надежного поставщика и партнера. Направления деятельности БЗКО: - изготовление, гарантийное и сервисное обслуживание отопительных котлов ТМ ARDENZ - изготовление металлоконструкций различной степени сложности, которые производятся как в единичном экземпляре, так и серийно - изготовление сальниковых компенсаторов - разработка новых проектов - порошковая, полимерная покраска

NAICS: None
NAICS Definition: Others
Employees: 5
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/environmental-and-engineering-services-inc-.jpeg
Environmental and Engineering Services 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/bzku.jpeg
BZKU
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
Environmental and Engineering Services Inc.
100%
Compliance Rate
0/4 Standards Verified
BZKU
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 Environmental and Engineering Services Inc. in 2025.

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

No incidents recorded for BZKU in 2025.

Incident History — Environmental and Engineering Services Inc. (X = Date, Y = Severity)

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

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

BZKU cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/environmental-and-engineering-services-inc-.jpeg
Environmental and Engineering Services Inc.
Incidents

No Incident

https://images.rankiteo.com/companyimages/bzku.jpeg
BZKU
Incidents

No Incident

FAQ

BZKU company demonstrates a stronger AI Cybersecurity Score compared to Environmental and Engineering Services Inc. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, BZKU company has disclosed a higher number of cyber incidents compared to Environmental and Engineering Services Inc. company.

In the current year, BZKU company and Environmental and Engineering Services Inc. company have not reported any cyber incidents.

Neither BZKU company nor Environmental and Engineering Services Inc. company has reported experiencing a ransomware attack publicly.

Neither BZKU company nor Environmental and Engineering Services Inc. company has reported experiencing a data breach publicly.

Neither BZKU company nor Environmental and Engineering Services Inc. company has reported experiencing targeted cyberattacks publicly.

Neither Environmental and Engineering Services Inc. company nor BZKU company has reported experiencing or disclosing vulnerabilities publicly.

Neither Environmental and Engineering Services Inc. nor BZKU holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Environmental and Engineering Services Inc. company nor BZKU company has publicly disclosed detailed information about the number of their subsidiaries.

Environmental and Engineering Services Inc. company employs more people globally than BZKU company, reflecting its scale as a Mechanical Or Industrial Engineering.

Neither Environmental and Engineering Services Inc. nor BZKU holds SOC 2 Type 1 certification.

Neither Environmental and Engineering Services Inc. nor BZKU holds SOC 2 Type 2 certification.

Neither Environmental and Engineering Services Inc. nor BZKU holds ISO 27001 certification.

Neither Environmental and Engineering Services Inc. nor BZKU holds PCI DSS certification.

Neither Environmental and Engineering Services Inc. nor BZKU holds HIPAA certification.

Neither Environmental and Engineering Services Inc. nor BZKU 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