Skip to content

Commit

Permalink
Merge pull request #8655 from TristankMS/master
Browse files Browse the repository at this point in the history
Update text and images for Module 1
  • Loading branch information
v-atulyadav authored Jul 28, 2023
2 parents bf03fa1 + ed835fc commit 62034ac
Show file tree
Hide file tree
Showing 11 changed files with 21 additions and 13 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -11,15 +11,20 @@ This module guides you through the deployment of the Microsoft Sentinel Training

To get started with Microsoft Sentinel, you must have a Microsoft Azure subscription. If you do not have a subscription, you can sign up for a free account [here](https://azure.microsoft.com/en/free).

Permissions to create a resource group in your Azure subscription.

- An Azure subscription
- Permissions to create a resource group in your Azure subscription
- Note: Installing Sentinel for the very first time in a Subscription needs Subscription Contributor or Owner permission

Microsoft Sentinel provides a "trial mode" where data ingestion up to 10GB/day is free for the first 31 days when first added to a workspace. Sentinel will prompt that it is in trial mode once installed.

### Exercise 1: The Microsoft Sentinel workspace

In this exercise we will show you how to create a brand new Microsoft Sentinel workspace. If you already have a pre-existing one that you would like to use, you can skip to [Exercise 2](Module-1-Setting-up-the-environment.md#exercise-2-deploy-the-microsoft-sentinel-training-lab-solution).
In this exercise we will show you how to create a brand new Microsoft Sentinel workspace to store your data. If you already have a pre-existing one that you would like to use, you can skip to [Exercise 2](Module-1-Setting-up-the-environment.md#exercise-2-deploy-the-microsoft-sentinel-training-lab-solution).

1. Navigate to the [Azure Portal](http://portal.azure.com) and log in with your account.

2. In the top search bar, type *Microsoft Sentinel* and click on **Microsoft Sentinel**.
2. In the top search bar, type *Sentinel* and click on **Microsoft Sentinel**.

![deployment](../Images/deployment1.png)

Expand All @@ -34,46 +39,49 @@ In this exercise we will show you how to create a brand new Microsoft Sentinel w
- **Subscription**: choose the Azure subscription where you would like to deploy the Microsoft Sentinel workspace
- **Resource Group**: select an existing resource group or create a new resource group (recommended) that will host the lab resources
- **Region**: from the drop down, select the Azure region where the lab will be located
- **Workspace Name**: provide a name for the Microsoft Sentinel workspace. Please note that the workspace name should include 4-63 letters, digits or '-'. The '-' shouldn't be the first or the last symbol
- **Workspace Name**: provide a name for the Microsoft Sentinel workspace. Please note that the workspace name should include 4-63 letters, digits or '-'. The '-' shouldn't be the first or the last symbol.
- Example: `sentinel-training-ws`

![deployment](../Images/deployment3.png)

Click **Review + create** and then **Create** after the validation completes. The creation takes a few seconds.

7. You will be redirected back to the *Add Microsoft Sentinel to a workspace*. Type the name of your new workspace in the search box, select your workspace and click **Add** at the bottom.
6. You will be redirected back to the *Add Microsoft Sentinel to a workspace*. Type the name of your new workspace in the search box, select your workspace and click **Add** at the bottom.

![deployment](../Images/deployment4.png)

7. Your Microsoft Sentinel workspace is now ready to use!
7. The deployment will begin. When it's complete in a minute or two, your Microsoft Sentinel workspace is ready to use!


### Exercise 2: Deploy the Microsoft Sentinel Training Lab Solution

In this exercise you will deploy the Training Lab solution into your existing workspace. This will ingest pre-recorded data (~20 MBs) and create several other artifacts that will be used during the exercises.
In this exercise you will deploy the Training Lab solution into your existing workspace. This will ingest pre-recorded data (~20 MB) and create several other artifacts that will be used during the exercises.

1. In the Azure Portal, go to the top search bar and type *Microsoft Sentinel Training*. Select the **Microsoft Sentinel Training Lab Solution (Preview)** marketplace item on the right.
1. In the Azure Portal, go to the top search bar and type *Microsoft Sentinel Training*. Select the **Microsoft Sentinel Training Lab Solution** marketplace item.

![deployment](../Images/deployment5.png)

2. Read the solution description and click **Create** at the top.

![deployment](../Images/deployment6.png)

3. In the Basics tab, select the Subscription, Resource Group and Workspace that you created in Exercise 1, or the details for your existing workspace. Optionally, review the different tabs (Workbooks, Analytics, Hunting Queries, Watchlists, Playbooks) in the solution. When ready, click on **Review + create**.
3. In the Basics tab, select the Subscription, Resource Group and Workspace that you created in Exercise 1, or provide the details for your existing workspace. Optionally, review the different tabs (Workbooks, Analytics, Hunting Queries, Watchlists, Playbooks) in the solution. When ready, click on **Review + create**.

![deployment](../Images/deployment7.png)


4. Once validation is ok, click on **Create**. The deployment process takes **about 15 minutes**, this is because we want to make sure that all the ingested data is ready for you to use once finished.
1. Once validation is ok, click **Create**. Note that the deployment process takes **about 15 minutes**, in part because we want to make sure all the ingested data is ready for you to use once finished.

2. Once the deployment finishes, you can go back to Microsoft Sentinel and select your workspace. To do this from the Azure Portal, type "Sentinel" and click the Microsoft Sentinel service, then click your workspace from the list.

5. Once the deployment finishes, you can go back to Microsoft Sentinel and select your workspace. In the home page you should see some ingested data and several recent incidents. Don't worry if you don't see 3 incidents like in the screenshot below, they might take a few minutes to be raised.
On the home page you should see some ingested data and several recent incidents. Don't worry if you don't see the incidents initially as in the screenshot below, they might take a few minutes to be raised.

![deployment](../Images/deployment8.png)


### Exercise 3: Configure Microsoft Sentinel Playbook

In this exercise, we will configure a Playbook that will be later used in the lab. This will allow the playbook to access Sentinel.
In this exercise, we will configure a Playbook which will be used later in the lab. We're going to allow our playbook to access Sentinel.

1. Navigate to the resource group where the lab has been deployed.

Expand All @@ -85,7 +93,7 @@ In this exercise, we will configure a Playbook that will be later used in the la

![playbook2](../Images/playbook2.png)

4. Click on **Authorize** and a new window will open to chose an account. Pick the user that you want to authenticate with. This should normally be the same user that you're logged in with.
1. Click on **Authorize** and a new window will open to chose an account. Pick the user that you want to authenticate with. This should normally be the user that you're logged in with.

![playbook3](../Images/playbook3.png)

Expand Down

0 comments on commit 62034ac

Please sign in to comment.