Security — Signify Interact for Intelligent Buildings

As lighting systems have become an integral part of the Internet of Things (IoT), they are exposed to the same security risks as any other Internet-connected device.

This section addresses security concerns and provides steps to mitigate security issues.

Companies use well established procedures to reduce risk of corporate data breaches via devices connected to the company’s internal network. Company-issued computers, smartphones, tablets, and so on, are considered attack vectors which are required to comply with certain rules to be trusted and granted access to an internal corporate network. The same procedures apply for IoT systems that connect to a corporate IT network.

At Signify, the Corporate Security Office manages security governance.

The Product Security Leadership Team, which includes members from the Corporate Product Security organization, business groups, and Product Innovation team, coordinates our security efforts.

A network of security architects and security specialists embedded in the development teams supports security activities related to product development.

All Signify employees are required to attend regular cybersecurity and privacy awareness training. System architects and development engineers must also receive additional security training and internal certifications.

Signify Interact for Intelligent Buildings mitigates security risks of a lighting IoT system by employing security strategies that are described later on in this section.

The key concerns regarding an IoT solution deployed on a corporate IT network are the following:

All of our internal and external development activities follow the Signify Security Development Lifecycle (SDL), which codifies industry accepted best practices. The major components of the SDL are security risk analysis and threat modeling, code analysis and review, and vulnerability management. We apply the SDL to all of our hardware products, systems, services, software, and cloud solutions.

In accordance with the SDL, Signify takes the following actions during design, development, and testing:

The Innovation team is responsible for evaluating the latest IoT security technologies, and supports the development team in making the right choices when introducing new security algorithms, solutions, and technology partners.

Signify regularly audits its partners and supply chain to maintain the appropriate level of security in the manufacturing process.

The figure below depicts an overview of a Signify Interact for Intelligent Buildings system.

Signify Interact for Intelligent Buildings connected system overview:

Cloud connected to a portal and, via the corporate IT network, to gateways. Each gateway bridges to Zigbee mesh networks of light and control devices. The mobile app connects to the cloud and, via Bluetooth, to individual lights for commissioning.

Signify Interact for Intelligent Buildings non-connected system overview:

Cloud used as a backup for secure access across phones/users. The mobile app connects to Zigbee mesh networks of lights via Bluetooth, with essential security data backed up in the cloud.

In Signify Interact for Intelligent Buildings, light control is implemented using a wireless mesh network based on the Zigbee protocol: two-way communication between lights and discrete controls is solely based on this protocol. Commissioning and user control are done using a mobile app.

When the system is connected to the internet via gateways:

For connected systems, each gateway is the trust center for all the other Zigbee devices in the network it is connecting to.

When the system is not connected via gateways:

For non-connected systems, mobile phone enables the creation of network.

In both cases, non-connected and connected, system security is addressed end-to-end to guarantee data confidentiality, integrity, and availability: to ensure this, network security, device and physical security, communication security for in-transit data, cloud security as well as installation security aspects are addressed.

Various encryption techniques are used to ensure that all communication is protected end-to-end between devices used in the Signify Interact for Intelligent Buildings system. To protect the Signify Interact for Intelligent Buildings cloud services, only Interact devices can access them. This is ensured by using unique device credentials that are assigned to all devices during production. The identities of all of these devices are maintained in the cloud platform. Only devices with a known credential can communicate with Signify Interact for Intelligent Buildings cloud services.

All communication between devices on-site and the cloud is done by Signify Interact for Intelligent Buildings gateways. This communication is encrypted using the standard TLS 1.2 or 1.3 protocol. Authentication ensures that only these Interact devices are communicating with our cloud services. Furthermore, all communication is enabled inside out: that is, the gateway connects to the cloud rather than the other way around.

Gateways do not store data: they relay data coming from other devices to the cloud. To optimize communication and to bridge periods with limited connectivity they may temporarily store some data in memory. However, they are connected to the customer’s IT network and have ample computing and memory resources. To prevent tampering with gateways, so that they can’t be used to compromise the customer network or access data, they are hardened to minimize attack surface and vectors.

