Unibeam

Cybersecurity Dual-Use Technology Priority Signal Founded 2016

Last updated: Jul 31, 2026

Unibeam provides SIM-native identity authentication that binds a physical SIM, eSIM, or iSIM to a mobile device and exposes the resulting verification through enterprise APIs. Its primary value proposition is phishing- and SIM-swap-resistant authentication for financial, enterprise, telecom, healthcare, and connected-device workflows without a separate app or hardware token.

Visit Website

Company Overview

Unibeam's product is a SIM Identity and Authentication (SIA) layer embedded in the subscriber's SIM or eSIM secure element. According to the company's technical documentation, the component generates SIM and device identifiers, signs authentication requests, and returns results to the Unibeam service and the enterprise. The platform supports silent authentication, in which the SIM responds without user interaction, and touch authentication, in which a native approval request is delivered to the device. Its REST API supports synchronous and asynchronous callback integration, identifier-based validation, device-change checks through a lastImeiChange signal, and an active-call check. This is a concrete integration surface rather than a general claim of hardware security: an enterprise can enroll a binding, compare later responses, or use a recent device change as a step-up-authentication trigger.

The commercial problem is the weakness of software-mediated identity signals. SMS one-time passwords can be intercepted or redirected after a SIM swap, while passwords, push approvals, and web sessions remain exposed to phishing and social engineering. Unibeam's proposed control is to verify that the expected SIM/eSIM and device are still associated, then optionally require a SIM-level approval. The product pages position this for login, transaction confirmation, anti-SIM-swap controls, anti-social-engineering checks, branded calls, employee access, and IoT authentication. It also claims not to store personally identifiable information and to use company-specific identifiers; those privacy and isolation properties require technical, contractual, and security-review validation before being treated as established controls.

The customer and distribution model is enterprise and carrier dependent. Banks, healthcare providers, digital services, contact centers, and IoT operators are plausible buyers because they already manage account takeover, transaction fraud, or device-integrity risk. Mobile operators remain important because applet provisioning and the SIM signaling path are part of the product architecture, although the June 2026 Hirsch announcement presents SecureSIM as a route to enterprise deployment and says the offering is designed to reduce regional and carrier limitations. The company site publishes API documentation and a product workflow, and its company page identifies founder and CEO Ran Ben David, CTO Steve Harkins, CPO Carlos DaSilva, and advisors with telecom-sector backgrounds. The same site names NFX and AnD Ventures as investors. These are meaningful commercialization signals, but public evidence still does not establish recurring revenue, deployment scale, carrier coverage, or independently audited efficacy.

Competitive dynamics are mixed. Unibeam has a differentiated trust anchor and a low-friction user experience, but it competes against FIDO2/passkeys, device-bound credentials, mobile-network identity APIs, adaptive fraud platforms, authenticator apps, and conventional enterprise IAM suites. Its advantage is strongest where a cellular device and SIM are already present and the buyer wants to avoid issuing tokens or installing software. Its weakness is that cellular connectivity, SIM/eSIM provisioning, device replacement, roaming, dual-SIM behavior, and carrier or handset variation can become operational constraints. Authentication decisions also need recovery paths for lost phones, legitimate device changes, weak signal, and users without compatible service.

The dual-use case is credible but presently indirect. The same hardware-bound verification can support contractor or employee access, critical-infrastructure operator authentication, secure transaction approval, and IoT identity in defense-adjacent environments. The Hirsch channel is relevant because Hirsch sells security and access-control products into high-assurance environments, but neither the company site nor the public announcement establishes a defense deployment or government contract. Unibeam should therefore be viewed as a commercial identity-security startup with security and national-resilience adjacency, not as a proven defense supplier.

Dual-Use Assessment

Military & Commercial Applications

The core capability has substantive commercial and security applicability because it binds an identity signal to a cellular secure element and device rather than relying only on passwords, SMS codes, or software prompts. Commercial fraud prevention is the demonstrated market focus; defense and critical-infrastructure applications are plausible extensions for workforce, contractor, facility, and IoT access, but no public defense customer or government contract is established.

Strategic Fit Assessment

Research priority signal

Priority signal means this entry may be worth researching within the Claw & Talon thesis. It does not mean investable, suitable, endorsed, available, or likely to produce returns.

