Integrate AquilaX security scanning into your Azure DevOps CI/CD pipelines to automatically detect vulnerabilities, security issues, and compliance violations in your codebase.
Table of Contents
Prerequisites
Setup Instructions
Pipeline Configuration
Viewing Scan Results
Troubleshooting
Advanced Configuration
Prerequisites
Azure DevOps organization and project with pipeline permissions
AquilaX account with API access
Required AquilaX credentials:
API Token
Organization ID
Group ID
Setup Instructions
Step 1: Obtain AquilaX Credentials
Log in to your AquilaX dashboard
Navigate to Settings → API Tokens
Copy your API Token, Organization ID, and Group ID
Step 2: Configure Azure DevOps Variables
In Azure DevOps, go to Pipelines → Select your pipeline → Edit → Variables
Add the following secret variable:
Name: AQUILAX_API_TOKEN
Value: Your API token
✅ Enable Keep this value secret
Step 3: Create Pipeline File
Create azure-pipelines.yml in your repository root with the configuration below.
Pipeline Configuration
Basic Pipeline Template
Configuration Parameters
Variable
Type
Description
AQUILAX_API_TOKEN
Secret
API authentication token (stored as secret variable)
AQUILAX_ORG_ID
Variable
Organization identifier
AQUILAX_GROUP_ID
Variable
Group/project identifier
AQUILAX_GIT_URL
Auto
Repository URL (auto-populated)
AQUILAX_BRANCH
Auto
Branch name (auto-populated)
Key Settings
Triggers
trigger: - main - Runs on commits to main branch
pr: - "*" - Runs on all pull requests
Pipeline Behavior
timeoutInMinutes: 10 - Scan timeout (adjust based on repository size)
continueOnError: true - Pipeline continues even if issues are found (set to false to enforce security gates)
# Add before PublishBuildArtifacts step to debug
- script: |
echo "Checking for SARIF file..."
ls -la *.sarif || echo "No SARIF files found"
displayName: "Debug: List SARIF files"
trigger:
branches:
include:
- main
- develop
- release/*