Comparison Overview

A1 Hrvatska d.o.o.

VS

Jio

A1 Hrvatska d.o.o.

Last Update: 2025-11-20
Between 700 and 749

At A1 Croatia we take care that among the thousands existing options we can help you to find the best smart solutions that will simplify the complicated, save time and enjoy more. We do our best to improve digital customer experience with constant innovations and solutions. We are proud to say that our 2.000 employees take care of the needs of 2 million customers on everyday basis. WE ARE PART OF A1 TELEKOM AUSTRIA GROUP A1 Hrvatska is a part of A1 Telekom Austria Group, leading provider of digital services and communications solutions in Central and Eastern Europe. Together we are offering a state-of-the art network infrastructure and strive to empower digital life of more than 24 million users in areas of communications, payment, entertainment services and integrated business solutions. In Europe, the Group operates also in Austria, Bulgaria, Croatia, Slovenia, Belarus, Republic of Serbia and Republic of Macedonia. Headquartered in Vienna, the Group is an European unit of América Móvil, one of the world´s largest wireless services providers. You can find more info about A1 Telekom Austria Group here: https://www.linkedin.com/company/a1-telekom-austria-group/

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

Jio

Reliance Corporate Park, Navi Mumbai, Maharashtra, 400701, IN
Last Update: 2025-11-20
Between 750 and 799

Make a new start. A start that will build beautiful relationships, shape millions of ideas. Enable a new way to live, learn, work and play. At Jio, we build products and services of the future to empower billions of Indians make their dreams a reality. Jio is about YOU. Join the movement to make India Digital. Chat on MyJio App: http://tiny.jio.com/chat1 Chat on WhatsApp: http://tiny.jio.com/LiveChat

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/a1hrvatska.jpeg
A1 Hrvatska d.o.o.
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/jio.jpeg
Jio
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
A1 Hrvatska d.o.o.
100%
Compliance Rate
0/4 Standards Verified
Jio
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for A1 Hrvatska d.o.o. in 2025.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Jio in 2025.

Incident History — A1 Hrvatska d.o.o. (X = Date, Y = Severity)

A1 Hrvatska d.o.o. cyber incidents detection timeline including parent company and subsidiaries

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

Jio cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/a1hrvatska.jpeg
A1 Hrvatska d.o.o.
Incidents

Date Detected: 02/2022
Type:Breach
Blog: Blog

Date Detected: 11/2019
Type:Breach
Blog: Blog
https://images.rankiteo.com/companyimages/jio.jpeg
Jio
Incidents

Date Detected: 05/2020
Type:Data Leak
Attack Vector: Unsecured Database
Blog: Blog

Date Detected: 07/2017
Type:Breach
Blog: Blog

Date Detected: 02/2017
Type:Data Leak
Blog: Blog

FAQ

Jio company demonstrates a stronger AI Cybersecurity Score compared to A1 Hrvatska d.o.o. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Jio company has faced a higher number of disclosed cyber incidents historically compared to A1 Hrvatska d.o.o. company.

In the current year, Jio company and A1 Hrvatska d.o.o. company have not reported any cyber incidents.

Neither Jio company nor A1 Hrvatska d.o.o. company has reported experiencing a ransomware attack publicly.

Both Jio company and A1 Hrvatska d.o.o. company have disclosed experiencing at least one data breach.

Neither Jio company nor A1 Hrvatska d.o.o. company has reported experiencing targeted cyberattacks publicly.

Neither A1 Hrvatska d.o.o. company nor Jio company has reported experiencing or disclosing vulnerabilities publicly.

Neither A1 Hrvatska d.o.o. nor Jio holds any compliance certifications.

Neither company holds any compliance certifications.

A1 Hrvatska d.o.o. company has more subsidiaries worldwide compared to Jio company.

Jio company employs more people globally than A1 Hrvatska d.o.o. company, reflecting its scale as a Telecommunications.

Neither A1 Hrvatska d.o.o. nor Jio holds SOC 2 Type 1 certification.

Neither A1 Hrvatska d.o.o. nor Jio holds SOC 2 Type 2 certification.

Neither A1 Hrvatska d.o.o. nor Jio holds ISO 27001 certification.

Neither A1 Hrvatska d.o.o. nor Jio holds PCI DSS certification.

Neither A1 Hrvatska d.o.o. nor Jio holds HIPAA certification.

Neither A1 Hrvatska d.o.o. nor Jio 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