
Key takeaways
• Intercom security stopped being a checkbox in 2024, and 2026 added deadlines. The UK PSTI Act bans default passwords on connected devices (since April 2024), NIS2 national laws have been coming into force since October 2024, and the EU Cyber Resilience Act has required 24-hour reporting of actively exploited vulnerabilities since 11 September 2026, with full application on 11 December 2027. Selling an insecure intercom into Europe is now a regulatory event, not just a reputational one.
• The threat picture has receipts. Akuvox CVE-2023-0354 (CVSS 9.1) let anyone reach an E11 intercom’s web server with no authentication; Zenitel’s TCIV-3+ intercom had three OS command-injection flaws scored CVSS v4 10.0 in November 2025; and a March 2026 internet scan by Modat found 8,074 RTSP video streams that returned a live frame with no password.
• Five non-negotiable controls. DTLS-SRTP for media, TLS 1.3 for signalling, signed firmware with rollback protection, FIDO2/passkey auth for admins, and an immutable audit log of every door-release event. Each one you skip shows up later as an incident or an audit finding.
• Hikvision and Dahua are not options for many buyers. US NDAA Section 889 bans them from federal procurement, the FCC keeps them on its Covered List, Canada ordered Hikvision to wind up its Canadian business in June 2025, and most enterprise security questionnaires now ask the question explicitly.
• Fora Soft has been shipping secure video and access platforms since 2005. We built the web version of Netcam Studio, a long-running IP camera surveillance product, and the WebRTC/SIP calling layer and apps of Nucleus, an on-premise communication platform. Book a 30-min call →
Updated November 2026: EU CRA vulnerability reporting (live since 11 September 2026), the AI Omnibus timeline for face recognition, FIPS 140-3 and FCC Covered List changes, new intercom CVEs and a 2026 count of open RTSP streams.
Why Fora Soft wrote this playbook
There is no shortage of intercom vendors willing to sell you a slick mobile app. There is a shortage of teams that can ship one without leaking video over plaintext RTSP. Fora Soft has been shipping multimedia products since 2005: 250+ projects, 50 in-house engineers. We built the web version of Netcam Studio, an IP camera surveillance product used in homes, offices and schools, and the WebRTC/SIP calling layer and mobile apps of Nucleus, an on-premise communication platform that is SOC 2, GDPR and HIPAA-compliant and now serves 5,000+ businesses. We also wrote the seven-volume Fora Soft Video Engineering Handbook, which shows up at the end of this article.
This playbook is what we tell prospective intercom clients in a discovery call: which threats are real, what the regulators now require, what an honest defence-in-depth architecture looks like, which off-the-shelf vendors are credible, when to build a custom platform instead, and what numbers to commit to. For the media path itself, our WebRTC development team ships DTLS-SRTP video and TLS signalling on the same stacks this playbook discusses. The audience is product managers, building owners, security integrators and PropTech founders who need to ship a secure intercom or replace one that no longer meets the bar.
Use the table of contents on the right to jump straight to the question you came to answer.
Building or hardening a secure intercom platform?
Tell us your deployment scope, compliance footprint and target latency. Within one working day we will come back with a first threat-model outline, a target architecture sketch and an estimate range.
What is secure intercom software? The short answer
Secure intercom software is the code that runs a door intercom (device firmware, cloud control plane, resident and operator apps), built so that video, audio, identities and door-release commands stay encrypted on every hop, authenticated and logged. In 2026 that means five controls you can test: DTLS-SRTP media, TLS 1.3 signalling, signed firmware with rollback protection, phishing-resistant admin login, and an immutable audit log. Buy it from a vendor that can prove all five, or build it once your door count, compliance scope or integrations make the vendor model too expensive.
A secure intercom is a system that lets a visitor request entry and a resident or operator grant or deny it — without leaking video, audio, identity, location or access logs to anyone outside that two-party transaction. The modern stack has four layers: an edge device (door station, panel, mobile reader), a network path (SIP/WebRTC over VLAN, often via a TURN/SBC), a cloud control plane (multi-tenant SaaS or self-hosted) and an identity layer (residents’ phones, operators’ SSO, visitors’ QR codes).
Each of those four layers has its own controls; secure means all four are doing their job at the same time. The intercom advisories in the next section were rarely about broken cryptography. They came from a single layer being treated as “internal” and left exposed. If you already run an intercom fleet and only need to lock it down, our secure intercom systems hardening playbook is the companion runbook to this buyer’s-and-builder’s guide.
What changed for secure intercom software buyers and builders in 2026?
Short answer: in 2026 the rules got fixed dates. EU CRA reporting went live on 11 September 2026, US federal crypto moved to FIPS 140-3 ten days later, and the AI Act’s high-risk rules for face identification now start on 2 December 2027. The weak spots stayed where they were. New intercom CVEs scored 9.8 and 10.0, and thousands of video streams are still open to anyone. The table turns each change into a question for a vendor or a task for your build. For the device-level hardening steps behind these items, see the intercom security hardening playbook.
| Change | Date | What it is | What to ask or build |
|---|---|---|---|
| EU CRA reporting | 11 Sep 2026 | Manufacturers report actively exploited vulnerabilities and severe incidents to ENISA’s Single Reporting Platform: 24-hour early warning, 72-hour notification, final report (Jones Day, 2026). Full CRA applies 11 Dec 2027. | Ask for the vendor’s CRA reporting runbook and named PSIRT contact. If you build, wire crash and exploit telemetry to an on-call rota before launch. |
| EU AI Act, Digital Omnibus | in force 27 Jul 2026 | Regulation (EU) 2026/1744 moved Annex III high-risk duties to 2 Dec 2027 (White & Case, 2026). 1:1 face verification sits outside Annex III; 1:N identification against a building gallery is high-risk. | Ask whether face access is 1:1 or 1:N and where templates live. Build 1:1 on-device matching first. |
| FIPS 140-2 → 140-3 | 21 Sep 2026 | FIPS 140-2 certificates moved to the Historical list; new US federal buys need FIPS 140-3 validated modules (SafeLogic, 2026). | Ask for the CMVP certificate number of every crypto module in the cloud and the device. |
| FCC Covered List | Oct 2025 order, in effect Jul 2026 | FCC 25-71 lets the FCC stop import and marketing of previously authorised Covered List gear; the part reaching Hikvision, Dahua and Hytera surveillance equipment is paused (FCC). | Ask for an NDAA Section 889 and Covered List statement per SKU, including OEM-rebadged hardware. |
| Canada and Hikvision | 28 Jun 2025 | Canada ordered Hikvision to cease Canadian operations and barred federal departments from buying or using its equipment (SecurityInfoWatch, 2025). | Multi-country fleets need a supply-chain plan for every market, not only the US. |
| New intercom CVEs | Jun and Nov 2025 | CyberData SIP intercom CVE-2025-30184, CVSS 3.1 9.8 (CVEfeed); Zenitel TCIV-3+ CVE-2025-64126/64127/64128, CVSS v4 10.0, fixed in 9.3.3.0 (CISA ICSA-25-329-03, Field Effect). | Ask for the median days from CVE to signed firmware over the last two years. |
| Open RTSP census | scanned Mar 2026 | Modat found 973,819 RTSP services online; 8,074 returned a live frame with no credentials (Modat, June 2026). | No RTSP port on the public internet; media only through an authenticated SFU or TURN. |
| Passkeys and mobile credentials | Aug 2025; 26 Feb 2026 | NIST finalised SP 800-63-4, with guidance on passkeys and syncable authenticators (NIST). The CSA published Aliro 1.0 for phone and wearable access credentials over NFC, BLE and UWB (CSA). | Ask for a passkey admin login and an Aliro roadmap. If you build, keep the credential layer swappable. |
| Post-quantum deadlines | 27 Oct 2026 | Final NIST IR 8547 deprecates RSA and elliptic-curve algorithms after 2030 and disallows them after 2035 (Cloud Security Alliance, 2026). | Ask how the firmware swaps to ML-KEM and ML-DSA by update. Devices sold now will still be on the wall in 2035. |
The 2025–2026 intercom threat picture (with receipts)
1. Firmware-level CVEs that ship in the box. CVE-2023-0354 (Akuvox, CVSS 9.1) was a missing-authentication flaw — unauthenticated access to the device’s web server and packet captures on the local network — that turned into remote code execution when chained with the command-injection bug CVE-2023-0351. CVE-2022-40903 (Aiphone GT-DMB-N) let an attacker with an NFC-capable phone brute-force the door station’s four-digit admin passcode. Neither is hypothetical: the Akuvox bugs were still unpatched when Claroty published them in March 2023, and CISA (advisory ICSA-23-068-01) told operators to isolate the devices. The pattern repeated in 2025: CyberData’s SIP intercom (CVE-2025-30184, CVSS 9.8) and Zenitel’s TCIV-3+ (three command-injection flaws at CVSS v4 10.0, fixed in firmware 9.3.3.0).
2. Default credentials. Mirai-class botnets still scan the internet for devices that accept factory logins such as admin/admin, and older IP intercom installs that were never re-commissioned are easy finds. The UK PSTI Act made selling connected products with universal default passwords illegal in the UK from 29 April 2024; vendors who have not refreshed their commissioning UX are out of compliance.
3. Plaintext SIP and exposed RTSP. In a March 2026 scan, Modat counted 973,819 RTSP services on the internet, and 8,074 of them handed over a live frame with no credentials (Modat, 2026). Bitsight counted 40,000+ exposed security cameras a year earlier. Anyone with a scanner can scout buildings remotely, which is a gift to physical-intrusion teams.
4. Replay and BLE spoofing on mobile credentials. The convenience of a phone-as-key is undone if the door-release signal can be captured and replayed. Modern mobile credentials must use ECDH key exchange, signed nonces and proximity verification. On UWB-capable phones that means secure ranging; RSSI thresholds are only a UX filter, because a relay attack simply re-amplifies the signal.
5. Insider abuse and supply-chain risk. A property manager with cloud admin can open any unit at any time; without granular audit and behavioural analytics, that is a privacy disaster waiting to happen. On the supply side, NDAA Section 889 bans Hikvision and Dahua from US federal procurement, both sit on the FCC Covered List, and Canada ordered Hikvision to cease its Canadian operations in June 2025.

