Comparison Overview

I work for NSW

VS

U.S. Department of the Treasury

I work for NSW

undefined, Sydney, NSW, 2000, AU
Last Update: 2025-11-25
View Profile
Between 750 and 799
http://iworkfor.nsw.gov.au/

The NSW public sector includes ten departments and many agencies and organisations working together to develop policy and deliver important services such as health, education, housing, transport and infrastructure across NSW. We are over 300,000 dedicated people who share the same values - making a difference, giving back and responding to the future. Read our community guidelines: bit.ly/PD-community-guidelines

NAICS: 92
NAICS Definition: Public Administration
Employees: 59,726
Subsidiaries: 17
12-month incidents
0
Known data breaches
1
Attack type number
4
View Profile

U.S. Department of the Treasury

1500 Pennsylvania Ave NW, Washington, DC, US, 20005
Last Update: 2025-11-24
Between 0 and 549
https://home.treasury.gov/

The Treasury Department is the executive agency responsible for promoting economic prosperity and ensuring the financial security of the United States. The Department is responsible for a wide range of activities such as advising the President on economic and financial issues, encouraging sustainable economic growth, and fostering improved governance in financial institutions. The Department of the Treasury operates and maintains systems that are critical to the nation's financial infrastructure, such as the production of coin and currency, the disbursement of payments to the American public, revenue collection, and the borrowing of funds necessary to run the federal government. The Department works with other federal agencies, foreign governments, and international financial institutions to encourage global economic growth, raise standards of living, and to the extent possible, predict and prevent economic and financial crises. The Treasury Department also performs a critical and far-reaching role in enhancing national security by implementing economic sanctions against foreign threats to the U.S., identifying and targeting the financial support networks of national security threats, and improving the safeguards of our financial systems.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/nsw-government.jpeg
I work for NSW
—
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/us-treasury.jpeg
U.S. Department of the Treasury
—
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
I work for NSW
100%
Compliance Rate
0/4 Standards Verified
U.S. Department of the Treasury
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for I work for NSW in 2025.

Incidents vs Government Administration Industry Average (This Year)

U.S. Department of the Treasury has 669.23% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — I work for NSW (X = Date, Y = Severity)

I work for NSW cyber incidents detection timeline including parent company and subsidiaries

Incident History — U.S. Department of the Treasury (X = Date, Y = Severity)

U.S. Department of the Treasury cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/nsw-government.jpeg
I work for NSW
Incidents

Date Detected: 02/2022
Type:Breach
Attack Vector: Accidental Exposure
Blog: Blog

Date Detected: 07/2021
Type:Cyber Attack
Blog: Blog

Date Detected: 02/2021
Type:Data Leak
Attack Vector: Exploitation of Vulnerability
Blog: Blog
https://images.rankiteo.com/companyimages/us-treasury.jpeg
U.S. Department of the Treasury
Incidents

Date Detected: 8/2025
Type:Cyber Attack
Attack Vector: exploitation of trusted cloud relationships (SaaS providers, Microsoft CSPs), zero-day vulnerabilities (e.g., Citrix NetScaler CVE-2023-3519, Ivanti Pulse Connect CVE-2025-0282), ProxyLogon (Microsoft Exchange), compromised SOHO devices as proxies, web shells (Neo-reGeorg, China Chopper), custom Linux RAT (CloudedHope)
Motivation: cyberespionage (targeting government, technology, legal, and professional services for sensitive data)
Blog: Blog

Date Detected: 3/2025
Type:Breach
Motivation: Espionage, Strategic Advantage
Blog: Blog

Date Detected: 1/2025
Type:Breach
Attack Vector: Exploited flaws in BeyondTrust software
Motivation: Data Theft
Blog: Blog

FAQ

I work for NSW company demonstrates a stronger AI Cybersecurity Score compared to U.S. Department of the Treasury company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

U.S. Department of the Treasury company has faced a higher number of disclosed cyber incidents historically compared to I work for NSW company.

In the current year, U.S. Department of the Treasury company has reported more cyber incidents than I work for NSW company.

I work for NSW company has confirmed experiencing a ransomware attack, while U.S. Department of the Treasury company has not reported such incidents publicly.

Both U.S. Department of the Treasury company and I work for NSW company have disclosed experiencing at least one data breach.

Both U.S. Department of the Treasury company and I work for NSW company have reported experiencing targeted cyberattacks.

Neither I work for NSW company nor U.S. Department of the Treasury company has reported experiencing or disclosing vulnerabilities publicly.

Neither I work for NSW nor U.S. Department of the Treasury holds any compliance certifications.

Neither company holds any compliance certifications.

I work for NSW company has more subsidiaries worldwide compared to U.S. Department of the Treasury company.

I work for NSW company employs more people globally than U.S. Department of the Treasury company, reflecting its scale as a Government Administration.

Neither I work for NSW nor U.S. Department of the Treasury holds SOC 2 Type 1 certification.

Neither I work for NSW nor U.S. Department of the Treasury holds SOC 2 Type 2 certification.

Neither I work for NSW nor U.S. Department of the Treasury holds ISO 27001 certification.

Neither I work for NSW nor U.S. Department of the Treasury holds PCI DSS certification.

Neither I work for NSW nor U.S. Department of the Treasury holds HIPAA certification.

Neither I work for NSW nor U.S. Department of the Treasury 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