80 lines
3.4 KiB
YAML
80 lines
3.4 KiB
YAML
name: "DevSecOps Enterprise Pipeline"
|
|
on:
|
|
push:
|
|
branches: [ main ] # Apenas deploys via branch protegida
|
|
|
|
jobs:
|
|
security-gate:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Checkout Code
|
|
uses: actions/checkout@v3
|
|
with:
|
|
fetch-depth: 0 # Necessário para o Gitleaks analisar histórico
|
|
|
|
# 1. SECRET SCANNING (Deteta chaves expostas no histórico e no código)
|
|
- name: Gitleaks Scan
|
|
run: |
|
|
curl -sL https://github.com/gitleaks/gitleaks/releases/download/v8.18.2/gitleaks_8.18.2_linux_x64.tar.gz | tar -xz -C /tmp
|
|
/tmp/gitleaks detect --source . --verbose --redact --exit-code 0
|
|
|
|
# 2. SCA (Software Composition Analysis) - Verifica vulnerabilidades no Nginx
|
|
- name: Scan Docker Image Vulnerabilities (Trivy)
|
|
run: |
|
|
# Verifica se a imagem base que estás a usar tem CVEs (vulnerabilidades) conhecidas
|
|
curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sh -s -- -b /usr/local/bin
|
|
trivy image --severity HIGH,CRITICAL nginx:alpine
|
|
|
|
# 3. LINTING & QUALIDADE
|
|
- name: HTML/CSS Linter
|
|
run: |
|
|
sudo npm install -g htmlhint stylelint stylelint-config-standard
|
|
htmlhint index.html
|
|
# Adiciona validação de CSS se tiveres ficheiros .css
|
|
|
|
# 4. SAST (Static Application Security Testing) - Análise de Código com SonarQube
|
|
- name: SonarQube Analysis
|
|
run: |
|
|
curl -sL https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-5.0.1.3006-linux.zip -o sonar-scanner.zip
|
|
unzip -q sonar-scanner.zip
|
|
./sonar-scanner-5.0.1.3006-linux/bin/sonar-scanner \
|
|
-Dsonar.projectKey=website-test \
|
|
-Dsonar.sources=. \
|
|
-Dsonar.host.url=http://51.89.40.2:9000 \
|
|
-Dsonar.token=${{ secrets.SONAR_TOKEN }}
|
|
|
|
deploy:
|
|
needs: security-gate
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Checkout Code
|
|
uses: actions/checkout@v3
|
|
|
|
# 5. DEPLOY ATÓMICO E HARDENING
|
|
- name: Hardened Deploy
|
|
run: |
|
|
# Criar um backup rápido caso o deploy falhe
|
|
docker exec website-test-backend tar -czf /tmp/index_backup.tar.gz -C /usr/share/nginx/html index.html || true
|
|
|
|
# Limpeza de ambiente e remoção de ferramentas desnecessárias no container
|
|
# (Removemos shells ou gestores de pacotes se existirem para dificultar invasores)
|
|
docker exec website-test-backend sh -c "rm -rf /usr/share/nginx/html/*"
|
|
|
|
# Copia o ficheiro com verificação de integridade (Checksum)
|
|
docker cp index.html website-test-backend:/usr/share/nginx/html/index.html
|
|
|
|
# POLÍTICA DE PRIVILÉGIO MÍNIMO:
|
|
# Definimos o dono como root e a permissão 444 (apenas leitura para o processo nginx)
|
|
docker exec website-test-backend chown root:root /usr/share/nginx/html/index.html
|
|
docker exec website-test-backend chmod 444 /usr/share/nginx/html/index.html
|
|
|
|
# Verifica se o site está a responder (Healthcheck pós-deploy)
|
|
# Se der erro aqui, o pipeline marca falha
|
|
curl --silent --show-error --fail http://localhost:80 || exit 1
|
|
|
|
# 6. AUDITORIA DE DEPLOY
|
|
- name: Slack/Discord Notification (Opcional)
|
|
if: always()
|
|
run: |
|
|
echo "Deploy finalizado com status: ${{ job.status }}"
|