Figure 1. Insecure vs hardened intercom — the same box, two postures.
Reach for an immediate audit when: any device in your fleet still accepts default credentials, exposes RTSP to the internet, or runs firmware older than 12 months. These are the three findings that turn into incidents fastest.
The regulatory squeeze on intercom software in 2026
EU NIS2 (transposition deadline 17 October 2024). Brings “essential” and “important” entities — healthcare, transport, public administration — under a hard security baseline with a staged incident-reporting cascade: a 24-hour early warning, a 72-hour notification and a one-month final report. Member states have been bringing their national laws into force since then, and hospitals, airports and critical-infrastructure buildings flow those duties down to their intercom suppliers.
EU Cyber Resilience Act (CRA): reporting since September 2026, full rules from December 2027. Every “product with digital elements” sold into the EU needs a coordinated vulnerability disclosure process, state-of-the-art encryption and security updates for the product’s expected lifetime, with five years as the floor. Since 11 September 2026 manufacturers must report actively exploited vulnerabilities and severe incidents within 24 hours through ENISA’s Single Reporting Platform; full application lands 11 December 2027 (Jones Day, 2026; European Commission). Intercoms with 10-year service lives are squarely in scope. Radio-equipped door stations sold in the EU have also had to meet the RED cybersecurity delegated act (EN 18031) since 1 August 2025.
UK PSTI Act 2022 (product rules since April 2024). No default or easily-guessed passwords, a published vulnerability-disclosure policy with a named point of contact, and a stated minimum security-update period — in force since 29 April 2024, backed by fines up to £10M or 4 % of global turnover.
GDPR + EU AI Act. Intercom video and audio are personal data, and face templates are special-category biometric data under GDPR Article 9, so run a Data Protection Impact Assessment before turning face access on. Under the AI Act, 1:1 face verification that only confirms an enrolled resident is outside the Annex III high-risk list, while 1:N identification against a building-wide gallery is high-risk; the AI Digital Omnibus moved those high-risk duties to 2 December 2027 (White & Case, 2026). Emotion recognition in workplaces and schools has been banned since 2 February 2025.
US federal and defence: NDAA, FCC and FIPS 140-3. NDAA Section 889 keeps Hikvision and Dahua out of federal procurement, the FCC Covered List order FCC 25-71 took effect in July 2026 with parts paused, and since 21 September 2026 new federal deployments need FIPS 140-3 validated crypto modules (SafeLogic, 2026). Some vendors now state NDAA and TAA compliance across the whole portfolio; Commend is one (Commend).
HIPAA (US healthcare), PCI DSS (if you process payments), SOC 2 Type II, ISO/IEC 27001:2022. Enterprise procurement now expects at least one of SOC 2 or ISO 27001 in the data room. Plan the audit, do not retrofit it.
The five non-negotiable controls — a baseline you can hold a vendor to
| Control | What “good” looks like | Tolerated during migration | Walk away |
|---|---|---|---|
| Media encryption | DTLS-SRTP, perfect forward secrecy, AES-256-GCM | SDES-keyed SRTP over TLS signalling (no forward secrecy) | Plain RTP / RTSP |
| Signalling encryption | TLS 1.3 only, mTLS device enrolment | TLS 1.2 | SIP over UDP, no TLS |
| Firmware integrity | Signed images, secure boot, rollback protection | Signed images, no rollback protection | Unsigned firmware |
| Admin auth | FIDO2 / passkeys, SSO, RBAC | TOTP MFA, RBAC | Username + password only |
| Audit log | Immutable, exported to SIEM, 365 days | Immutable, 90 days | No log / mutable log |

