The protocols used to communicate with readers must be secured because the
communication with a reader can be listened to and manipulated by an attacker.
What you should know
Some communication protocols are more secure than others. Follow the recommendations
to ensure your reader connections are secure:
- Avoid using the Wiegand protocol.
- Use the OSDP v2 protocol with the secure channel mode enabled.
- Use the SSCP v2 protocol with STid readers.
NOTE: The reader must be online for the connection settings to be taken into account
in the security score.
Procedure
-
From the Config Tool homepage, open
the Access control task, and click the Roles and
units view.
-
From the entity browser, select an access control unit.
-
If you are using Mercury controllers, click the Peripherals
tab, then expand the Mercury controllers and downstream panels.
-
If you are using any other type of interface modules, click the
Hardware tab, then click the tabs for your
integrations.
-
Change the reader settings to follow the recommendations, if applicable.
Not all interface module and reader combinations support secure connections.
The
following reader connections are not secure:
- Wiegand readers.
- Clock and Data readers.
- OSDP readers that have not been enabled for secure pairing.
- OSDP readers that use a default key.
-
Click Apply.