Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
vre:solution:service_description:securityprivacy [2026/08/05 07:03] hansvre:solution:service_description:securityprivacy [2026/08/26 08:26] (current) marguerite
Line 1: Line 1:
 {{indexmenu_n>1}} {{indexmenu_n>1}}
-[hskb>] 
-aanvullen met fully locally hosted at UG 
-jaartal weghalen achter data protection plan & security baseline   
-[<hskb] 
  
 ====== Security & privacy ====== ====== Security & privacy ======
Line 13: Line 9:
 landscape, and policies, guidelines and regulations are subject to change. Because of this, the landscape, and policies, guidelines and regulations are subject to change. Because of this, the
 PDCA-cycle is executed annually. Reference: ‘Regulation annual information security and PDCA-cycle is executed annually. Reference: ‘Regulation annual information security and
-data protection plan. 20 March 2019’.+data protection plan’.
  
 The following security and privacy measures are in place for the VRE: The following security and privacy measures are in place for the VRE:
-  * Zoning and isolation, backend services & network. The virtual research environment resides in a very trusted zone (UG Baseline Information Security 2021). By default, no direct inbound or outbound traffic will be allowed. No direct internet access;+  * Zoning and isolation, backend services & network. The virtual research environment resides in a very trusted zone, fully locally hosted at UG (UG Baseline Information Security 2021). By default, no direct inbound or outbound traffic will be allowed. No direct internet access;
   * Multifactor authentication;   * Multifactor authentication;
   * Federated identity management: login and password management lie within the user’s own institution;   * Federated identity management: login and password management lie within the user’s own institution;
Line 24: Line 20:
   * Role based access for layered authorization.   * Role based access for layered authorization.
  
-{{ :vre:solution:service_description:roles.png |}}+{{ :vre:solution:service_description:vrelicenses.png?800 |}}