HTTPS, Certificates and Activity Logs: Corporate Security Settings

A queue management system carries user names, transaction records and corporate user data. Security settings are therefore not "extra work after installation" but part of the installation.

Certificates and HTTPS

When configured with your corporate certificates, the system runs over HTTPS. The same certificate can be used by the branch software, in which case in-branch communication is also protected by HTTPS. No additional certificate management burden is created.

Network and port discipline

Certain ports must be open for communication between client and server. For a secure communication environment, configuring only the necessary ports and permissions is recommended; leaving unnecessary openings is the main pitfall.

Identity and records

• Passwords are stored hashed in the database
• Password reset flows over e-mail
• Actions are recorded in an activity log
• User permissions are defined per role and branch

Operational visibility

The activity log is not only a security tool; because it answers "who changed this definition?", it is also the screen operations teams use most. In a structure synchronised with corporate user data, user changes are reflected in the system without extra work.

Related articles