Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit aff5a95

Browse files
committedFeb 2, 2022
images/links to Microsoft Sentinel docs
1 parent 58b2415 commit aff5a95

File tree

7 files changed

+5490
-1785
lines changed

7 files changed

+5490
-1785
lines changed
 

‎articles/machine-learning/how-to-network-security-overview.md

Lines changed: 23 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Secure Azure Machine Learning workspace resources and compute environments using
3232
3333
## Prerequisites
3434

35-
This article assumes that you have familiarity with the following topics:
35+
This article assumes that you have familiarity with the following articles:
3636
+ [Azure Virtual Networks](../virtual-network/virtual-networks-overview.md)
3737
+ [IP networking](../virtual-network/ip-services/public-ip-addresses.md)
3838
+ [Azure Machine Learning workspace with private endpoint](how-to-configure-private-link.md)
@@ -137,8 +137,9 @@ In this section, you learn how Azure Machine Learning securely communicates betw
137137

138138
1. Azure Batch service receives the job from the workspace. It then submits the training job to the compute environment through the public load balancer for the compute resource.
139139

140-
1. The compute resource receives the job and begins training. The compute resource accesses secure storage accounts to download training files and upload output.
140+
1. The compute resource receives the job and begins training. The compute resource uses information stored in key vault to access storage accounts to download training files and upload output.
141141

142+
:::image type="content" source="./media/how-to-network-security-overview/secure-training-job-submission.svg" alt-text="Diagram showing the secure training job submission workflow.":::
142143
### Limitations
143144

144145
- Azure Compute Instance and Azure Compute Clusters must be in the same VNet, region, and subscription as the workspace and its associated resources.
@@ -208,6 +209,26 @@ If you need to use a custom DNS solution for your virtual network, you must add
208209

209210
For more information on the required domain names and IP addresses, see [how to use a workspace with a custom DNS server](how-to-custom-dns.md).
210211

212+
## Microsoft Sentinel
213+
214+
Microsoft Sentinel is a security solution that can integrate with Azure Machine Learning. For example, using Jupyter notebooks provided through Azure Machine Learning. For more information, see [Use Jupyter notebooks to hunt for security threats](/azure/sentinel/notebooks).
215+
216+
### Public access
217+
218+
Microsoft Sentinel can automatically create a workspace for you if you are OK with a public endpoint. In this configuration, the security operations center (SOC) analysts and system administrators connect to notebooks in your workspace through Sentinel.
219+
220+
For information on this process, see [Create an Azure ML workspace from Microsoft Sentinel](/azure/sentinel/notebooks?tabs=public-endpoint#create-an-azure-ml-workspace-from-microsoft-sentinel)
221+
222+
:::image type="content" source="./media/how-to-network-security-overview/common-public-endpoint-deployment.svg" alt-text="Diagram showing Microsoft Sentinel public connection.":::
223+
224+
### Private endpoint
225+
226+
If you want to secure your workspace and associated resources in a VNet, you must create the Azure Machine Learning workspace first. You must also create a virtual machine 'jump box' in the same VNet as your workspace, and enable Azure Bastion connectivity to it. Similar to the public configuration, SOC analysts and administrators can connect using Microsoft Sentinel, but some operations must be performed using Azure Bastion to connect to the VM.
227+
228+
For more information on this configuration, see [Create an Azure ML workspace from Microsoft Sentinel](/azure/sentinel/notebooks?tabs=private-endpoint#create-an-azure-ml-workspace-from-microsoft-sentinel)
229+
230+
:::image type="content" source="./media/how-to-network-security-overview/private-endpoint-deploy-bastion.svg" alt-text="Daigram showing Microsoft Sentinel connection through a VNet.":::
231+
211232
## Next steps
212233

213234
This article is part of a series on securing an Azure Machine Learning workflow. See the other articles in this series:

‎articles/machine-learning/media/how-to-network-security-overview/common-public-endpoint-deployment.svg

Lines changed: 763 additions & 0 deletions
Loading

‎articles/machine-learning/media/how-to-network-security-overview/private-endpoint-deploy-bastion.svg

Lines changed: 956 additions & 0 deletions
Loading

‎articles/machine-learning/media/how-to-network-security-overview/secure-inferencing-environment.svg

Lines changed: 687 additions & 729 deletions
Loading

‎articles/machine-learning/media/how-to-network-security-overview/secure-training-environment.svg

Lines changed: 599 additions & 632 deletions
Loading

‎articles/machine-learning/media/how-to-network-security-overview/secure-training-job-submission.svg

Lines changed: 712 additions & 0 deletions
Loading

‎articles/machine-learning/media/how-to-network-security-overview/secure-workspace-resources.svg

Lines changed: 1750 additions & 422 deletions
Loading

0 commit comments

Comments
 (0)
Please sign in to comment.