Comparison Overview

Yandex

VS

Avnet

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

Avnet

2211 South 47th Street, Phoenix, AZ, US, 85034
Last Update: 2025-12-09
Between 750 and 799

Avnet is a global electronic components distributor with extensive design, product, marketing and supply chain expertise for customers and suppliers at every stage of the product lifecycle. For the past 100 years, Avnet has helped its customers and suppliers around the world realize the transformative possibilities of technology. Our culture was founded on new ideas and emerging technology. Headquartered in Phoenix, Arizona, Avnet is a leading global technology distributor and solutions provider at the center of the technology value chain. Founded in 1921, we work with suppliers in every major technology segment to serve customers worldwide across a broad range of markets. Whether working on large-scale production or early prototypes, we meet customer needs through individualized, end-to-end service to streamline solutions and improve efficiency for customers worldwide. Headquartered in Phoenix, Arizona, we serve more than 1 million customers in more than 140 countries and partner with global suppliers from almost every technology segment. Learn more about Avnet at www.avnet.com.

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

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/avnet.jpeg
Avnet
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
Avnet
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 Avnet in 2025.

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

Yandex cyber incidents detection timeline including parent company and subsidiaries

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

Avnet 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/avnet.jpeg
Avnet
Incidents

No Incident

FAQ

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

Yandex company has historically faced a number of disclosed cyber incidents, whereas Avnet company has not reported any.

In the current year, Avnet company and Yandex company have not reported any cyber incidents.

Neither Avnet company nor Yandex company has reported experiencing a ransomware attack publicly.

Yandex company has disclosed at least one data breach, while the other Avnet company has not reported such incidents publicly.

Neither Avnet company nor Yandex company has reported experiencing targeted cyberattacks publicly.

Neither Yandex company nor Avnet company has reported experiencing or disclosing vulnerabilities publicly.

Neither Yandex nor Avnet holds any compliance certifications.

Neither company holds any compliance certifications.

Avnet company has more subsidiaries worldwide compared to Yandex company.

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

Neither Yandex nor Avnet holds SOC 2 Type 1 certification.

Neither Yandex nor Avnet holds SOC 2 Type 2 certification.

Neither Yandex nor Avnet holds ISO 27001 certification.

Neither Yandex nor Avnet holds PCI DSS certification.

Neither Yandex nor Avnet holds HIPAA certification.

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