Comparison Overview

Correios

VS

Ministry of Environment and Urbanism

Correios

SBN Quadra 1 Bloco A Edifício Correios, Brasília, 70002-900, BR
Last Update: 2025-11-24
Between 750 and 799

Empresa Brasileira de Correios e Telégrafos foi criada como empresa em 1969 por decreto lei. Hoje conta com mais de 100.000 empregados, tem presença em todos os municípios do Brasil. NEGÓCIO: Soluções que aproximam. MISSÃO: Fornecer soluções acessíveis e confiáveis para conectar pessoas, instituições e negócios, no Brasil e no mundo. VISÃO: Ser uma empresa de classe mundial. VALORES: A. Ética B. Meritocracia C. Respeito às Pessoas D. Compromisso com o Cliente E. Sustentabilidade

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

Ministry of Environment and Urbanism

Söğütözü Mh. 2179. Sk Ankara, 06105, TR
Last Update: 2025-11-21

MINISTRY of ENVIRONMENT and URBANISM (MEU) MAIN SERVICE UNITS ================== 1) General Directorate of Construction Works 2) General Directorate of Spatial Planning 3) General Directorate of Environmental Management 4) General Directorate of EIA, Permits and Control 5) General Directorate of Infrastructure Services 6) General Directorate of Geographic Information Systems 7) General Directorate of Professional Services 8) General Directorate of Natural Assets Protection

NAICS: 922
NAICS Definition:
Employees: 10,001
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/correios.jpeg
Correios
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/ministry-of-environment-and-urbanism.jpeg
Ministry of Environment and Urbanism
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
Correios
100%
Compliance Rate
0/4 Standards Verified
Ministry of Environment and Urbanism
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Correios in 2025.

Incidents vs Government Administration Industry Average (This Year)

No incidents recorded for Ministry of Environment and Urbanism in 2025.

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

Correios cyber incidents detection timeline including parent company and subsidiaries

Incident History — Ministry of Environment and Urbanism (X = Date, Y = Severity)

Ministry of Environment and Urbanism cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/correios.jpeg
Correios
Incidents

No Incident

https://images.rankiteo.com/companyimages/ministry-of-environment-and-urbanism.jpeg
Ministry of Environment and Urbanism
Incidents

No Incident

FAQ

Correios company demonstrates a stronger AI Cybersecurity Score compared to Ministry of Environment and Urbanism company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Ministry of Environment and Urbanism company has disclosed a higher number of cyber incidents compared to Correios company.

In the current year, Ministry of Environment and Urbanism company and Correios company have not reported any cyber incidents.

Neither Ministry of Environment and Urbanism company nor Correios company has reported experiencing a ransomware attack publicly.

Neither Ministry of Environment and Urbanism company nor Correios company has reported experiencing a data breach publicly.

Neither Ministry of Environment and Urbanism company nor Correios company has reported experiencing targeted cyberattacks publicly.

Neither Correios company nor Ministry of Environment and Urbanism company has reported experiencing or disclosing vulnerabilities publicly.

Neither Correios nor Ministry of Environment and Urbanism holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Correios company nor Ministry of Environment and Urbanism company has publicly disclosed detailed information about the number of their subsidiaries.

Correios company employs more people globally than Ministry of Environment and Urbanism company, reflecting its scale as a Government Administration.

Neither Correios nor Ministry of Environment and Urbanism holds SOC 2 Type 1 certification.

Neither Correios nor Ministry of Environment and Urbanism holds SOC 2 Type 2 certification.

Neither Correios nor Ministry of Environment and Urbanism holds ISO 27001 certification.

Neither Correios nor Ministry of Environment and Urbanism holds PCI DSS certification.

Neither Correios nor Ministry of Environment and Urbanism holds HIPAA certification.

Neither Correios nor Ministry of Environment and Urbanism 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