Wireless lights, sensors and switches communicate over a Zigbee mesh network (IEEE 802.15.4), with frames protected by symmetric AES-128 encryption in CCM mode for both confidentiality and integrity. Each network uses its own randomly generated key, managed by the network’s trust center.

The Signify Interact Builder app can directly communicate with the latest generation of wireless devices that besides Zigbee also allow for Bluetooth communication (only between mobile devices and an Interact device). Bluetooth security builds on the security libraries of the operating system of the supported mobile phone platforms, iOS and Android. The complete security solution consists of:

Interfaces on Wireless Gateways are always using encrypted communication. Our end devices always use the Zigbee security layer.

All device features and requirements are aligned with the OWASP IoT framework and built with security in mind. The devices' Operating Systems are hardened by whitelisting of services and libraries.

Firmware updates are started using the app or portal by authorized users. All firmware images are signed and verified before being deployed on end devices.

The cloud platform is a key component of Signify Interact for Intelligent Buildings:

Because the lighting system (in the connected configuration) is permanently connected to the cloud platform, system security is given top priority from the specification phase onwards, taking into account the full hardware lifespan of each installation.

All cloud development and operations follow the Signify Security Development Lifecycle (SDL) described in Section 2. In accordance with the SDL, cloud releases are subject to security risk analysis and threat modeling, automated and manual code review, analysis of third-party and open-source code for vulnerabilities, operating-system and application hardening, regular review of network security and firewall rules, encryption of data in transit and at rest according to generally accepted industry standards, and penetration testing by internal and/or external parties before each customer release. The Innovation team evaluates the latest IoT security technologies and supports the development team when introducing new security algorithms, solutions, and technology partners. Signify also regularly audits its partners and supply chain to maintain the appropriate level of security in the manufacturing process.

At Signify, we implement a security policy which enforces segregation of duties and least privilege access.

The Signify Interact for Intelligent Buildings cloud services are managed by a specialized global operations team to ensure proper segregation of duties for system administration purposes. Responsibilities of the team include producing operational specifications and performing maintenance, security updates, vulnerability management, backup, logging, monitoring, and management of events and incidents. The team also performs periodic review of network and application security. Development teams and in general other personnel do not have access to production systems or production data. In case access to data is necessary, for supporting operations, only the Operations team is allowed and strictly for the limited time and scope needed.

Signify Interact Builder application services (mobile app, and web portal) are managed by the concept of Projects. A Project is characterized by (part of) a building at a specific location and dedicated user account(s). Data of different projects are separated from each other. All data of a project is considered confidential.

Data of all Projects (except China) is stored with the following cloud provider at the following locations:

For reliability and availability, backups are stored at two different locations to be able to recover from a major system event.

Data is stored in the form of:

Project data can only be accessed by authorized users or Signify user managers via user accounts. User accounts are created through self-registration, which results in a profile having project ownership, and by invitation, which results in a profile giving a user the necessary rights to access the project data via its application services. Signify Interact for Intelligent Buildings supports different user profiles with associated access rights and capabilities for its application services.

Project data consists of system telemetry and personal identifiable information, each of which will be processed differently (see also 'Data processing').

For more information on Signify’s privacy and data governance, visit our privacy notice page.

Signify policies and processes are aligned with global standards such as ISO/IEC 2700x — Information Security Management Systems (ISMS) and the ISA/IEC 62443 standards suite for product development. Signify is IEC 62443-4-1 certified, which ensures that development and maintenance processes enable the creation of secure systems.

Through our Standards and Regulation department, we collaborate with many worldwide standardization organizations, such as IEC, ANSI, and CENELEC, and with industry alliances such as the IoT Security Foundation.

Signify also aligns its practices with the Cloud Security Alliance (CSA) self-assessment tool.

Signify business processes are internally and externally audited on a regular basis.

In terms of data protection of storage and privacy, Signify complies with GDPR. Signify also aligns its practices with the Cloud Security Alliance (CSA) self-assessment tool. More details about standards are available in the General Security Statement under Signify Security: selected best practices > Governance, education and training: https://www.signify.com/global/product-security/professional-systems-and-services.

