LUCY

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== FILE BASED ATTACKS (INSIDE OUT) ======

===== Introduction =====

Inside-Out attacks try to initiate network connections from the trusted (corporate) to the untrusted (Internet) network. These attacks require that an “insider” execute code. This is usually because the person that executes the code is unaware of security issues and doesn’t realize that an application can do anything to their system within the limits of the access that is granted to that user. The inside out attack consists of three steps:

  * STEP 1 Getting the backdoor in the network (delivery)
  * STEP 2 Executing the backdoor by the user (execution)
  * STEP 3 Sending the data out (output delivery)

===== LUCY's approach =====

With LUCY's file-based attack you are able to perform the following steps:

  * **STEP 0 Trojan compilation**: Via the Web GUI you will be able to define the settings of the trojan simulation (e.g. what the file should look like & do upon execution). The trojan simulation can be either an executable (which gets compiled during the campaign), some payload which you upload to LUCY yourself or some [[create_a_phishing_campaign_with_a_word_macro|Office file that contains a Macro]].
  *** STEP 1 Delivery**: The trojan simulation can be integrated into a landing page on LUCY so it may be downloaded from the clients or it can be attached in the mail. 
  * **STEP 2 Execution**: By using a phishing mail which can be edited on LUCY you can try to lure the recipient into opening the Trojan simulation. Once the Malware Simulation is executed on a Windows Client, you can see the file in the Task Manager as "file.exe". LUCY has some command restrictions to prevent LUCY administrators from damaging the client's system, therefore not all shell commands are allowed.

 {{ 117.jpg?600 }}

  * **STEP 3 Output Delivery**: The files compiled by LUCY communicate back to your server using HTTP/HTTPS. Therefore LUCY needs to be reachable via those protocols to make the scenarios work. 


**Note:** The files are non-intrusive, run only in the memory and have no effect on the System (no changes are made). In the current edition, the executable runs only on Windows (Windows 7/8/10).


===== File based attack simulation templates =====

List of all **file-based attack templates**, with **Success actions** and **Preferable delivery methods** can be found [[file_based_attack_simulation_templates|here]].




===== File based attack simulation configuration =====

**STEP 1 - Create a New Campaign:** After the login, you can create your first Phishing Campaign by pressing the button “**New Campaign**”. Then choose **Attack Simulation** campaign type. \\
\\
{{ file-1.png?600 }}\\
\\
**STEP 2 - Choose Attack Type:** In order to configure file-based campaign choose **File Attack** type.\\
\\
{{ file-2.png?600 }}\\
\\
**STEP 3 - Select or Create a Client:** Create a client or choose the built-in client (a client can be your own organization or the company that asked you to perform a phishing test). This is important because you can also create [[user_management|view only accounts]] which are associated with those clients.\\
\\
{{ file-3.png?600 }}\\
\\
New clients are created under **Settings -> Clients -> New Client**.\\
\\
{{ file-4.png?600 }}\\
\\
**STEP 4 - Select your Phishing Scenario:** Now you need to select one or multiple phishing scenarios. Since you are going to do a file-based attack you need to pick a scenario either from the "file-based templates" or the "mixed templates"\\
\\
{{ file-5.png?600 }}\\
\\
You are able to preview every template before selecting it. In the **[[links_in_preview_mode|Preview Mode]]** you can test the site using all the features (just enter some random login to get to the next page). \\
\\
{{ file-6.png?600 }}\\
\\
**Note**: **You can allocate multiple scenarios within one campaign** and they can all be started simultaneously! Example: A company might want to split the employees into 2 or 3 groups. One group could get a phishing mail with a landing page that contains many obvious errors and should be easily detectable while the other scenario is almost perfect. This way the client can identify the variables that drive the awareness in one single campaign.\\
\\

**STEP 5:** For this tutorial, as an example, we select the **SRA Cloud Encryption 1.1** template, where the user will be asked to download an encrypted file. To select the template for the campaign click the **Select Language** button and choose the preferred language from the drop-down menu.\\
\\

{{ file-7.png?600 }}\\

\\
**STEP 6 - Configure basic attack settings of Your Campaign** Once you have selected the scenario, you need to configure the **Base Settings** of the campaign. First, give your campaign a name and then choose how your recipients will be able to access LUCY by defining the [[domain_configuration|Domain]]. Finding the appropriate domain name is a very important step for success and it depends very much on your campaign scenario. If you plan to create a fake webmail login you might try to reserve a domain like "webmail-server365.com" and point it to LUCY.\\

