Comparison Overview

Bell Electric

VS

International Brotherhood of Electrical Workers (IBEW)

Bell Electric

75 Rainmaker Dr, B, Portland, Maine, US, 04103
Last Update: 2025-12-17
Between 650 and 699

Founded in 2016 by Stephen Bell, Bell Electric is a premier electrical company based in South Portland, ME, dedicated to delivering excellence across residential, commercial, and generator electrical services. With over 18 years of industry experience and master electrician credentials in multiple states, Stephen Bell brings a wealth of expertise to every project. At Bell Electric, we specialize in new home installations, remodeling projects, and commercial electrical solutions, including a focus on Generac generators to ensure your power needs are always met. Our commitment to exceeding industry standards drives us to provide high-quality work and exceptional service, tailored to meet the unique needs of each client. Trust Bell Electric for reliable, top-class electrical services that power your home or business with precision and care. Specializing in new homes, remodels, and commercial projects, Stephen and the Bell Electric crew guarantee work that will not only meet your needs but surpass all expectations, covering all project phases from design and planning to executing and building the vision. Going above and beyond industry standards, Bell Electric is committed to putting out only the highest quality work, and providing top-class service to our customers, no matter the job!

NAICS: 23
NAICS Definition: Construction
Employees: 8
Subsidiaries: 0
12-month incidents
1
Known data breaches
0
Attack type number
1

International Brotherhood of Electrical Workers (IBEW)

900 7th Street, NW, Washington, DC, US, 20001
Last Update: 2025-12-17
Between 700 and 749

The IBEW represents 860,000 active. and retired who work in a wide variety of fields, including utilities, construction, telecommunications, broadcasting, manufacturing, railroads and government. The IBEW has members in both the United States and Canada and stands out among the American unions in the AFL-CIO because it is among the largest and has members in so many skilled occupations. As union members, we bargain collectively with our employers over wages, benefits, and rights. Most of us have very limited bargaining power as one person, but as a group, we are strong. And, with a good negotiated contract, we have legal protections we would not have otherwise. Follow us on: Twitter: https://twitter.com/IBEW Facebook: https://www.facebook.com/IBEWFB YouTube: http://www.youtube.com/user/TheElectricalWorker

NAICS: 23
NAICS Definition: Construction
Employees: 12,643
Subsidiaries: 0
12-month incidents
1
Known data breaches
2
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/bell-electric207.jpeg
Bell Electric
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/ibew.jpeg
International Brotherhood of Electrical Workers (IBEW)
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
Bell Electric
100%
Compliance Rate
0/4 Standards Verified
International Brotherhood of Electrical Workers (IBEW)
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Construction Industry Average (This Year)

Bell Electric has 4.17% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Construction Industry Average (This Year)

International Brotherhood of Electrical Workers (IBEW) has 4.17% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — Bell Electric (X = Date, Y = Severity)

Bell Electric cyber incidents detection timeline including parent company and subsidiaries

Incident History — International Brotherhood of Electrical Workers (IBEW) (X = Date, Y = Severity)

International Brotherhood of Electrical Workers (IBEW) cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bell-electric207.jpeg
Bell Electric
Incidents

Date Detected: 3/2025
Type:Ransomware
Motivation: Financial (Ransom)
Blog: Blog
https://images.rankiteo.com/companyimages/ibew.jpeg
International Brotherhood of Electrical Workers (IBEW)
Incidents

Date Detected: 8/2025
Type:Breach
Blog: Blog

Date Detected: 12/2012
Type:Breach
Attack Vector: Inadvertent Disclosure
Blog: Blog

FAQ

International Brotherhood of Electrical Workers (IBEW) company demonstrates a stronger AI Cybersecurity Score compared to Bell Electric company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

International Brotherhood of Electrical Workers (IBEW) company has faced a higher number of disclosed cyber incidents historically compared to Bell Electric company.

