Comparison Overview

Office for Budget Responsibility

VS

State of Tennessee

Office for Budget Responsibility

102 Petty France, London, SW1H 9AF, GB
Last Update: 2025-11-26
Between 650 and 699

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

State of Tennessee

undefined, undefined, undefined, undefined, US
Last Update: 2025-11-26
Between 750 and 799

State government is the largest employer in Tennessee, with approximately 43,500 employees in the three branches of government. The State of Tennessee has approximately 1,300 different job classifications in areas such as administrative, health services, historic preservation, legal, agriculture, counseling, and medical. If you are interested in becoming a data scientist, attorney, nurse, wildlife officer, physician, education consultant, trooper, computer programmer or an epidemiologist, explore all of the job opportunities the State of Tennessee has to offer. The State is looking to recruit, retain, and reward a talented workforce through the implementation of a merit-based pay system. Stop back often for news, updates and opportunities -- thanks for visiting!

NAICS: 92
NAICS Definition: Public Administration
Employees: 14,624
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

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/state-of-tennessee.jpeg
State of Tennessee
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
State of Tennessee
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 State of Tennessee 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 — State of Tennessee (X = Date, Y = Severity)

State of Tennessee 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/state-of-tennessee.jpeg
State of Tennessee
Incidents

No Incident

FAQ

State of Tennessee 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 company has historically faced a number of disclosed cyber incidents, whereas State of Tennessee company has not reported any.

In the current year, Office for Budget Responsibility company has reported more cyber incidents than State of Tennessee company.

Neither State of Tennessee company nor Office for Budget Responsibility company has reported experiencing a ransomware attack publicly.

Office for Budget Responsibility company has disclosed at least one data breach, while the other State of Tennessee company has not reported such incidents publicly.

Neither State of Tennessee company nor Office for Budget Responsibility company has reported experiencing targeted cyberattacks publicly.

Neither Office for Budget Responsibility company nor State of Tennessee company has reported experiencing or disclosing vulnerabilities publicly.

Neither Office for Budget Responsibility nor State of Tennessee holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Office for Budget Responsibility company nor State of Tennessee company has publicly disclosed detailed information about the number of their subsidiaries.

State of Tennessee company employs more people globally than Office for Budget Responsibility company, reflecting its scale as a Government Administration.

Neither Office for Budget Responsibility nor State of Tennessee holds SOC 2 Type 1 certification.

Neither Office for Budget Responsibility nor State of Tennessee holds SOC 2 Type 2 certification.

Neither Office for Budget Responsibility nor State of Tennessee holds ISO 27001 certification.

Neither Office for Budget Responsibility nor State of Tennessee holds PCI DSS certification.

Neither Office for Budget Responsibility nor State of Tennessee holds HIPAA certification.

Neither Office for Budget Responsibility nor State of Tennessee 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.

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

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

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

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

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