Comparison Overview

Servicepunt71

VS

EAT

Servicepunt71

Tweelingstraat 4, 2312LX, Leiden, NL
Last Update: 2025-11-27

Servicepunt71, shared service organisatie voor de interne bedrijfsvoering in de publieke sector Servicepunt71 zorgt sinds 1 januari 2012 voor de interne bedrijfsvoering van de gemeenten Leiden, Leiderdorp, Oegstgeest en Zoeterwoude en de eigen organisatie. De gemeenten zijn tevens eigenaar. Servicepunt71 levert producten en diensten op het gebied van ICT, HRM, Financiën, Juridische Zaken en Inkoop en voor de gemeenten Leiden en Leiderdorp ook Facilitaire Zaken.

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

EAT

Kongensgate 11, Oslo, undefined, 0152, NO
Last Update: 2025-11-27
Between 700 and 749

EAT is an international foundation linking food, health and sustainable development across science, business and policy. Originally launched in 2013, EAT is now an independent foundation with three core partners: The Stordalen Foundation, the Stockholm Resilience Centre and the Wellcome Trust. The overall objective of EAT is to expand scientific knowledge on the interconnections between food, health and environmental sustainability, spur innovation along the food value chain, and facilitate the development of evidence-based policies to radically transform the global food system to be able to deliver healthy, affordable diets to a growing world population within the planetary boundaries. Multi-stakeholder, multidisciplinary and multi-scale collaboration between business, science, politics and civil society lies at the heart of EAT’s work. EAT believes that a transformation of the food system is only possible if these diverse actors collectively address the intertwined issues of food, health and sustainability, and develop integrated strategies on food production and consumption to leverage multiple benefits for human and planetary health.

NAICS: 921
NAICS Definition:
Employees: 82
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/servicepunt71.jpeg
Servicepunt71
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/eatfoundation.jpeg
EAT
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
Servicepunt71
100%
Compliance Rate
0/4 Standards Verified
EAT
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for Servicepunt71 in 2025.

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for EAT in 2025.

Incident History — Servicepunt71 (X = Date, Y = Severity)

Servicepunt71 cyber incidents detection timeline including parent company and subsidiaries

Incident History — EAT (X = Date, Y = Severity)

EAT cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/servicepunt71.jpeg
Servicepunt71
Incidents

No Incident

https://images.rankiteo.com/companyimages/eatfoundation.jpeg
EAT
Incidents

No Incident

FAQ

Servicepunt71 company demonstrates a stronger AI Cybersecurity Score compared to EAT company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, EAT company has disclosed a higher number of cyber incidents compared to Servicepunt71 company.

In the current year, EAT company and Servicepunt71 company have not reported any cyber incidents.

Neither EAT company nor Servicepunt71 company has reported experiencing a ransomware attack publicly.

Neither EAT company nor Servicepunt71 company has reported experiencing a data breach publicly.

Neither EAT company nor Servicepunt71 company has reported experiencing targeted cyberattacks publicly.

Neither Servicepunt71 company nor EAT company has reported experiencing or disclosing vulnerabilities publicly.

Neither Servicepunt71 nor EAT holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Servicepunt71 company nor EAT company has publicly disclosed detailed information about the number of their subsidiaries.

EAT company employs more people globally than Servicepunt71 company, reflecting its scale as a Public Policy Offices.

Neither Servicepunt71 nor EAT holds SOC 2 Type 1 certification.

Neither Servicepunt71 nor EAT holds SOC 2 Type 2 certification.

Neither Servicepunt71 nor EAT holds ISO 27001 certification.

Neither Servicepunt71 nor EAT holds PCI DSS certification.

Neither Servicepunt71 nor EAT holds HIPAA certification.

Neither Servicepunt71 nor EAT 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