Comparison Overview

Macon County, NC

VS

Poarch Creek Indians

Macon County, NC

5 West Main Street, Franklin, North Carolina, 28734, US
Last Update: 2025-12-13
Between 750 and 799

Macon County shall remain the most prosperous and most livable county in WNC through active support of new and existing business and active recruiting of compatible business. The county was formed in 1828 from the western part of Haywood County. It was named for Nathaniel Macon, who represented North Carolina in the United States House of Representatives from 1791 to 1815 (serving as Speaker of the House from 1801 to 1807), and in the United States Senate from 1815 to 1828. In 1839 the western part of Macon County became Cherokee County. In 1851 parts of Macon County and Haywood County were combined to form Jackson County.

NAICS: None
NAICS Definition: Others
Employees: 113
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Poarch Creek Indians

5811 Jack Springs Rd, Atmore, 36502, US
Last Update: 2025-12-12
Between 750 and 799

The Poarch Creek Indians is the only federally recognized Indian Tribe in the state of Alabama, operating as a sovereign nation with its own system of government and bylaws. The Tribe operates a variety of economic enterprises: Wind Creek Hospitality, Creek Indian Enterprises Authority, OWA, and others which employ thousands of area residents. The Poarch Band of Creek Indians is an active partner in the state of Alabama, contributing to economic, educational, social and cultural projects benefiting both Tribal Members and residents of these local communities and neighboring towns.

NAICS: None
NAICS Definition: Others
Employees: 307
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/macon-county-nc.jpeg
Macon County, NC
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/poarch-creek-indians.jpeg
Poarch Creek Indians
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
Macon County, NC
100%
Compliance Rate
0/4 Standards Verified
Poarch Creek Indians
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Relations Industry Average (This Year)

No incidents recorded for Macon County, NC in 2025.

Incidents vs Government Relations Industry Average (This Year)

No incidents recorded for Poarch Creek Indians in 2025.

Incident History — Macon County, NC (X = Date, Y = Severity)

Macon County, NC cyber incidents detection timeline including parent company and subsidiaries

Incident History — Poarch Creek Indians (X = Date, Y = Severity)

Poarch Creek Indians cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/macon-county-nc.jpeg
Macon County, NC
Incidents

No Incident

https://images.rankiteo.com/companyimages/poarch-creek-indians.jpeg
Poarch Creek Indians
Incidents

No Incident

FAQ

Macon County, NC company demonstrates a stronger AI Cybersecurity Score compared to Poarch Creek Indians company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Poarch Creek Indians company has disclosed a higher number of cyber incidents compared to Macon County, NC company.

In the current year, Poarch Creek Indians company and Macon County, NC company have not reported any cyber incidents.

Neither Poarch Creek Indians company nor Macon County, NC company has reported experiencing a ransomware attack publicly.

Neither Poarch Creek Indians company nor Macon County, NC company has reported experiencing a data breach publicly.

Neither Poarch Creek Indians company nor Macon County, NC company has reported experiencing targeted cyberattacks publicly.

Neither Macon County, NC company nor Poarch Creek Indians company has reported experiencing or disclosing vulnerabilities publicly.

Neither Macon County, NC nor Poarch Creek Indians holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Macon County, NC company nor Poarch Creek Indians company has publicly disclosed detailed information about the number of their subsidiaries.

Poarch Creek Indians company employs more people globally than Macon County, NC company, reflecting its scale as a Government Relations.

Neither Macon County, NC nor Poarch Creek Indians holds SOC 2 Type 1 certification.

Neither Macon County, NC nor Poarch Creek Indians holds SOC 2 Type 2 certification.

Neither Macon County, NC nor Poarch Creek Indians holds ISO 27001 certification.

Neither Macon County, NC nor Poarch Creek Indians holds PCI DSS certification.

Neither Macon County, NC nor Poarch Creek Indians holds HIPAA certification.

Neither Macon County, NC nor Poarch Creek Indians holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Nagios XI versions prior to 2026R1.1 are vulnerable to local privilege escalation due to an unsafe interaction between sudo permissions and application file permissions. A user‑accessible maintenance script may be executed as root via sudo and includes an application file that is writable by a lower‑privileged user. A local attacker with access to the application account can modify this file to introduce malicious code, which is then executed with elevated privileges when the script is run. Successful exploitation results in arbitrary code execution as the root user.

Risk Information
cvss4
Base: 8.6
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/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

Out of bounds read and write in V8 in Google Chrome prior to 143.0.7499.147 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Description

Use after free in WebGPU in Google Chrome prior to 143.0.7499.147 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Description

SIPGO is a library for writing SIP services in the GO language. Starting in version 0.3.0 and prior to version 1.0.0-alpha-1, a nil pointer dereference vulnerability is in the SIPGO library's `NewResponseFromRequest` function that affects all normal SIP operations. The vulnerability allows remote attackers to crash any SIP application by sending a single malformed SIP request without a To header. The vulnerability occurs when SIP message parsing succeeds for a request missing the To header, but the response creation code assumes the To header exists without proper nil checks. This affects routine operations like call setup, authentication, and message handling - not just error cases. This vulnerability affects all SIP applications using the sipgo library, not just specific configurations or edge cases, as long as they make use of the `NewResponseFromRequest` function. Version 1.0.0-alpha-1 contains a patch for the issue.

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

GLPI is a free asset and IT management software package. Starting in version 9.1.0 and prior to version 10.0.21, an unauthorized user with an API access can read all knowledge base entries. Users should upgrade to 10.0.21 to receive a patch.

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