Tips and Tricks #48: Automate Security Scanning in CI Pipeline

Catch vulnerabilities early by integrating security scanning into your CI workflow.

Code Snippet

# .github/workflows/security.yml
name: Security Scan
on:
  push:
    branches: [main]
  pull_request:
  schedule:
    - cron: '0 0 * * *'  # Daily scan

jobs:
  security:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      
      - name: Run Trivy vulnerability scanner
        uses: aquasecurity/trivy-action@master
        with:
          scan-type: 'fs'
          scan-ref: '.'
          severity: 'CRITICAL,HIGH'
          exit-code: '1'
      
      - name: Run SAST with Semgrep
        uses: returntocorp/semgrep-action@v1
        with:
          config: p/default

Why This Helps

• Catches vulnerabilities before production
• Automated compliance checking
• Shift-left security approach

How to Test

• Introduce known vulnerable dependency
• Verify pipeline fails appropriately

When to Use

Every project. Essential for healthcare, financial services, and regulated industries.

Performance/Security Notes

Start with high/critical only to avoid alert fatigue. Gradually increase coverage.

References

• https://github.com/aquasecurity/trivy
• https://semgrep.dev/

Try this tip in your next project and share your results in the comments!