Comparison Overview

Iowa Secretary of State

VS

FDA

Iowa Secretary of State

321 E. 12th St., Des Moines, Iowa, 50319, US
Last Update: 2025-12-17
Between 700 and 749

Paul D. Pate of Cedar Rapids was elected to serve as the thirty-second Iowa Secretary of State. He is Iowa's Commissioner of Elections. Pate also oversees Business Services for the State of Iowa. A recognized business leader by the Small Business Administration, Pate is the owner of a paving construction firm and was recognized as a Patriotic Employer by the National Committee for Employer Support of the Guard and Reserve. Pate also served two terms as Mayor of Cedar Rapids from 2002 –2006. While Mayor, Pate was elected President of the non-partisan Iowa League of Cities representing over 870 municipalities. He previously served with Governor Branstad as Iowa Secretary of State from 1995-1999. Paul was elected twice to the Iowa State Senate representing NE Cedar Rapids, Marion and parts of Linn, Buchanan and Delaware Counties from 1989-1995. Upon returning to the Secretary of State's Office in January 2015, Pate set out to institute a Safe at Home program in Iowa. Safe at Home is an address confidentiality program for survivors of domestic violence, sexual abuse, trafficking and stalking. The bill passed both chambers of the Iowa Legislature unanimously and was signed into law by Governor Terry Branstad in May. Secretary Pate's Office administers the program. Pate also instituted online voter registration in Iowa in January 2016. More than 70,000 Iowans used the system to register to vote in its first year. Paul Pate was selected to participate in the prestigious 2015 Toll Fellowship Program. It is a leadership development program for state government officials, bringing 48 of the nation’s top officials from all three branches of state government together for an intensive six-day intellectual boot camp.[17] Google awarded Secretary Pate in July 2015 for his efforts to increase voter participation in Iowa. The award was presented during the National Association of Secretaries of State's annual conference.[18] Secretary Pate was named the co-chair of the National Association of Secretaries of State’s Standing Committee on Business Services in July 2015.[19] Pate was named the co-chair of the NASS Business ID Theft Task Force in March 2016.[20] Secretary Pate was elected the Midwestern Region Vice-president of the National Association of Secretaries of State in July 2016. Pate also serves on the Council of State Governments’ International Relations Committee. The National State Boards of Education rewarded Secretary Pate with the Award for Outstanding Leadership in Voter Education in March 2017. Pate was recognized for his efforts in conducting two statewide Iowa Youth Straw Polls and the Iowa Youth Caucus. Both straw polls included more than 58,000 students from more than 250 schools statewide. Paul Pate is a lifelong Iowa resident, born in Ottumwa, growing up in Linn County. His family includes his wife Jane, three children and five grandchildren who all reside in Iowa.

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

FDA

10903 New Hampshire Ave, None, Silver Spring, MD, US, 20993
Last Update: 2025-12-17
Between 800 and 849

The Food and Drug Administration is an agency within the Department of Health and Human Services. The FDA is responsible for protecting the public health by ensuring the safety, efficacy, and security of human and veterinary drugs, biological products, and medical devices; and by ensuring the safety of our nation's food supply, cosmetics, and products that emit radiation. FDA also has responsibility for regulating the manufacturing, marketing, and distribution of tobacco products to protect the public health and to reduce tobacco use by minors. FDA is responsible for advancing the public health by helping to speed innovations that make medical products more effective, safer, and more affordable and by helping the public get the accurate, science-based information they need to use medical products and foods to maintain and improve their health. FDA also plays a significant role in the Nation's counterterrorism capability. FDA fulfills this responsibility by ensuring the security of the food supply and by fostering development of medical products to respond to deliberate and naturally emerging public health threats.

NAICS: 92
NAICS Definition: Public Administration
Employees: 17,599
Subsidiaries: 2
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/iowa-secretary-of-state.jpeg
Iowa Secretary of State
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/fda.jpeg
FDA
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
Iowa Secretary of State
100%
Compliance Rate
0/4 Standards Verified
FDA
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Iowa Secretary of State in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for FDA in 2025.

