You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/container-image-mapping.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -49,7 +49,9 @@ The following is an example of an advanced query that utilizes container image m
49
49
50
50
## Map your container image from GitHub workflows to the container registry
51
51
52
-
1. Add the container image mapping tool to your MSDO workflow:
52
+
1. Ensure you have onboarded a [GitHub connector](quickstart-onboard-github.md) to Defender for Cloud.
53
+
54
+
1. Run the following MSDO workflow:
53
55
54
56
```yml
55
57
name: Build and Map Container Image
@@ -68,7 +70,8 @@ jobs:
68
70
- uses: actions/setup-python@v4
69
71
with:
70
72
python-version: '3.8'
71
-
# Set Authentication to Container Registry of Choice
73
+
# Set Authentication to Container Registry of Choice.
74
+
# The example below is for Azure Container Registry. Amazon Elastic Container Registry and Google Artifact Registry are also supported.
72
75
- name: Azure Container Registry Login
73
76
uses: Azure/docker-login@v1
74
77
with:
@@ -86,8 +89,6 @@ jobs:
86
89
- name: Run Microsoft Security DevOps Analysis
87
90
uses: microsoft/security-devops-action@latest
88
91
id: msdo
89
-
with:
90
-
include-tools: container-mapping
91
92
```
92
93
93
94
After building a container image in a GitHub workflow and pushing it to a registry, see the mapping by using the [Cloud Security Explorer](how-to-manage-cloud-security-explorer.md):
0 commit comments