Figure 2. The five non-negotiable controls, as a go / caution / walk-away matrix.
A reference architecture: defence in depth, four layers
A secure intercom design we would sign off on slots into the four-layer architecture below. The point is not to look impressive in a sales deck — it is that an attacker who breaks one layer still has to break the next three before they get to the door strike.

Figure 3. Defence in depth: four layers, each carrying its own controls, under one compliance overlay.
1. Edge device
Secure boot anchored in a hardware root of trust (boot ROM and fused keys, with a TPM or secure element for attestation), signed firmware with rollback protection, sealed UART/JTAG, a tamper switch tied to a heartbeat, and a local PIN fallback so a network outage does not strand residents at the door. Run any AI inference (face blur for GDPR, package detection) on-device so audio and video never leave the building unnecessarily.
2. Network
A dedicated IoT VLAN with no general internet egress, SIP carried over TLS 1.3, media over DTLS-SRTP, NAT traversal via authenticated TURN behind a Session Border Controller. Egress firewall whitelists, inbound DDoS protection, and mTLS device enrolment so unknown devices cannot enrol themselves.
3. Cloud / control plane
Multi-tenant SaaS with row-level isolation per building, AES-256-GCM at rest, secrets in a KMS or HSM, immutable audit logs streamed to a SIEM with anomaly detection, backups with 90–365 day retention. If your customers are regulated, support a self-hosted or single-tenant deployment option.
4. Identity
SSO via SAML or OIDC, FIDO2 / passkeys for admin login, MFA on every privileged action, and per-building RBAC plus per-unit ABAC so a manager in Building A cannot see Building B. Visitors get time-bound credentials (QR codes, NFC tokens) that expire automatically; residents’ mobile credentials live in the Secure Enclave (iOS) or StrongBox/TEE (Android) with revocation pushed within 60 seconds when a phone is lost. Cap the door’s offline credential cache (24 hours, as in the attack table below), so a revocation issued during an outage still lands within a bounded window.
Consider an on-prem or self-hosted deployment when: the building falls under EU NIS2 essential services, HIPAA, or a national-security context, or the customer’s lawyers will not accept any cloud egress.
Where the major commercial vendors stand
| Vendor | Category | Security posture | Compliance to verify | Watch out for |
|---|---|---|---|---|
| ButterflyMX | Cloud SaaS, multi-family | Encryption in transit and at rest, 2FA (vendor, 2025) | Ask for the SOC 2 report and data-processing terms | Cloud-only; check data residency |
| Swiftlane | Cloud SaaS, office + multi-family | Mobile credentials, face access option | Ask for the SOC 2 report; GDPR DPA | Face recognition needs DPIA in EU |
| 2N (Axis Comm.) | IP intercom, hybrid | SIP TLS, LDAP/RADIUS | Ask for ISO 27001 scope (Axis group) and EN 18031 for radio models | Default creds in legacy installs |
| Aiphone IXG | IP / hybrid intercom | SIP TLS | UL listings; ask for an NDAA statement | GT-series NFC bug (CVE-2022-40903) history |
| Akuvox | IP intercom | SIP TLS (post-patch) | Limited | CVE-2023-0354; verify firmware |
| Comelit | EU IP intercom | TLS, VLAN, SIP TLS | CE / RED; ask for EN 18031 evidence | Limited cloud features |
| Commend | IP intercom, critical sites | SIP TLS, hardened IP stations | NDAA and TAA across the portfolio (vendor statement) | Enterprise pricing; integrator-led sales |
| Hikvision / Dahua | IP camera + intercom | Mixed; weak history | NDAA 889; FCC Covered List; Canada order (2025) | Procurement risk under NIS2 |
Need a security audit of your existing intercom platform?
Threat model, architecture review, firmware analysis, penetration test against the cloud and mobile clients. We come back with a prioritised punch list mapped to NIS2, CRA, GDPR and your customer commitments.
Eight attack scenarios — and the controls that defeat them
| Scenario | Mitigation |
|---|---|
| Credential stuffing on the property-manager portal | Rate limiting, account lockout, FIDO2 MFA, breached-password screening (haveibeenpwned API). |
| MITM on RTSP video feed | TLS 1.3 + cert pinning in mobile and viewer apps; never expose RTSP to the public internet. |
| Replay of a door-release SIP message | Timestamp + nonce in SIP headers, one-time door-release codes, server-side replay window check. |
| BLE credential spoofing | ECDH key exchange, signed nonces, UWB secure ranging where supported (RSSI alone does not stop relays). |
| Supply-chain firmware attack | Code signing, attestation on boot, staged rollout (5/25/100 %), canary devices. |
| Lost or stolen mobile device | 24-hour credential expiry, push-based revocation in <60 s, MDM integration. |
| Insider sysadmin abuse | Granular RBAC, immutable audit log, behavioural analytics, quarterly access review. |
| Network outage cuts off the door | Local PIN fallback, offline credential cache, UPS, signed offline audit log on the device. |
A realistic cost model — what hardening or building costs in 2026
The numbers below are starting points from real Fora Soft engagements; they assume our agent-engineering workflow, which has trimmed our typical timelines by roughly 25–35 % versus 2024 baselines. Treat them as a sanity check, not a quote. If you want a first read of an existing intercom codebase before paying for a pentest, our free security code audit lists every issue with file, line and fix in a report within three business days.
| Scenario | Approach | Engineering | Time to ship |
|---|---|---|---|
| Security audit of an existing platform | Threat model + pentest + remediation plan | ~$25–55K | 4–6 weeks |
| Hardening pass + auth modernisation | FIDO2, mTLS, signed firmware, audit log | ~$45–90K | 8–14 weeks |
| Cloud-managed SaaS for a vertical (e.g. multi-family) | WebRTC SFU + multi-tenant + SOC 2 readiness | ~$180–320K | 5–9 months |
| Enterprise / NIS2-grade hybrid platform | On-prem option, HSM, SIEM, ISO 27001 evidence | ~$320–600K | 7–12 months |

