Comparison Overview

Office for Budget Responsibility

VS

NOAA: National Oceanic & Atmospheric Administration

Office for Budget Responsibility

102 Petty France, London, SW1H 9AF, GB
Last Update: 2025-11-26
View Profile
Between 650 and 699
https://obr.uk/

The Office for Budget Responsibility (OBR) was established in May 2010 to provide independent assessments of the economy, public finances and fiscal sustainability. We provide independent forecasts of the economy and public finances, examine the impact of the Government's policy decisions on the public finances, and assess the prospects for achieving the Government's fiscal targets and welfare cap. We publish reports on long-term fiscal sustainability, fiscal risks and trends in welfare spending, and produce papers on economic and fiscal issues. Contact us at [email protected] or 02033346117

NAICS: 92
NAICS Definition: Public Administration
Employees: 52
Subsidiaries: 0
12-month incidents
1
Known data breaches
1
Attack type number
1
View Profile

NOAA: National Oceanic & Atmospheric Administration

1401 Constitution Avenue NW, Room 5128 HCHB, Washington, DC, US, 20230
Last Update: 2025-11-23
Between 750 and 799
http://www.noaa.gov

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 vitality and affect more than one-third of America’s gross domestic product. NOAA’s dedicated scientists use cutting-edge research and high-tech instrumentation to provide citizens, planners, emergency managers and other decision makers with reliable information they need when they need it. *Looking for your official local weather forecast? Enter your zip code at www.weather.gov or mobile.weather.gov for mobile device users. *Interested in working for NOAA? Find job openings by typing "NOAA" in the search field at www.USAjobs.gov. Connect with us on social media: Twitter: @NOAA Facebook: www.facebook.com/noaa Instagram: www.instagram.com/noaa YouTube: www.youtube.com/noaa LinkedIn: www.linkedin.com/company/noaa For a list of NOAA's major social media channels by mission area, please visit www.noaa.gov/stay-connected

NAICS: 92
NAICS Definition: Public Administration
Employees: 11,338
Subsidiaries: 21
12-month incidents
0
Known data breaches
1
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/office-for-budget-responsibility.jpeg
Office for Budget Responsibility
—
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/noaa.jpeg
NOAA: National Oceanic & Atmospheric Administration
—
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
Office for Budget Responsibility
100%
Compliance Rate
0/4 Standards Verified
NOAA: National Oceanic & Atmospheric Administration
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

Office for Budget Responsibility has 53.85% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for NOAA: National Oceanic & Atmospheric Administration in 2025.

Incident History — Office for Budget Responsibility (X = Date, Y = Severity)

Office for Budget Responsibility 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

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/office-for-budget-responsibility.jpeg
Office for Budget Responsibility
Incidents

Date Detected: 11/2025
Type:Breach
Motivation: Accidental (no malicious intent confirmed)
Blog: Blog
https://images.rankiteo.com/companyimages/noaa.jpeg
NOAA: National Oceanic & Atmospheric Administration
Incidents

Date Detected: 02/2017
Type:Breach
Attack Vector: SQL Injection
Motivation: Financial Gain
Blog: Blog

FAQ

NOAA: National Oceanic & Atmospheric Administration company demonstrates a stronger AI Cybersecurity Score compared to Office for Budget Responsibility company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Office for Budget Responsibility and NOAA: National Oceanic & Atmospheric Administration have experienced a similar number of publicly disclosed cyber incidents.

In the current year, Office for Budget Responsibility company has reported more cyber incidents than NOAA: National Oceanic & Atmospheric Administration company.

Neither NOAA: National Oceanic & Atmospheric Administration company nor Office for Budget Responsibility company has reported experiencing a ransomware attack publicly.

Both NOAA: National Oceanic & Atmospheric Administration company and Office for Budget Responsibility company have disclosed experiencing at least one data breach.

Neither NOAA: National Oceanic & Atmospheric Administration company nor Office for Budget Responsibility company has reported experiencing targeted cyberattacks publicly.

Neither Office for Budget Responsibility company nor NOAA: National Oceanic & Atmospheric Administration company has reported experiencing or disclosing vulnerabilities publicly.

Neither Office for Budget Responsibility nor NOAA: National Oceanic & Atmospheric Administration holds any compliance certifications.

Neither company holds any compliance certifications.

NOAA: National Oceanic & Atmospheric Administration company has more subsidiaries worldwide compared to Office for Budget Responsibility company.

NOAA: National Oceanic & Atmospheric Administration company employs more people globally than Office for Budget Responsibility company, reflecting its scale as a Government Administration.

Neither Office for Budget Responsibility nor NOAA: National Oceanic & Atmospheric Administration holds SOC 2 Type 1 certification.

Neither Office for Budget Responsibility nor NOAA: National Oceanic & Atmospheric Administration holds SOC 2 Type 2 certification.

Neither Office for Budget Responsibility nor NOAA: National Oceanic & Atmospheric Administration holds ISO 27001 certification.

Neither Office for Budget Responsibility nor NOAA: National Oceanic & Atmospheric Administration holds PCI DSS certification.

Neither Office for Budget Responsibility nor NOAA: National Oceanic & Atmospheric Administration holds HIPAA certification.

Neither Office for Budget Responsibility nor NOAA: National Oceanic & Atmospheric Administration 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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References