Differences

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

--- network_design_-_where_to_setup_lucy [2018/01/12 14:36] – lucy
+++ network_design_-_where_to_setup_lucy [2018/05/31 11:10] – [Introduction] lucy
@@ Line 12: / Line 12: @@
 Reasons for installing LUCY on premises are:
-  * **Legal**: Some laws might not allow you to store sensitive data on an external server outside your network or outside your country. Especially with the new data protection law in Europe (GDPR) you need to make sure any personalized or sensitive data is secured.
+  * **Legal**: Some laws might not allow you to store sensitive data on an external server outside your network or outside your country. Especially with the new data protection law in Europe ([[privacy_data_protection_and_gdpr|GDPR]]) you need to make sure any personalized or sensitive data is secured.
   * **Integration with certain features**: LUCY comes with different API's such as the[[ldap_integration| LDAP API]], the [[api|REST API]] etc. which are common for backend applications that are usually not exposed to the internet.
   * **Security**: LUCY might store sensitive data like windows login, user names, emails etc. within the database. Integrating the LUCY server in the internal protection layers (IDS, FW etc.) will minimize the risks of successful attacks.
@@ Line 50: / Line 50: @@
 If you setup LUCY in a DMZ, you could as well consider using a LUCY instance only as a reverse proxy in the secured zone, and install the main application within the intranet as a "master instance". This configuration is described [[setting_up_a_lucy_master_slave|here]]. Other than that, the challenges in a DMZ installation are the same as the ones described in the intranet installation above.
+===== LUCY Vmware technical components =====
+When you download and boot the VMware Image, all software components are integrated in that image. There is no need to install any additional software. All components (DB, mail server, web server etc,) are bundles within the VMware images and controlled by the internal LUCY software, which runs transparently in the background. The updating of those components is also done within the LUCY software through internal processes, which are not visible to the end user.
+{{ vmwared1.png?600 }}