Comparison Overview

inCharge Global

VS

Barclays

inCharge Global

4th Floor, Ghana House Ghana Multimedia Center Accra High Street, Greater Accra AN 16731, GH
Last Update: 2025-11-21

inCharge is an Mobile Financial Services company, providing Mobile Banking, mCommerce, Card products, Loyalty programs, Electronic Banking platforms and an Agent network to support Financial Inclusion and Mobile Money. inCharge is partnered with Ecobank, to develop and offer Financial services to the unbanked. Our portfolio of services include: > Agent Network - Recruitment and Management > Technology platform development for Mobile Banking, Mobile Payments and Mobile Commerce > Bulk Disbursements > Customer loyalty management > Revenue collection inCharge Global offers the last mile to all Corporates, Governments, Multi-Nationals and organizations looking for an easier way to pay and collect from the unbanked public in Africa.

NAICS: 52
NAICS Definition:
Employees: 10,001
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Barclays

1 Churchill Place, London, GB, E14 5HP
Last Update: 2025-11-20
Between 800 and 849

Barclays is a British universal bank. Our vision is to be the UK-centred leader in global finance. We are a diversified bank with comprehensive UK consumer, corporate and wealth and private banking franchises, a leading investment bank and a strong, specialist US consumer bank. Through these five divisions, we are working together for a better financial future for our customers, clients and communities. With over 325 years of history and expertise in banking, Barclays operates in over 40 countries and employs approximately 83,500 people. Barclays moves, lends, invests and protects money for customers and clients worldwide. Barclays is a trading name of Barclays Bank PLC and its subsidiaries. Barclays Bank PLC is registered in England and is authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Registered in England. Registered No. 1026167. Registered office: 1 Churchill Place, London E14 5HP.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/incharge-global.jpeg
inCharge Global
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/barclays-bank.jpeg
Barclays
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
inCharge Global
100%
Compliance Rate
0/4 Standards Verified
Barclays
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for inCharge Global in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Barclays in 2025.

Incident History — inCharge Global (X = Date, Y = Severity)

inCharge Global cyber incidents detection timeline including parent company and subsidiaries

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

Barclays cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/incharge-global.jpeg
inCharge Global
Incidents

No Incident

https://images.rankiteo.com/companyimages/barclays-bank.jpeg
Barclays
Incidents

No Incident

FAQ

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

Historically, Barclays company has disclosed a higher number of cyber incidents compared to inCharge Global company.

In the current year, Barclays company and inCharge Global company have not reported any cyber incidents.

Neither Barclays company nor inCharge Global company has reported experiencing a ransomware attack publicly.

Neither Barclays company nor inCharge Global company has reported experiencing a data breach publicly.

Neither Barclays company nor inCharge Global company has reported experiencing targeted cyberattacks publicly.

Neither inCharge Global company nor Barclays company has reported experiencing or disclosing vulnerabilities publicly.

Neither inCharge Global nor Barclays holds any compliance certifications.

Neither company holds any compliance certifications.

Barclays company has more subsidiaries worldwide compared to inCharge Global company.

Barclays company employs more people globally than inCharge Global company, reflecting its scale as a Financial Services.

Neither inCharge Global nor Barclays holds SOC 2 Type 1 certification.

Neither inCharge Global nor Barclays holds SOC 2 Type 2 certification.

Neither inCharge Global nor Barclays holds ISO 27001 certification.

Neither inCharge Global nor Barclays holds PCI DSS certification.

Neither inCharge Global nor Barclays holds HIPAA certification.

Neither inCharge Global nor Barclays 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