Incident History — Iowa Secretary of State (X = Date, Y = Severity)

Iowa Secretary of State cyber incidents detection timeline including parent company and subsidiaries

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

FDA cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/iowa-secretary-of-state.jpeg
Iowa Secretary of State
Incidents

Date Detected: 4/2017
Type:Breach
Attack Vector: Phishing Emails
Blog: Blog
https://images.rankiteo.com/companyimages/fda.jpeg
FDA
Incidents

No Incident

FAQ

FDA company demonstrates a stronger AI Cybersecurity Score compared to Iowa Secretary of State company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Iowa Secretary of State company has historically faced a number of disclosed cyber incidents, whereas FDA company has not reported any.

In the current year, FDA company and Iowa Secretary of State company have not reported any cyber incidents.

Neither FDA company nor Iowa Secretary of State company has reported experiencing a ransomware attack publicly.

Iowa Secretary of State company has disclosed at least one data breach, while the other FDA company has not reported such incidents publicly.

Neither FDA company nor Iowa Secretary of State company has reported experiencing targeted cyberattacks publicly.

Neither Iowa Secretary of State company nor FDA company has reported experiencing or disclosing vulnerabilities publicly.

Neither Iowa Secretary of State nor FDA holds any compliance certifications.

Neither company holds any compliance certifications.

FDA company has more subsidiaries worldwide compared to Iowa Secretary of State company.

FDA company employs more people globally than Iowa Secretary of State company, reflecting its scale as a Government Administration.

Neither Iowa Secretary of State nor FDA holds SOC 2 Type 1 certification.

Neither Iowa Secretary of State nor FDA holds SOC 2 Type 2 certification.

Neither Iowa Secretary of State nor FDA holds ISO 27001 certification.

Neither Iowa Secretary of State nor FDA holds PCI DSS certification.

Neither Iowa Secretary of State nor FDA holds HIPAA certification.

Neither Iowa Secretary of State nor FDA holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Zerobyte is a backup automation tool Zerobyte versions prior to 0.18.5 and 0.19.0 contain an authentication bypass vulnerability where authentication middleware is not properly applied to API endpoints. This results in certain API endpoints being accessible without valid session credentials. This is dangerous for those who have exposed Zerobyte to be used outside of their internal network. A fix has been applied in both version 0.19.0 and 0.18.5. If immediate upgrade is not possible, restrict network access to the Zerobyte instance to trusted networks only using firewall rules or network segmentation. This is only a temporary mitigation; upgrading is strongly recommended.

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

Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter framework. Starting in version 3.4.0 and prior to version 3.4.2, a Cross-Site Request Forgery (CSRF) vulnerability exists in the application's filter configuration. The CSRF protection mechanism was **explicitly disabled**, allowing the application to process state-changing requests (POST) without verifying a valid CSRF token. An unauthenticated remote attacker can exploit this by hosting a malicious web page. If a logged-in administrator visits this page, their browser is forced to send unauthorized requests to the application. A successful exploit allows the attacker to silently create a new Administrator account with full privileges, leading to a complete takeover of the system and loss of confidentiality, integrity, and availability. The vulnerability has been patched in version 3.4.2. The fix re-enables the CSRF filter in `app/Config/Filters.php` and resolves associated AJAX race conditions by adjusting token regeneration settings. As a workaround, administrators can manually re-enable the CSRF filter in `app/Config/Filters.php` by uncommenting the protection line. However, this is not recommended without applying the full patch, as it may cause functionality breakage in the Sales module due to token synchronization issues.

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

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Model Context Protocol (MCP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious MCP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered automatically without any user interaction besides opening the project in the IDE. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

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

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Language Server Protocol (LSP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious LSP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered when a user opens project file for which there is an LSP entry. A concerted effort by an attacker to seed a project settings file (`./zed/settings.json`) with malicious language server configurations could result in arbitrary code execution with the user's privileges if the user opens the project in Zed without reviewing the contents. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

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

Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of environment variables defined in a `.env` file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the `storybook build` command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly) in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than `.env` files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with `STORYBOOK_` or use the `env` property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

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