CI/CD Integration Setup
Integrate HAIEC security scanning into your continuous integration pipeline
Automated Security Scanning
Run HAIEC security scans automatically on every pull request or commit
Continuous Security
Catch vulnerabilities before they reach production
Quality Gates
Block merges that fail security thresholds
SARIF Reports
Native integration with GitHub Security tab
GitHub Actions Workflow
Add this workflow file to your repository
1. Create workflow file
Create .github/workflows/haiec-security.yml
name: HAIEC Security Scan
on:
pull_request:
branches: [main, develop]
push:
branches: [main]
jobs:
security-scan:
runs-on: ubuntu-latest
permissions:
contents: read
security-events: write
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Run HAIEC Security Scan
uses: haiec/security-action@v1
with:
api-key: ${{ secrets.HAIEC_API_KEY }}
fail-on-severity: high
- name: Upload SARIF results
uses: github/codeql-action/upload-sarif@v2
if: always()
with:
sarif_file: haiec-results.sarif2. Add API Key Secret
Go to Settings → Secrets → Actions → New repository secret
- Name:
HAIEC_API_KEY - Value: Your API key from HAIEC dashboard
Configuration Options
Customize scan behavior with these options
fail-on-severityFail build on: critical, high, medium, low
exclude-pathsComma-separated paths to exclude from scanning
output-formatOutput format: sarif, json, html
timeoutScan timeout in minutes (default: 30)
Best Practices
Run on Pull Requests
Catch issues before they're merged into main branch
Use Quality Gates
Set appropriate severity thresholds for your project
Cache Dependencies
Speed up scans by caching scanner dependencies
Monitor Trends
Track security metrics over time in the HAIEC dashboard