Comparison Overview

Hunger Free Vermont

VS

Greater Starkville Development Partnership

Hunger Free Vermont

38 Eastwood Drive, South Burlington, VT, 05401, US
Last Update: 2025-11-27
Between 700 and 749

Hunger Free Vermont operates on a simple formula: it ensures that children have food wherever they are in their day, that adults and seniors can provide healthy meals at home, and Hunger Free Vermont offers nutrition and cooking classes to ensure that Vermont youth and adults know how to prepare nutritious meals on a budget. Formerly called the Vermont Campaign to End Childhood Hunger (1993-2010), the mission of Hunger Free Vermont is to end the injustice of hunger and malnutrition for all Vermonters.

NAICS: 921
NAICS Definition:
Employees: 23
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Greater Starkville Development Partnership

200 E Main St, Starkville, Mississippi, 39759, US
Last Update: 2025-11-27
Between 700 and 749

The mission of the Greater Starkville Development Partnership (GSDP) is to promote a healthy and sustainable Starkville and Oktibbeha County by enhancing the quality of life for all citizens through business growth and job creation, tourism and retirement opportunities, and progressive educational and community initiatives. As the leader in economic development, tourism, and community development in Starkville and Oktibbeha County, the GSDP recognizes the importance of a community that reflects the rich diversity of the people of the Great State of Mississippi and our nation. We believe in the inclusive treatment of all people. We are our best when everyone is equally engaged and valued. The GSDP is comprised of the Starkville Area Chamber of Commerce, Oktibbeha County Economic Development Authority, Starkville Convention and Visitors Bureau, and the Starkville Main Street Association.

NAICS: 921
NAICS Definition: Executive, Legislative, and Other General Government Support
Employees: 9
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/hunger-free-vermont.jpeg
Hunger Free Vermont
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/greater-starkville-development-partnership.jpeg
Greater Starkville Development Partnership
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
Hunger Free Vermont
100%
Compliance Rate
0/4 Standards Verified
Greater Starkville Development Partnership
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for Hunger Free Vermont in 2025.

Incidents vs Public Policy Offices Industry Average (This Year)

No incidents recorded for Greater Starkville Development Partnership in 2025.

Incident History — Hunger Free Vermont (X = Date, Y = Severity)

Hunger Free Vermont cyber incidents detection timeline including parent company and subsidiaries

Incident History — Greater Starkville Development Partnership (X = Date, Y = Severity)

Greater Starkville Development Partnership cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/hunger-free-vermont.jpeg
Hunger Free Vermont
Incidents

No Incident

https://images.rankiteo.com/companyimages/greater-starkville-development-partnership.jpeg
Greater Starkville Development Partnership
Incidents

No Incident

FAQ

Both Hunger Free Vermont company and Greater Starkville Development Partnership company demonstrate a comparable AI Cybersecurity Score, with strong governance and monitoring frameworks in place.

Historically, Greater Starkville Development Partnership company has disclosed a higher number of cyber incidents compared to Hunger Free Vermont company.

In the current year, Greater Starkville Development Partnership company and Hunger Free Vermont company have not reported any cyber incidents.

Neither Greater Starkville Development Partnership company nor Hunger Free Vermont company has reported experiencing a ransomware attack publicly.

Neither Greater Starkville Development Partnership company nor Hunger Free Vermont company has reported experiencing a data breach publicly.

Neither Greater Starkville Development Partnership company nor Hunger Free Vermont company has reported experiencing targeted cyberattacks publicly.

Neither Hunger Free Vermont company nor Greater Starkville Development Partnership company has reported experiencing or disclosing vulnerabilities publicly.

Neither Hunger Free Vermont nor Greater Starkville Development Partnership holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Hunger Free Vermont company nor Greater Starkville Development Partnership company has publicly disclosed detailed information about the number of their subsidiaries.

Hunger Free Vermont company employs more people globally than Greater Starkville Development Partnership company, reflecting its scale as a Public Policy Offices.

Neither Hunger Free Vermont nor Greater Starkville Development Partnership holds SOC 2 Type 1 certification.

Neither Hunger Free Vermont nor Greater Starkville Development Partnership holds SOC 2 Type 2 certification.

Neither Hunger Free Vermont nor Greater Starkville Development Partnership holds ISO 27001 certification.

Neither Hunger Free Vermont nor Greater Starkville Development Partnership holds PCI DSS certification.

Neither Hunger Free Vermont nor Greater Starkville Development Partnership holds HIPAA certification.

Neither Hunger Free Vermont nor Greater Starkville Development Partnership 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