{{ file-8.png?600 }}\\
\\


**STEP 7 - Configure Your File:** There are several types of the file available in a file-based campaign:
  * Archive
  * Tunnel Executable
  * Java Applet
  * PDF document

In this particular case, we choose the Archive type of the file with .RAR extension. Instead of sending the attachment as a plain file (e.g. file.exe) or providing it as an executable file to download, you can set the compression option (this is recommended). Like this, the file will be archived.
\\
{{ file-9.png?600 }}\\
\\
**Custom file name**: you can give the archive a custom name (e.g. "encrypteddoc.zip")\\
**Archive Type**: you can choose which compression type you want (the common type which is supported by all windows clients is .zip; other compression types will need additional client software)\\
**Password**: You can set up a password for your archive and insert it into the message to make the simulation more realistic.
**Delivery Method** checkbox: 
\\
{{ file-10.png?600 }}\\
\\
Then add Recipients to the campaign and watch through the **Review** of the campaign. 
\\
{{ file-11.png?600 }}\\
\\ 
The campaign can be started from that point by pushing the **Start** button. Otherwise, push **Go to the Campaign** button in order to set up the campaign further.
\\
\\
All the further configuration is performed through **Base Settings**. 
\\
{{ file-12.png?600 }}\\
\\
**STEP 8 - Edit your Landing Web Page within Your Campaign:** After saving the Base Settings, you can now [[Edit_Landing_Page|Edit the Landing Page]], [[Upload_Your_Web_Page|Upload Your Own Webpage]] or simply [[copy_web_page|copy any website on the internet]]. The Landing Page is the webpage that the users will see when they click on the link in the email they receive. First, select the drop-down menu at the top of the page where you want to edit. Please note that the same landing page may be available in different languages. So make sure you [[dealing_with_multiple_languages_in_your_recipient_group|edit the correct language]]. When you choose a file-based attack scenario you will see some additional configuration options appearing at the bottom of the page. Those settings define what file is provided within the download button for the recipient and what the executable should do upon opening. We recommend starting with a "harmless", non-intrusive trojan simulation that doesn't violate the recipients' data privacy. A harmless simulation is, for example, the ConsolePost" Trojan, which will stealthily execute a few pre-defined commands (like "whoami") in the user's shell and send the output back to LUCY. You have a few additional options:

  * Decide if the user should see [[file_based_gui_options|some fake GUI]] upon execution or not
  * Specify a specific error message that will appear upon execution
  * Specify the Trojan settings (e.g. enable/disable specific Trojan features or define custom commands)

{{ 79.jpg?600 }}


**STEP 9 - Configure Message Settings (Email):**  It’s time to set up email communication (if you want you can also use [[smishing|SMS]] as an alternative). Choose your sender's name, email address, and subject. Please also choose the language for each group. If you configured an English landing page, then select English also within that recipient group. If you have different groups with different languages within your company you can simply create a group and select a language for each recipient. LUCY then will direct each user to an individual landing page that [[dealing_with_multiple_languages_in_your_recipient_group|matches that language]]. Please read the [[Mail_Settings|Mail Settings Chapter]] for more configuration options.

{{ 42.jpg?direct&600 }}

When choosing a file-based scenario LUCY will offer you additionally to send the Trojan simulation via mail. If you already have chosen a landing page where the Trojan simulation can be downloaded it is not necessary to attach it via mail as well. Therefore if you don't want LUCY to send the file via mail choose "NA" within the malware simulation template dropdown menu:

{{ mail_file.png?600 }}


**STEP 10 - Add Recipients to Your Campaign**: You need to create the Recipients List in the Menu item "Recipients". 

{{ 47.jpg?direct&600 }}

This is the list of users that will get the phishing emails. You can add them manually, import a file with all your recipients or even search them on the internet. Once you have created that group, you can select it in your campaign and map it to a specific scenario. You can also define if they should be used only for the Landing Page link, the [[Awareness_E-learning_settings|Awareness site link (e-learning)]], or both.  

{{ 49.jpg?direct&600 }}

Please read the [[Add_Mail_Recipients|Recipients Settings Chapter]] for more configuration options. 

**STEP 11 - Add Scheduling Options to Your Campaign:** If you want, you can create a schedule to run the campaign using a delay or customized time delays between campaign phases. If you are new to the system, we'd recommend that you go with the Default Timing Settings and skip this step. Please read the [[Scheduler|Schedule Settings Chapter]] for more configuration options.

