Skip to content
This repository was archived by the owner on Aug 5, 2024. It is now read-only.
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 16 additions & 14 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,15 +1,16 @@
# Azure Red Team Attack and Detect Workshop

This is a vulnerable-by-design Azure lab containing 2 x attack paths with common misconfigurations. These vulnerabilities are intended to represent those found in live production environments and the attack vectors are intended to be as realistic as possible to real Threat Actors TTPs. If you would like to see what detections and alerts these attack path vectors are causing, I recommend signing up for a Microsoft E5 trial which has Microsoft Defender for Cloud and Azure AD premium P2 plan. Links for signing up to an Azure Developer account can be found in the resources.txt file.
This is a vulnerable-by-design Azure lab containing 2 attack paths with common misconfigurations. These vulnerabilities are intended to represent those found in live production environments, and the attack vectors are intended to be as realistic as possible to real Threat Actors TTPs. If you would like to see what detections and alerts these attack path vectors are causing, we recommend signing up for a Microsoft E5 trial which has Microsoft Defender for Cloud and Azure AD Premium P2 plan. Links for signing up for an Azure Developer account can be found in the resources.txt file.

Author - Roxana Kovaci (@RoxanaKovaci)

## Requirements

- Azure tenant
- Azure CLI
- Terraform version 1.2.2 or above
- Azure User with Global Admin role in the AAD tenant
- add your external IP on lines 248-249 in kc1.tf
- Add your external IP on lines 248-249 in kc1.tf

## Deployment
```
Expand All @@ -33,31 +34,32 @@ terraform plan -out kc2.tfplan
terraform apply kc2.tfplan
```

## Get started
- the entry point for each kill-chain is user1. To get the initial user's credentials, run the following query:
## Getting started
- The entry point for each kill-chain is user1. To get the initial user's credentials, run the following query:

```
terraform output
```

## Kill-Chain objectives and other resources
Kill-Chain #1:

- Objective: Gain access to the Customers PII data.
#### Kill-Chain #1:

- Solutions: The full attack path solutions can be found in kc1/kc1_solution.txt
- Objective: Gain access to the customers' PII data.
- Solutions: The full attack path solutions can be found in kc1/kc1_solution.txt.

Kill-Chain #2:
#### Kill-Chain #2:

- Objective: Gain access to the super secret file.
- Objective: Gain access to the super secret file.
- Solutions: The full attack path solutions can be found in kc2/kc2_solution.txt.

- Solutions: The full attack path solutions can be found in kc2/kc2_solution.txt
Each kill-chain has its Terraform script (and other pre-reqs files needed for deployment) and the solutions to the challenges in its folder.

Each kill-chain has in its folder the Terraform script (and other pre-reqs files needed for deployment) and the solutions to the challenges.

Other resources and useful links to learn more can be found in resources.txt file.
Other resources and useful links to learn more can be found in the `resources.txt` file.

## Clean up
After finishing with each kill-chain scenario, you can remove all resources previously added in your tenant:

After finishing each kill-chain scenario, you can remove all resources previously added in your tenant:
```
az login

Expand Down