|
| 1 | +--- |
| 2 | +title: Defender for DevOps FAQ |
| 3 | +description: If you're having issues with Defender for DevOps perhaps, you can solve it with these frequently asked questions. |
| 4 | +ms.topic: reference |
| 5 | +ms.date: 01/26/2023 |
| 6 | +--- |
| 7 | + |
| 8 | +# Defender for DevOps frequently asked questions (FAQ) |
| 9 | + |
| 10 | +If you're having issues with Defender for DevOps these frequently asked questions may assist you, |
| 11 | + |
| 12 | +## FAQ |
| 13 | + |
| 14 | +- [I don’t see Recommendations for findings](#i-dont-see-recommendations-for-findings) |
| 15 | +- [Why can't I find my repository](#why-cant-i-find-my-repository) |
| 16 | +- [Secret scan didn't run on my code](#secret-scan-didnt-run-on-my-code) |
| 17 | +- [I don’t see generated SARIF file in the path I chose to drop it](#i-dont-see-generated-sarif-file-in-the-path-i-chose-to-drop-it) |
| 18 | +- [I don’t see the results for my ADO projects in Microsoft Defender for Cloud](#i-dont-see-the-results-for-my-ado-projects-in-microsoft-defender-for-cloud) |
| 19 | +- [What information does Defender for DevOps store about me and my enterprise, and where is the data stored?](#what-information-does-defender-for-devops-store-about-me-and-my-enterprise-and-where-is-the-data-stored) |
| 20 | + |
| 21 | +### I don’t see Recommendations for findings |
| 22 | + |
| 23 | +Ensure that you've onboarded the project with the connector and that your repository (that build is for), is onboarded to Microsoft Defender for Cloud. You can learn how to [onboard your DevOps repository](/azure/defender-for-cloud/quickstart-onboard-devops?branch=main) to Defender for Cloud. |
| 24 | + |
| 25 | +You must have more than a [stakeholder license](https://azure.microsoft.com/pricing/details/devops/azure-devops-services/) to the repos to onboard them. You can confirm if you've onboarded the repositories by seeing them in the inventory list in Microsoft Defender for Cloud. |
| 26 | + |
| 27 | +### Why can't I find my repository |
| 28 | + |
| 29 | +Only TfsGit is supported on Azure DevOps service. |
| 30 | + |
| 31 | +Ensure that you've [onboarded your repositories](/azure/defender-for-cloud/quickstart-onboard-devops?branch=main) to Microsoft Defender for Cloud. If you still can't see your repository, ensure that you're signed in with the correct Azure DevOps organization user account. If the user for the connector is wrong, you need to delete the connector that was created, sign in with the correct user account and re-create the connector. |
| 32 | + |
| 33 | +### Secret scan didn't run on my code |
| 34 | + |
| 35 | +To ensure your code is scanned for secrets, make sure you've [onboarded your repositories](/azure/defender-for-cloud/quickstart-onboard-devops?branch=main) to Defender for Cloud. |
| 36 | + |
| 37 | +In addition to onboarding resources, you must have the [Microsoft Security DevOps (MSDO) Azure DevOps extension](/azure/defender-for-cloud/azure-devops-extension?branch=main) configured for your pipelines. The extension runs secret scan along with other scanners. |
| 38 | + |
| 39 | +If no secrets are identified through scans, the total exposed secret for the resource shows `Healthy` in Microsoft Defender for Cloud. If secret scan isn't enabled (meaning MSDO isn't configured for your pipeline), the resource shows as `N/A` in Defender for Cloud. |
| 40 | + |
| 41 | +### I don’t see generated SARIF file in the path I chose to drop it |
| 42 | + |
| 43 | +If you don’t see SARIF file in the expected path, you may have chosen a different drop path than the `CodeAnalysisLogs/msdo.sarif` one. Currently you should drop your SARIF files to `CodeAnalysisLogs/msdo.sarif`. |
| 44 | + |
| 45 | +### I don’t see the results for my ADO projects in Microsoft Defender for Cloud |
| 46 | + |
| 47 | +Currently, OSS vulnerabilities, IaC scanning vulnerabilities, and Total code scanning vulnerabilities are only available for GitHub repositories. |
| 48 | + |
| 49 | +Azure DevOps repositories only have the total exposed secrets available and will show `N/A` for all other fields. You can learn more about how to [Review your findings](defender-for-devops-introduction.md). |
| 50 | + |
| 51 | +### What information does Defender for DevOps store about me and my enterprise, and where is the data stored? |
| 52 | + |
| 53 | +Data Defender for DevOps connects to your source code management system, for example, Azure DevOps, GitHub, to provide a central console for your DevOps resources and security posture. Defender for DevOps processes and stores the following information: |
| 54 | + |
| 55 | +- Metadata on your connected source code management systems and associated repositories. This data includes user, organizational, and authentication information. |
| 56 | + |
| 57 | +- Scan results for recommendations and assessments results and details. |
| 58 | + |
| 59 | +Data is stored within the region your connector is created in. You should consider which region to create your connector in, for any data residency requirements as you design and create your DevOps connector. |
| 60 | + |
| 61 | +Defender for DevOps currently doesn't process or store your code, build, and audit logs. |
| 62 | + |
| 63 | +## Next steps |
| 64 | + |
| 65 | +- [Overview of Defender for DevOps](defender-for-devops-introduction.md) |
0 commit comments