What it does
SecureOps brings Gitleaks, Trivy, and OSV-Scanner into a GitHub Actions workflow. It scans for exposed secrets, vulnerable dependencies, and infrastructure configuration issues. Read findings in pull request comments or export JSON, HTML, and SARIF reports.
What’s included
Secret Detection
Catch exposed API keys, passwords, and tokens before they reach production.
- Powered by Gitleaks v8.28.0
- Custom rule definitions via TOML configuration
- Token masking in reports (first/last 4 chars)
- Supports pre-commit and CI/CD scanning
Vulnerability Scanning
Find CVEs and security issues in dependencies and infrastructure code.
- Trivy v0.65.0 for CVE and misconfiguration detection
- OSV-Scanner v2.2.1 for open source vulnerability identification
- Scans application dependencies, container images, and IaC
- Fail-on-critical build policies
Reports in your workflow
Read findings in pull requests and the GitHub Security tab, or export reports for other tools.
- JSON, HTML, and SARIF output formats
- Automated PR comments with severity breakdown
- GitHub Security tab integration via SARIF upload
- Multi-factor risk scoring and assessment
Getting it running
Add the GitHub Action
Add SecureOps to your workflow YAML with a single step. Configure scan type, fail thresholds, and reporting options.
Scan on Every Push
SecureOps runs automatically on pushes and pull requests, scanning for secrets, vulnerabilities, and misconfigurations.
Review Findings
Findings appear as PR comments with severity levels and remediation guidance. Critical issues can block merges.
Org-Wide Audits
Run scheduled scans across your entire GitHub organization with consolidated dashboards and Slack summaries.
What it helps with
Check changes early
Run checks on pushes and pull requests. Configure required status checks to block merges when findings exceed your thresholds.
Start with the defaults
Add the action to your workflow, then adjust the scan types and failure thresholds to suit your repository.
Supply Chain Security
Tool downloads use SHA256 checksum verification. The scanner container runs as a non-root user.
Keep findings close to the code
Pull request comments include severity, context, and guidance so reviewers can investigate without leaving the workflow.
Built with
A few things you might be wondering
How do I add SecureOps to my repository?
What types of security issues does SecureOps detect?
Can SecureOps scan my entire GitHub organization?
Is SecureOps free for private repositories?
What report formats are supported?
Other CloudOn Tools
KubeLaunch
KubeLaunch brings together Terraform and Terragrunt configurations for AWS EKS, application delivery, security, and monitoring. It includes Argo CD, Kyverno, Falco, Istio, and Kubecost, with component settings you can adapt to your workloads.
Multi-Cloud Runway
Multi-Cloud Runway provides Terraform and Terragrunt templates for cloud accounts, projects, networking, access, and security monitoring. Use the AWS or Google Cloud modules independently and adapt the structure to how your organization works.
FinOps Guardian
FinOps Guardian checks AWS and Google Cloud for idle resources and opportunities to reduce costs. Terraform modules deploy scheduled functions that send findings to Slack or email. Review the reports and use dry-run mode before enabling AWS resource cleanup.