Comparison Overview

Google Chrome

VS

NetEase

Google Chrome

1600 Amphitheatre Parkway, Mountain View, CA, US, 94043
Last Update: 2025-11-23

Fast, simple and secure. The browser built by Google is designed to help you stay productive while on the web. Find the latest features, news and stories behind the technology from the browser.

NAICS: 513
NAICS Definition: Others
Employees: None
Subsidiaries: 48
12-month incidents
1
Known data breaches
6
Attack type number
5

NetEase

No.599 Wangshang Road, Binjiang District, Hangzhou, Zhejiang, CN, 310052
Last Update: 2025-11-27
Between 800 and 849

As a leading internet technology company based in China, NetEase, Inc. (NASDAQ: NTES and HKEX:9999, "NetEase") provides premium online services centered around content creation. With extensive offerings across its expanding gaming ecosystem, NetEase develops and operates some of China's most popular and longest running mobile and PC games. Powered by industry-leading inhouse R&D capabilities in China and globally, NetEase creates superior gaming experiences, inspires players and passionately delivers value for its thriving community worldwide. Beyond games, NetEase service offerings include its majority-controlled subsidiaries Youdao (NYSE:DAO), China's leading technology-focused intelligent learning company, and Cloud Music (HKEX:9899), China's leading online music content community, as well as Yanxuan, NetEase's private label consumer lifestyle brand.

NAICS: 513
NAICS Definition: Others
Employees: 11,907
Subsidiaries: 4
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/google-chrome.jpeg
Google Chrome
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/netease.jpeg
NetEase
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
Google Chrome
100%
Compliance Rate
0/4 Standards Verified
NetEase
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Technology, Information and Internet Industry Average (This Year)

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

Incidents vs Technology, Information and Internet Industry Average (This Year)

No incidents recorded for NetEase in 2025.

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

Google Chrome cyber incidents detection timeline including parent company and subsidiaries

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

NetEase cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/google-chrome.jpeg
Google Chrome
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
https://images.rankiteo.com/companyimages/netease.jpeg
NetEase
Incidents

No Incident

FAQ

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

Google Chrome company has historically faced a number of disclosed cyber incidents, whereas NetEase company has not reported any.

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

Google Chrome company has confirmed experiencing a ransomware attack, while NetEase company has not reported such incidents publicly.

Google Chrome company has disclosed at least one data breach, while the other NetEase company has not reported such incidents publicly.

Google Chrome company has reported targeted cyberattacks, while NetEase company has not reported such incidents publicly.

Google Chrome company has disclosed at least one vulnerability, while NetEase company has not reported such incidents publicly.

Neither Google Chrome nor NetEase holds any compliance certifications.

Neither company holds any compliance certifications.

Google Chrome company has more subsidiaries worldwide compared to NetEase company.

Neither Google Chrome nor NetEase holds SOC 2 Type 1 certification.

Neither Google Chrome nor NetEase holds SOC 2 Type 2 certification.

Neither Google Chrome nor NetEase holds ISO 27001 certification.

Neither Google Chrome nor NetEase holds PCI DSS certification.

Neither Google Chrome nor NetEase holds HIPAA certification.

Neither Google Chrome nor NetEase 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