forked from p15670423/monkey
43 lines
2.2 KiB
Markdown
43 lines
2.2 KiB
Markdown
---
|
|
title: "Zero Trust assessment"
|
|
date: 2020-10-22T16:58:09+03:00
|
|
draft: false
|
|
description: "See where you stand in your Zero Trust journey."
|
|
weight: 1
|
|
---
|
|
|
|
## Overview
|
|
|
|
Infection Monkey will help you assess your progress on your journey to achieve Zero Trust network.
|
|
The Infection Monkey will automatically assess your readiness across the different
|
|
[Zero Trust Extended Framework](https://www.forrester.com/report/The+Zero+Trust+eXtended+ZTX+Ecosystem/-/E-RES137210) principles.
|
|
|
|
## Configuration
|
|
|
|
- **Exploits -> Credentials** This configuration value will be used for brute-forcing. We use most popular passwords
|
|
and usernames, but feel free to adjust it according to the default passwords used in your network.
|
|
Keep in mind that long lists means longer scanning times.
|
|
- **Network -> Scope** Disable “Local network scan” and instead provide specific network ranges in the “Scan target list”.
|
|
- **Network -> Network analysis -> Network segmentation testing** This configuration setting allows you to define
|
|
subnets that should be segregated from each other.
|
|
|
|
In general, other configuration value defaults should be good enough, but feel free to see the “Other” section
|
|
for tips and tricks about other features and in-depth configuration parameters you can use.
|
|
|
|
![Exploit password and user lists](/images/usage/scenarios/user-password-lists.png "Exploit password and user lists")
|
|
|
|
## Suggested run mode
|
|
|
|
Run the Monkey on as many machines as you can. This can be easily achieved by selecting the “Manual” run option and
|
|
executing the command shown on different machines in your environment manually or with your deployment tool.
|
|
In addition, you can use any other run options you see fit.
|
|
|
|
## Assessing results
|
|
|
|
See the results in the Zero Trust report section. “The Summary” section will give you an idea about which Zero Trust
|
|
pillars were tested, how many tests were done and test statuses. Specific tests are described in the “Test Results”
|
|
section. The “Findings” section shows details about the Monkey actions. Click on “Events” of different findings to
|
|
observe what exactly Infection Monkey did and when it was done. This should make it easy to cross reference events
|
|
with your security solutions and alerts/logs.
|
|
|