SecuriThings Raises $21M for Physical-Security Device Protection

SecuriThings raises $21 million for physical-security device monitoring

SecuriThings closed a $21 million Series B round on October 17, according to Calcalist. The platform monitors and protects physical-security devices including cameras, access-control systems, and related infrastructure. The company did not disclose valuation, lead investor, revenue, or customer count.

The financing indicates sustained investor appetite for securing operational devices that traditionally receive minimal security oversight. Physical-security fleets sit outside the standard endpoint-protection perimeter, often running outdated firmware and connected to enterprise networks without authentication controls or centralized inventory.

SecuriThings competes with broader IoT and operational-technology platforms from Palo Alto Networks, Microsoft, and Cisco, plus specialist device-identity vendors including Device Authority. The company's focus on physical-security equipment distinguishes it from generic asset-discovery tools. That narrower scope may appeal to enterprises that need operational monitoring, firmware tracking, and remediation workflows specific to cameras and access systems rather than network-wide device visibility.

Enterprise buyers evaluating the platform should verify whether it provides authenticated device inventory, firmware and configuration monitoring, vulnerability prioritization tied to known exploits, remote remediation capability, and direct integrations with physical-security management systems. The absence of published customer counts, performance benchmarks, or pricing means the financing itself does not establish product superiority. Procurement teams should request proof points: time to inventory completeness, false-positive rates for anomaly detection, and per-device licensing costs.

Exein–Deutsche Telekom partnership bundles runtime security with connectivity

Exein, which announced a $270 million funding round valuing the company at $1.7 billion, partnered with Deutsche Telekom IoT to combine on-device runtime security with global connectivity. Exein's Photon architecture operates at the kernel level and claims to protect more than 2 billion devices globally. The partnership announcement fell on October 8, outside the seven-day analysis window but relevant to broader procurement trends.

The deal positions Exein against endpoint and IoT platforms that rely on network inspection, including Palo Alto Networks' Device Security. Exein says its runtime enforcement works in environments with limited or no connectivity, a requirement for robots, drones, and industrial machines operating outside persistent network coverage. Deutsche Telekom's connectivity footprint provides a carrier-managed distribution channel that standalone security vendors lack.

Buyers deploying autonomous edge systems should evaluate whether the integrated offering reduces tooling complexity and operational overhead or simply bundles two contracts. Critical diligence questions include per-device pricing, supported operating systems and chipsets, update-management responsibilities, detection false-positive rates, and whether protection remains effective during offline operation. The "2 billion devices" claim is unverified by independent benchmarks in available sources.

EU Cyber Resilience Act forces device-lifecycle procurement criteria

The EU Cyber Resilience Act imposes cybersecurity obligations on connected products, with reporting duties for actively exploited vulnerabilities beginning September 11, 2026, and broader requirements applying December 11, 2027. Potential penalties reach up to €15 million or 2.5 percent of annual worldwide revenue, whichever is higher. The regulation requires 24-hour reporting for actively exploited vulnerabilities, though buyers should confirm exact obligations with EU regulatory guidance.

The CRA shifts competitive differentiation toward vendors that provide software bills of materials, vulnerability intake processes, coordinated disclosure workflows, update commitments, and auditable product-security processes. Vendors without those capabilities will face procurement disadvantages in EU markets regardless of device-management feature parity.

Procurement teams should add CRA evidence requirements to IoT and device-management RFPs now rather than waiting for the 2027 deadline. Required vendor submissions should include vulnerability-reporting workflows, supported security-update periods, product ownership and support boundaries, SBOM availability in machine-readable formats, incident-notification SLAs, and contractual allocation of regulatory responsibility. This will increase total cost of ownership for low-cost devices that lack long-term update support and formalized security processes.

What to watch

The SecuriThings financing and Exein valuation indicate investor confidence in specialized device-security platforms, but publicly available data provides limited pricing, accuracy, or adoption benchmarks. Buyers should treat vendor claims as starting points for diligence rather than proof of capability. The CRA reporting timeline creates immediate procurement pressure: vendors unable to demonstrate compliance workflows by mid-2027 represent regulatory risk, not just technical gaps. Enterprises should prioritize device-management platforms that supply verifiable update commitments, machine-readable SBOMs, and contractual regulatory-liability allocation.