Finished adding use-cases section to documentation.

docs/content/usage/scenarios.md

@@ -1,104 +0,0 @@
----
-title: "Scenarios"
-date: 2020-05-26T21:01:19+03:00
-draft: false
-weight: 2
-tags: ["usage"]
-pre: "<i class='fas fa-map-marked-alt'></i> "
----
-
-In this page we show how you can use the Infection Monkey to simulate breach and attack scenarios as well as to share some cool tips and tricks you can use to up your Infection Monkey game. This page is aimed at both novice and experienced Monkey users. You can also refer to [our FAQ](../../faq) for more specific questions and answers.
-
-Here are a few scenarios that can be replicated in your own environment by executing the Monkey from different locations within the network, or with some tweaks to the Monkey’s configuration.
-
-{{% notice note %}}
-No worries! The Monkey does not cause any permanent system modifications that impact security or operations. You will be able to track the Monkey using the log files it leaves in well defined locations. [See our FAQ for more details](../faq).
-{{% /notice %}}
-
-- [Your network has been breached via internet facing servers](#your-network-has-been-breached-via-internet-facing-servers)
-  - [Simulate this scenario using the Monkey](#simulate-this-scenario-using-the-monkey)
-- [You are the newest victim of a phishing fraud! 🎣](#you-are-the-newest-victim-of-a-phishing-fraud)
-  - [Simulate this scenario using the Monkey](#simulate-this-scenario-using-the-monkey-1)
-- [You want to test your network segmentation](#you-want-to-test-your-network-segmentation)
-  - [Simulate this scenario using the Monkey](#simulate-this-scenario-using-the-monkey-2)
-- [You want to verify your security solutions, procedures and teams are working as intended](#you-want-to-verify-your-security-solutions-procedures-and-teams-are-working-as-intended)
-  - [Simulate this scenario using the Monkey](#simulate-this-scenario-using-the-monkey-3)
-- [Other useful tips](#other-useful-tips)
-
-## Your network has been breached via internet facing servers
-
-Whether it was the [Hex-men campaign](https://www.guardicore.com/2017/12/beware-the-hex-men/) that hit your Internet-facing DB server, a [cryptomining operation that attacked your WordPress site](https://www.guardicore.com/2018/06/operation-prowli-traffic-manipulation-cryptocurrency-mining-2/) or any other malicious campaign – the attackers are now trying to go deeper into your network.
-
-### Simulate this scenario using the Monkey
-
-To simulate this breach scenario, execute the Infection Monkey on different machines that host  internet-facing services such as your web servers (Apache, Tomcat, NGINX…) or your VPN servers. To see how to execute the Monkey on these servers, [refer to this FAQ question](../../faq#after-ive-set-up-monkey-island-how-can-i-execute-the-monkey).
-
-{{% notice tip %}}
-If you want to simulate a very “deep” attack into your network, see our [configuration documentation](../configuration).
-{{% /notice %}}
-
-After executing the Monkey, evaluate the results of this simulation using the information in the Report page. There you will find a summary of the most important things the simulation has discovered, a detailed report of all the Monkey’s findings and more. You can also use the Infection Map to analyze the Monkey’s progress through the network, and to see each Monkey’s detailed telemetry and logs.
-
-## You are the newest victim of a phishing fraud! 🎣
-
-Almost everyone is prone to phishing attacks. Results of a successful phishing attempt can be **extremely costly** as demonstrated in our report [IResponse to IEncrypt](https://www.guardicore.com/2019/04/iresponse-to-iencrypt/).
-
-This scenario begins in a section of the network which is a potential phishing spot. Phishing attacks target human users - as such, these types of attacks try to penetrate the network via a service an employee is using, such as an email with an attached malware or social media message with a link redirecting to a malicious website. These are just two examples of where and how an attacker may choose to launch their campaign.
-
-### Simulate this scenario using the Monkey
-
-To simulate the damage from a successful phishing attack using the Infection Monkey, choose machines in your network from potentially problematic group of machines, such as the laptop of one of your heavy email users or one of your strong IT users (think of people who are more likely to correspond with people outside of your organization).
-
-- After setting up the Island add the users’ **real** credentials (usernames and passwords) to the Monkey’s configuration (Don’t worry, this sensitive data is not accessible and is not distributed or used in any way other than being sent to the monkeys, and can be easily eliminated by resetting the Monkey Island’s configuration). Now you can simulate an attacker attempting to probe deeper in the network with credentials “successfully” phished.
-- You can configure these credentials for the Monkey as follows:
-From the **“Basic - Credentials”** tab of the Island’s configuration, under the **“Exploit password list”** press the ‘+’ button and add the passwords you would like the Monkey to use. Do the same with usernames in the **“Exploit user list”**.
-
-![Exploit password and user lists](/images/usage/scenarios/user-password-lists.png "Exploit password and user lists")
-
-After supplying the Monkey with the passwords and usernames, execute the Monkey from the simulated “victim” machines. To do this, click “**2. Run Monkey**” from the left sidebar menu and choose “**Run on machine of your choice**”.
-
-## You want to test your network segmentation
-
-Segmentation is a method of creating secure zones in data centers and cloud deployments that allows companies to isolate workloads from one another and secure them individually, typically using policies. A useful way to test the effectiveness of your segmentation is to ensure that your network segments are properly separated, e,g, your Development is separated from your Production, your applications are separated from one another etc. "to security test is to verify that your network segmentation is configured properly. This way you make sure that even if a certain attacker has breached your defenses, it can’t move laterally from point A to point B.
-
-[Segmentation is key](https://www.guardicore.com/use-cases/micro-segmentation/) to protecting your network, reducing the attack surface and minimizing the damage of a breach. The Monkey can help you test your segmentation settings with its cross-segment traffic testing feature.
-
-### Simulate this scenario using the Monkey
-
-As an example, the following configuration makes sure machines in the “10.0.0.0/24” segment (segment A) and the “11.0.0.2/32” segment (segment B) can’t communicate with each other, along with an additional machine in 13.37.41.50.
-
-![How to configure network segmentation testing](/images/usage/scenarios/segmentation-config.png "How to configure network segmentation testing")
-
-## You want to verify your security solutions, procedures and teams are working as intended
-
-The Infection Monkey can help you verify that your security solutions are working the way you expected them to. These may include your IR and SOC teams, your SIEM, your firewall, your endpoint security solution, and more.
-
-### Simulate this scenario using the Monkey
-
-Run the Monkey with whichever configuration you prefer. The default is good enough for many cases; but for example, you can add some old users and passwords. Running the Monkey on both the Island and on a few other machines in the network is also recommended, as it increases coverage and propagation rates.
-
-After running the Monkey, follow the Monkeys’ actions on the Monkey Island’s infection map.
-
-Now you can match this activity from the Monkey timeline display to your internal SIEM and make sure your security solutions are identifying and correctly alerting on different attacks.
-
-- The red arrows indicate successful exploitations. If you see red arrows, those incidents ought to be reported as exploitation attempts, so check whether you are receiving alerts from your security systems as expected.
-- The orange arrows indicate scanning activity, usually used by attackers to locate potential vulnerabilities. If you see orange arrows, those incidents ought to be reported as scanning attempts (and possibly as segmentation violations).
-- The blue arrows indicate tunneling activity, usually used by attackers to infiltrate “protected” networks from the Internet. Perhaps someone is trying to bypass your firewall to gain access to a protected service in your network? Check if your micro-segmentation / firewall solution identify or report anything.
-
-While running this scenario, be on the lookout for the action that should arise: Did you get a phone call telling you about suspicious activity inside your network? Are events flowing into your security events aggregators? Are you getting emails from your IR teams? Is the endpoint protection software you installed on machines in the network reporting on anything? Are your compliance scanners detecting anything wrong?
-
-## Other useful tips
-
-Here are a few tips which can help you push the Infection Monkey even further:
-
-- Make sure the Monkey is configured to scan its local network but in addition, configure it with specific targets. To add these targets, add their IP addresses (or the IP ranges in which they reside) to the Scan IP/subnet list using the `+` button. Here’s an example of how this is achieved:
-
-![How to configure Scan IP/subnet list](/images/usage/scenarios/scan-list-config.png "How to configure Scan IP/subnet list")
-
-- Every network has its old “skeleton keys” that should have long been discarded. Configure the Monkey with old and stale passwords, but make sure that they were really discarded using the Monkey. To add the old passwords, in the island’s configuration, go to the “Exploit password list” under “Basic - Credentials” and use the “+” button to add the old passwords to the configuration. For example, here we added a few extra passwords (and a username as well) to the configuration:
-
-![Exploit password and user lists](/images/usage/scenarios/user-password-lists.png "Exploit password and user lists")
-
-- To see the Monkey executing in real-time on your servers, add the **post-breach action** command: `wall “Infection Monkey was here”`. This post breach command will broadcast a message across all open terminals on the servers the Monkey breached, to achieve the following: Let you know the Monkey ran successfully on the server. let you follow the breach “live” alongside the infection map, and check which terminals are logged and monitored inside your network. See below:
-
-![How to configure post breach commands](/images/usage/scenarios/pba-example.png "How to configure post breach commands.")

docs/content/usage/use-cases/_index.md

@@ -13,16 +13,12 @@ understand how this tool can be configured.
 You can also refer to [our FAQ](../../faq) for more specific questions and answers.
 
 {{% notice note %}}
-No worries! The Monkey uses safe exploiters and does not cause any permanent system modifications that impact security or operations. [See our FAQ for more details](../faq).
+No worries! The Monkey uses safe exploiters and does not cause any permanent system modifications that impact security or operations.
 {{% /notice %}}
 
-Section contains:
+#### Section contents:
-- [Your network has been breached via internet facing servers](#your-network-has-been-breached-via-internet-facing-servers)
+- [Network breach](./network-breach) - Simulate internal network breach.
-  - [Simulate this scenario using the Monkey](#simulate-this-scenario-using-the-monkey)
+- [Network segmentation](./network-segmentation) - Test network segmentation.
-- [You are the newest victim of a phishing fraud! 🎣](#you-are-the-newest-victim-of-a-phishing-fraud)
+- [Credential leak](./credential-leak) - Assess the impact of successful phishing attack or other form of credential leak. 
-  - [Simulate this scenario using the Monkey](#simulate-this-scenario-using-the-monkey-1)
+- [IDS/IPS Test](./ids-test) - Test your network defence solutions.
-- [You want to test your network segmentation](#you-want-to-test-your-network-segmentation)
+- [Other](./other) - Tips and tricks about configuring monkey for your needs.
-  - [Simulate this scenario using the Monkey](#simulate-this-scenario-using-the-monkey-2)
-- [You want to verify your security solutions, procedures and teams are working as intended](#you-want-to-verify-your-security-solutions-procedures-and-teams-are-working-as-intended)
-  - [Simulate this scenario using the Monkey](#simulate-this-scenario-using-the-monkey-3)
-- [Other useful tips](#other-useful-tips)

docs/content/usage/use-cases/network-breach.md

@@ -26,8 +26,8 @@ safe exploiters are selected.
  and allow Monkey to propagate until maximum **Scan depth**(hop count) is reached or you can fine tune it by providing 
  specific network ranges in **Scan target list**. Scanning local network is more realistic, but providing specific 
  targets will make scanning process substantially faster.
-- **(Optional)Internal -> Network -> TCP scanner** You can add custom ports your organization is using.
+- **(Optional) Internal -> Network -> TCP scanner** You can add custom ports your organization is using.
-- **(Optional)Monkey -> Post Breach Actions** If you only want to test propagation in the network, you can turn off 
+- **(Optional) Monkey -> Post Breach Actions** If you only want to test propagation in the network, you can turn off 
 all post breach actions. These actions simulate attacker's behaviour after getting access to a new system, but in no
  way helps to exploit new machines.
 

docs/content/usage/use-cases/network-segmentation.md

@@ -25,9 +25,9 @@ its cross-segment traffic testing feature.
 - **Network -> Network analysis -> Network segmentation testing** This configuration setting allows you to define
  subnets that should be segregated from each other. If any of provided networks can reach each other, you'll see it 
  in security report.
-- **(Optional)Network -> Scope** You can disable **Local network scan** and leave other options by default if you only want to
+- **(Optional) Network -> Scope** You can disable **Local network scan** and leave other options by default if you only want to
  test for network segmentation without any lateral movement.
-- **(Optional)Monkey -> Post Breach Actions** If you only want to test segmentation in the network, you can turn off 
+- **(Optional) Monkey -> Post Breach Actions** If you only want to test segmentation in the network, you can turn off 
 all post breach actions. These actions simulate attacker's behaviour after getting access to a new system, so they
  might trigger your defence solutions which will interrupt segmentation test.
 

docs/content/usage/use-cases/other.md

@@ -9,8 +9,25 @@ weight: 100
 
 This page provides additional information about configuring monkeys, tips and tricks and creative usage scenarios.
 
+## ATT&CK & Zero Trust scanning
+
+You can use **ATT&CK** configuration section to select which techniques you want to scan. Keep in mind that ATT&CK
+ matrix configuration just changes the overall configuration by modifying related fields, thus you should start by
+ modifying and saving the matrix. After that you can change credentials and scope of the scan, but exploiters,
+ post breach actions and other configuration values will be already chosen based on ATT&CK matrix and shouldn't be
+ modified.
+ 
+There's currently no way to configure monkey using Zero Trust framework, but regardless of configuration options,
+ you'll always be able to see ATT&CK and Zero Trust reports.
+
 ## Tips and tricks
 
+- Use **Monkey -> Persistent scanning** configuration section to either have periodic scans or to increase
+ reliability of exploitations.
+ 
+- To increase propagation run monkey as root/administrator. This will ensure that monkey will gather credentials
+ on current system and use them to move laterally.
+
 - Every network has its old “skeleton keys” that should have long been discarded. Configure the Monkey with old and stale passwords, but make sure that they were really discarded using the Monkey. To add the old passwords, in the island’s configuration, go to the “Exploit password list” under “Basic - Credentials” and use the “+” button to add the old passwords to the configuration. For example, here we added a few extra passwords (and a username as well) to the configuration:
 
 ![Exploit password and user lists](/images/usage/scenarios/user-password-lists.png "Exploit password and user lists")
@@ -19,29 +36,6 @@ This page provides additional information about configuring monkeys, tips and tr
 
 ![How to configure post breach commands](/images/usage/scenarios/pba-example.png "How to configure post breach commands.")
 
+- If you're scanning a large network, consider narrowing the scope and scanning it bit by bit if scan times become too
+ long. Lowering the amount of credentials, exploiters or post breach actions can also help to lower scanning times.
 
-## Assessing results
-
-After running the Monkey, follow the Monkeys’ actions on the Monkey Island’s infection map.
-
-Now you can match this activity from the Monkey timeline display to your internal SIEM and make sure your security
- solutions are identifying and correctly alerting on different attacks.
-
-- The red arrows indicate successful exploitations. If you see red arrows, those incidents ought to be reported as
- exploitation attempts, so check whether you are receiving alerts from your security systems as expected.
-- The orange arrows indicate scanning activity, usually used by attackers to locate potential vulnerabilities.
- If you see orange arrows, those incidents ought to be reported as scanning attempts (and possibly as segmentation violations).
-- The blue arrows indicate tunneling activity, usually used by attackers to infiltrate “protected” networks from
- the Internet. Perhaps someone is trying to bypass your firewall to gain access to a protected service in your network?
- Check if your micro-segmentation / firewall solution identify or report anything.
-
-While running this scenario, be on the lookout for the action that should arise:
- Did you get a phone call telling you about suspicious activity inside your network? Are events flowing
- into your security events aggregators? Are you getting emails from your IR teams?
- Is the endpoint protection software you installed on machines in the network reporting on anything? Are your
- compliance scanners detecting anything wrong?
- 
-Lastly, check Zero Trust and Mitre ATT&CK reports, to see which attacks can be executed on the network and how to
- fix it.
- 
- ![Map](/images/usage/scenarios/map-full-cropped.png "Map")

docs/layouts/shortcodes/homepage_shortcuts.html

@@ -59,21 +59,28 @@
 <section id="homepage-shortcuts">
     <div class="container">
         <div class="row justify-content-center">
-            <div class="col-lg-4 col-sm-6 mb-3">
+            <div class="col-lg-3 col-sm-6 mb-3">
                 <a href="setup/" class="px-4 py-5 bg-white shadow text-center d-block">
                     <i class="fas fa-cogs d-block mb-4" style="font-size: x-large;"></i>
                     <h4 class="mb-3 mt-0">Setup</h4>
                     <p class="mb-0">See how to install the Infection Monkey.</p>
                 </a>
             </div>
-            <div class="col-lg-4 col-sm-6 mb-3">
+            <div class="col-lg-3 col-sm-6 mb-3">
                 <a href="usage/getting-started/" class="px-4 py-5 bg-white shadow text-center d-block">
                     <i class="fas fa-play-circle d-block mb-4" style="font-size: x-large;"></i>
                     <h4 class="mb-3 mt-0">Getting Started</h4>
                     <p class="mb-0">Set the Monkey wild in your datacenter.</p>
                 </a>
             </div>
-            <div class="col-lg-4 col-sm-6 mb-3">
+            <div class="col-lg-3 col-sm-6 mb-3">
+                <a href="usage/use-cases" class="px-4 py-5 bg-white shadow text-center d-block">
+                    <i class="fas fa-map-marked-alt d-block mb-4"  style="font-size: x-large;"></i>
+                    <h4 class="mb-3 mt-0">Use Cases</h4>
+                    <p class="mb-0">Learn about use cases of the Infection Monkey</p>
+                </a>
+            </div>
+            <div class="col-lg-3 col-sm-6 mb-3">
                 <a href="faq/" class="px-4 py-5 bg-white shadow text-center d-block">
                     <i class="fas fa-question d-block mb-4"  style="font-size: x-large;"></i>
                     <h4 class="mb-3 mt-0">FAQs</h4>