Comparison Overview

Japan Airport Terminal Co Ltd

VS

EV Initiative Inc.

Japan Airport Terminal Co Ltd

None
Last Update: 2025-12-04

Japan Airport Terminal Co Ltd is a company based out of Japan.

NAICS: 53
NAICS Definition: Real Estate and Rental and Leasing
Employees: 25
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

EV Initiative Inc.

2108 N St, Sacramento, 95816, US
Last Update: 2025-12-09
Between 750 and 799

Company Description: EV Initiative is a B2B SaaS business; our technology enables Charge Port Operators (CPOs)—third-party organizations that are creating and maintaining EV Charging Networks—to establish their EV-related businesses. What’s a CPO? The entities grow and maintaining Electric Vehicle (EV) charging networks. CPOs are plenty; utilities, property owners and managers, fleet operators, solar and electrical, quick service restaurants, corporate, hospitality, government. and more. Our mission is to Enable the Next Generation. We provide the platform for CPOs with EV initiative. Our offerings: • Charge Port Management Software (CPMS) - the operating system for EV Charging Networks, we white label for our customers • Point-of-Sale Driver App - white labeled for CPOs • EV Initiative Hardware Shop - EV Charging Stations (EVCS) for CPOs • Additional services: CPO sales and marketing bundles

NAICS: 53
NAICS Definition: Real Estate and Rental and Leasing
Employees: 5
Subsidiaries: 2
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Japan Airport Terminal Co Ltd
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/ev-initiative.jpeg
EV Initiative Inc.
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
Japan Airport Terminal Co Ltd
100%
Compliance Rate
0/4 Standards Verified
EV Initiative Inc.
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Real Estate and Equipment Rental Services Industry Average (This Year)

No incidents recorded for Japan Airport Terminal Co Ltd in 2025.

Incidents vs Real Estate and Equipment Rental Services Industry Average (This Year)

No incidents recorded for EV Initiative Inc. in 2025.

Incident History — Japan Airport Terminal Co Ltd (X = Date, Y = Severity)

Japan Airport Terminal Co Ltd cyber incidents detection timeline including parent company and subsidiaries

Incident History — EV Initiative Inc. (X = Date, Y = Severity)

EV Initiative Inc. cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/defaultcompany.jpeg
Japan Airport Terminal Co Ltd
Incidents

No Incident

https://images.rankiteo.com/companyimages/ev-initiative.jpeg
EV Initiative Inc.
Incidents

No Incident

FAQ

Japan Airport Terminal Co Ltd company demonstrates a stronger AI Cybersecurity Score compared to EV Initiative Inc. company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, EV Initiative Inc. company has disclosed a higher number of cyber incidents compared to Japan Airport Terminal Co Ltd company.

In the current year, EV Initiative Inc. company and Japan Airport Terminal Co Ltd company have not reported any cyber incidents.

Neither EV Initiative Inc. company nor Japan Airport Terminal Co Ltd company has reported experiencing a ransomware attack publicly.

Neither EV Initiative Inc. company nor Japan Airport Terminal Co Ltd company has reported experiencing a data breach publicly.

Neither EV Initiative Inc. company nor Japan Airport Terminal Co Ltd company has reported experiencing targeted cyberattacks publicly.

Neither Japan Airport Terminal Co Ltd company nor EV Initiative Inc. company has reported experiencing or disclosing vulnerabilities publicly.

Neither Japan Airport Terminal Co Ltd nor EV Initiative Inc. holds any compliance certifications.

Neither company holds any compliance certifications.

EV Initiative Inc. company has more subsidiaries worldwide compared to Japan Airport Terminal Co Ltd company.

Japan Airport Terminal Co Ltd company employs more people globally than EV Initiative Inc. company, reflecting its scale as a Real Estate and Equipment Rental Services.

Neither Japan Airport Terminal Co Ltd nor EV Initiative Inc. holds SOC 2 Type 1 certification.

Neither Japan Airport Terminal Co Ltd nor EV Initiative Inc. holds SOC 2 Type 2 certification.

Neither Japan Airport Terminal Co Ltd nor EV Initiative Inc. holds ISO 27001 certification.

Neither Japan Airport Terminal Co Ltd nor EV Initiative Inc. holds PCI DSS certification.

Neither Japan Airport Terminal Co Ltd nor EV Initiative Inc. holds HIPAA certification.

Neither Japan Airport Terminal Co Ltd nor EV Initiative Inc. holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.

Risk Information
cvss4
Base: 6.9
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/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

Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 9.4
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H
Description

Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.

Risk Information
cvss3
Base: 8.2
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N
Description

Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.

Risk Information
cvss3
Base: 8.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L
Description

The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.

Risk Information
cvss3
Base: 5.4
Severity: HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N