Centum VP Authentication
Centum VP Authentication
CONTENTS
1. Overview.................................................................................................... 1-1
1.1 1.2 Security Threats to be Handled. ...................................................................... 1-2 Security Measures............................................................................................. 1-3 Security Models................................................................................................. 2-2 User/Group Management. ................................................................................. 2-4 2.2.1 2.2.2 2.2.3 2.2.4 2.2.5 User Management Methods............................................................... 2-5 CENTUM VP User Authentication Modes.......................................... 2-6 Users/Groups with Respect to the Combination of User Management and Security Model.............................................. 2-9 User Name and Password Policies.................................................. 2-14 Special User. ..................................................................................... 2-15
2.
3.
Personal Firewall Tuning. ................................................................................ 3-14 Stopping Unused Window Services.............................................................. 3-17 Changing IT Environment Settings............................................................... 3-18 3.4.1 3.4.2 3.4.3 3.4.4 3.4.5 3.4.6 3.4.7 3.4.8 3.4.9 3.4.10 3.4.11 3.4.12 Changing or Disabling the User Name of Administrator ............... 3-19 Hiding the Last Logon User Name .................................................. 3-20 Applying the Software Restriction Policies....................................... 3-21 Applying AutoRun Restrictions......................................................... 3-23 Applying the StorageDevicePolicies Function. ................................. 3-24 Disabling USB Storage Devices....................................................... 3-25 Disabling NetBIOS over TCP/IP....................................................... 3-26 Changing the LAN Manager Authentication Level........................... 3-27 Applying the Password Policies. ....................................................... 3-28 Applying the Audit Policy. .................................................................. 3-29 Applying the Account Lockout Policy................................................ 3-30 HDD Password Function by BIOS. .................................................. 3-31
IM 33K01C30-50E
Toc-2
4. Selection of Security Functions.............................................................. 4-1
4.1 4.2 Items to be Considered before Setting Security Functions. ........................ 4-2 Model Cases....................................................................................................... 4-4 Windows Account Management...................................................................... 5-2 5.1.1 5.1.2 5.1.3 5.2 Common Account Management......................................................... 5-3 Individual Account Management........................................................ 5-4 Common Precautions for Common Account Management/ Individual Account Management........................................................ 5-5
5.
Related Programs.............................................................................................. 5-6 IT Security Tool.................................................................................................. 6-2 Other Utility Programs.................................................................................... 6-14
6.
IM 33K01C30-50E
<1. Overview>
1-1
1.
Overview
This manual is a guide for implementing security measures in the system and for its operation. By operating the system with security measures implemented, the system is protected from existing and future security threats. The security models described in this manual are based on general configuration of the product. You must consider engineering and operation practices when applying these models to the actual systems.
Kerberos authentication
Personal firewall
IM 33K01C30-50E
1-2
1.1
This section explains security threats that the security of CENTUM VP must handle.
n Security Threats
The security threats that may harm the CENTUM VP system are as follows: 1. Attacks over network Threats to the CENTUM VP system from people without any rights to the CENTUM VP system via networks such as intranets, as well as the resultant threats of leakage of important data of the CENTUM VP system. Direct attack to a system by operating on an HIS or on a PC installed with system builders Threats from unauthorized individuals to the CENTUM VP system by directly operating an HIS or PC installed with system builders to affect the system for the purpose of stealing important data. Theft of an HIS or PC installed with system builders or theft of data Threats where an HIS or PC installed with system builders is stolen or data are stolen from it for the purpose of analyzing the data.
1. Attacks over network
2.
3.
Intranet
Firewall
Ethernet
HIS
Control bus
3. Theft of an HIS or PC installed with system builders or theft of data FCS FCS
010101E.ai
IM 33K01C30-50E
1-3
1.2
This section describes the security measures to prevent against security threats. Identify security measure items required for the CENTUM VP system and, from among them, select the required security measures according to the level of security strength.
Security Measures
Security type
[2] Handling Handling Handling Handling Handling Handling Handling Handling Handling Handling
Handling Handling Handling Handling Handling Handling Handling Handling Handling Handling Handling
[1]: Attacks over network [2]: Direct attack to a system by operating on an HIS or on a PC installed with system builders [3]: Theft of an HIS or PC installed with system builders or theft of data Handling: Applicable : Not applicable
IM 33K01C30-50E
Blank Page
2-1
2.
Security Models
CENTUM VP provides three types of security models, Legacy model, Standard model, and strengthened model, according to the required security strength, in order to flexibly accommodate system configuration and operation. Required security measure items are incorporated in the security models.
IMPORTANT
Please consult Yokogawa if IT security of the Strengthened model is required.
IM 33K01C30-50E
2-2
2.1
In order to support system configurations and operations in flexible manners, three models of security settings, Legacy model, Standard model and Strengthened model are provided.
Security Models
n Security Models
The features of the security models are shown in the following table.
Table Features of Security Models Feature This model does not strengthen security. Use this model when you connect the system with Yokogawa products that do not support security measures. This model places importance on operation of CENTUM VP systems and collaboration with other systems (Exaopc, ProSafe-RS, etc.) to guard against attacks over network and direct attack to a system by operating on an HIS or on a PC installed with system builders. Nevertheless, Standard model cannot prevent the data in an HIS or PC installed with system builders when the HIS or the PC is stolen. Considering the deployment of CENTUM VP systems, the risk of this threat is relatively low. Security model Legacy model
Standard model
This model takes all measures against any security treats. If all security measures Strengthened model are taken, operation and so on may be affected. Take measures according to the characteristics of each system for non-mandatory items.
IM 33K01C30-50E
2-3
Security type Access control Personal firewall tuning Stopping unused Windows services
Support Support Support Support Support Support Support Support Support Support Support Support Support Support Support
SEE
ALSO
For details of security measures, see the following: 3, Details of Security Measures A security setting tool is available for setup legacy model and standard model of security settings, for more information, see the following: 6.1, IT Security Tool
IM 33K01C30-50E
2-4
2.2
This section explains the relationship between user management of Windows and the CENTUM VP system. Access control is set for each user group explained in this section.
User/Group Management
IM 33K01C30-50E
2-5
2.2.1
Windows environment provides two methods of managing users, workgroup management and domain management. CENTUM VP also supports a user management method called combination management that combines workgroup management and domain management.
Table User Management Methods Configuration Operation Operated by registering user accounts used in each of all the PCs of HIS and system builders. Operated by registering user accounts used to the domain controller. Operated the same way as for the domain management in normal operation. Feature Simple configuration not requiring domain controller. Since account management is required for each PC, all PCs must be maintained at user account maintenance, making this method not suited for large-scale systems. It is not possible to separate administrator rights to PC and maintenance rights to CENTUM VP system. Centralized management of users is possible, allowing less human errors. It is possible to separate administrator rights to PC and maintenance rights to CENTUM VP system. Even if a domain controller is not available, continuous operation is possible by managing accounts of each PC. It is not possible to separate administrator rights to PC and maintenance rights to CENTUM VP system. Management method
Construction of domain controller, Domain in addition to management CENTUM VP system, is required. Construction of domain controller, Combination in addition to management CENTUM VP system, is required.
TIP
The combination management is used when operation similar to workgroup management is assumed in normal operation although the main user management is performed by the domain management. Specifically, it refers to a case as follows: In normal operation, user creation is centralized using the domain management. However, it is desired that assignment of rights to users is enabled on certain PCs on the authority of the person in charge at a site.
IM 33K01C30-50E
2-6
2.2.2
Two user authentication modes are provided to authenticate users of CENTUM VP, Windows authentication mode and CENTUM authentication mode.
IMPORTANT
The Windows authentication mode is available only when Standard security model or strengthened security model is applied.
The CENTUM VP users need to be authenticated are the following group users. HIS group users Users who use the operation and monitoring function. These users are registered using the Security Builder. ENG group users A collective term for system engineers, recipe engineers, and report users who are registered at installation of the Access Control Package or the Access Administrator Package (FDA:21 CFR Part 11 compliant). Users and builders that manage the users are shown in the table below.
Table Users and Builders Managing Users User HIS group user System engineer ENG group user ENG Group User Recipe engineer Registration Builder (*1) Report user
*1:
Engineers Engineers who perform engineering Account Builder for tasks in the System View and various system engineers builders started from the System View Engineers Account Builder for Engineers who use the recipe function recipe engineers Users Account Builder for report users Users of the report function
A collective term for Engineers Account Builder for system engineers, Engineers Account Builder for recipe engineers, and Users Account Builder for report users.
When Windows authentication mode is set, user authentication is performed when a user log on to Windows. And when the user tries to use the operation and monitoring functions or builders, the authentication is internally performed with the Windows logon user name, allowing the user to continue tasks without entering a user name and password again. The user authentication mode can be applied to the following identities: HIS group user: For each project (for each project in the case of multiple project connection) ENG group user: For each engineers account file and users account file
IM 33K01C30-50E
2-7
HIS
HIS
HIS
The user authentication modes are set in the project properties of the System View. Downloading is required after the setting. The information of the downloaded user authentication mode (CENTUM authentication mode or Windows authentication mode) is used as follows. If the Standard model is set as the security model of HIS, the selected authentication mode downloaded to the HIS will take effect when the HIS is restarted. If the Standard model is set as the security model of HIS and the downloaded user authentication mode is different from the current user authentication mode while the operation and monitoring functions are running, a system alarm will occur. The user authentication mode will change when the HIS is restarted. If the Legacy model is set as the security model of HIS and the downloaded user authentication mode is the Windows authentication mode, a system alarm will occur. The CENTUM authentication mode remains unchanged even if the HIS is restarted. In this case, you need to set the Standard model for the security model of HIS using the IT Security Tool or revert to CENTUM authentication mode.
IM 33K01C30-50E
2-8
IMPORTANT
Although the user authentication mode is not switched until the HIS is restarted, the settings in the Security Builder are changed to the downloaded information. If a user is deleted, the deleted user cannot be used. For gradually migrating the system from the CENTUM authentication mode to the Windows authentication mode, temporarily keeping CENTUM authentication mode in the running HIS may be necessary, thus you need to keep the HIS users in the Security Builder.
l Single Sign On
When the Windows authentication mode is set as the user authentication mode for HIS group users, once a user passed the user authentication, a user can logon both Windows and HIS. This is referred to single sign on. There are two following types of single sign on. Windows Type Single Sign On If a user logs on from the Windows logon dialog box, this user will automatically logon the operation and monitoring console, i.e., the user becomes user-in status of the Operation and Monitoring Functions. On the user-in dialog box, you can switch user. When you set a user to user-out status, the user you previously logged on the Windows will become user-in status. HIS Type Single Sign On When a PC is started, this function automatically makes the user log onto the Windows and starts the operation and monitoring function as OFFUSER (default user). After automatic logon via the HIS Type Single Sign On, the CENTUM desktop is always applied.
TIP
In CENTUM authentication mode, anonymous user be used to sign on the operation and monitoring console due to HS group users are able to share information. However, In Windows authentication mode, the anonymous user is restricted for singing on so as to improve the operation traceability and securer operation.
Reference
Ethernet
The user authentication modes are set using the Access Control Utilities. The information on user authentication mode is immediately reflected and used at the timing of user authentication.
IM 33K01C30-50E
2-9
2.2.3
Users/Groups with Respect to the Combination of User Management and Security Model
Type 1: Legacy Model Type 2: Standard Model / Strengthened Model - Standalone management Type 3: Standard Model / Strengthened Model - Domain Management Type 4: Standard Model / Strengthened Model - Combination Management
When applying a security model, the security model will work with Windows user management to create users and groups.
TIP
No matter what security model is applied, CENTUM VP installer will create a CTM_MAINTENANCE group and add the user who installed the CENTUM VP as a member of this group. However, if legacy model is applied, the CTM_MAINTENANCE group should not be used. Moreover, if domain management type or combination management type is used for user management, the CTM_MAINTENANCE group in the domain should be used instead of CTM_MAINTENANCE group in the local PC.
User name
CENTUM
User
Local PC
Users
CTM_PROCESS
User
Local PC
Users
LIC_PROCESS
User
Local PC
Users
IMPORTANT
These user accounts should be used for running CENTUM products only.
IM 33K01C30-50E
2-10
Local PC
Local PC Local PC
OFFUSER
User
Local PC
Users
CTM_PROCESS
User
Local PC
Users
LIC_PROCESS
User
Local PC
Users
*1:
You need to add the users who belong to the created group to the group shown in the Right group column.
IMPORTANT
These user accounts should be used for running CENTUM products only. When changing security model, the group name may be changed or groups may be deleted without prompting the confirmation dialogs.
IM 33K01C30-50E
2-11
CTM_OPC_LCL
Group
Local PC
Users (*1)
CTM_ MAINTENANCE
Group
Domain controller
Group
Local PC
Administrators (*1)
OFFUSER
User
Local PC
Users
CTM_PROCESS
User
Local PC
Users
LIC_PROCESS
User
Local PC
Users
*1:
You need to add the users who belong to the created group to the group shown in the Right group column.
IMPORTANT
These user accounts should be used for running CENTUM products only. When changing security model, the group name may be changed or groups may be deleted without prompting the confirmation dialogs.
IM 33K01C30-50E
2-12
Domain controller
Group of users who use the System View Domain Admins and so on for engineering of CENTUM (*1) VP with stronger rights than CTM_ ENGINEER. Administrators (*1) Domain Users (*1) Group of users who use the System View and so on for engineering of CENTUM VP with stronger rights than CTM_ENGINEER and are used in PC of a workgroup. Group of users for performing OPC communication with CENTUM VP. Supplementary group for users not supporting domain management, such as users embedded in the EXA package, having the same rights as CTM_OPC. It is not used in normal operation.
Local PC
CTM_OPC
Group
Domain controller
CTM_OPC_LCL
Group
Local PC
Users (*1)
CTM_ MAINTENANCE
Group
Domain controller
Group of users who perform system Domain Admins installation and CENTUM VP (*1) maintenance. Emergency group used when the domain environment is abnormal, having the same rights as CTM_MAINTENANCE. It is not used in normal operation. After the installation of CENTUM VP is completed in the domain environment, the administrator user of each PC (local user) should be manually added to this local group.
Group
Local PC
Administrators (*1)
*1:
You need to add the users who belong to the created group to the group shown in the Right group column.
IM 33K01C30-50E
2-13
Table
Standard Model/Strengthened Model - Combination Management (2/2) User/group Created location Right group Explanation User used to automatically log on with HIS Type Single Sign On of the Windows authentication mode. It has minimum rights for the Windows environment. The password of OFFUSER is not disclosed. User for performing processes of CENTUM VP (Windows services) who does not have Windows logon rights. The password of CTM_PROCESS is not disclosed. User for running license management processes (Windows services) that does not have Windows logon rights. The password of LIC_PROCESS is not disclosed. You must not change the password.
OFFUSER
User
Local PC
Users
CTM_PROCESS
User
Local PC
Users
LIC_PROCESS
User
Local PC
Users
IMPORTANT
These user accounts should be used for running CENTUM products only. When changing security model, the group name may be changed or groups may be deleted without prompting the confirmation dialogs.
IM 33K01C30-50E
2-14
2.2.4
The policies regarding the Windows user names and passwords are in Windows environment. While, the HIS group users and ENG group users are defined with a certain policies. The HIS group users, ENG group users and the Windows users in Windows authentication mode need to be created according to these policies.
n User Name
The user name convention is as follows.
Table User Name Convention Up to 16 characters Alphanumeric including symbols of ! # $ % ( ) - . ^ _ { } ~ Double-byte character is invalid Capital letters only The first character can be an alpha or numeric character as well as a symbol of ^ _ { } ~ A period character cannot be put at the last place. Number of characters Character type
Restriction
TIP
ENG group user and HIS group user names can be created with capital letters only. Windows user names are not case sensitive, but it is recommended to use the capital letters.
n Password
There are the following rules for passwords.
Table Password Convention The password of a HIS group user or ENG group user can be defined using up to 32 alpha-numeric characters. The password of a Windows user used in Windows authentication mode can be defined using up to 63 alpha-numeric characters. Alphanumeric including symbols of ! # $ % & ( ) * + , - . / : ; < = > ? @ [ \ ] ^ _ ` { | } ~ and space character. Restricted by password policies set in Windows
Number of characters
TIP
The passwords for HIS group users are restricted by the password policies defined by HIS Utility. The passwords for ENG group users are restricted by the password policies defined Access Control Utilities.
IM 33K01C30-50E
2-15
2.2.5
Special User
This section explains special HIS group users and ENG group users linked to Windows users in Windows authentication mode.
n OFFUSER
OFFUSER in the Windows authentication mode has the following characteristics. A user account is used for automatically logon by HIS Type Single Sign On in the Windows authentication mode. It is created as a local user regardless of the domain or standalone management. The initial password contains 32 characters and is not disclosed (the password can be changed but the changed password needs to be standardized on all HISs of the CENTUM VP system).
IM 33K01C30-50E