Comparison Overview

MCB Bank Limited

VS

SEB

MCB Bank Limited

15 Main Gulberg, Lahore, undefined, -, PK
Last Update: 2025-12-09
Between 750 and 799

Welcome to the Official LinkedIn page of MCB Bank Limited. Established in 1947, MCB Bank Limited is one of the largest Banks in Pakistan with a total customer base exceeding 7 million. We have products and services to suit the every need of customers. To learn more about MCB Bank, please visit our website www.mcb.com.pk or call the MCB Contact Center 111-000-622. Disclaimer: MCB Bank will never ask for our customer’s personal data on any public platform. Please avoid sharing any such data via social media.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 13,689
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

SEB

Kungsträdgårdsgatan 8, Stockholm, Stockholm, SE, 10640
Last Update: 2025-12-09
Between 800 and 849

SEB is a leading northern European financial services group with a strong belief that entrepreneurial minds and innovative companies are key in creating a better world. SEB takes a long-term perspective and supports its customers in good times and bad. In Sweden and the Baltic countries, SEB offers financial advice and a wide range of financial services. In Denmark, Finland, Norway and Germany the bank's operations have a strong focus on corporate and investment banking based on a full-service offering to corporate and institutional clients. The international nature of SEB's business is reflected in its presence in some 20 countries worldwide. Read more about SEB at www.sebgroup.com Privacy note about SEB’s processing of your personal data can be found at: www.sebgroup.com/legal-and-regulatory-information/privacy-at-seb-group Content shared on this page may contain commercial information from SEB.

NAICS: 52211
NAICS Definition: Commercial Banking
Employees: 14,737
Subsidiaries: 5
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/mcb-bank-limited.jpeg
MCB Bank Limited
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/seb.jpeg
SEB
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
MCB Bank Limited
100%
Compliance Rate
0/4 Standards Verified
SEB
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Banking Industry Average (This Year)

No incidents recorded for MCB Bank Limited in 2025.

Incidents vs Banking Industry Average (This Year)

No incidents recorded for SEB in 2025.

Incident History — MCB Bank Limited (X = Date, Y = Severity)

MCB Bank Limited cyber incidents detection timeline including parent company and subsidiaries

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

SEB cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/mcb-bank-limited.jpeg
MCB Bank Limited
Incidents

No Incident

https://images.rankiteo.com/companyimages/seb.jpeg
SEB
Incidents

No Incident

FAQ

SEB company demonstrates a stronger AI Cybersecurity Score compared to MCB Bank Limited company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, SEB company has disclosed a higher number of cyber incidents compared to MCB Bank Limited company.

In the current year, SEB company and MCB Bank Limited company have not reported any cyber incidents.

Neither SEB company nor MCB Bank Limited company has reported experiencing a ransomware attack publicly.

Neither SEB company nor MCB Bank Limited company has reported experiencing a data breach publicly.

Neither SEB company nor MCB Bank Limited company has reported experiencing targeted cyberattacks publicly.

Neither MCB Bank Limited company nor SEB company has reported experiencing or disclosing vulnerabilities publicly.

Neither MCB Bank Limited nor SEB holds any compliance certifications.

Neither company holds any compliance certifications.

SEB company has more subsidiaries worldwide compared to MCB Bank Limited company.

SEB company employs more people globally than MCB Bank Limited company, reflecting its scale as a Banking.

Neither MCB Bank Limited nor SEB holds SOC 2 Type 1 certification.

Neither MCB Bank Limited nor SEB holds SOC 2 Type 2 certification.

Neither MCB Bank Limited nor SEB holds ISO 27001 certification.

Neither MCB Bank Limited nor SEB holds PCI DSS certification.

Neither MCB Bank Limited nor SEB holds HIPAA certification.

Neither MCB Bank Limited nor SEB holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

NXLog Agent before 6.11 can load a file specified by the OPENSSL_CONF environment variable.

Risk Information
cvss3
Base: 8.1
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
Description

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Risk Information
cvss3
Base: 2.9
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
Description

A vulnerability was detected in Mayan EDMS up to 4.10.1. The affected element is an unknown function of the file /authentication/. The manipulation results in cross site scripting. The attack may be performed from remote. The exploit is now public and may be used. Upgrading to version 4.10.2 is sufficient to fix this issue. You should upgrade the affected component. The vendor confirms that this is "[f]ixed in version 4.10.2". Furthermore, that "[b]ackports for older versions in process and will be out as soon as their respective CI pipelines complete."

Risk Information
cvss2
Base: 5.0
Severity: LOW
AV:N/AC:L/Au:N/C:N/I:P/A:N
cvss3
Base: 4.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
cvss4
Base: 5.3
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P/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

MJML through 4.18.0 allows mj-include directory traversal to test file existence and (in the type="css" case) read files. NOTE: this issue exists because of an incomplete fix for CVE-2020-12827.

Risk Information
cvss3
Base: 4.5
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L
Description

A half-blind Server Side Request Forgery (SSRF) vulnerability exists in kube-controller-manager when using the in-tree Portworx StorageClass. This vulnerability allows authorized users to leak arbitrary information from unprotected endpoints in the control plane’s host network (including link-local or loopback services).

Risk Information
cvss3
Base: 5.8
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N