Comparison Overview

Seattle Police Department

VS

INSS

Seattle Police Department

Seattle, WA, US
Last Update: 2026-01-21

The Seattle Police Department is a large metropolitan public safety agency in Washington state with nearly 1,100 sworn officers. We receive over 800,000 911 calls annually in a city of 84 square miles. We have more specialty units than any other department in the state, including: traffic, harbor, mounted patrol, major crimes, property crimes, crisis response, SWAT, arson and bombs, K9, collaborative (community) policing, forensics, training and community response. On a daily basis, our officers are asked to do a little bit of everything - from investigating and solving crimes; to patrolling our waterways, parks and city streets; to keeping everyone safe during sporting events and parades; to connecting our city's most vulnerable residents with much-needed services. The mission of the Seattle Police Department is to prevent crime, enforce the law, and support quality public safety by delivering respectful, professional and dependable police services. View the City’s policies at seattle.gov/digital.

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

INSS

SAS, Quadra 2, Bloco O, Brasília, 70070-907, BR
Last Update: 2026-01-18
Between 750 and 799

O Instituto Nacional do Seguro Social (INSS) é uma autarquia do Governo Federal do Brasil que recebe as contribuições para a manutenção do Regime Geral da Previdência Social, sendo responsável pelo pagamento da aposentadoria, pensão por morte, auxílio-doença, auxílio-acidente, entre outros benefícios previstos em lei. O INSS trabalha junto com a Dataprev, empresa de tecnologia que faz o processamento de todos os dados da Previdência. Está vinculado ao Ministério da Previdência Social.

NAICS: 92
NAICS Definition: Public Administration
Employees: 17,778
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/seattle-police-department.jpeg
Seattle Police Department
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/inss.jpeg
INSS
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
Seattle Police Department
100%
Compliance Rate
0/4 Standards Verified
INSS
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Seattle Police Department in 2026.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for INSS in 2026.

Incident History — Seattle Police Department (X = Date, Y = Severity)

Seattle Police Department cyber incidents detection timeline including parent company and subsidiaries

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

INSS cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/seattle-police-department.jpeg
Seattle Police Department
Incidents

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

No Incident

FAQ

INSS company demonstrates a stronger AI Cybersecurity Score compared to Seattle Police Department company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Seattle Police Department company has historically faced a number of disclosed cyber incidents, whereas INSS company has not reported any.

In the current year, INSS company and Seattle Police Department company have not reported any cyber incidents.

Neither INSS company nor Seattle Police Department company has reported experiencing a ransomware attack publicly.

Neither INSS company nor Seattle Police Department company has reported experiencing a data breach publicly.

Seattle Police Department company has reported targeted cyberattacks, while INSS company has not reported such incidents publicly.

Neither Seattle Police Department company nor INSS company has reported experiencing or disclosing vulnerabilities publicly.

Neither Seattle Police Department nor INSS holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Seattle Police Department company nor INSS company has publicly disclosed detailed information about the number of their subsidiaries.

INSS company employs more people globally than Seattle Police Department company, reflecting its scale as a Government Administration.

Neither Seattle Police Department nor INSS holds SOC 2 Type 1 certification.

Neither Seattle Police Department nor INSS holds SOC 2 Type 2 certification.

Neither Seattle Police Department nor INSS holds ISO 27001 certification.

Neither Seattle Police Department nor INSS holds PCI DSS certification.

Neither Seattle Police Department nor INSS holds HIPAA certification.

Neither Seattle Police Department nor INSS holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Typemill is a flat-file, Markdown-based CMS designed for informational documentation websites. A reflected Cross-Site Scripting (XSS) exists in the login error view template `login.twig` of versions 2.19.1 and below. The `username` value can be echoed back without proper contextual encoding when authentication fails. An attacker can execute script in the login page context. This issue has been fixed in version 2.19.2.

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

A DOM-based Cross-Site Scripting (XSS) vulnerability exists in the DomainCheckerApp class within domain/script.js of Sourcecodester Domain Availability Checker v1.0. The vulnerability occurs because the application improperly handles user-supplied data in the createResultElement method by using the unsafe innerHTML property to render domain search results.

Description

A Remote Code Execution (RCE) vulnerability exists in Sourcecodester Modern Image Gallery App v1.0 within the gallery/upload.php component. The application fails to properly validate uploaded file contents. Additionally, the application preserves the user-supplied file extension during the save process. This allows an unauthenticated attacker to upload arbitrary PHP code by spoofing the MIME type as an image, leading to full system compromise.

Description

A UNIX symbolic link following issue in the jailer component in Firecracker version v1.13.1 and earlier and 1.14.0 on Linux may allow a local host user with write access to the pre-created jailer directories to overwrite arbitrary host files via a symlink attack during the initialization copy at jailer startup, if the jailer is executed with root privileges. To mitigate this issue, users should upgrade to version v1.13.2 or 1.14.1 or above.

Risk Information
cvss3
Base: 6.0
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H
cvss4
Base: 6.0
Severity: LOW
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:H/SA:H/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

An information disclosure vulnerability exists in the /srvs/membersrv/getCashiers endpoint of the Aptsys gemscms backend platform thru 2025-05-28. This unauthenticated endpoint returns a list of cashier accounts, including names, email addresses, usernames, and passwords hashed using MD5. As MD5 is a broken cryptographic function, the hashes can be easily reversed using public tools, exposing user credentials in plaintext. This allows remote attackers to perform unauthorized logins and potentially gain access to sensitive POS operations or backend functions.