Comparison Overview

Yandex

VS

YouTube

Yandex

Last Update: 2025-12-09
Between 650 and 699

Yandex is a technology company that builds intelligent products and services powered by machine learning. Our goal is to help consumers and businesses better navigate the online and offline world. Since 1997, we have delivered world-class, locally relevant search and information services. Additionally, we have developed market-leading on-demand transportation services, navigation products, and other mobile applications for millions of consumers across the globe. Yandex, which has 34 offices worldwide, has been listed on the NASDAQ since 2011.

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

YouTube

901 Cherry Ave., San Bruno, CA, US, 94066
Last Update: 2025-12-09
Between 800 and 849

YouTube is a team-oriented, creative workplace where every single employee has a voice in the choices we make and the features we implement. We work together in small teams to design, develop, and roll out key features and products in very short time frames. Which means something you write today could be seen by millions of viewers tomorrow. And even though we’re a part of Google and enjoy all of the corporate perks, it still feels like you’re working at a startup. YouTube is headquartered in San Bruno, California, 12 miles south of San Francisco. We also have many job openings in Mountain View, and across the globe

NAICS: 513
NAICS Definition: Others
Employees: 139,702
Subsidiaries: 44
12-month incidents
0
Known data breaches
4
Attack type number
5

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/yandex.jpeg
Yandex
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/youtube.jpeg
YouTube
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
Yandex
100%
Compliance Rate
0/4 Standards Verified
YouTube
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

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

No incidents recorded for Yandex in 2025.

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

No incidents recorded for YouTube in 2025.

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

Yandex cyber incidents detection timeline including parent company and subsidiaries

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

YouTube cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/yandex.jpeg
Yandex
Incidents

Date Detected: 8/2024
Type:Breach
Attack Vector: Android Spyware
Motivation: Cyberespionage
Blog: Blog

Date Detected: 01/2023
Type:Breach
Attack Vector: Insider Threat
Motivation: Unknown
Blog: Blog

Date Detected: 2/2022
Type:Data Leak
Attack Vector: Insider Threat
Blog: Blog
https://images.rankiteo.com/companyimages/youtube.jpeg
YouTube
Incidents

Date Detected: 12/2025
Type:Vulnerability
Attack Vector: Email processing systems, Calendar invitation structures, Document files
Blog: Blog

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: 7/2025
Type:Vulnerability
Attack Vector: Prompt-injection technique through crafted HTML and CSS code
Motivation: Credential theft, social engineering
Blog: Blog

FAQ

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

YouTube company has faced a higher number of disclosed cyber incidents historically compared to Yandex company.

In the current year, YouTube company has reported more cyber incidents than Yandex company.

YouTube company has confirmed experiencing a ransomware attack, while Yandex company has not reported such incidents publicly.

Both YouTube company and Yandex company have disclosed experiencing at least one data breach.

YouTube company has reported targeted cyberattacks, while Yandex company has not reported such incidents publicly.

YouTube company has disclosed at least one vulnerability, while Yandex company has not reported such incidents publicly.

Neither Yandex nor YouTube holds any compliance certifications.

Neither company holds any compliance certifications.

YouTube company has more subsidiaries worldwide compared to Yandex company.

YouTube company employs more people globally than Yandex company, reflecting its scale as a Technology, Information and Internet.

Neither Yandex nor YouTube holds SOC 2 Type 1 certification.

Neither Yandex nor YouTube holds SOC 2 Type 2 certification.

Neither Yandex nor YouTube holds ISO 27001 certification.

Neither Yandex nor YouTube holds PCI DSS certification.

Neither Yandex nor YouTube holds HIPAA certification.

Neither Yandex nor YouTube 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