Comparison Overview
Grid Deployment Office | U.S. Department of Energy

Grid Deployment Office | U.S. Department of Energy
N/A
Last Update: 05/04/2026
The U.S. Department of Energy’s Grid Deployment Office (GDO) works to catalyze the development of new and upgraded electric infrastructure across the country by maintaining and investing in critical generation facilities; developing and upgrading high-capacity electric ...

NOAA: National Oceanic & Atmospheric Administration
1401 Constitution Avenue NW, Washington, 20230, US
Last Update: 04/04/2026
Welcome! We're the National Oceanic & Atmospheric Administration or NOAA. From daily weather forecasts, severe storm warnings and climate monitoring to fisheries management, coastal restoration and supporting marine commerce, our products and services support economic ...
Compliance Ranges Comparison

Grid Deployment Office | U.S. Department of Energy







NOAA: National Oceanic & Atmospheric Administration






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Grid Deployment Office | U.S. Department of Energy in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for NOAA: National Oceanic & Atmospheric Administration in 2026.
Incident History - Grid Deployment Office | U.S. Department of Energy (X = Date, Y = Severity)
Grid Deployment Office | U.S. Department of Energy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NOAA: National Oceanic & Atmospheric Administration (X = Date, Y = Severity)
NOAA: National Oceanic & Atmospheric Administration cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Grid Deployment Office | U.S. Department of Energy

NOAA: National Oceanic & Atmospheric Administration
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.