Reports for Every Cloud

Purpose-built reports that answer the questions cloud and security teams actually ask — across AWS, Azure, and Google Cloud.

58
Curated Reports
1705+
Controls Checked
3
Cloud Providers
5 min
To First Results
ASecureCloud report preview
Azure logo

DevOps Security

8 controls
3 services covered

Reviews Azure DevOps security signals for repository protection, advanced security, secret scanning, fork-build secrets, classic pipelines, secure file and variable-group access, self-review policy, and two-reviewer approval.

What we check

Repositories and Code3
  • Azure DevOps Repositories Should Have GitHub Advanced Security Enabled
  • Azure DevOps Repositories Should Have Secrets Scanning Findings Resolved
  • Azure Pipelines Should Not Have Secrets Available to Builds of Forks
Pipelines3
  • Azure DevOps Projects Should Have Creation of Classic Pipelines Disabled
  • Azure DevOps Secure Files Should Not Grant Access to All Pipelines
  • Azure DevOps Variable Groups With Secret Variables Should Not Grant Access to All Pipelines
Review Controls2
  • Azure DevOps Repositories Should Not Allow Requestors to Approve Their Own Pull Requests
  • Azure DevOps Repositories Should Require Minimum Two-Reviewer Approval for Code Pushes

Run these reports on your own cloud

Connect an account and get your first set of reports in minutes — free to start, no credit card required.