Comparison Overview

Sicredi

VS

BMO

Sicredi

Av. Assis Brasil, Porto Alegre, Rio Grande do Sul, 91010-003, BR
Last Update: 2025-11-21
Between 800 and 849

We are born collaborative We believe that change is only possible when everyone works together for the same purpose, after all, cooperativism is in our DNA. Besides this, we know that as important as it is to provide affordable financial solutions it is just as important to value growing together, quality of life and the social and economic development of everyone who makes this happen. Therefore, we are committed to our employees, our associates and the regions in which we operate. Together we make a difference We were fortunate to be recognized as one of the best companies in Brazil to work for. This recognition is a reflection of all the collective effort put into creating and maintaining a safe and welcoming work environment. Here numbers are not the most important thing, what really matters is that we are made up of people for people. We have opportunities for professionals from different areas and we recognize that working together makes a difference in our lives. Be part of this history, be Sicredi!

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 19,425
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

BMO

First Canadian Place, 100 King Street, Toronto, ON, CA, M5X 1A1
Last Update: 2025-11-22
Between 800 and 849

We’re a bank, but there’s more to it than that. ​ When you join BMO, it opens a world of opportunities. This is a team that's committed to helping you succeed – personally and professionally. Because at BMO, when you grow, we grow. ​ You know your worth and so do we. That’s why we offer the right mix of learning programs, on-the-job experiences, and opportunities to build personal and professional connections – so you can build a meaningful career and thrive as a part of a winning culture. ​ Sound like your kind of place? Then we should be co-workers.

NAICS: 52
NAICS Definition: Finance and Insurance
Employees: 58,139
Subsidiaries: 11
12-month incidents
0
Known data breaches
2
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/sicredi.jpeg
Sicredi
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/bank-of-montreal.jpeg
BMO
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
Sicredi
100%
Compliance Rate
0/4 Standards Verified
BMO
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Sicredi in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for BMO in 2025.

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

Sicredi cyber incidents detection timeline including parent company and subsidiaries

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

BMO cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/sicredi.jpeg
Sicredi
Incidents

No Incident

https://images.rankiteo.com/companyimages/bank-of-montreal.jpeg
BMO
Incidents

Date Detected: 05/2018
Type:Breach
Motivation: Financial Gain
Blog: Blog

Date Detected: 5/2017
Type:Breach
Attack Vector: Error
Blog: Blog

FAQ

BMO company demonstrates a stronger AI Cybersecurity Score compared to Sicredi company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

BMO company has historically faced a number of disclosed cyber incidents, whereas Sicredi company has not reported any.

In the current year, BMO company and Sicredi company have not reported any cyber incidents.

Neither BMO company nor Sicredi company has reported experiencing a ransomware attack publicly.

BMO company has disclosed at least one data breach, while Sicredi company has not reported such incidents publicly.

Neither BMO company nor Sicredi company has reported experiencing targeted cyberattacks publicly.

Neither Sicredi company nor BMO company has reported experiencing or disclosing vulnerabilities publicly.

Neither Sicredi nor BMO holds any compliance certifications.

Neither company holds any compliance certifications.

BMO company has more subsidiaries worldwide compared to Sicredi company.

BMO company employs more people globally than Sicredi company, reflecting its scale as a Financial Services.

Neither Sicredi nor BMO holds SOC 2 Type 1 certification.

Neither Sicredi nor BMO holds SOC 2 Type 2 certification.

Neither Sicredi nor BMO holds ISO 27001 certification.

Neither Sicredi nor BMO holds PCI DSS certification.

Neither Sicredi nor BMO holds HIPAA certification.

Neither Sicredi nor BMO 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