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:49] – lucy | network_design_-_where_to_setup_lucy [2019/10/14 15:45] (current) – lucy | ||
---|---|---|---|
Line 24: | Line 24: | ||
===== On premise installation technical checklist ===== | ===== On premise installation technical checklist ===== | ||
- | * Mail integration: | + | Please |
- | + | ||
- | {{ setup_lan.png? | + | |
- | + | ||
- | + | ||
- | * **DNS integration**. You can quickly setup new domains in LUCY. Details are described | + | |
- | + | ||
- | * **Creating DNS records**. You will need two domain types in LUCY: Attack simulation domains and domains for your awareness training. The **attack simulation domain** could be used for your phishing website in your attack simulation. We recommend reserving first a generic domain like " | + | |
- | You can use the domain from your landing page also for the email sender (like sender@cloud-services625.com). But as the sender email domain is a free text field that can be used with any domain name, it is not required to reserve a domain for just sending emails. There are some rules though when it comes to sending on behalf of other domain names: You can only use domain names that really exist. You can only use domain names that are not SPF protected (unless you white list them on your mail server). You can only use domains that also have an MX record. That means, you cannot use " | + | |
- | + | ||
- | + | ||
- | * **HTTP/ | + | |
- | + | ||
- | * **HTTP/ | + | |
- | + | ||
- | * 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 procedure ===== | + | |
- | + | ||
- | **Hardware** | + | |
- | Please make sure you have the hardware ready with sufficient disk space (>200 GB) and memory (>4 GB). More details here: https:// | + | |
- | + | ||
- | **Download** | + | |
- | If you have decided to do an on premise installation you will first need to download LUCY from our webpage. Please choose one of our installers or images: | + | |
- | + | ||
- | * **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 " | + | |
- | + | ||
- | **Installation** | + | |
- | Once downloaded, please install LUCY according to the download type: | + | |
- | * [[Installing LUCY on LINUX]] | + | |
- | * [[Installing LUCY in Virtualbox]] | + | |
- | * [[Installing LUCY in Vmware]] | + | |
- | * [[Installing LUCY in Amazon]] | + | |
- | * [[installing_lucy_on_windows|Installing LUCY on Windows]] | + | |
- | * [[converting_vmware_to_hyperv|Converting LUCY from VMware ESX to Hyper-V]] | + | |
- | + | ||
- | **Connect to LUCY using an admin domain name** | + | |
- | Connect to your LUCY instance with the root or phishing account. If you connect as root, please execute the command | + | |
- | • python / | + | |
- | If you have a docker based installation, | + | |
- | • docker exec -it lucy /bin/bash | + | |
- | • python / | + | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | **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?600 }} | + | |
- | + | ||
network_design_-_where_to_setup_lucy.txt · Last modified: 2019/10/14 15:45 by lucy