Figure 4. Buy vs build: 5-year total cost crosses over near ~2,500 doors (illustrative).
Mini case: what Netcam Studio and Nucleus taught us about intercom security
A long-running client of ours, Netcam Studio, makes IP camera surveillance software for homes, offices and schools. We built its web version and redesigned the interface: remote PTZ control, motion and sound detection with rule-based alerts, a multi-camera grid, and access from the browser and mobile apps.
Our intercom rule of thumb comes from that work. Every remote view of a camera exposes what happens inside the building, so the browser and mobile paths need the same authentication, permissions and logging as the device itself, even when the console looks as simple as a consumer app.
A separate project, Nucleus, sits at the other extreme: an on-premise communication platform where audio and video stay inside the customer’s network. We built its WebRTC/SIP calling layer and iOS/Android apps. Together, these two projects are the engineering heritage we draw on for any new intercom build. Want a similar review of your platform? Book a 30-min discovery call →
A decision framework — pick the right path in five questions
Q1. Where will the buildings be? EU only → design for NIS2 / CRA / GDPR from day one and avoid Hikvision/Dahua. US federal → NDAA-compliant supply chain. Multi-region → multi-tenant SaaS with selectable data residency.
Q2. How regulated is the use case? Multi-family residential → cloud SaaS is fine. Hospitals, gov, finance → on-prem or single-tenant cloud + HIPAA / NIS2 controls.
Q3. How many doors and tenants? <500 doors → buy ButterflyMX, Swiftlane or 2N. >~3,000 doors, or custom integrations at any size → build a private platform. Between 500 and ~2,500 doors, buy unless integrations or compliance force a build; the unit economics flip somewhere around 2,500–3,000 doors, depending on per-door pricing and how much custom integration you need (see Figure 4).
Q4. What is your identity story? Off-the-shelf SSO acceptable → SAML/OIDC integration with vendor portal. Need passkeys, MDM-bound credentials and tight revocation → build.
Q5. Where does the audit log go? Internal compliance only → vendor dashboard is fine. SOC 2 customers → you need exportable, immutable logs into the customer’s SIEM.
Five pitfalls we see every quarter
1. Treating the local network as “internal”. The intercom VLAN is not magically safer than the internet. Apply the same controls inside the building you would on the public path.
2. Forgetting to revoke. A lost phone or a fired employee should lose access in under a minute. Most field deployments we audit have revocation latencies measured in hours or days.
3. Letting the audit log be mutable. If admins can edit the log, the log is theatre. Stream every event to a write-only sink; sign the entries.
4. Shipping face recognition because “it’s cool”. In the EU, face templates are special-category data under GDPR, and 1:N identification is high-risk AI from December 2027; in Illinois, BIPA litigation follows biometric collection without written consent. Always have a non-biometric fallback and a documented DPIA before turning it on.
5. No firmware update story. A door device with a 10-year lifespan that cannot be updated is a CVE waiting to be filed. Sign images, support OTA, plan rollback, fund the SLA.
Reach for an external pentest when: the platform is about to enter production, before any RFP that requires a security questionnaire, after any major architectural change, and at minimum every 12 months thereafter.
Reach for a custom build over off-the-shelf when: the deployment runs past the ~2,500–3,000-door crossover, the audit log must stream into the customer’s SIEM, you need a vertical-specific UX (hospital, government, hospitality), or you want to private-label the platform for a network of security integrators.
KPIs — what to actually measure
Security KPIs. Mean time to patch a critical CVE (target <30 days), revocation latency for lost devices (target <60 s), share of devices on the latest signed firmware (target >95 %), MFA enforcement on admin accounts (target 100 %).
Reliability KPIs. Cloud control-plane uptime (target 99.95 %), local fallback PIN success rate during cloud outages (target 100 %), door-release latency p95 (target <1 s for mobile, <2 s for QR).
Business KPIs. Reduction in security-guard hours per building, reduction in lost-key replacement cost per resident per year, NPS from residents and managers, time-to-occupancy for new tenants (mobile credentials cut this dramatically vs. issuing physical keys).
When you should not deploy a connected intercom
Three situations where we have advised pausing. If you cannot fund the patch SLA, you will own a fleet of internet-connected boxes that quietly become a liability. Either commit to the operational discipline or stick with a non-networked intercom. If you want face identification across a whole building in the EU, expect a DPIA, an explicit-consent basis under GDPR and AI Act high-risk duties from December 2027. That is often a reason to switch to 1:1 verification or non-biometric methods. If your only differentiator is “cheaper”, cheap rebadged hardware will undercut you quickly; lead with security and compliance instead.
There is also a softer failure mode: shipping mobile credentials without a clean offline fallback. Networks fail. Phones die. A door that cannot be opened during an outage is a worse outcome than a door that needs a key.
Privacy and compliance — the artefacts a regulator will ask for
Data Protection Impact Assessment (DPIA). Required under GDPR Article 35 for systematic monitoring of publicly accessible areas on a large scale, and in practice for biometric door access. Run it before the system goes live; revisit annually.
Records of Processing Activities (RoPA). Your customers will ask for them; have them ready, building by building.
Data Processing Agreements with every sub-processor. Cloud hosting, video storage, push-notification provider, email vendor — if any of them sees personal data, you need a DPA on file.
Vulnerability disclosure policy + SBOM. CRA-aligned disclosure programme, a published security.txt, and a signed Software Bill of Materials per firmware release. Auditors will ask; your customers’ CISOs will ask.
Wiring intercom security into a WebRTC stack
For modern video intercoms the canonical pattern is a Selective Forwarding Unit (Janus, mediasoup, LiveKit) terminating SRTP / DTLS streams from the door device, with WebSocket signalling secured via TLS 1.3. Door commands ride MQTT with per-device ACLs; push notifications go through APNs/FCM with end-to-end encrypted payloads, never with the door-release token in plaintext.
Co-locate the SFU and the cloud control plane in the same region as the building to keep door-release latency under one second. Reserve a separate STUN/TURN tier for the intercom traffic so it cannot be flooded by other tenants. We covered the broader streaming pattern in our overview of secure video communication software, and it is the same stack discipline behind our custom video-surveillance development.
2026–2027 trends to watch
Passkeys and passwordless. FIDO2 / WebAuthn replace passwords for both admin portals and resident apps, and NIST SP 800-63-4 (final, August 2025) gives federal-grade guidance for syncable passkeys. For the door itself, Aliro 1.0 (CSA, 26 February 2026) is the first shared standard for phone and wearable credentials over NFC, BLE and UWB, so wallet-native credentials can work across reader brands.
Post-quantum cryptography. Door devices have 10-year lifespans. NIST published ML-KEM (FIPS 203, formerly Kyber) for key exchange and ML-DSA (FIPS 204, formerly Dilithium) for signatures in August 2024, and its final transition plan, NIST IR 8547 (27 October 2026), deprecates RSA and elliptic-curve algorithms of every key size after 2030 and disallows them after 2035 (Cloud Security Alliance, 2026). A device sold in 2026 will still be on the wall then, so plan two things now: key exchange that can move to ML-KEM by update, because recorded traffic is exposed to “harvest-now-decrypt-later” attacks, and a firmware-signing root that is already post-quantum or hybrid (for example LMS or XMSS under NIST SP 800-208), because a key fused into boot ROM cannot be swapped later.
Edge AI for privacy. Face blur, package detection, loitering alerts and visitor classification run on the device; only metadata leaves the building — the on-device approach we detail in our video-surveillance engineering track. The same pipeline that powers our real-time audio emotion analysis work applies here.
AI assistants on the intercom. LLM-driven visitor screening (“package or person?”) and voice control (“buzz in the courier”) become table stakes for premium tiers. Audit log them carefully.
FAQ
What is the single most common security failure in intercom platforms?
Default or weak credentials in field-deployed devices: botnets still scan for intercoms that accept factory logins. Close behind are RTSP video streams left open to the internet (a March 2026 scan found 8,074 that needed no password) and firmware more than 12 months behind.
Which encryption protocols are mandatory for a 2026-grade intercom?
DTLS-SRTP with perfect forward secrecy for media; TLS 1.3 for signalling and APIs (TLS 1.2 only as a time-boxed migration fallback, TLS 1.0/1.1 disabled); AES-256-GCM for data at rest; mTLS for device enrolment; and code-signing on every firmware image with rollback protection enforced by secure boot.
Can I still buy Hikvision or Dahua intercoms in 2026?
Yes, but expect friction. NDAA Section 889 bans both from US federal procurement, both are on the FCC Covered List (since 2022 the FCC has refused new authorisations for their surveillance gear marketed for public safety, government facilities and critical infrastructure), and Canada ordered Hikvision to cease Canadian operations in June 2025. Many private buyers have inherited those policies, and most enterprise security questionnaires now ask about Covered List vendors explicitly.
When should you use face recognition for intercom access?
Use 1:1 face verification, with explicit consent, a documented DPIA and templates kept on the device or in the resident’s phone. Under the EU AI Act, 1:1 verification is outside the high-risk list, while 1:N identification against a building gallery is high-risk from 2 December 2027. Always offer a non-biometric fallback (passkey, NFC, PIN).
What does the EU Cyber Resilience Act require from intercom software makers in 2026?
Since 11 September 2026, intercom makers selling in the EU must report actively exploited vulnerabilities and severe incidents through ENISA’s Single Reporting Platform: an early warning within 24 hours, a notification within 72 hours and a final report later. The rest of the CRA, including secure-by-default design and security updates for at least five years, applies from 11 December 2027.
What is NDAA-compliant intercom software?
It is intercom software running on hardware and components that contain no equipment from the companies named in NDAA Section 889, such as Hikvision and Dahua, so US federal agencies and their contractors can buy it. Ask the vendor for a per-SKU NDAA statement that covers OEM chips and rebadged devices, not only the brand on the box.
Cloud, on-prem or hybrid — how do I choose?
Cloud SaaS works for multi-family residential, small office and hospitality — lowest operational burden, fastest time to ship. On-prem is often the simpler answer for hospitals, government and finance, and for buildings in EU NIS2 essential-services scope; NIS2 does not require it, but it shortens the supplier-security review. Hybrid (cloud control plane, on-prem media) is increasingly the enterprise default.
How do I prove SOC 2 / ISO 27001 readiness to enterprise buyers?
Maintain a public security page, a DPA, an SBOM per firmware release, an immutable audit log accessible to the customer, a vulnerability disclosure programme, and the SOC 2 Type II or ISO 27001 report under NDA. Most enterprise procurements now require at least one of those certifications in the data room.
How long does a Fora Soft secure intercom build typically take?
A security audit + remediation plan ships in 4–6 weeks. A hardening + auth modernisation pass runs 8–14 weeks. A multi-tenant cloud SaaS for a vertical (multi-family, hospitality) takes 5–9 months including SOC 2 readiness. An enterprise / NIS2-grade hybrid platform with on-prem option, HSM and ISO 27001 evidence runs 7–12 months. Our agent-engineering workflow has trimmed all of these by ~25–35 % versus 2024.
What about post-quantum cryptography — do intercoms need it now?
Yes for any device with a 10-year service life. NIST IR 8547, finalised on 27 October 2026, deprecates RSA and elliptic-curve algorithms after 2030 and disallows them after 2035, so plan for ML-KEM (FIPS 203) for key exchange and ML-DSA (FIPS 204) for signatures, design key exchange so the algorithm can be swapped by update, and choose a firmware-signing root that is post-quantum or hybrid from day one, because a key fused into boot ROM cannot be changed later.
What to read next
Secure video
Secure video communication software for facilities
The wider video-comms patterns that an intercom platform inherits.
Architecture
Video intercom software — integrating video and audio
A deeper look at the multimedia stack underneath any modern intercom.
AI features
AI-powered intercom software systems
Where edge AI fits inside a hardened intercom platform.
Healthcare
Healthcare intercom software benefits
HIPAA-grade considerations when intercom meets clinical workflow.
Case study
Netcam Studio — modernising a video surveillance UI
How we built the web version of a long-running IP camera surveillance product.
Ready to ship a secure intercom platform?
Security in intercom software stopped being a marketing line in 2024. NIS2, the UK PSTI Act, CRA vulnerability reporting (live since September 2026) and the supply-chain rules around Hikvision and Dahua now make insecure intercoms a regulatory event — not just a reputational one. The good news is that the engineering pattern is settled: defence in depth across edge, network, cloud and identity, with five non-negotiable controls (DTLS-SRTP, TLS 1.3, signed firmware, FIDO2 admin auth, immutable audit log) and a serious patch SLA.
Buy ButterflyMX, Swiftlane or 2N when you have under ~500 doors and a vanilla use case. Build a custom platform when you serve a regulated vertical, when the audit log has to live in your customer’s SIEM, or when the unit economics tip past the ~2,500–3,000-door crossover. Either way, design the security in — do not retrofit it.


The handbook · 7 volumes
Fora Soft Video Engineering Handbook
A hardened intercom is still a real-time video product, and its security depends on how media moves end to end. We wrote seven volumes on that stack. Volume 3 covers WebRTC, DRM and live delivery, Volume 2 the transport layer, NAT traversal and QUIC, and Volume 7 biometric rules and the EU AI Act for camera products. Written by Nikolay Sapunov, CEO at Fora Soft.
Browse the handbook on Amazon →7 volumes · 9,000+ pages · Kindle & paperback
Let’s scope your secure intercom project
A 30-minute call covers your deployment scope, compliance footprint and target architecture. You leave with a first buy-vs-build view; a written threat model and estimate follow.