Comparison Overview

iCana

VS

onsemi

iCana

No. 28-2, Baogao Road, Xindian District, 5F, New Taipei City, TW, 231
Last Update: 2026-04-04
View Profile
Between 750 and 799
https://www.icana-rf.com

At iCana, we are passionate and dedicated to designing and building RF Semiconductor ICs for Wireless Communication. Our company was formed in 2022 when Foxconn acquired arQana Technologies 5G Wireless Telecommunication business. iCana, with R&D offices in Taiwan, Belgium, USA and Singapore, is a dynamic international company in the semiconductor industry. Today, we have more than 75 people working across the globe and we will grow even more! In iCana we focus on 5G infrastructure, manage the end-to-end process from designing RF and mmWave integrated circuits to manufacturing them with the foundries. If you are looking for a challenging and exciting career in the world of technology and semiconductors, then look no further. Imagine what you could reach at iCana, where new ideas are turned into inspiring products with extraordinary performance.

NAICS: 3344
NAICS Definition: Semiconductor and Other Electronic Component Manufacturing
Employees: 41
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0
View Profile

onsemi

5701 N. Pima Rd, Scottsdale, Arizona, US, 85250
Last Update: 2026-04-01
Between 750 and 799
http://www.onsemi.com

onsemi (Nasdaq: ON) is driving disruptive innovations to help build a better future. With a focus on automotive and industrial end-markets, the company is accelerating change in megatrends such as vehicle electrification and safety, sustainable energy grids, industrial automation, and 5G and cloud infrastructure. With a highly differentiated and innovative product portfolio, onsemi creates intelligent power and sensing technologies that solve the world’s most complex challenges and leads the way in creating a safer, cleaner, and smarter world. Learn more about onsemi at www.onsemi.com.

NAICS: 3344
NAICS Definition: Semiconductor and Other Electronic Component Manufacturing
Employees: 15,326
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/icana-rf.jpeg
iCana
—
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/onsemi.jpeg
onsemi
—
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
iCana
100%
Compliance Rate
0/4 Standards Verified
onsemi
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Semiconductor Manufacturing Industry Average (This Year)

No incidents recorded for iCana in 2026.

Incidents vs Semiconductor Manufacturing Industry Average (This Year)

No incidents recorded for onsemi in 2026.

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

iCana cyber incidents detection timeline including parent company and subsidiaries

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

onsemi cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/icana-rf.jpeg
iCana
Incidents

No Incident

https://images.rankiteo.com/companyimages/onsemi.jpeg
onsemi
Incidents

No Incident

FAQ

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

Historically, onsemi company has disclosed a higher number of cyber incidents compared to iCana company.

In the current year, onsemi company and iCana company have not reported any cyber incidents.

Neither onsemi company nor iCana company has reported experiencing a ransomware attack publicly.

Neither onsemi company nor iCana company has reported experiencing a data breach publicly.

Neither onsemi company nor iCana company has reported experiencing targeted cyberattacks publicly.

Neither iCana company nor onsemi company has reported experiencing or disclosing vulnerabilities publicly.

Neither iCana nor onsemi holds any compliance certifications.

Neither company holds any compliance certifications.

Neither iCana company nor onsemi company has publicly disclosed detailed information about the number of their subsidiaries.

onsemi company employs more people globally than iCana company, reflecting its scale as a Semiconductor Manufacturing.

Neither iCana nor onsemi holds SOC 2 Type 1 certification.

Neither iCana nor onsemi holds SOC 2 Type 2 certification.

Neither iCana nor onsemi holds ISO 27001 certification.

Neither iCana nor onsemi holds PCI DSS certification.

Neither iCana nor onsemi holds HIPAA certification.

Neither iCana nor onsemi holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
References
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

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

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

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

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

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

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Published
Date
2026-04-03
Updated
Date
2026-04-03
Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
References