Building automation without blind spots

secnostic® connects building automation, building management systems, and technical building services in a dependable OTOT covers hardware and software that monitor and control physical devices, plants, processes, or infrastructure. view. Facilities, ITIT comprises systems, networks, and software that process, store, transmit, or provide information., and security teams can see assetsAn asset is a physical or digital element that is relevant to operations, control, monitoring, or security., communication paths, remote access, vulnerabilitiesA vulnerability is an exploitable weakness in software, hardware, configuration, process, or architecture., and ownership without unnecessarily touching live building functions.

For facilities, building services, IT, security, and property portfolios.

See what controls a building and who can reach it

NISTNIST is a US federal agency for standards, metrology, and technical guidance. explicitly classifies building automation systems as operational technologyNIST guide to operational technology and industrial control system security.. The BSIBSI security information from 2023 on documentation gaps, ownership, patch management, IT crossings, and undocumented remote maintenance in building automation and management. recommends starting with remote-maintenance access, ITIT comprises systems, networks, and software that process, store, transmit, or provide information. crossings, and the device inventory; its INF.14 implementation guidanceBSI implementation guidance covering documentation, roles, remote maintenance, segmentation, and protection of building-automation networks such as BACnet, KNX, and M-Bus. adds segmentationSegmentation divides a network into bounded areas so that data flows, access, and risk become more controllable., roles, and protected building-automation networks.

What this covers

Building automation is operational technologyOT covers hardware and software that monitor and control physical devices, plants, processes, or infrastructure.: NIST SP 800-82NIST guide to operational technology and industrial control system security. explicitly includes building automation systems in OTOT covers hardware and software that monitor and control physical devices, plants, processes, or infrastructure. and names HVACHVAC refers to systems for heating, ventilation, and air conditioning., electrical systems, lighting, and access control among the examples. The BSI INF.14 moduleBSI IT-Grundschutz module for integrating information security into the planning, implementation, and operation of building automation. places information security across the planning, implementation, and operation of building automation.

The BSI security informationBSI security information from 2023 on documentation gaps, ownership, patch management, IT crossings, and undocumented remote maintenance in building automation and management. recommends identifying remote-maintenance access, ITIT comprises systems, networks, and software that process, store, transmit, or provide information. crossings, and the device estate early. For the communication layer, ISO 16484-5Official ISO page for the data communication protocol used to monitor and control HVAC/R and other building systems. specifies a data communication protocol for HVACHVAC refers to systems for heating, ventilation, and air conditioning./R and other building systems. Section 71a of the German Building Energy ActCurrent German statutory text on building automation and control in specified non-residential buildings, including energy monitoring and interoperability. sets requirements for specified non-residential buildings. Applicability must be assessed for each building; secnostic® supplies context and evidence but replaces neither the BMS nor a conformity assessment.

Management servers, automation stations, gateways, sensors, and actuators connect HVACHVAC refers to systems for heating, ventilation, and air conditioning., energy, lighting, access, and other building disciplines. In existing buildings, BACnet, KNX, Modbus, M-Bus, proprietary interfaces, remote maintenance, and cloudCloud refers to on-demand IT resources such as compute, storage, platforms, or software that are consumed over a network. connections meet divided responsibilities. Without current shared context, dependencies, changes, and risks across buildings, ITIT comprises systems, networks, and software that process, store, transmit, or provide information., and suppliers remain hidden.

Outcomes

  • a current view of BMS, automation, and field components
  • traceable remote maintenance and supplier access
  • vulnerabilitiesA vulnerability is an exploitable weakness in software, hardware, configuration, process, or architecture. and EOL/EOSEOL/EOS describes lifecycle states in which a vendor no longer regularly maintains, sells, or supports a product, firmware, or system. prioritized by building impact
  • dependable documentation for risk assessmentA risk assessment evaluates threats, impacts, and protection needs so security measures are set based on risk rather than uniformly. and modernization

Four blind spots in building operations

The technical function is visible, but inventory, access paths, and ownership are often split across several disciplines.

Remote access without an owner

A permanent or forgotten supplier path remains risky when purpose, approval, and ownership are missing.

Plans without operating reality

Retrofits, gateway replacements, and supplier changes cause documentation and the actual estate to diverge.

Legacy technology on a flat network

Long-lived components and older communication need tightly controlled crossings when modern safeguards are unavailable.

A finding without building impact

A vulnerabilityA vulnerability is an exploitable weakness in software, hardware, configuration, process, or architecture. becomes actionable only when its building, discipline, dependency, maintenance window, and owner are known.

In practice, four building situations

Each situation starts with an observable signal or an existing source and ends with an accountable person.

  1. NoticeAn observation or import shows a previously unknown device or a new connection.
  2. Place itThe assetAn asset is a physical or digital element that is relevant to operations, control, monitoring, or security. is mapped to its building, room, discipline, zoneZones & Conduits is an IEC 62443 concept that groups systems with similar protection needs into security zones and describes permitted communication paths between these zones as conduits., and communication partners.
  3. AssessVersion, exposure, dependency, and intended function are reviewed together.
  4. AssignFacilities, ITIT comprises systems, networks, and software that process, store, transmit, or provide information., or the accountable integrator takes ownership of the clarification.

From network signal to building context

The secnostic® sensor observes approved IP segments passively. BMS exports, network data, and maintenance records add dormant or serial components; active queries run only after technical approval.

secnostic® inventory connects devices to buildings, disciplines, communication paths, lifecycle, and owners. The secnostic® platform governs tenants, roles, and access to secnostic® applications. focusAlert routes suitable operational and security events, but does not replace certified fire, evacuation, or safety alerting. Passing sensor data to inventory requires a configured integration. A configured webhook/API connection can pass events to focusAlert. This integration is optional.

FAQ

Key questions before a first scoping conversation.

Does secnostic replace the BMS or building control system?

No. The BMS remains responsible for control, regulation, and visualization. secnostic® adds technical assetAn asset is a physical or digital element that is relevant to operations, control, monitoring, or security., communication, risk, and ownership context.

Can the environment be discovered without interrupting operations?

The starting point is passive-first. Dormant, serial, or unobserved components may require additional exports, documentation, or approved queries. Active discovery is therefore never assumed by default.

Which systems belong in scope?

The scope can include management and engineering systems, automation stations, controllers, gateways, network components, sensors, actuators, meters, and remote-maintenance paths. Safety systems are included only where real interfaces exist.

Does secnostic make BACnet or KNX secure automatically?

No. Visibility and context show where segmentationSegmentation divides a network into bounded areas so that data flows, access, and risk become more controllable., access controls, secure protocol variants, or replacement are needed. Technical protection must be implemented in the relevant building automation system.

Does the solution automatically meet GEG, IEC 62443, NIS2, or BSI requirements?

No. secnostic® can support evidence for assetsAn asset is a physical or digital element that is relevant to operations, control, monitoring, or security., communication, measures, and ownership. Applicability and conformity must be assessed for the specific organization and system.

Which integrations need to be configured?

Passing sensor data to inventory requires a configured integration. A configured webhook/API connection can pass events to focusAlert. This integration is optional. Users sign in through the configured external identity providerAn IdP creates and manages identity information and provides authentication services for applications.. platform manages tenants and access to connected applications.

Start building automation with a dependable scope

We start with one building, campus, discipline, or remote-maintenance scope and show which operating and risk data is already usable.