You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 23, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: doc/servermd/Server.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -447,7 +447,7 @@ Customers must be familiar with industry standards and best practices for deploy
447
447
448
448
The following instructions are provided only as recommendations regarding security best practices and by no means are they fully complete:
449
449
450
-
1. For the key pair access on OWT server, make sure only people with high enough privilege can have the clearance.
450
+
1. For the key pair access on OWT server, make sure only people/process with high enough privilege can have the clearance. For service key, authentication service is recommended to integrate with OWT server and access it. For cipher key, hardware security storage is recommended.
451
451
2. Regular system state audits or system change auto-detection. For example, OWT server system changes notification mechanism by third-party tool.
452
452
3. Establish policy of file based operation history for the tracking purpose.
453
453
4. Establish policy disallowing saving credentials for remote system access on OWT server.
0 commit comments