Integrating CyberGuard with Your CI/CD Pipeline
Shift security left by integrating CyberGuard directly into your development workflow. Catch vulnerabilities before they reach production.
Why CI/CD Integration?
- Early Detection: Find security issues during development, not after deployment
- Faster Feedback: Developers get immediate security feedback on their code
- Automated Gates: Block insecure code from reaching production
- Continuous Security: Every commit is tested for vulnerabilities
GitHub Actions Integration
name: CyberGuard Security Scan
on: [push, pull_request]
jobs:
security-scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- name: Run CyberGuard Scan
uses: cyberguard/scan-action@v1
with:
api-key: ${{ secrets.CYBERGUARD_API_KEY }}
target: ${{ github.event.repository.url }}
severity-threshold: highGitLab CI Integration
cyberguard-scan:
stage: security
image: cyberguard/scanner:latest
script:
- cyberguard scan --target $CI_PROJECT_URL
only:
- merge_requests
- mainJenkins Integration
pipeline {
agent any
stages {
stage('Security Scan') {
steps {
sh 'cyberguard scan --target ${env.GIT_URL}'
}
}
}
}Best Practices
- Fail Fast: Configure scans to fail builds on critical vulnerabilities
- Incremental Scans: Scan only changed code for faster feedback
- Parallel Execution: Run security scans in parallel with other tests
- Dashboard Integration: Send results to your security dashboard
