KNXGuard user defined
1Pages

KNXGuardThe EIB/KNX security element Highlights • Protects your EIB/KNX system from unwanted programming access • Blocks all physical write telegrams, Physical device monitoring possible, Can be used as an ACK device, EIB/KNX-2-wire connection, Alarming, Device readout still permitted but programming is prevented, The device can be acti'vated/deactived with the EIBDoktor to permit device programming, The deactivation is secured by means of a PIN/RSA algorithm, Housing for installation in flush-mounted socket, • No physical address needed KNXGuard „User defined" The KNXGuard „User defined" has the same functionality as the „High security" device, but you can acti'vate/deactive this type of KNXGuard by sending special telegrams (using the EIBDoktor software). The telegrams will be send to the broadcast address 15/7/255. Inside the telegram is the serial number of the KNXGuard and a special security code, using a RSA algorithm: even if somebody else is able to protocol the telegrams to deactivate the KNXGuard, sending them later will be useless, since the telegrams are only correct at a special time. Trying to send the deactivation telegram on a later time will have no effect at all. Remark: The KNXGuard is delivered ex factory with the high security configuration. To change this configuration an EIBDoktor EIBWeiche is required! Requirements for all KNXGuard devices: You have to install an KNXGuard into every line you want to protect: security on the „backbone" will not grant security in lower lines most times. Alarming: You can define an „Alarming group address", the KNXGuard will send a telegram to this address each time somebody is trying to do an illegal access. This telegram can be used to display a warning inside a visualization software, for example. ACK functionality: The KNXGuard also acts as an „ACK device", which means that it will acknowledge all groupaddress telegrams, and prevents unnecessary busload this way. This will not affect the function of the EIB/KNX, damaged telegrams will still get repeated. No physical address: The KNXGuard acts as an ^invisible" device, it will not get used inside the ETS project. The ETS is also not able to detect the KNXGuard. Therefore the KNXGuard does not need a physical address. errors and omissions excepted b+b Automations- und Steuerungstechnik GmbH Beerfelden Site I ■ DieselstraBe 18 ■ Airlenbach Site II ■ EichenstraBe 38a ■ 64760 Oberzent (Germany) phone: +49 (0) 6068 9310-0 ■ fax: +49 (0) 6068 9310-99 info@bb-automation.com ■ www.bb-automation.com