Comparison Overview

City of Cologne

VS

State of California

City of Cologne

DE
Last Update: 2025-12-10

Sie möchten sich neu ansiedeln, Ihren Betrieb erweitern oder Ihr Unternehmen verlagern. Sie suchen ein neues Grundstück oder eine Immobilie. Sie möchten ein gewerblich nutzbares Grundstück vermieten, verpachten oder veräußern. Sie haben ein Anliegen an die Stadtverwaltung (zum Beispiel Planungsrecht, Baugenehmigungen, Denkmalschutz, Grünausgleich etc.). Sie möchten Ihr Netzwerk erweitern und neue Kontakte in Köln knüpfen.

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

State of California

Sacramento, None, Sacramento, California, US, 95814
Last Update: 2025-12-09
Between 750 and 799

Californians deserve a government that works for them and with them. One that will work to ensure opportunity and justice. We are building a California not for the few, but for all — including those who have historically been left out. We are doing the work to make our state a place for every Californian and all the diversity that makes us strong. Our state will be known as a place where everyone is respected, protected, and connected.

NAICS: 92
NAICS Definition: Public Administration
Employees: 44,043
Subsidiaries: 29
12-month incidents
0
Known data breaches
28
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
City of Cologne
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-california.jpeg
State of California
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
City of Cologne
100%
Compliance Rate
0/4 Standards Verified
State of California
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for City of Cologne in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for State of California in 2025.

Incident History — City of Cologne (X = Date, Y = Severity)

City of Cologne cyber incidents detection timeline including parent company and subsidiaries

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

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

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
City of Cologne
Incidents

Date Detected: 10/2023
Type:Cyber Attack
Attack Vector: DDoS
Blog: Blog
https://images.rankiteo.com/companyimages/state-of-california.jpeg
State of California
Incidents

Date Detected: 1/2025
Type:Breach
Attack Vector: Inadvertent Email
Blog: Blog

Date Detected: 6/2024
Type:Breach
Attack Vector: Unauthorized Access
Blog: Blog

Date Detected: 2/2024
Type:Breach
Attack Vector: Unauthorized Dissemination
Blog: Blog

FAQ

State of California company demonstrates a stronger AI Cybersecurity Score compared to City of Cologne company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

State of California company has faced a higher number of disclosed cyber incidents historically compared to City of Cologne company.

In the current year, State of California company has reported more cyber incidents than City of Cologne company.

State of California company has confirmed experiencing a ransomware attack, while City of Cologne company has not reported such incidents publicly.

State of California company has disclosed at least one data breach, while City of Cologne company has not reported such incidents publicly.

City of Cologne company has reported targeted cyberattacks, while State of California company has not reported such incidents publicly.

Neither City of Cologne company nor State of California company has reported experiencing or disclosing vulnerabilities publicly.

Neither City of Cologne nor State of California holds any compliance certifications.

Neither company holds any compliance certifications.

State of California company has more subsidiaries worldwide compared to City of Cologne company.

State of California company employs more people globally than City of Cologne company, reflecting its scale as a Government Administration.

Neither City of Cologne nor State of California holds SOC 2 Type 1 certification.

Neither City of Cologne nor State of California holds SOC 2 Type 2 certification.

Neither City of Cologne nor State of California holds ISO 27001 certification.

Neither City of Cologne nor State of California holds PCI DSS certification.

Neither City of Cologne nor State of California holds HIPAA certification.

Neither City of Cologne nor State of California holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

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

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

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

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

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

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N