forked from p15670423/monkey
Merge pull request #1378 from guardicore/docs-use-cases
Documentation: Scenarios
This commit is contained in:
commit
101c0a3870
|
@ -0,0 +1,29 @@
|
|||
+++
|
||||
title = "Scenarios"
|
||||
date = 2020-08-12T12:52:59+03:00
|
||||
weight = 3
|
||||
chapter = true
|
||||
pre = "<i class='fas fa-map-marked-alt'></i> "
|
||||
+++
|
||||
|
||||
# Scenarios
|
||||
|
||||
This section describes the different attack scenarios that the Infection Monkey can simulate.
|
||||
|
||||
{{% notice note %}}
|
||||
Don't worry! The Infection Monkey uses safe exploiters and does not cause any permanent system modifications that could impact security or operations.
|
||||
{{% /notice %}}
|
||||
|
||||
The Infection Monkey has pre-built scenarios to simulate common types of attacks that take place. These scenarios, when selected, manipulate the configuration to only show you what you need to see for that scenario. This makes it possible for you to quickly run the Monkey on your network in order to accomplish a specific objective.
|
||||
|
||||
Choosing the "Custom" scenario will allow you to fine-tune your simulation and access all available features. [Read more about configuring a custom simulation.](/custom-scenario/_index.md)
|
||||
|
||||
![Choose scenario](/images/usage/scenarios/choose-scenario.png "Choose a scenario")
|
||||
|
||||
To exit a scenario and select another one, click on "Start Over".
|
||||
|
||||
![Start over](/images/usage/scenarios/start-over.png "Start over")
|
||||
|
||||
## Section contents
|
||||
|
||||
{{% children description=True style="p"%}}
|
|
@ -0,0 +1,18 @@
|
|||
---
|
||||
title: " Custom"
|
||||
date: 2021-07-28T14:36:02+05:30
|
||||
description: "Configure a custom scenario to test your network's defenses."
|
||||
weight: 100
|
||||
pre: "<i class='fas fa-edit'></i>"
|
||||
chapter: true
|
||||
---
|
||||
|
||||
# Custom
|
||||
|
||||
The Infection Monkey is a versatile breach and attack simulation tool. Choosing the "Custom" scenario will allow you to access all of its capabilities and configure the simulation exactly according to your needs. You can enhance, optimize, and fine-tune the Monkey's behavior.
|
||||
|
||||
![Custom scenario](/images/usage/scenarios/custom-scenario.png "Custom scenario")
|
||||
|
||||
Below are some examples with instructions on how to configure them.
|
||||
|
||||
{{% children description=True style="p"%}}
|
|
@ -1,33 +1,15 @@
|
|||
---
|
||||
title: "Ransomware Simulation"
|
||||
title: " Ransomware Simulation"
|
||||
date: 2021-06-23T18:13:59+05:30
|
||||
draft: true
|
||||
weight: 10
|
||||
description: "Simulate a ransomware attack on your network and assess the potential damage."
|
||||
weight: 1
|
||||
pre: "<i class='fa fa-lock'></i>"
|
||||
---
|
||||
|
||||
The Infection Monkey is capable of simulating a ransomware attack on your
|
||||
network using a set of configurable behaviors.
|
||||
|
||||
## Leaving a README.txt file
|
||||
|
||||
Many ransomware packages leave a README.txt file on the victim machine with an
|
||||
explanation of what has occurred and instructions for paying the attacker.
|
||||
The Infection Monkey can also leave a README.txt file in the target directory on
|
||||
the victim machine in order to replicate this behavior. This can be enabled or
|
||||
disabled by checking the box on the configuration screen. Note that if no
|
||||
target directory is specified for encryption, the Infection Monkey will not
|
||||
leave a README.txt file.
|
||||
|
||||
<!-- add screenshot highlighting readme option -->
|
||||
|
||||
The README.txt file informs the user that a ransomware simulation has taken
|
||||
place and that they should contact their administrator. The contents of the
|
||||
file can be found
|
||||
[here](https://github.com/guardicore/monkey/tree/develop/monkey/infection_monkey/ransomware/ransomware_readme.txt).
|
||||
|
||||
|
||||
<!-- add config screenshot here -->
|
||||
|
||||
|
||||
## Encryption
|
||||
|
||||
|
@ -55,7 +37,7 @@ To ensure minimum interference and easy recoverability, the ransomware
|
|||
simulation will only encrypt files contained in a user-specified directory. If
|
||||
no directory is specified, no files will be encrypted.
|
||||
|
||||
<!-- add screenshot highlighting encryption options -->
|
||||
![Ransomware configuration](/images/usage/scenarios/ransomware-config.png "Ransomware configuration")
|
||||
|
||||
### How are the files encrypted?
|
||||
|
||||
|
@ -164,3 +146,16 @@ BitDefender](https://labs.bitdefender.com/2017/07/a-technical-look-into-the-gold
|
|||
- .xlsx
|
||||
- .xvd
|
||||
- .zip
|
||||
|
||||
|
||||
## Leaving a README.txt file
|
||||
|
||||
Many ransomware packages leave a README.txt file on the victim machine with an
|
||||
explanation of what has occurred and instructions for paying the attacker.
|
||||
The Infection Monkey will also leave a README.txt file in the target directory on
|
||||
the victim machine in order to replicate this behavior.
|
||||
|
||||
The README.txt file informs the user that a ransomware simulation has taken
|
||||
place and that they should contact their administrator. The contents of the
|
||||
file can be found
|
||||
[here](https://github.com/guardicore/monkey/tree/develop/monkey/infection_monkey/ransomware/ransomware_readme.txt).
|
|
@ -1,20 +0,0 @@
|
|||
+++
|
||||
title = "Use Cases"
|
||||
date = 2020-08-12T12:52:59+03:00
|
||||
weight = 3
|
||||
chapter = true
|
||||
pre = "<i class='fas fa-map-marked-alt'></i> "
|
||||
+++
|
||||
|
||||
# Use cases
|
||||
|
||||
This section describes possible use cases for the Infection Monkey and how you can configure the tool.
|
||||
You can also refer to [our FAQ](../../faq) for more specific questions and answers.
|
||||
|
||||
{{% notice note %}}
|
||||
Don't worry! The Infection Monkey uses safe exploiters and does not cause any permanent system modifications that could impact security or operations.
|
||||
{{% /notice %}}
|
||||
|
||||
## Section contents
|
||||
|
||||
{{% children description=True style="p"%}}
|
Binary file not shown.
After Width: | Height: | Size: 310 KiB |
Binary file not shown.
After Width: | Height: | Size: 296 KiB |
Binary file not shown.
After Width: | Height: | Size: 136 KiB |
Binary file not shown.
After Width: | Height: | Size: 104 KiB |
|
@ -91,12 +91,11 @@ function MonkeyInfo() {
|
|||
}
|
||||
|
||||
function ScenarioInfo() {
|
||||
// TODO change link when scenarios are added to documentation
|
||||
return (
|
||||
<>
|
||||
<div className={'scenario-info'}>
|
||||
Check the Infection Monkey documentation hub for more information
|
||||
on <a href='https://www.guardicore.com/infectionmonkey/docs' rel="noopener noreferrer" target="_blank">
|
||||
on <a href='https://www.guardicore.com/infectionmonkey/docs/usage/scenarios/' rel="noopener noreferrer" target="_blank">
|
||||
scenarios
|
||||
</a>.
|
||||
</div>
|
||||
|
|
Loading…
Reference in New Issue