1. HAMILTON VENUS Security Settings

2. Security Settings are set in the System Configuration Editor

3. HAMILTON VENUS Security Settings Checksum Verification Each method file contains a check sum. Checksum is a count of the number of bits in a file, this is included with the file so the software can check to see if file is intact. The check sum is updated each time the method is saved. The method files are tested for valid check sum on opening. If the check sum of one file is not valid, an error message box is displayed and the method is not opened.

4. HAMILTON VENUS Security Settings Checksum Verification Benefits: Prevents editing of files outside Hamilton software, which would circumvent other security settings. Detects file corruption.

5. HAMILTON VENUS Security Settings List Used Files This lists all the files that were used in the method at the end of the trace file when a method runs.

6. HAMILTON VENUS Security Settings Function Protection If enabled, it allows the access rights of users to be limited via use of an authentication system with password protection.

7. HAMILTON VENUS Security Settings File Validation Only available if Function Protection is enabled This function is used to notify the method user whether the method has been validated or not.

8. HAMILTON VENUS Security Settings Audit Trail Validation only – Audit trail information is requested while validating files. Always – Audit trail information is requested while validating and saving files.

9. HAMILTON VENUS Security Settings Audit Trail The method editor shows the Enter Change Description dialog box before saving the method files. If the dialog is cancelled, the method is not saved.

10. HAMILTON VENUS Security Settings Audit Trail View method Design History – with method open in method editor, select File, View Design History. Action on Save and Save As – The Save As command deletes the design history.

11. HAMILTON VENUS Security Settings File ValidationAudit TrailSaveValidate Enabled Always Programmer asked to comment, but not forced to Programmer must comment and enter version Validation only Programmer not asked to comment Programmer must comment and enter version Disabled Programmer not asked to comment Disabled Always Programmer asked to comment, but not forced to NA Validation only Programmer not asked to comment NA Disabled Programmer not asked to comment NA

12. HAMILTON VENUS Security Settings Authentication System Only available if Function Protection is enabled Hamilton Authentication System – User access is determined by logging in to Venus. The user can be changed while the application is running. Operating System – User access is determined by logging on to the computer. Privileges are set in ‘Computer Management \ System Tools \ Local Users and Groups \ Groups \ …’ Using both types of authentication systems a user can still delete the method files via the windows interface. The customer’s IT department would need to lock these files.

13. HAMILTON VENUS Security Settings Authentication System Operating System Hamilton Authentication System Individual system logonYesNo Enforced password changeYesNo Lock all Hamilton files in operating systemYesNo Enforce strong passwordsYesNo Centralised IT management of loginYesNo Management of access to network resourcesYesNo Simple system of user logonNoYes User management that doesn’t interfere with other IT systems NoYes Which authentication system is most suitable?

14. HAMILTON VENUS Security Settings Authentication System – Hamilton Authentication System Set up users and privileges in System Configuration Editor \ Manage Users.

15. HAMILTON VENUS Security Settings Authentication System – User Groups GroupUserAuthorisation Lab OperatorRoutine userOperators may run any method Lab OperatorRoutine user Operators 2 may run any method and move elements on deck Lab method programmer Method programmer Laboratory manager Method programmers may modify methods and labware definitions Lab remote service LAN manager PC adminstrator Remote service Lab service Service technician Laboratory manager Service technician for Hamilton’s laboratory software

16. HAMILTON VENUS Security Settings Authentication System – Operating System Need to restart the computer after managing users in operating system authentication Details of how to setup authentication system are found in the Venus Two Programmers Manual - with screenshots Authentication systems - chapter 2.4 Choose authentication system - 2.4.1 Operating system authentication system - 2.4.2 Hamilton authentication system - 2.4.3

17. HAMILTON VENUS Security Settings Authentication System Warning Turning on either authentication system may lock you out of the system. You need to check you have sufficient access rights needed to make the user changes before turning it on. For Hamilton Authentication System – all the information needed is in the programmers manual. For Operating System Authentication – it is advised that you have support from the customer’s IT department.

18. HAMILTON VENUS Security Settings Example 1: Prevent a user from running an unvalidated method. Secutity Settings File Validation - Enabled Function Protection - Enabled Authentication System - Hamilton Authentication or Operating System Manage Users Set up a user in one of the following groups: Lab Operator Lab Operator 2

19. HAMILTON VENUS Security Settings Example 2: Prevent a user from changing anything in a method. Secutity Settings File Validation - Enabled Function Protection - Enabled Authentication System - Hamilton Authentication or Operating System Manage Users Set up a user as a Lab Operator

20. HAMILTON VENUS Security Settings Warning When using the Hamilton Authentication System and running a method that appends, or writes to a file, a user with a low level of access, e.g. lab operator can be prevented from running the method. Error message: Cannot update. Database or object is read-only. To overcome this the customer’s IT department need to change the access rights of the files or folders to give ‘write’ access.