Skip to content

Commit 880fc08

Browse files
committed
Merge branch '2442-remove-pba-documentation' into develop
PR #2478
2 parents a88f0e4 + df671ac commit 880fc08

File tree

7 files changed

+3
-103
lines changed

7 files changed

+3
-103
lines changed

docs/content/development/adding-exploits.md

+1-3
Original file line numberDiff line numberDiff line change
@@ -14,9 +14,7 @@ An exploit is a sequence of commands that takes advantage of a security vulnerab
1414

1515
### Do I need a new Exploit?
1616

17-
If all you want to do is execute a shell command, configure the required commands in the Monkey Island's post-breach action (PBA) configuration section or [add a new PBA](../adding-post-breach-actions/).
18-
19-
However, if you have your eye on an interesting CVE that you would like the Infection Monkey to support, you must add a new exploit. Keep reading to learn how to add a new exploit.
17+
If you have your eye on an interesting CVE that you would like the Infection Monkey to support, you must add a new exploit. Keep reading to learn how to add a new exploit.
2018

2119

2220
## How to add a new Exploit

docs/content/development/adding-post-breach-actions.md

-75
This file was deleted.

docs/content/reference/data_directory.md

+2-3
Original file line numberDiff line numberDiff line change
@@ -8,9 +8,8 @@ weight: 9
88

99
## What is the data directory?
1010

11-
The data directory is where the Island server stores runtime artifacts.
12-
These include the Island logs, any custom post-breach action files,
13-
configuration files, etc.
11+
The data directory is where the Island server stores runtime artifacts. These
12+
include the Island logs, configuration files, etc.
1413

1514
## Where is it located?
1615

docs/content/reports/security.md

-7
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,6 @@ The report is split into three main categories:
2727
- [The network from the Monkey's eyes](#the-network-from-the-monkeys-eyes)
2828
- [Network infection map](#network-infection-map)
2929
- [Scanned servers](#scanned-servers)
30-
- [Exploits and post-breach actions](#exploits-and-post-breach-actions)
3130
- [Stolen credentials](#stolen-credentials)
3231

3332
## Overview
@@ -86,12 +85,6 @@ This section shows the attack surface the Infection Monkey discovered.
8685

8786
![Scanned servers](/images/usage/reports/sec_report_8_network_services.png "Scanned servers")
8887

89-
### Exploits and post-breach actions
90-
91-
This section shows which exploits and post-beach actions the Infection Monkey performed during the simulation.
92-
93-
![Exploits and PBAs](/images/usage/reports/sec_report_9_exploits_pbas.png "Exploits and PBAs")
94-
9588
### Stolen credentials
9689

9790
This section shows which credentials the Infection Monkey was able to steal from breached machines during this simulation.

docs/content/usage/scenarios/custom-scenario/other.md

-15
Original file line numberDiff line numberDiff line change
@@ -49,18 +49,3 @@ passwords (and a username as well) to the configuration:
4949
![Exploit password and user
5050
lists](/images/usage/scenarios/user-password-lists.png "Exploit password and
5151
user lists")
52-
53-
## Check logged and monitored terminals
54-
55-
To see the Infection Monkey executing in real-time on your servers, add the
56-
**post-breach action** command:
57-
`wall “Infection Monkey was here”`. This post-breach command will broadcast a
58-
message across all open terminals on the servers the Infection Monkey breached
59-
to achieve the following:
60-
- Let you know the Monkey ran successfully on the server.
61-
- Let you follow the breach “live” alongside the infection map.
62-
- Check which terminals are logged and monitored inside your network.
63-
64-
![How to configure post breach
65-
commands](/images/usage/scenarios/pba-example.png "How to configure post breach
66-
commands.")
Binary file not shown.
Binary file not shown.

0 commit comments

Comments
 (0)