Comparison Overview

Aboitiz Group

VS

Block

Aboitiz Group

NAC Tower, 32nd Street,, Bonifacio Global City, Taguig City, PH
Last Update: 2025-12-09
Between 750 and 799

Here at Aboitiz, we aim to change today to shape the future. With five generations of success behind us, the Aboitiz Group is currently transforming into the Philippines’ first techglomerate. Amidst this evolution, we remain committed to our core mission of driving change for a better world by advancing businesses and communities.

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

Block

None, None, Oakland, California, US, None
Last Update: 2025-12-11
Between 700 and 749

Block is one company built from many blocks, all united by the same purpose of economic empowerment. The blocks that form our foundational teams — People, Finance, Counsel, Hardware, Information Security, Platform Infrastructure Engineering, and more — provide support and guidance at the corporate level. They work across business groups and around the globe, spanning time zones and disciplines to develop inclusive People policies, forecast finances, give legal counsel, safeguard systems, nurture new initiatives, and more. Every challenge creates possibilities, and we need different perspectives to see them all. Bring yours to Block.

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/aboitiz.jpeg
Aboitiz 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/joinblock.jpeg
Block
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
Aboitiz Group
100%
Compliance Rate
0/4 Standards Verified
Block
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Aboitiz Group in 2025.

Incidents vs Financial Services Industry Average (This Year)

No incidents recorded for Block in 2025.

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

Aboitiz Group cyber incidents detection timeline including parent company and subsidiaries

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

Block cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/aboitiz.jpeg
Aboitiz Group
Incidents

No Incident

https://images.rankiteo.com/companyimages/joinblock.jpeg
Block
Incidents

Date Detected: 12/2021
Type:Breach
Attack Vector: Insider Threat (former employee)
Motivation: Financial Gain (alleged by shareholders), Unauthorized Data Access
Blog: Blog

FAQ

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

Block company has historically faced a number of disclosed cyber incidents, whereas Aboitiz Group company has not reported any.

In the current year, Block company and Aboitiz Group company have not reported any cyber incidents.

Neither Block company nor Aboitiz Group company has reported experiencing a ransomware attack publicly.

Block company has disclosed at least one data breach, while Aboitiz Group company has not reported such incidents publicly.

Neither Block company nor Aboitiz Group company has reported experiencing targeted cyberattacks publicly.

Neither Aboitiz Group company nor Block company has reported experiencing or disclosing vulnerabilities publicly.

Neither Aboitiz Group nor Block holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Aboitiz Group company nor Block company has publicly disclosed detailed information about the number of their subsidiaries.

Block company employs more people globally than Aboitiz Group company, reflecting its scale as a Financial Services.

Neither Aboitiz Group nor Block holds SOC 2 Type 1 certification.

Neither Aboitiz Group nor Block holds SOC 2 Type 2 certification.

Neither Aboitiz Group nor Block holds ISO 27001 certification.

Neither Aboitiz Group nor Block holds PCI DSS certification.

Neither Aboitiz Group nor Block holds HIPAA certification.

Neither Aboitiz Group nor Block 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