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

title	date	draft	description	weight
Other	2020-08-12T13:07:55+03:00	false	Tips and tricks about configuring Monkeys for your needs.	100

Overview

This page provides additional information about configuring monkeys, tips and tricks and creative usage scenarios.

Custom behaviour

If you want Monkey to run some kind of script or a tool after it breaches a machine, you can configure it in Configuration -> Monkey -> Post breach. Just input commands you want executed in the corresponding fields. You can also upload files and call them through commands you entered in command fields.

Speed and coverage

There are some trivial ways to increase the coverage, for example you can run the Monkey as a privileged user since it’s safe. To improve scanning speed you could specify a subnet instead of scanning all of the local network. The following configuration values have a significant impact on speed/coverage:

• Credentials - the more usernames and passwords you input, the longer it will take the Monkey to scan machines having remote access services. Monkeys try to stay elusive and leave a low impact, thus brute forcing takes longer than with loud conventional tools.
• Network scope - scanning large networks with a lot of propagations can become unwieldy. Instead, try to scan your networks bit by bit with multiple runs.
• Post breach actions - you can disable most of these if you only care about propagation.
• Internal -> TCP scanner - you can trim the list of ports monkey tries to scan increasing performance even further.

Combining different scenarios

Infection Monkey is not limited to the scenarios mentioned in this section, once you get the hang of configuring it, you might come up with your own use case or test all of suggested scenarios at the same time! Whatever you do, Security, ATT&CK and Zero Trust reports will be waiting for you!

Persistent scanning

Use Monkey -> Persistent scanning configuration section to either have periodic scans or to increase reliability of exploitations by running consecutive Infection Monkey scans.

Credentials

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:

Check logged and monitored terminals

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:

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.

• 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.