Comparison Overview

State of Tennessee

VS

Workingfor.be

State of Tennessee

US
Last Update: 2026-01-17
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: 15,294
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Workingfor.be

Simon Bolivarlaan 30, Bld. Simon Bolivar 30, Brussels, Brabant, BE, 1000
Last Update: 2026-01-18
Between 750 and 799

Workingfor.be is the job platform of the federal administration. Here, you will find a wide variety of jobs in different fields of profession. Every day thousands of our employees help build tomorrow's society. When you choose the federal administration, you choose an employer who embraces your talent and individuality and gives you the opportunity to develop yourself and your skills further every single day. Moreover, we offer you a job where you can easily find the balance between your professional and personal life. Do you want to contribute to the Belgium of tomorrow? Feel like making a difference and developing your talents? Discover our wide range of vacancies at www.workingfor.be

NAICS: 92
NAICS Definition: Public Administration
Employees: 17,078
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/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
https://images.rankiteo.com/companyimages/workingforbe.jpeg
Workingfor.be
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
State of Tennessee
100%
Compliance Rate
0/4 Standards Verified
Workingfor.be
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for State of Tennessee in 2026.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Workingfor.be in 2026.

Incident History — State of Tennessee (X = Date, Y = Severity)

State of Tennessee cyber incidents detection timeline including parent company and subsidiaries

Incident History — Workingfor.be (X = Date, Y = Severity)

Workingfor.be cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/state-of-tennessee.jpeg
State of Tennessee
Incidents

No Incident

https://images.rankiteo.com/companyimages/workingforbe.jpeg
Workingfor.be
Incidents

No Incident

FAQ

State of Tennessee company demonstrates a stronger AI Cybersecurity Score compared to Workingfor.be company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Workingfor.be company has disclosed a higher number of cyber incidents compared to State of Tennessee company.

In the current year, Workingfor.be company and State of Tennessee company have not reported any cyber incidents.

Neither Workingfor.be company nor State of Tennessee company has reported experiencing a ransomware attack publicly.

Neither Workingfor.be company nor State of Tennessee company has reported experiencing a data breach publicly.

Neither Workingfor.be company nor State of Tennessee company has reported experiencing targeted cyberattacks publicly.

Neither State of Tennessee company nor Workingfor.be company has reported experiencing or disclosing vulnerabilities publicly.

Neither State of Tennessee nor Workingfor.be holds any compliance certifications.

Neither company holds any compliance certifications.

Neither State of Tennessee company nor Workingfor.be company has publicly disclosed detailed information about the number of their subsidiaries.

Workingfor.be company employs more people globally than State of Tennessee company, reflecting its scale as a Government Administration.

Neither State of Tennessee nor Workingfor.be holds SOC 2 Type 1 certification.

Neither State of Tennessee nor Workingfor.be holds SOC 2 Type 2 certification.

Neither State of Tennessee nor Workingfor.be holds ISO 27001 certification.

Neither State of Tennessee nor Workingfor.be holds PCI DSS certification.

Neither State of Tennessee nor Workingfor.be holds HIPAA certification.

Neither State of Tennessee nor Workingfor.be holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/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

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Risk Information
cvss3
Base: 8.1
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H