Comparison Overview

Alphabet Inc.

VS

SRG

Alphabet Inc.

1600 Amphitheatre Parkway, None, Mountain View, CA, US, 94043
Last Update: 2025-11-21
Between 800 and 849

Alphabet is a collection of companies, including Google, Verily Life Sciences, GV, Calico, and X. In October 2015, Alphabet became the parent holding company of Google, with the companies far afield of our main internet products contained in Alphabet.

NAICS: 55
NAICS Definition: Management of Companies and Enterprises
Employees: 2,593
Subsidiaries: 0
12-month incidents
1
Known data breaches
1
Attack type number
1

SRG

PO Box 6669, Dammam 31452, Saudi Arabia. Dammam, Eastern 31452, SA
Last Update: 2025-11-26
Between 750 and 799

Saeed Raddad Group (SRG) has had an influential and substantial presence in the commercial and business life of Saudi Arabia since 1982 with manpower of more than 34,000 employees. SRG companies operate in diversified business sectors having significant local & international operations. SRG is an investment holding powerhouse headquartered in Dammam, Saudi Arabia. The Group, which has a diverse portfolio of market leading businesses across the Construction, Manufacturing, Oil & Gas, Travel & Tourism, Manpower, Pharmaceutical and Trading sectors, is the region’s preferred investment partner and employer of choice. SRG main subsidiaries are, SRACO group, UCC group, GTS, Dammam palace, Manifa, Napesco, TST, and Alrazi pharma. Show more Show less

NAICS: 551
NAICS Definition:
Employees: 10,001
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/alphabet-inc.jpeg
Alphabet Inc.
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/sraco.jpeg
SRG
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
Alphabet Inc.
100%
Compliance Rate
0/4 Standards Verified
SRG
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Holding Companies Industry Average (This Year)

Alphabet Inc. has 0.0% fewer incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Holding Companies Industry Average (This Year)

No incidents recorded for SRG in 2025.

Incident History — Alphabet Inc. (X = Date, Y = Severity)

Alphabet Inc. cyber incidents detection timeline including parent company and subsidiaries

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

SRG cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/alphabet-inc.jpeg
Alphabet Inc.
Incidents

Date Detected: 8/2025
Type:Breach
Attack Vector: Third-Party Vendor (Salesforce Database), Data Exposure via Search Engines
Blog: Blog
https://images.rankiteo.com/companyimages/sraco.jpeg
SRG
Incidents

No Incident

FAQ

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

Alphabet Inc. company has historically faced a number of disclosed cyber incidents, whereas SRG company has not reported any.

In the current year, Alphabet Inc. company has reported more cyber incidents than SRG company.

Neither SRG company nor Alphabet Inc. company has reported experiencing a ransomware attack publicly.

Alphabet Inc. company has disclosed at least one data breach, while the other SRG company has not reported such incidents publicly.

Neither SRG company nor Alphabet Inc. company has reported experiencing targeted cyberattacks publicly.

Neither Alphabet Inc. company nor SRG company has reported experiencing or disclosing vulnerabilities publicly.

Neither Alphabet Inc. nor SRG holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Alphabet Inc. company nor SRG company has publicly disclosed detailed information about the number of their subsidiaries.

SRG company employs more people globally than Alphabet Inc. company, reflecting its scale as a Holding Companies.

Neither Alphabet Inc. nor SRG holds SOC 2 Type 1 certification.

Neither Alphabet Inc. nor SRG holds SOC 2 Type 2 certification.

Neither Alphabet Inc. nor SRG holds ISO 27001 certification.

Neither Alphabet Inc. nor SRG holds PCI DSS certification.

Neither Alphabet Inc. nor SRG holds HIPAA certification.

Neither Alphabet Inc. nor SRG 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