In the current year, International Brotherhood of Electrical Workers (IBEW) and Bell Electric have reported a similar number of cyber incidents.

Bell Electric company has confirmed experiencing a ransomware attack, while International Brotherhood of Electrical Workers (IBEW) company has not reported such incidents publicly.

International Brotherhood of Electrical Workers (IBEW) company has disclosed at least one data breach, while Bell Electric company has not reported such incidents publicly.

Neither International Brotherhood of Electrical Workers (IBEW) company nor Bell Electric company has reported experiencing targeted cyberattacks publicly.

Neither Bell Electric company nor International Brotherhood of Electrical Workers (IBEW) company has reported experiencing or disclosing vulnerabilities publicly.

Neither Bell Electric nor International Brotherhood of Electrical Workers (IBEW) holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Bell Electric company nor International Brotherhood of Electrical Workers (IBEW) company has publicly disclosed detailed information about the number of their subsidiaries.

International Brotherhood of Electrical Workers (IBEW) company employs more people globally than Bell Electric company, reflecting its scale as a Construction.

Neither Bell Electric nor International Brotherhood of Electrical Workers (IBEW) holds SOC 2 Type 1 certification.

Neither Bell Electric nor International Brotherhood of Electrical Workers (IBEW) holds SOC 2 Type 2 certification.

Neither Bell Electric nor International Brotherhood of Electrical Workers (IBEW) holds ISO 27001 certification.

Neither Bell Electric nor International Brotherhood of Electrical Workers (IBEW) holds PCI DSS certification.

Neither Bell Electric nor International Brotherhood of Electrical Workers (IBEW) holds HIPAA certification.

Neither Bell Electric nor International Brotherhood of Electrical Workers (IBEW) holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Zerobyte is a backup automation tool Zerobyte versions prior to 0.18.5 and 0.19.0 contain an authentication bypass vulnerability where authentication middleware is not properly applied to API endpoints. This results in certain API endpoints being accessible without valid session credentials. This is dangerous for those who have exposed Zerobyte to be used outside of their internal network. A fix has been applied in both version 0.19.0 and 0.18.5. If immediate upgrade is not possible, restrict network access to the Zerobyte instance to trusted networks only using firewall rules or network segmentation. This is only a temporary mitigation; upgrading is strongly recommended.

Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description

Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter framework. Starting in version 3.4.0 and prior to version 3.4.2, a Cross-Site Request Forgery (CSRF) vulnerability exists in the application's filter configuration. The CSRF protection mechanism was **explicitly disabled**, allowing the application to process state-changing requests (POST) without verifying a valid CSRF token. An unauthenticated remote attacker can exploit this by hosting a malicious web page. If a logged-in administrator visits this page, their browser is forced to send unauthorized requests to the application. A successful exploit allows the attacker to silently create a new Administrator account with full privileges, leading to a complete takeover of the system and loss of confidentiality, integrity, and availability. The vulnerability has been patched in version 3.4.2. The fix re-enables the CSRF filter in `app/Config/Filters.php` and resolves associated AJAX race conditions by adjusting token regeneration settings. As a workaround, administrators can manually re-enable the CSRF filter in `app/Config/Filters.php` by uncommenting the protection line. However, this is not recommended without applying the full patch, as it may cause functionality breakage in the Sales module due to token synchronization issues.

Risk Information
cvss3
Base: 8.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Description

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Model Context Protocol (MCP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious MCP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered automatically without any user interaction besides opening the project in the IDE. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Language Server Protocol (LSP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious LSP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered when a user opens project file for which there is an LSP entry. A concerted effort by an attacker to seed a project settings file (`./zed/settings.json`) with malicious language server configurations could result in arbitrary code execution with the user's privileges if the user opens the project in Zed without reviewing the contents. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of environment variables defined in a `.env` file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the `storybook build` command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly) in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than `.env` files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with `STORYBOOK_` or use the `env` property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

Risk Information
cvss3
Base: 7.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L