AZ-400 Question 268
Select 2Your company hosts its source code in GitHub and utilizes GitHub Advanced Security features (such as code scanning and secret scanning) to identify security vulnerabilities and potential leaks. Leadership wants all identified issues to appear in Microsoft Defender for Cloud for centralized visibility. Which two actions must you take to ensure the GitHub Advanced Security findings are surfaced in Microsoft Defender for Cloud?
- A
Enable Advanced Security scanning (code scanning, secret scanning) in your GitHub repository settings.
- B
Set up the GitHub connector in Microsoft Defender for Cloud and authorize your GitHub organization.
- C
Enable Azure Repos in your Azure DevOps project settings to import repository scanning results.
- D
Configure an Azure Pipeline to manually upload code scanning logs to Microsoft Defender for Cloud.
- E
Enable Microsoft Defender for Servers in your subscription for scanning your GitHub repositories.
Show answer and explanation
Correct answers: A, B
Explanation
To integrate GitHub Advanced Security with Microsoft Defender for Cloud, you need to enable the relevant GitHub Advanced Security features (code scanning, secret scanning) in your repositories and configure the GitHub connector within the Defender for Cloud environment settings. Once the connector is set up and authorized to access your GitHub organization, Microsoft Defender for Cloud automatically imports and surfaces vulnerabilities and other findings from GitHub. For more details, refer to Microsoft� official documentation on connecting GitHub Advanced Security to Defender for Cloud.
- A. Correct.
Correct. You must enable GitHub Advanced Security features (code scanning, secret scanning, etc.) at the repository or organization level to generate findings that can then be sent to Microsoft Defender for Cloud.
- B. Correct.
Correct. Setting up the GitHub connector within Microsoft Defender for Cloud allows it to fetch security alerts directly from GitHub Advanced Security repositories. Without this connector, Defender for Cloud cannot retrieve scanning results.
- C. Incorrect.
Incorrect. Azure Repos is a different service within Azure DevOps. Enabling Azure Repos does not affect GitHub repositories nor does it provide a connection to surfacing GitHub security findings in Microsoft Defender for Cloud.
- D. Incorrect.
Incorrect. You do not need to configure a manual pipeline to upload logs. Once Defender for Cloud is connected to GitHub, findings are automatically imported without additional pipeline tasks.
- E. Incorrect.
Incorrect. While Microsoft Defender for Servers is useful for protecting and assessing servers, it's not a prerequisite for pulling GitHub Advanced Security findings into Microsoft Defender for Cloud. The GitHub connector handles that integration independently.