Comparison Overview

City of Seattle

VS

State of Michigan

City of Seattle

Seattle City Hall, 600 Fourth Avenue, Seattle, WA, US, 98124
Last Update: 2025-11-20
Between 750 and 799

Work With Purpose. Shape Seattle. Inspire the World. Seattle is more than a world-class city — it’s a vibrant, evolving community rooted in shared values of sustainability, innovation, and inclusion. As a public employer, the City of Seattle is committed to building a city that works for everyone — where communities thrive, opportunity is accessible, and public service drives real, lasting impact. With more than 12,000 employees across 40+ departments, we’re proud to serve the people of Seattle in every aspect of city life — from transportation and utilities to immigrant and refugee affairs, arts and culture, housing, and environmental stewardship. Whether you're maintaining parks, delivering clean water, strengthening neighborhoods, or shaping policy, your work helps power a city that puts people first. We offer more than 1,100 job titles — from seasonal and entry-level positions to senior leadership roles — across a wide range of fields: skilled trades, technology, finance, urban planning, public health, human services, public safety, and more. Whatever your background or career path, there’s a meaningful place for you here. At the City of Seattle, public service is more than a job — it's a shared purpose. We don’t just serve our community — we strive to be a model of what good government can be: inclusive, innovative, equitable, transparent, collaborative, and visionary. We believe that local leadership, done right, can inspire change far beyond our city limits. Joining the City of Seattle means joining a diverse, dedicated team that believes in the power of community and the possibility of progress. Together, we’re building a city where everyone can live, work, and thrive, and showing what’s possible when government works for the people it serves. Come build your career and community with us! #OneSeattle View the City's policies at seattle.gov/digital

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

State of Michigan

State Capitol, Lansing, Michigan, US, 48913
Last Update: 2025-11-21

Every day the contributions and achievements of State of Michigan employees have a direct impact on over 10 million Michiganders across the state. If you're looking for a fulfilling career in state government that can make a real difference in the lives of others, you can find your place working with us. We have opportunities in a number of career pathways, including, but not limited to, business and administrative support, education and human services, IT and computers, medical and healthcare, natural resources, law enforcement and public safety, skilled trades and more. Join our team for an: - Opportunity to make a difference - Challenging and rewarding work - Competitive salaries - Fun working environment - Great benefits (community service, vacation and sick leave, paid holidays, paid parental leave, longevity bonuses) - Job stability and career advancement - Flexible alternative and remote work schedules - Tuition discounts and student loan forgiveness - Professional development/training - Employee discount plan With positions in over 18 state departments, your perfect career fit is waiting for you at the State of Michigan. From urban centers to beach towns to the great outdoors, the opportunities are endless in Pure Michigan. With your state salary and benefits and Michigan’s affordable cost of living, you can explore all that Michigan has to offer. Ready to join our team? Visit www.Michigan.gov/Employment to search hundreds of state job openings by key word, job type, location, department, job category, salary and more. The State of Michigan is an Equal Opportunity Employer. We aim to recruit, hire, develop, and retain a diverse and high performing workforce. Our diversity helps drive our creative and effective problem solving, mutual respect, teamwork, and effective communication with the people we serve. Follow us on social media at www.Michigan.gov/SocialMedia and search hashtag #MiGovJobs for updates from state agencies.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/city-of-seattle.jpeg
City of Seattle
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/migovernment.jpeg
State of Michigan
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 Seattle
100%
Compliance Rate
0/4 Standards Verified
State of Michigan
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 Seattle in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for State of Michigan in 2025.

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

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

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

State of Michigan 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-seattle.jpeg
City of Seattle
Incidents

Date Detected: 5/2024
Type:Ransomware
Attack Vector: Ransomware
Blog: Blog

Date Detected: 3/2021
Type:Cyber Attack
Attack Vector: Cyberattack on Microsoft Exchange email servers
Blog: Blog
https://images.rankiteo.com/companyimages/migovernment.jpeg
State of Michigan
Incidents

Date Detected: 8/2025
Type:Breach
Motivation: Prevent identity theft and protect consumer privacy by strengthening data breach accountability and corporate safeguards.
Blog: Blog

FAQ

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

City of Seattle company has faced a higher number of disclosed cyber incidents historically compared to State of Michigan company.

In the current year, State of Michigan company has reported more cyber incidents than City of Seattle company.

City of Seattle company has confirmed experiencing a ransomware attack, while State of Michigan company has not reported such incidents publicly.

State of Michigan company has disclosed at least one data breach, while City of Seattle company has not reported such incidents publicly.

City of Seattle company has reported targeted cyberattacks, while State of Michigan company has not reported such incidents publicly.

Neither City of Seattle company nor State of Michigan company has reported experiencing or disclosing vulnerabilities publicly.

Neither City of Seattle nor State of Michigan holds any compliance certifications.

Neither company holds any compliance certifications.

State of Michigan company has more subsidiaries worldwide compared to City of Seattle company.

State of Michigan company employs more people globally than City of Seattle company, reflecting its scale as a Government Administration.

Neither City of Seattle nor State of Michigan holds SOC 2 Type 1 certification.

Neither City of Seattle nor State of Michigan holds SOC 2 Type 2 certification.

Neither City of Seattle nor State of Michigan holds ISO 27001 certification.

Neither City of Seattle nor State of Michigan holds PCI DSS certification.

Neither City of Seattle nor State of Michigan holds HIPAA certification.

Neither City of Seattle nor State of Michigan 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