Comparison Overview
Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy

Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy
N/A
Last Update: 04/04/2026
Our mission is to Accelerate AI-enabled capabilities through strategic portfolio alignment while scaling Department-wide use cases that advance the agency’s core missions; advocate for program offices; lead responsible and trustworthy AI strategies; and expand public, p...

Social Security Administration
6401 Security Blvd, Baltimore, 21235, US
Last Update: 02/04/2026
Social Security provides financial protection for our nation’s people, supporting more than 64 million individuals and families. With retirement, disability, and survivors benefits, Social Security is one of the most successful anti-poverty programs in our nation's his...
Compliance Ranges Comparison

Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy







Social Security Administration






Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy in 2026.
Incidents vs Government Administration Industry Avg (This Year)
Social Security Administration has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy (X = Date, Y = Severity)
Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Social Security Administration (X = Date, Y = Severity)
Social Security Administration cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Artificial Intelligence and Technology Office (AITO), U.S. Department of Energy

Social Security 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.