network_design_-_where_to_setup_lucy
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
network_design_-_where_to_setup_lucy [2019/05/22 09:31] – lucy | network_design_-_where_to_setup_lucy [2019/10/14 15:45] (current) – lucy | ||
---|---|---|---|
Line 20: | Line 20: | ||
You can place LUCY in the intranet or within a secured zone (DMZ). If you want to allow external users (e.g. mobile users with smartphones) to access LUCY's websites (attack simulations or e-learning), | You can place LUCY in the intranet or within a secured zone (DMZ). If you want to allow external users (e.g. mobile users with smartphones) to access LUCY's websites (attack simulations or e-learning), | ||
- | |||
- | |||
- | ===== Challenges in an on-premise installation ===== | ||
- | |||
- | * Mail integration: | ||
- | |||
- | |||
- | |||
- | If you use the build-in mail server, LUCY would need to be able to resolve the MX record for your own organisation and then deliver the mails to that server. Depending where LUCY is installed, you probably need to open SMTP communication ports. An easier method is using the internal mail server as a relay. In such a case LUCY would communicate with the internal mail server (A). You also need to allow relaying for the LUCY IP address on your internal mail server. | ||
- | |||
- | {{ setup_lan.png? | ||
- | |||
- | |||
- | |||
- | * DNS integration: | ||
- | |||
- | * HTTP/HTTPS access: The landing pages and the E-learning needs to be accessible via http or https (see [[ssl_configuration|this chapter]] for SSL configuration). If users from the internet have to access those pages, you need to make sure that you have set up an according port forwarding rule on your firewall together with a NAT entry, that points to LUCY. | ||
- | |||
- | * Security products and whitelisting: | ||
- | |||
- | * Securing the access: Once you finished the setup, you might want to prevent users from accessing the web based administration. In [[security_considerations|this chapter]] we discuss a few tips on how to secure LUCY. | ||
- | |||
- | |||
===== On premise installation technical checklist ===== | ===== On premise installation technical checklist ===== | ||
- | **Download: | + | Please consult [[installation_checklist|this chapter]]. |
- | If you have decided to do an on premise installation you will first need to download LUCY from our webpage. | + | |
- | + | ||
- | * **Virtual Box**: http:// | + | |
- | * **Linux Installer**: | + | |
- | * **ESX/ | + | |
- | * **Vmware Image**: http:// | + | |
- | * **Amazon**: http:// | + | |
- | + | ||
- | If you require a different format (e.g. ovf), search for the according converter (e.g. search for " | + | |
- | + | ||
- | **License: | + | |
- | For testing purposes please send us the workstation ID (http:// | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | ===== 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? | + | |
- | + | ||
network_design_-_where_to_setup_lucy.1558510261.txt.gz · Last modified: 2019/07/25 12:52 (external edit)