Unibeam is a credible strategic-priority signal for a dual-use cybersecurity database because it addresses a real identity-attack problem with a differentiated hardware anchor, publishes technical integration material, and has visible investor and channel signals. The June 2025 seed financing reported by ecosystem sources, the named NFX and AnD Ventures investors on the company site, and the June 2026 Hirsch SecureSIM launch suggest progression from product development toward distribution. The diligence case is not yet equivalent to an investment recommendation: public evidence does not establish revenue, retention, deployment volume, independent security testing, or the economics of SIM provisioning. Key questions are carrier coverage, applet lifecycle control, recovery and fallback behavior, false-positive rates, enterprise conversion, and whether Hirsch becomes a repeatable channel or a single reference partnership.

Strategic Value to U.S.-Israel Alliance

Unibeam could strengthen identity resilience for financial services, healthcare, telecom, public-sector, and critical-infrastructure operators by reducing dependence on phishable credentials and SMS OTP. Its SIM-native approach may also lower token logistics and user-training burdens in distributed workforces. For defense and national-security planners, the relevant value is an additional device-and-subscriber binding signal for zero-trust access, contractor authentication, and connected equipment; the value is limited where devices lack cellular service or where policy requires hardware separation from a personal handset. The strategic thesis is therefore strongest as identity infrastructure and resilience, with defense relevance still requiring customer, certification, and deployment evidence.

Key Technologies

  • SIM/eSIM/iSIM secure-element applets
  • SIM-to-device cryptographic binding
  • Silent and touch authentication APIs
  • SIM and device identifier validation
  • Device-change and active-call risk signals
  • Asynchronous callbacks and synchronous REST integration

Use Cases & Applications

  • Bank and fintech login protection
  • High-risk payment and transaction approval
  • Healthcare member authentication
  • Employee and contractor access control
  • Anti-SIM-swap and anti-social-engineering controls
  • Verified or branded business calls
  • IoT device identity and SIM-movement detection
  • Defense-adjacent critical-infrastructure authentication

Sources and verification

This profile is based on public-source research, Claw & Talon curation, and editorial judgment. Inclusion does not imply endorsement, partnership, investment, or a recommendation to transact. Readers should still confirm current status, customers, funding, and product claims before relying on this profile. The editorial policy explains how profiles are researched, where automated drafting is used, and how corrections work.

This record lists 7 public references used for company identity, status, positioning, or material-claim review.

Public sources

The links below are visible public references used for source discipline around company identity, status, funding, customer, acquisition, public-company, or other material claims where available.

Investor Lens

What this entry is

Private startup

Why it may matter

Unibeam may matter as a Cybersecurity entry with not currently an investable standalone company for Israeli technology research.

How an independent investor should read this

Not currently an investable standalone company. Read this profile as a starting point for independent verification, not as a recommendation or suitability assessment.

Evidence to verify

  • Verify current status
  • Verify traction
  • Verify cap table/funding
  • Verify technical claims
  • Verify regulatory/export-control issues
  • Verify customer concentration

Main investor questions

  • Is the company currently active, independently financeable, and raising or not raising on terms you can verify?
  • What customer, revenue, product, and technical evidence supports the company story?
  • What valuation, cap table, rights, and follow-on assumptions would govern any private exposure?
  • Does the dual-use claim map to actual commercial and government/defense/resilience buyer evidence?
  • What evidence would change the thesis or show that the profile is stale?

What not to infer

  • Inclusion does not imply endorsement.
  • Inclusion does not imply allocation availability or current fundraising.
  • Scores do not indicate investment suitability or expected returns.
  • Strategic importance does not automatically imply venture return potential.

Diligence questions

  • What evidence verifies Unibeam's current customer traction, deployment status, and revenue concentration?
  • Which technical claims are independently demonstrable today, and which remain roadmap or pilot-stage assertions?
  • Where does the product create real defense, intelligence, critical-infrastructure, or emergency-response value beyond ordinary commercial adoption?
  • How does the platform integrate into existing SOC, cloud, identity, or compliance workflows without adding operational burden?
  • What would disconfirm the priority signal: weak customer references, thin technical differentiation, poor capital efficiency, or limited allied-market access?

Related sector

See the Cybersecurity sector page for market context, related subcategories, and other Israeli companies in this part of the database.

Need a diligence readout?

Use the profile and related checklists as a starting point. If the decision needs more context, request a company screen, founder-call prep, diligence memo, or sector readout.