Comparison Overview

Analytical Center for the Government of the Russian Federation

VS

Gemeente Zutphen

Analytical Center for the Government of the Russian Federation

12 Prospekt Akademika Sakharova, Moscow, RU, 107078
Last Update: 2025-11-25
Between 700 and 749

Analytical Center for the Government of the Russian Federation is a Moscow-based think-tank providing real-time information and analytical support to the Government, dealing with independent analysis and forecast studies of the social and economic situation in Russia and the world, giving recommendations and proposals on priority issues of policies and reforms to the senior decision-makers. An essential part of Analytical Center’s activities is international expert networking which serves to attracting high-profile experts to independent policy-relevant research, analysis and discussion, and providing time-sensitive expert opinion on actual issues.

NAICS: 921
NAICS Definition: Executive, Legislative, and Other General Government Support
Employees: 48
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Gemeente Zutphen

's-Gravenhof 2, Zutphen, Gelderland, NL, 7201 DN
Last Update: 2025-11-27
Between 700 and 749

Bij ons werk je niet alleen aan een nog mooiere gemeente Zutphen. Je werkt ook aan jezelf, aan je ontwikkeling als professional. Dat vraagt het vermogen tot aanpassing. Beweging is overal in en rond Zutphen. De wereld verandert. Inwoners en ondernemers stellen nieuwe vragen, waar wij als bestuurlijke organisatie graag op inspelen. Dat doen we als gelijkwaardige partners in een netwerksamenleving. Dat vraagt initiatief, mensen die de regie durven nemen. Iemand als jij? Te midden van verandering is jouw bekwaamheid ons anker: je talent, kennis en professionaliteit. Samenwerking verbindt al die goede krachten stevig aan elkaar. Samenwerking in het werk voor onze inwoners en ondernemers én samenwerking in je persoonlijke groei.

NAICS: 921
NAICS Definition: Executive, Legislative, and Other General Government Support
Employees: 373
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/analytical-center-for-the-government-of-the-russian-federation.jpeg
Analytical Center for the Government of the Russian Federation
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/gemeente-zutphen.jpeg
Gemeente Zutphen
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
Analytical Center for the Government of the Russian Federation
100%
Compliance Rate
0/4 Standards Verified
Gemeente Zutphen
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for Analytical Center for the Government of the Russian Federation in 2025.

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for Gemeente Zutphen in 2025.

Incident History — Analytical Center for the Government of the Russian Federation (X = Date, Y = Severity)

Analytical Center for the Government of the Russian Federation cyber incidents detection timeline including parent company and subsidiaries

Incident History — Gemeente Zutphen (X = Date, Y = Severity)

Gemeente Zutphen cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/analytical-center-for-the-government-of-the-russian-federation.jpeg
Analytical Center for the Government of the Russian Federation
Incidents

No Incident

https://images.rankiteo.com/companyimages/gemeente-zutphen.jpeg
Gemeente Zutphen
Incidents

No Incident

FAQ

Gemeente Zutphen company demonstrates a stronger AI Cybersecurity Score compared to Analytical Center for the Government of the Russian Federation company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Gemeente Zutphen company has disclosed a higher number of cyber incidents compared to Analytical Center for the Government of the Russian Federation company.

In the current year, Gemeente Zutphen company and Analytical Center for the Government of the Russian Federation company have not reported any cyber incidents.

Neither Gemeente Zutphen company nor Analytical Center for the Government of the Russian Federation company has reported experiencing a ransomware attack publicly.

Neither Gemeente Zutphen company nor Analytical Center for the Government of the Russian Federation company has reported experiencing a data breach publicly.

Neither Gemeente Zutphen company nor Analytical Center for the Government of the Russian Federation company has reported experiencing targeted cyberattacks publicly.

Neither Analytical Center for the Government of the Russian Federation company nor Gemeente Zutphen company has reported experiencing or disclosing vulnerabilities publicly.

Neither Analytical Center for the Government of the Russian Federation nor Gemeente Zutphen holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Analytical Center for the Government of the Russian Federation company nor Gemeente Zutphen company has publicly disclosed detailed information about the number of their subsidiaries.

Gemeente Zutphen company employs more people globally than Analytical Center for the Government of the Russian Federation company, reflecting its scale as a Public Policy Offices.

Neither Analytical Center for the Government of the Russian Federation nor Gemeente Zutphen holds SOC 2 Type 1 certification.

Neither Analytical Center for the Government of the Russian Federation nor Gemeente Zutphen holds SOC 2 Type 2 certification.

Neither Analytical Center for the Government of the Russian Federation nor Gemeente Zutphen holds ISO 27001 certification.

Neither Analytical Center for the Government of the Russian Federation nor Gemeente Zutphen holds PCI DSS certification.

Neither Analytical Center for the Government of the Russian Federation nor Gemeente Zutphen holds HIPAA certification.

Neither Analytical Center for the Government of the Russian Federation nor Gemeente Zutphen 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