Comparison Overview

QNB Group

VS

Security Bank Corporation

QNB Group

Doha, Qatar, Doha, undefined, 1000, QA
Last Update: 2025-11-25
Between 750 and 799

Since its establishment in 1964, QNB Group has steadily grown to become the biggest bank in Qatar and the largest financial institution in the Middle East and Africa (MEA) region. Network expansion comes in support of the Group’s vision to become a leading bank in the Middle East, Africa, and Southeast Asia. In addition, the Bank is establishing a foothold in highly competitive markets, including Hong Kong, where the Group opened recently its first branch. Proud to be the Official Middle East and Africa Supporter of the FIFA World Cup 2022™, QNB Group extends through its subsidiaries and associate companies to more than 30 countries across three continents providing a comprehensive range of advanced products and services. QNB Group has maintained its position as the highest-rated bank in Qatar and one of the highest rated banks in the world from leading credit rating agencies including Standard & Poor’s (A) and Moody’s (Aa3), The Bank has also been the recipient of many awards from leading international specialised financial publications. QNB Group has an active community support program and sponsors various social, educational and sporting events. For further information, please contact QNB’s Public Relations Department through [email protected]

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 8,656
Subsidiaries: 11
12-month incidents
0
Known data breaches
0
Attack type number
1

Security Bank Corporation

6776 Ayala Avenue, Makati, NCR, 1200, PH
Last Update: 2025-11-23
Between 750 and 799

Security Bank is one of the Philippines’ best-capitalized private domestic universal banks. Established in 1951 and publicly listed with the Philippine Stock Exchange (PSE: SECB) in 1995, our major businesses cover retail, corporate, commercial, and business (MSME) banking. We’re recognized as an Employer of Choice in Philippine banking by various award-giving bodies for our values-based culture, industry-leading engagement and benefits, and commitment to work-life balance. Most recently, we ranked #2 best employer in the Philippines and #54 globally on the prestigious Forbes’ World’s Best Employers 2023 list. At Security Bank, our approach to Human Capital Management (HCM) is embodied by our Employee Value Proposition (EVP): “YOU matter.” Start your BetterBankingcareer with us today. For the complete list of Security Bank's awards, you may visit: https://www.securitybank.com/about-us/awards/

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 14,494
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/qatar-national-bank-group.jpeg
QNB Group
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/security-bank-corporation.jpeg
Security Bank Corporation
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
QNB Group
100%
Compliance Rate
0/4 Standards Verified
Security Bank Corporation
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for QNB Group in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for Security Bank Corporation in 2025.

Incident History — QNB Group (X = Date, Y = Severity)

QNB Group cyber incidents detection timeline including parent company and subsidiaries

Incident History — Security Bank Corporation (X = Date, Y = Severity)

Security Bank Corporation cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/qatar-national-bank-group.jpeg
QNB Group
Incidents

Date Detected: 05/2016
Type:Data Leak
Blog: Blog

Date Detected: 04/2016
Type:Data Leak
Blog: Blog
https://images.rankiteo.com/companyimages/security-bank-corporation.jpeg
Security Bank Corporation
Incidents

No Incident

FAQ

Security Bank Corporation company demonstrates a stronger AI Cybersecurity Score compared to QNB Group company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

QNB Group company has historically faced a number of disclosed cyber incidents, whereas Security Bank Corporation company has not reported any.

In the current year, Security Bank Corporation company and QNB Group company have not reported any cyber incidents.

Neither Security Bank Corporation company nor QNB Group company has reported experiencing a ransomware attack publicly.

Neither Security Bank Corporation company nor QNB Group company has reported experiencing a data breach publicly.

Neither Security Bank Corporation company nor QNB Group company has reported experiencing targeted cyberattacks publicly.

Neither QNB Group company nor Security Bank Corporation company has reported experiencing or disclosing vulnerabilities publicly.

Neither QNB Group nor Security Bank Corporation holds any compliance certifications.

Neither company holds any compliance certifications.

QNB Group company has more subsidiaries worldwide compared to Security Bank Corporation company.

Security Bank Corporation company employs more people globally than QNB Group company, reflecting its scale as a Banking.

Neither QNB Group nor Security Bank Corporation holds SOC 2 Type 1 certification.

Neither QNB Group nor Security Bank Corporation holds SOC 2 Type 2 certification.

Neither QNB Group nor Security Bank Corporation holds ISO 27001 certification.

Neither QNB Group nor Security Bank Corporation holds PCI DSS certification.

Neither QNB Group nor Security Bank Corporation holds HIPAA certification.

Neither QNB Group nor Security Bank Corporation 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