Comparison Overview

Kigen

VS

TIM Brasil

Kigen

Kigen Ltd, c/o Mishcon de Reya, Four Station Square,, Cambridge, England, GB, CB1 2GE
Last Update: 2026-01-19
View Profile
Between 750 and 799
https://kigen.com

At Kigen, we are making the future of securing connectivity simple. As simple as can be. Together with our partners and customers, we are unlocking new opportunities as (integrated) eSIM becomes the cornerstone of connected devices security. Our industry-leading SIM OS products enable over 2 billion SIMs. Our remote SIM provisioning and eSIM services drive this momentum further placing us amongst top 5 SIM vendors globally. Our 150 employees globally are guided by the vision of a world where every device can connect securely and reliably. For more information, go to kigen.com or speak to us here or on @KigenLtd on Twitter about #futureofSIM.

NAICS: 517
NAICS Definition: Telecommunications
Employees: 146
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
1
View Profile

TIM Brasil

Avenida João Cabral de Mello Neto, 850. Torre Sul. Barra da Tijuca, Rio de Janeiro, 22.775-057, BR
Last Update: 2026-01-20
Between 750 and 799
http://www.tim.com.br

A TIM é a empresa de telefonia móvel que mais cresce no Brasil. Atualmente, possui mais de 13 mil colaboradores em todo o país que trabalham entregando serviços inovadores e de qualidade em telefonia móvel, fixa e internet banda larga. É uma companhia feita de pessoas criativas, com energia realizadora e foco no cliente. Transparência, qualidade e inovação para que os consumidores brasileiros possam fazer cada vez mais e ir mais longe. Conheça as oportunidades na aba de Carreiras!

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/kigen.jpeg
Kigen
—
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/timbrasil.jpeg
TIM Brasil
—
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
Kigen
100%
Compliance Rate
0/4 Standards Verified
TIM Brasil
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Kigen in 2026.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for TIM Brasil in 2026.

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

Kigen cyber incidents detection timeline including parent company and subsidiaries

Incident History — TIM Brasil (X = Date, Y = Severity)

TIM Brasil cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/kigen.jpeg
Kigen
Incidents

Date Detected: 7/2025
Type:Vulnerability
Attack Vector: Java Card Virtual Machine implementation flaws
Motivation: Unauthorized access to eSIM profiles
Blog: Blog
https://images.rankiteo.com/companyimages/timbrasil.jpeg
TIM Brasil
Incidents

No Incident

FAQ

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

Kigen company has historically faced a number of disclosed cyber incidents, whereas TIM Brasil company has not reported any.

In the current year, TIM Brasil company and Kigen company have not reported any cyber incidents.

Neither TIM Brasil company nor Kigen company has reported experiencing a ransomware attack publicly.

Neither TIM Brasil company nor Kigen company has reported experiencing a data breach publicly.

Neither TIM Brasil company nor Kigen company has reported experiencing targeted cyberattacks publicly.

Kigen company has disclosed at least one vulnerability, while TIM Brasil company has not reported such incidents publicly.

Neither Kigen nor TIM Brasil holds any compliance certifications.

Neither company holds any compliance certifications.

Neither Kigen company nor TIM Brasil company has publicly disclosed detailed information about the number of their subsidiaries.

TIM Brasil company employs more people globally than Kigen company, reflecting its scale as a Telecommunications.

Neither Kigen nor TIM Brasil holds SOC 2 Type 1 certification.

Neither Kigen nor TIM Brasil holds SOC 2 Type 2 certification.

Neither Kigen nor TIM Brasil holds ISO 27001 certification.

Neither Kigen nor TIM Brasil holds PCI DSS certification.

Neither Kigen nor TIM Brasil holds HIPAA certification.

Neither Kigen nor TIM Brasil holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss4
Base: 7.7
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/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
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle VM VirtualBox accessible data as well as unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.1
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:L
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References
Description

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are 7.1.14 and 7.2.4. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Published
Date
2026-01-20
Updated
Date
2026-01-20
Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
References