microsoft / microsoft/security-devops-action
Validate Azure DevOps pipeline steps (integration of other SAST/SCA tooling)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 164
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
Could I also use this to check for the existence of certain steps in an Azure DevOps YAML pipeline? Does it have this capability? For example, if there is a step that uses SonarQube or Nexus IQ - ie. can MSDO scan the following Azure DevOps YAML file and look for the existence of the steps involving SonarQube (example YAML below):
trigger:
- master # or the name of the main branch
- feature/*
steps:
- task: SonarQubePrepare@5
inputs:
SonarQube: 'YourSonarqubeServerEndpoint'
scannerMode: 'Other'
extraProperties: 'sonar.projectKey=YourProjectKey'
- task: SonarQubePublish@5
inputs:
pollingTimeoutSec: '300'
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The payload names no repository files or tests. Start by reading the Azure DevOps YAML example and checking the project's documented pipeline entry points for whether MSDO scans pipeline definitions; done would be a clear supported or unsupported answer for detecting SonarQube or Nexus IQ steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- yaml
- Domain
- ci-cd, devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100