forked from p34709852/monkey
36 lines
1.9 KiB
Markdown
36 lines
1.9 KiB
Markdown
---
|
|
title: "Credentials Leak"
|
|
date: 2020-08-12T13:04:25+03:00
|
|
draft: false
|
|
description: "Assess the impact of a successful phishing attack, insider threat, or other form of credentials leak."
|
|
weight: 5
|
|
---
|
|
|
|
## Overview
|
|
|
|
Numerous attack techniques (from phishing to dumpster diving) might result in a credential leak,
|
|
which can be **extremely costly** as demonstrated in our report [IResponse to IEncrypt](https://www.guardicore.com/2019/04/iresponse-to-iencrypt/).
|
|
|
|
The Infection Monkey can help you assess the impact of stolen credentials by automatically searching
|
|
where bad actors can reuse these credentials in your network.
|
|
|
|
## Configuration
|
|
|
|
- **Exploits -> Credentials** After setting up the Monkey Island, add your users' **real** credentials
|
|
(usernames and passwords) here. Don't worry; this sensitive data is not accessible, distributed or used in any way other than being sent to the Infection Monkey agents. You can easily eliminate it by resetting the configuration of your Monkey Island.
|
|
- **Internal -> Exploits -> SSH keypair list** When enabled, the Infection Monkey automatically gathers SSH keys on the current system.
|
|
For this to work, the Monkey Island or initial agent needs to access SSH key files.
|
|
To make sure SSH keys were gathered successfully, refresh the page and check this configuration value after you run the Infection Monkey
|
|
(content of keys will not be displayed, it will appear as `<Object>`).
|
|
|
|
## Suggested run mode
|
|
|
|
Execute the Infection Monkey on a chosen machine in your network using the “Manual” run option.
|
|
Run the Infection Monkey as a privileged user to make sure it gathers as many credentials from the system as possible.
|
|
|
|
|
|
|
|
## Assessing results
|
|
|
|
To assess the impact of leaked credentials see the Security report. Examine **Security report -> Stolen credentials** to confirm.
|