Comparison Overview

City of Lafayette

VS

FEMA

City of Lafayette

20 N. 6th St. , Lafayette, Indiana, 47901, US
Last Update: 2025-12-28
Between 700 and 749

A warm welcome from the City of Lafayette, known as the place of choice for singles, families and retirees. Our community values long-time residents, welcomes newcomers and enjoys visitors. A high-energy community, the Greater Lafayette area is a thriving business and industry hub focused on progress, investment and job creation. We offer great sports and recreation, fine cultural activities, year round festivals and affordable housing. And we're known for our blue-ribbon schools, regional healthcare services and historic downtown loaded with shopping, dining and night life. With a wide-ranging and strong economy, many career and business opportunities abound. Greater Lafayette is home to advanced manufacturers General Electric, Caterpillar, Subaru of Indiana Automotive Inc., Wabash National and other top industries, as well as thriving life science companies, from Evonik Degussa Corp. to startups licensing Purdue technologies. Small business, arts and culture and entrepreneurs all contribute to making the area economy strong. Lafayette's city departments, civic leaders and organizations such as Greater Lafayette Commerce stand ready to help our citizens succeed on the job or in business. Greater Lafayette is a well-educated community. We're home to Purdue University, Ivy Tech Community College, three outstanding public school corporations and several private educational systems. You will see in our community a growing, involved population; dynamic public and private sectors with many opportunities; and a quality of life second to none. We invite you to experience our community's hopes and aspirations and share your own as well. New developments in the city and along the Wabash River all point to a bright future for Lafayette, the place of choice.

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

FEMA

500 C Street SW, None, Washington, DC, US, 20472
Last Update: 2025-12-23
Between 0 and 549

Welcome to the official LinkedIn page for the Federal Emergency Management Agency (FEMA). When disaster strikes, America looks to FEMA to support survivors and first responders in communities all across the country. This page provides career related information, job announcements and relevant updates for the agency’s current and future workforce. FEMA fosters innovation, rewards performance and creativity, and provides challenges on a routine basis with a well-skilled, knowledgeable, and high performance workforce. Join our mission to support Americans when they need you most!

NAICS: 92
NAICS Definition: Public Administration
Employees: 19,641
Subsidiaries: 10
12-month incidents
3
Known data breaches
7
Attack type number
5

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/city-of-lafayette-indiana.jpeg
City of Lafayette
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/fema.jpeg
FEMA
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 Lafayette
100%
Compliance Rate
0/4 Standards Verified
FEMA
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 Lafayette in 2025.

Incidents vs Government Administration Industry Average (This Year)

FEMA has 252.94% more incidents than the average of same-industry companies with at least one recorded incident.

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

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

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

FEMA cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/city-of-lafayette-indiana.jpeg
City of Lafayette
Incidents

Date Detected: 7/2020
Type:Ransomware
Motivation: Financial Gain
Blog: Blog
https://images.rankiteo.com/companyimages/fema.jpeg
FEMA
Incidents

Date Detected: 9/2025
Type:Breach
Attack Vector: Exploitation of Citrix Remote Access Software, Lateral Movement, Privilege Escalation
Motivation: Espionage, Data Theft, Potential Sabotage
Blog: Blog

Date Detected: 7/2025
Type:Breach
Attack Vector: Exploitation of Citrix Remote Access Software, Lateral Movement within Network
Motivation: Espionage, Data Theft
Blog: Blog

Date Detected: 6/2025
Type:Breach
Attack Vector: Compromised Credentials, Exploitation of Citrix Remote Desktop Software, Lateral Movement via VPN Software
Blog: Blog

FAQ

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

FEMA company has faced a higher number of disclosed cyber incidents historically compared to City of Lafayette company.

In the current year, FEMA company has reported more cyber incidents than City of Lafayette company.

Both FEMA company and City of Lafayette company have confirmed experiencing at least one ransomware attack.

FEMA company has disclosed at least one data breach, while City of Lafayette company has not reported such incidents publicly.

FEMA company has reported targeted cyberattacks, while City of Lafayette company has not reported such incidents publicly.

FEMA company has disclosed at least one vulnerability, while City of Lafayette company has not reported such incidents publicly.

Neither City of Lafayette nor FEMA holds any compliance certifications.

Neither company holds any compliance certifications.

FEMA company has more subsidiaries worldwide compared to City of Lafayette company.

FEMA company employs more people globally than City of Lafayette company, reflecting its scale as a Government Administration.

Neither City of Lafayette nor FEMA holds SOC 2 Type 1 certification.

Neither City of Lafayette nor FEMA holds SOC 2 Type 2 certification.

Neither City of Lafayette nor FEMA holds ISO 27001 certification.

Neither City of Lafayette nor FEMA holds PCI DSS certification.

Neither City of Lafayette nor FEMA holds HIPAA certification.

Neither City of Lafayette nor FEMA holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.

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

A vulnerability has been found in jackq XCMS up to 3fab5342cc509945a7ce1b8ec39d19f701b89261. Affected is the function Upload of the file Admin/Home/Controller/ProductImageController.class.php of the component Backend. Such manipulation of the argument File leads to unrestricted upload. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. The project was informed of the problem early through an issue report but has not responded yet.

Risk Information
cvss2
Base: 5.8
Severity: LOW
AV:N/AC:L/Au:M/C:P/I:P/A:P
cvss3
Base: 4.7
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L
cvss4
Base: 5.1
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/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

In PHP versions 8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1 when using the PDO PostgreSQL driver with PDO::ATTR_EMULATE_PREPARES enabled, an invalid character sequence (such as \x99) in a prepared statement parameter may cause the quoting function PQescapeStringConn to return NULL, leading to a null pointer dereference in pdo_parse_params() function. This may lead to crashes (segmentation fault) and affect the availability of the target server.

Risk Information
cvss4
Base: 8.2
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/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

In PHP versions:8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1, a heap buffer overflow occurs in array_merge() when the total element count of packed arrays exceeds 32-bit limits or HT_MAX_SIZE, due to an integer overflow in the precomputation of element counts using zend_hash_num_elements(). This may lead to memory corruption or crashes and affect the integrity and availability of the target server.

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

In PHP versions:8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1, the getimagesize() function may leak uninitialized heap memory into the APPn segments (e.g., APP1) when reading images in multi-chunk mode (such as via php://filter). This occurs due to a bug in php_read_stream_all_chunks() that overwrites the buffer without advancing the pointer, leaving tail bytes uninitialized. This may lead to information disclosure of sensitive heap data and affect the confidentiality of the target server.

Risk Information
cvss4
Base: 6.3
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/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