Comparison Overview

Nippon Telegraph and Telephone

VS

Claro Brasil

Nippon Telegraph and Telephone

East Tower, 5-1, Otemachi 1-Chome, Chiyoda-ku, Tokyo, None, Tokyo, Tokyo, JP, 100-8116
Last Update: 2025-11-27

Nippon Telegraph and Telephone The Japan Telegraph and Telephone Corporation is a Japanese telecommunications company headquartered in Tokyo, Japan. Wikipedia Stock price: 9432 (TYO) JP¥ 5,170 -137.00 (-2.58%) Revenue: 11.39 lakh crores JPY (2017) CEO: Hiroo Unoura (Jun 2012–) Headquarters: Chiyoda, Tokyo, Japan Number of employees: 2,74,844 (2016) Nippon Telegraph & Tel is the fourth-largest telephone operating company by total revenue ($94.2 B USD). The Japan Telegraph and Telephone Corporation (日本電信電話株式会社 Nippon Denshin Denwa Kabushiki-gaisha), is a Japanese telecommunications company headquartered in Tokyo, Japan. Ranked 65th in Fortune Global 500, Nippon Telegraph and Telephone is the fourth largest telecommunications company in the world in terms of revenue. The company is incorporated pursuant to the Nippon Telegraph and Telephone Law (Law Concerning Japan Telegraph and Telephone Corporation, Etc.).[3] The purpose of the company defined by the Law is to own all the shares issued by Japan Telegraph and Telephone East Corporation (Nippon Telegraph and Telephone East) and Japan Telegraph and Telephone West Corporation (Nippon Telegraph and Telephone West) and to ensure proper and stable provision of telecommunications services all over Japan including remote rural areas by these companies as well as to conduct research relating to the telecommunications technologies that will form the foundation for telecommunications. While Nippon Telegraph and Telephone is listed on Tokyo, Osaka, New York, and London stock exchanges, the Japanese government still owns roughly one-third of Nippon Telegraph and Telephone's shares, regulated by the Nippon Telegraph and Telephone Law.

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

Claro Brasil

Rua Henri Dunant, 780, Santo Amaro, São Paulo, SP, BR, 04709-110
Last Update: 2025-11-27
Between 800 and 849

Prazer, somos a Claro! Aqui, temos um grande time que faz tudo acontecer! É com o esforço e a dedicação de cada uma de nossas Pessoas que somos hoje referência no que fazemos, atuando unidos no nosso propósito, que é “Conectar para uma vida mais divertida e produtiva”. Somamos todas as tecnologias para criar a melhor e mais completa infraestrutura de conectividade do País. Somos multicampeões confirmado pelo Speedtest como Internet móvel mais rápida e estável e com rede wi-fi mais estável do Brasil, entre tantos outros reconhecimentos. Também somos a 4º marca mais valiosa do Brasil (BrandZ). No Brasil, estamos presentes em mais de 4.800 municípios, somando mais de 83 milhões de clientes. Lideramos o saldo de portabilidade há mais de 5 anos, sendo que, em 2022, tivemos 1,2 milhão de linhas portadas. E tem mais: inovamos nossos produtos e serviços para atender cada vez melhor nossos usuários! Por isso, hoje, contamos com soluções de entretenimento (Claro música, Claro tv+, Claro livros, Claro vídeo e Claro gaming), finanças (Claro pay) e muito mais! Temos presença aeroespacial (com 5 satélites em órbita) e somos referência em conectividade industrial, automotiva, agronegócio e outros. Também temos um ambiente de conexão entre nossos negócios e o ecossistema de inovação, que é o beOn, o hub de inovação da Claro. Sustentabilidade é um valor para a Claro. Investimos no desenvolvimento ambiental, econômico e social, prezando sempre pela governança, responsabilidade ambiental, proteção de dados e impacto social. Por meio do Instituto Claro, conectamos pessoas para um futuro melhor, aliando os serviços prestados a investimentos sociais em projetos de educação e cidadania. #VempraClaro

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

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/nippon-telegraph-and-telephone.jpeg
Nippon Telegraph and Telephone
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/clarobrasil.jpeg
Claro 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
Nippon Telegraph and Telephone
100%
Compliance Rate
0/4 Standards Verified
Claro Brasil
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Nippon Telegraph and Telephone in 2025.

Incidents vs Telecommunications Industry Average (This Year)

No incidents recorded for Claro Brasil in 2025.

Incident History — Nippon Telegraph and Telephone (X = Date, Y = Severity)

Nippon Telegraph and Telephone cyber incidents detection timeline including parent company and subsidiaries

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

Claro Brasil cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/nippon-telegraph-and-telephone.jpeg
Nippon Telegraph and Telephone
Incidents

Date Detected: 05/2020
Type:Breach
Attack Vector: Internal Network Access
Motivation: Data Theft
Blog: Blog
https://images.rankiteo.com/companyimages/clarobrasil.jpeg
Claro Brasil
Incidents

No Incident

FAQ

Nippon Telegraph and Telephone company demonstrates a stronger AI Cybersecurity Score compared to Claro Brasil company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Nippon Telegraph and Telephone company has historically faced a number of disclosed cyber incidents, whereas Claro Brasil company has not reported any.

In the current year, Claro Brasil company and Nippon Telegraph and Telephone company have not reported any cyber incidents.

Neither Claro Brasil company nor Nippon Telegraph and Telephone company has reported experiencing a ransomware attack publicly.

Nippon Telegraph and Telephone company has disclosed at least one data breach, while the other Claro Brasil company has not reported such incidents publicly.

Neither Claro Brasil company nor Nippon Telegraph and Telephone company has reported experiencing targeted cyberattacks publicly.

Neither Nippon Telegraph and Telephone company nor Claro Brasil company has reported experiencing or disclosing vulnerabilities publicly.

Neither Nippon Telegraph and Telephone nor Claro Brasil holds any compliance certifications.

Neither company holds any compliance certifications.

Claro Brasil company has more subsidiaries worldwide compared to Nippon Telegraph and Telephone company.

Claro Brasil company employs more people globally than Nippon Telegraph and Telephone company, reflecting its scale as a Telecommunications.

Neither Nippon Telegraph and Telephone nor Claro Brasil holds SOC 2 Type 1 certification.

Neither Nippon Telegraph and Telephone nor Claro Brasil holds SOC 2 Type 2 certification.

Neither Nippon Telegraph and Telephone nor Claro Brasil holds ISO 27001 certification.

Neither Nippon Telegraph and Telephone nor Claro Brasil holds PCI DSS certification.

Neither Nippon Telegraph and Telephone nor Claro Brasil holds HIPAA certification.

Neither Nippon Telegraph and Telephone nor Claro Brasil 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