Comparison Overview

GitHub

VS

Google

GitHub

88 Colin P Kelly Jr St, None, San Francisco, CA, US, 94107
Last Update: 2025-11-21
View Profile
Between 550 and 599
https://github.com

As the global home for all developers, GitHub is the complete AI-powered developer platform to build, scale, and deliver secure software. Over 100 million people, including developers from 90 of the Fortune 100 companies, use GitHub to build amazing things together across 330+ million repositories. With all the collaborative features of GitHub, it has never been easier for individuals and teams to write faster, better code.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 5,536
Subsidiaries: 49
12-month incidents
7
Known data breaches
9
Attack type number
5
View Profile

Google

1600 Amphitheatre Parkway, Mountain View, 94043, US
Last Update: 2025-11-22
Between 700 and 749
https://goo.gle/3DLEokh

A problem isn't truly solved until it's solved for all. Googlers build products that help create opportunities for everyone, whether down the street or across the globe. Bring your insight, imagination and a healthy disregard for the impossible. Bring everything that makes you unique. Together, we can build for everyone. Check out our career opportunities at goo.gle/3DLEokh

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 324,578
Subsidiaries: 52
12-month incidents
15
Known data breaches
6
Attack type number
5

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/github.jpeg
GitHub
—
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/google.jpeg
Google
—
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
GitHub
100%
Compliance Rate
0/4 Standards Verified
Google
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

GitHub has 1490.91% more incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs Software Development Industry Average (This Year)

Google has 3309.09% more incidents than the average of same-industry companies with at least one recorded incident.

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

GitHub cyber incidents detection timeline including parent company and subsidiaries

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

Google cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/github.jpeg
GitHub
Incidents

Date Detected: 11/2025
Type:Cyber Attack
Attack Vector: AI Agent Exploitation (e.g., autonomous decision-making, broad data access), SaaS Infrastructure Compromise (e.g., widely-deployed firewalls), Identity Sprawl (e.g., over-permissioned roles, shadow identities), Synthetic Social Engineering (e.g., deepfakes, adaptive phishing), Critical Infrastructure Targeting (e.g., energy grids, water systems), Supply Chain Attacks (e.g., multi-cloud complexities), Concentrated Infrastructure Risk (e.g., Microsoft, Amazon, Google backbones)
Motivation: Financial Gain (e.g., ransomware, data exfiltration), Geopolitical Disruption (e.g., critical infrastructure sabotage), Espionage (e.g., AI-driven data theft), Market Manipulation (e.g., disrupting cloud providers), Talent Pipeline Exploitation (e.g., targeting entry-level job gaps)
Blog: Blog

Date Detected: 11/2025
Type:Ransomware
Attack Vector: Malicious Extension (VS Code Marketplace), Trojanized npm Packages, GitHub C2, Postinstall Scripts
Motivation: Testing/Experimental (susvsex), Financial Gain (Vidar Infostealer), Data Theft
Blog: Blog

Date Detected: 10/2025
Type:Cyber Attack
Attack Vector: Microsoft Teams Chats/Messages, Malicious Links/Files in Teams, Fake Profiles/Impersonation, Exploiting Privacy Mode Disabled, Guest/External Access Abuse, Public Meeting Links, Teams as Command-and-Control (C2), Ransom Demands via Teams
Motivation: Financial Gain (e.g., Ransomware, Data Theft), Espionage (Corporate/State), Credential Theft, Lateral Movement in Target Networks, Disruption (e.g., Locking Personal/Work Files)
Blog: Blog
https://images.rankiteo.com/companyimages/google.jpeg
Google
Incidents

Date Detected: 8/2025
Type:Cyber Attack
Attack Vector: Email Spoofing, Messaging Platform (WhatsApp)
Motivation: Financial Gain (Fraudulent Services/Products) or Data Theft
Blog: Blog

Date Detected: 8/2025
Type:Vulnerability
Attack Vector: Use-After-Free (UAF) vulnerability in the Linux HFSC queuing discipline
Motivation: Security Research and Bounty
Blog: Blog

Date Detected: 7/2025
Type:Vulnerability
Attack Vector: Prompt-injection technique through crafted HTML and CSS code
Motivation: Credential theft, social engineering
Blog: Blog

FAQ

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

GitHub company has faced a higher number of disclosed cyber incidents historically compared to Google company.

In the current year, GitHub company has reported more cyber incidents than Google company.

Both Google company and GitHub company have confirmed experiencing at least one ransomware attack.

Both Google company and GitHub company have disclosed experiencing at least one data breach.

Both Google company and GitHub company have reported experiencing targeted cyberattacks.

Both GitHub company and Google company have disclosed vulnerabilities.

Neither GitHub nor Google holds any compliance certifications.

Neither company holds any compliance certifications.

Google company has more subsidiaries worldwide compared to GitHub company.

Google company employs more people globally than GitHub company, reflecting its scale as a Software Development.

Neither GitHub nor Google holds SOC 2 Type 1 certification.

Neither GitHub nor Google holds SOC 2 Type 2 certification.

Neither GitHub nor Google holds ISO 27001 certification.

Neither GitHub nor Google holds PCI DSS certification.

Neither GitHub nor Google holds HIPAA certification.

Neither GitHub nor Google 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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References
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.

Published
Date
2025-11-26
Updated
Date
2025-11-26
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
References