Comparison Overview

beeline Russia

VS

Bouygues Telecom

beeline Russia

Krasnoproletarskaya, 4, Moscow, RU, 127006
Last Update: 2025-11-28
Between 700 and 749

VimpelCom is one of the world’s largest integrated telecommunications services operators providing voice and data services through a range of traditional and broadband mobile and fixed technologies in Russia, Italy, Ukraine, Kazakhstan, Uzbekistan, Tajikistan, Armenia, Georgia, Kyrgyzstan, Laos, Algeria, Bangladesh, Pakistan, and Zimbabwe. VimpelCom’s operations around the globe cover territory with a total population of approximately 740 million people. VimpelCom provides services under the "Beeline"​, "Kyivstar"​, “WIND”, "Infostrada"​ “Mobilink”, “Banglalink”, “Telecel”, and “Djezzy” brands. As of 6 August, 2015 VimpelCom had 213 million mobile customers on a combined basis. VimpelCom is headquartered in Amsterdam, the Netherlands and is traded on the NASDAQ Global Select Market under the symbol "VIP"​. With annual 2014 revenue of USD 19.6 billion and EBITDA of USD 8 billion, we are one of the largest telecommunications companies in the industry and have established the scale for successful growth and development of our group of companies going forward.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 2,017
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1

Bouygues Telecom

13/15 avenue du Maréchal Juin, None, Meudon-la-Forêt, None, FR, 92360
Last Update: 2025-11-25

🤝Ce qui fait notre singularité ? Chez Bouygues Telecom, nous croyons que les relations humaines sont un besoin vital. La qualité de nos relations avec notre famille, nos amis, ceux qui nous entourent est déterminante pour notre bien-être, notre santé et même notre espérance de vie. Ce sont ces relations qui nous épanouissent, nous font aller de l’avant et nous permettent de vivre plus heureux, plus longtemps. C’est pourquoi depuis notre création en 1996, les équipes Bouygues Telecom mettent toute leur énergie pour que la technologie soit avant tout au service de vos relations. Nous souhaitons agir pour faire grandir les relations humaines. En permettant à tous sans exception de garder le contact avec ses proches et la société. En devenant une source d’inspiration qui donne à chacun l’envie d’enrichir et d’améliorer la qualité de ses relations. Nos 10 500 collaborateurs relèvent tous ensemble au quotidien ce même défi : être engagés pour un numérique qui nous réunit. 💼 Nos métiers ? Quelles que soient vos aspirations il y aura forcément un métier pour vous chez Bouygues Telecom ! Plus de 150 métiers interagissent tous les jours : Télécom / Réseau, IT, Big Data, Innovation, Marketing, Commerce, Finance, Achats, Juridique… Nous avons besoin de tous les talents pour accomplir notre mission; car c’est cette richesse de profils et de compétences qui fait la qualité de nos services et contribue à la satisfaction de nos clients. 👉Alors si... Vous avez envie de mettre votre talent au service du développement numérique pour tous et de faire grandir les relations humaines : vous frappez à la bonne porte. Vous rêvez d’une entreprise qui donne le meilleur d’elle-même pour que vous puissiez donner le meilleur à votre tour : alors bienvenue ! #OnEstFaitPourEtreEnsemble

NAICS: 517
NAICS Definition: Telecommunications
Employees: 12,549
Subsidiaries: 0
12-month incidents
1
Known data breaches
0
Attack type number
1

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/beeline-russia.jpeg
beeline Russia
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/bouygues-telecom.jpeg
Bouygues Telecom
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
beeline Russia
100%
Compliance Rate
0/4 Standards Verified
Bouygues Telecom
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for beeline Russia in 2025.

Incidents vs Telecommunications Industry Average (This Year)

Bouygues Telecom has 69.49% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — beeline Russia (X = Date, Y = Severity)

beeline Russia cyber incidents detection timeline including parent company and subsidiaries

Incident History — Bouygues Telecom (X = Date, Y = Severity)

Bouygues Telecom cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/beeline-russia.jpeg
beeline Russia
Incidents

Date Detected: 6/2016
Type:Data Leak
Blog: Blog
https://images.rankiteo.com/companyimages/bouygues-telecom.jpeg
Bouygues Telecom
Incidents

Date Detected: 8/2025
Type:Cyber Attack
Blog: Blog

FAQ

Bouygues Telecom company demonstrates a stronger AI Cybersecurity Score compared to beeline Russia company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

beeline Russia and Bouygues Telecom have experienced a similar number of publicly disclosed cyber incidents.

In the current year, Bouygues Telecom company has reported more cyber incidents than beeline Russia company.

Neither Bouygues Telecom company nor beeline Russia company has reported experiencing a ransomware attack publicly.

Neither Bouygues Telecom company nor beeline Russia company has reported experiencing a data breach publicly.

Bouygues Telecom company has reported targeted cyberattacks, while beeline Russia company has not reported such incidents publicly.

Neither beeline Russia company nor Bouygues Telecom company has reported experiencing or disclosing vulnerabilities publicly.

Neither beeline Russia nor Bouygues Telecom holds any compliance certifications.

Neither company holds any compliance certifications.

Neither beeline Russia company nor Bouygues Telecom company has publicly disclosed detailed information about the number of their subsidiaries.

Bouygues Telecom company employs more people globally than beeline Russia company, reflecting its scale as a Telecommunications.

Neither beeline Russia nor Bouygues Telecom holds SOC 2 Type 1 certification.

Neither beeline Russia nor Bouygues Telecom holds SOC 2 Type 2 certification.

Neither beeline Russia nor Bouygues Telecom holds ISO 27001 certification.

Neither beeline Russia nor Bouygues Telecom holds PCI DSS certification.

Neither beeline Russia nor Bouygues Telecom holds HIPAA certification.

Neither beeline Russia nor Bouygues Telecom 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