Comparison Overview

Coinmama

VS

Mizuho

Coinmama

Ontario, CA
Last Update: 2025-12-01
Between 700 and 749

Coinmama believes that the future of money is open source, decentralized and borderless. We believe that economic freedom and financial services should be available to every human being. It's why our mission is to simplify the way the world does cryptocurrency, and why we work to make crypto easy, friendly, and safe for our growing community of 2 million users around the world. We're here to serve you in this financial revolution. For more information, visit our company site at www.coinmama.com

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

Mizuho

1–5–5 Otemachi, Chiyoda–ku, Tokyo, Japan, JP, 100–8176
Last Update: 2025-12-01
Between 800 and 849

This is not your typical financial institution. It’s our people who make us a cut above. Here, every person is respected because of their differences, not in spite of them. We pride ourselves on a culture of purpose, passion and compassion. At Mizuho, we provide the stability of an international industry leader with the career trajectory of a growing business. Our steady, strategic growth gives our people at all levels rewarding degrees of responsibility and a richer work experience than a boutique firm or an established giant could offer alone. Working for Mizuho opens doors not just to a rewarding career with excellent prospects, but to lasting friendships with colleagues from diverse cultures. It’s the local expertise of our employees that makes our global network so powerful. By collaborating with colleagues and clients who have your same ambition, you can amplify your sphere of influence and base of knowledge as part of one of the largest—and growing—banks in the world. We’re all global citizens, and that’s why our company feels compelled to make an impact through more than just drawing up deals. We prove that it’s possible to do well and do good. We do right by our clients, our community and each other.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/coinmama.jpeg
Coinmama
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/mizuho.jpeg
Mizuho
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
Coinmama
100%
Compliance Rate
0/4 Standards Verified
Mizuho
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Coinmama in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Mizuho in 2025.

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

Coinmama cyber incidents detection timeline including parent company and subsidiaries

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

Mizuho cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/coinmama.jpeg
Coinmama
Incidents

Date Detected: 6/2017
Type:Data Leak
Attack Vector: Multi-platform Hack
Blog: Blog
https://images.rankiteo.com/companyimages/mizuho.jpeg
Mizuho
Incidents

No Incident

FAQ

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

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

In the current year, Mizuho company and Coinmama company have not reported any cyber incidents.

Neither Mizuho company nor Coinmama company has reported experiencing a ransomware attack publicly.

Neither Mizuho company nor Coinmama company has reported experiencing a data breach publicly.

Neither Mizuho company nor Coinmama company has reported experiencing targeted cyberattacks publicly.

Neither Coinmama company nor Mizuho company has reported experiencing or disclosing vulnerabilities publicly.

Neither Coinmama nor Mizuho holds any compliance certifications.

Neither company holds any compliance certifications.

Mizuho company has more subsidiaries worldwide compared to Coinmama company.

Mizuho company employs more people globally than Coinmama company, reflecting its scale as a Financial Services.

Neither Coinmama nor Mizuho holds SOC 2 Type 1 certification.

Neither Coinmama nor Mizuho holds SOC 2 Type 2 certification.

Neither Coinmama nor Mizuho holds ISO 27001 certification.

Neither Coinmama nor Mizuho holds PCI DSS certification.

Neither Coinmama nor Mizuho holds HIPAA certification.

Neither Coinmama nor Mizuho holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: hide VRAM sysfs attributes on GPUs without VRAM Otherwise accessing them can cause a crash.

Description

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix NULL pointer dereference in VRAM logic for APU devices Previously, APU platforms (and other scenarios with uninitialized VRAM managers) triggered a NULL pointer dereference in `ttm_resource_manager_usage()`. The root cause is not that the `struct ttm_resource_manager *man` pointer itself is NULL, but that `man->bdev` (the backing device pointer within the manager) remains uninitialized (NULL) on APUs—since APUs lack dedicated VRAM and do not fully set up VRAM manager structures. When `ttm_resource_manager_usage()` attempts to acquire `man->bdev->lru_lock`, it dereferences the NULL `man->bdev`, leading to a kernel OOPS. 1. **amdgpu_cs.c**: Extend the existing bandwidth control check in `amdgpu_cs_get_threshold_for_moves()` to include a check for `ttm_resource_manager_used()`. If the manager is not used (uninitialized `bdev`), return 0 for migration thresholds immediately—skipping VRAM-specific logic that would trigger the NULL dereference. 2. **amdgpu_kms.c**: Update the `AMDGPU_INFO_VRAM_USAGE` ioctl and memory info reporting to use a conditional: if the manager is used, return the real VRAM usage; otherwise, return 0. This avoids accessing `man->bdev` when it is NULL. 3. **amdgpu_virt.c**: Modify the vf2pf (virtual function to physical function) data write path. Use `ttm_resource_manager_used()` to check validity: if the manager is usable, calculate `fb_usage` from VRAM usage; otherwise, set `fb_usage` to 0 (APUs have no discrete framebuffer to report). This approach is more robust than APU-specific checks because it: - Works for all scenarios where the VRAM manager is uninitialized (not just APUs), - Aligns with TTM's design by using its native helper function, - Preserves correct behavior for discrete GPUs (which have fully initialized `man->bdev` and pass the `ttm_resource_manager_used()` check). v4: use ttm_resource_manager_used(&adev->mman.vram_mgr.manager) instead of checking the adev->gmc.is_app_apu flag (Christian)

Description

In the Linux kernel, the following vulnerability has been resolved: exfat: fix improper check of dentry.stream.valid_size We found an infinite loop bug in the exFAT file system that can lead to a Denial-of-Service (DoS) condition. When a dentry in an exFAT filesystem is malformed, the following system calls — SYS_openat, SYS_ftruncate, and SYS_pwrite64 — can cause the kernel to hang. Root cause analysis shows that the size validation code in exfat_find() does not check whether dentry.stream.valid_size is negative. As a result, the system calls mentioned above can succeed and eventually trigger the DoS issue. This patch adds a check for negative dentry.stream.valid_size to prevent this vulnerability.

Description

In the Linux kernel, the following vulnerability has been resolved: smb/server: fix possible memory leak in smb2_read() Memory leak occurs when ksmbd_vfs_read() fails. Fix this by adding the missing kvfree().

Description

In the Linux kernel, the following vulnerability has been resolved: smb/server: fix possible refcount leak in smb2_sess_setup() Reference count of ksmbd_session will leak when session need reconnect. Fix this by adding the missing ksmbd_user_session_put().