We release patches for security vulnerabilities. Which versions are eligible for receiving such patches depends on the CVSS v3.0 Rating:
Version | Supported |
---|---|
latest | ✅ |
< latest | ❌ |
Please report security vulnerabilities to the maintainers via GitHub Security Advisories.
Our Docker images include the following security features:
- Non-root User: Containers run as a non-root user (UID 1000) by default
- Minimal Base Image: Using Python slim-bookworm base image (~40MB)
- Read-only Filesystem: Containers run with read-only root filesystem
- No New Privileges: Containers cannot gain new privileges
- Health Checks: Built-in health check endpoints
- Signed Images: All container images are signed using cosign
- SBOM Generation: Software Bill of Materials (SBOM) generated for every build
- Attestations: Build provenance attestations are generated and published
- Vulnerability Scanning: Automated scanning with Trivy for CRITICAL and HIGH vulnerabilities
- Dependency Updates: Automated dependency updates via Dependabot
You can verify the authenticity of our container images:
# Verify container signature
cosign verify ghcr.io/rknightion/meraki-dashboard-exporter:latest \
--certificate-identity-regexp "https://github.com/rknightion/meraki-dashboard-exporter/.github/workflows/docker-build.yml@refs/heads/main" \
--certificate-oidc-issuer "https://token.actions.githubusercontent.com"
# Download and inspect SBOM
cosign download sbom ghcr.io/rknightion/meraki-dashboard-exporter:latest
# Verify attestations
cosign verify-attestation ghcr.io/rknightion/meraki-dashboard-exporter:latest \
--type slsaprovenance \
--certificate-identity-regexp "https://github.com/rknightion/meraki-dashboard-exporter/.github/workflows/docker-build.yml@refs/heads/main" \
--certificate-oidc-issuer "https://token.actions.githubusercontent.com"
When deploying this exporter:
- API Key Security: Never commit API keys to version control. Use environment variables or secrets management.
- Network Security: Run the exporter in a private network, expose only to authorized Prometheus instances.
- Resource Limits: Apply appropriate CPU and memory limits to prevent resource exhaustion.
- Regular Updates: Keep the exporter updated to receive security patches.