**Step 12 - Add E-learning Content to Your Campaign** There is the option to have LUCY automatically send some e-learning content to all users or only users who have failed the phishing test. This configuration setting is part of an [[Awareness_E-learning_Settings|Separate Chapter (E-learning).]] 

**Step 13 - Start Your Campaign:** Now you are ready to start. Although we recommend performing a test run with a single recipient before you start attacking all users, additionally it is a good idea to use the [[Spam_Check|LUCY SPAM Checker]]. Just click “Real Attack” and LUCY will test your settings before starting the campaign. If you want to skip the checks, press "Skip Checks". Your first recipients should receive the emails within seconds. Please read the [[Start_a_Campaign_Campaign_Checks|Start Campaign Settings Page]] for more configuration options. If you experience any problems with starting/running your campaign, please [[Troubleshooting_Known_Issues|Consult the Troubleshoot Section]] first.

{{ 59.jpg?direct&600 }}


**Step 14 - Monitor Your Campaign**: The progress of the campaign can always be monitored in Real-Time. Click "Statistics" within your campaign.  Please read the [[Monitor_a_Campaign_Statistics|Statistics Chapter]] for more configuration options.

{{ 63.jpg?600 }}

The output from each Trojan execution can be found under "statistics/collected data":

{{ collected_data.png?200 }}


**Step 15 - Create Reports**: Once you have finished the campaign, you may create different types of reports (PDF, HTML or raw export). Please read the [[Create_Campaign_Reports|Creating Reports Chapter]] for more configuration options.

{{ 69.jpg?600 }}



===== Edit File based templates =====

All attachments can be edited within LUCY. The Attachments Settings can be stored as Default templates under Settings/Attachment templates.

{{ 83.jpg?600 }}

{{ 84.jpg?600 }}

You can rename the file templates from file.exe to any filename. In LUCY < 3.2 you can do that by downloading the file.exe, renaming it & then uploading it back to the generic file template.



===== Technical Details about the data delivery =====

Upon execution, this tool will execute the predefined commands or access documents. It will open the built-in Internet Explorer or another default browser (in hidden mode) or access Outlook and send out the collected data to LUCY via HTTP or HTTPS or via SMPT (it will automatically choose HTTPS if you run your campaign via SSL). This tool will also work in environments where the Internet is accessed with Proxy servers - only allowing access for authorized Windows users. The file can then be downloaded as a plain exe or as a zipped archive.

**Note**: The current edition of LUCY will include tools that access files on shares and upload them to the campaign or access the email client via MAPI. These features have restricted configuration options in the community edition (like maximum number of files that can be uploaded, etc.) the same goes for the number of screenshots or length of videos. Only the Commercial Editions have no limitations. You can upload your own custom payload. But keep in mind that reverse channels to LUCY won’t work; only attachments from LUCY are compiled in Real Time with certain settings (IP, Domain Name, URL etc.).


===== Delivery Challenges =====

Executable files usually cannot be delivered to a user via e-mail attachment. These are blocked by most email programs. 

In order to deliver a malware simulation to the user, the attachment should not be provided via email, but via download on a website. There you have the possibility to download the file:

  * Inside an archve (zip, jar, rar etc.)
  * Inside an encrypted file (e.g. zip with a password)
  * [[pdf_attacks|Inside a PDF]]
  * [[create_a_phishing_campaign_with_a_java_dropper_applet|Tunneled through an aplet]]
  * Download as a plain exe

Those settings can be applied within the scenario settings of the specific template. Choose archive (1), Tunnel (2) or PDF (3) for the according method:

{{ sc_et_fil.png?600 }}


===== Q&A =====

**Q: Do the files need to be installed?** \\
A: No, the files are non-intrusive, run only in the memory and have no effect on the System (no changes are made). 

**Q: Do the files need to be run with elevated permissions?** \\
A: No. The files can run with limited, standard windows user rights.

**Q: Our filters block file types like .exe- How can I still use the files?** \\
A: Use a different file format within the scenario settings (e.g. place the exe in an archive like a zip file or place it within a PDF as an attachment).


**Q: Can I run the files on MAC or Linux?** \\
A: No. In the current edition, the executable runs only on Windows (Windows 7/8/10). 


**Q: Windows Defender blocks the files - can this be prevented?** \\
A: Yes, It can be prevented using "whitelisting" inside the Windows Defender Security Center. But it is normal that the defender blocks the code as the defender will block any unknown code which is not officially signed. The files unfortunately cannot be signed, as the hash value is different for each user (the files get compiled on the fly individually for every single user)