Signify recognizes that the security of our products and services is an important part of our customers' in-depth security strategy. In practice, however, security is a responsibility shared by manufacturers and providers of products and services and their customers.

Appropriate evaluation of risks and proper care in installation, maintenance, and operations are essential to mitigate internal and external threats.

For Signify Interact for Intelligent Buildings, the following practices are the customer’s responsibility:

See the General Product Security Statement for more information: https://www.signify.com/global/product-security/professional-systems-and-services.

The following figures are provided for reference. The originals are in the General Product Security Statement.

A typical Signify system has both on-premise components and cloud components.

On-premise and cloud components

On-premise components are installed at the customer site (lighting gateways, networking equipment, lighting controllers, load controllers, luminaires, sensors, switches). Cloud components are reachable via the internet (backend / UI, API, analytics / reports).

Responsibility for security is typically shared between the manufacturer (Signify) and the customer.

Shared responsibility model

Security activities across the lifecycle — Development (Secure Development SDL, Encryption and Data Security), Infrastructure (Network Security, Data Center Physical Security), Installation (Secure Installation, Hardening), Operations (Business Continuity, Incident Management, Credential Management), Maintenance (Application Updates, OS Updates, Threat and Vulnerability Management), and Decommissioning (Secure Data Removal) — are divided between Signify and the customer depending on the deployment.

The Signify Interact for Intelligent Buildings gateways communicate with the cloud via a customer’s IT network using IPv4. Each gateway needs to receive an IP address from a DHCP server on that network. The use of static IP addresses for gateways is not possible.

All connections from Signify Interact for Intelligent Buildings devices to cloud services are initiated by the gateway using dedicated URLs and ports. New connections created outside the network are not allowed. Secure communication is always initiated by a gateway of the Signify Interact for Intelligent Buildings system. Communication between the gateways and the cloud uses the HTTPS protocol which uses the standard TCP port 443. MQTT messages are also sent using this port. The benefit is that only standard web browser ports need to be opened up for Signify Interact for Intelligent Buildings devices to communicate with the cloud.

For the list of URLs and ports used by Signify Interact for Intelligent Buildings, see Network Requirements.

Optionally, when allowed on the customer’s IT network, UDP port 123 needs to be open to allow for NTP (Network Time Protocol) time synchronization.

These URLs and ports need to be whitelisted using the security framework of the customer’s IT network to allow for communication between Signify Interact for Intelligent Buildings gateways and the cloud.

Note that the non-connected configuration doesn’t impose any requirements on the customer’s IT network. Only the phone used for setup and control of the system needs to be able to connect to the cloud platform for backup purposes.

Security incidents for Signify Interact for Intelligent Buildings are to be reported via its support channels, either the local support call center or the Customer Satisfaction team of the market.

Signify supports responsible vulnerability disclosures and encourages researchers and ethical hackers to report identified vulnerabilities. For more information on Signify responsible disclosure, visit the vulnerability disclosure page.

This information is provided for informational purposes only. It represents the current product information as of the date of publication. These are subject to change without notice.

Customers are responsible for making their own independent assessment of Signify products or services and the use thereof. This information is provided "as is" without warranty of any kind, whether express or implied. This information does not create any warranties, representations, contractual commitments, conditions, or assurances from Signify, its affiliates, suppliers, or licensors. The responsibilities and liabilities of Signify and its customers are defined in the agreements between Signify and its customers. This information is not part of, nor does it modify, any agreement between Signify and its customers.

Learn more about Interact — https://www.interact-lighting.com

© 2026 Signify Holding. All rights reserved.

The information provided herein is subject to change, without notice. Signify does not give any representation or warranty as to the accuracy or completeness of the information included herein and shall not be liable for any action in reliance thereon. The information presented in this document is not intended as any commercial offer and does not form part of any quotation or contract, unless otherwise agreed by Signify.

All trademarks are owned by Signify Holding or their respective owners.