Comparison Overview
Lansing Board of Water & Light

Lansing Board of Water & Light
1232 Haco Drive, Lansing, 48912, US
Last Update: 04/08/2026
The Board of Water & Light is a municipally owned public utility, not a private, investor-owned utility. Our roots go back to 1885, when Lansing citizens approved a $100,000 bond issue to build a water system to provide for drinking water and fire protection. Electricit...

EDP
Av. 24 de Julho, Lisboa, 1249 - 300, PT
Last Update: 01/04/2026
Our story began 50 years ago. Today, we are a global energy company leading the transition to a more sustainable future. We produce and deliver electricity to millions of families, businesses and communities worldwide, with a strong focus on renewable energy. More than...
Compliance Ranges Comparison

Lansing Board of Water & Light







EDP






Benchmark & Cyber Underwriting Signals
Incidents vs Utilities Industry Avg (This Year)
Lansing Board of Water & Light has 45.95% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Utilities Industry Avg (This Year)
No incidents recorded for EDP in 2026.
Incident History - Lansing Board of Water & Light (X = Date, Y = Severity)
Lansing Board of Water & Light cyber incidents detection timeline including parent company and subsidiaries.
Incident History - EDP (X = Date, Y = Severity)
EDP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Lansing Board of Water & Light

EDP
FAQ
Latest Global CVEs
A vulnerability has been found in SourceCodester Simple Online Food Ordering System 1.0. This affects an unknown function of the file /admin/ajax.php?action=login2. The manipulation of the argument email leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used.
A flaw was found in the ipa_getkeytab module of the community.general Ansible collection. The module's bind_pw parameter, used to supply the LDAP simple-bind password when retrieving a Kerberos keytab, is not declared with no_log, unlike the sibling password parameter in the same module. As a consequence, the supplied IPA/LDAP bind password is recorded in cleartext in the managed host's system journal/syslog (the module's "Invoked with" record), is included in the module's return values and verbose (-v) output, and is displayed in Automation Controller / AWX job output. The password is additionally passed on the command line to the ipa-getkeytab helper (as --bindpw <value>), exposing it in the process list to local users while the command runs. An attacker able to read these logs, job output, or the process table can obtain the directory bind credential, potentially compromising the accounts and objects that credential can access.
The device metadata import interface /device/instance/{productId}/property-metadata/import of jetlinks community 2.11 is vulnerable to Server-side request forgery (SSRF).
disconf (Distributed Configuration Management Platform) 2.6.36 is vulnerable to Incorrect Access Control. The config-fetching APIs /api/config/item, /api/config/file, /api/config/list and /api/config/simple/list are exposed without authentication. The LoginInterceptor explicitly whitelists these four paths, so any anonymous attacker can read every configuration item and configuration file managed by the config center.
Funiture 1.0.0 is vulnerable to SQL Injection in the backend tool interfaces /sys/tool/select.json and /sys/tool/update.json.