BeakrGo to website
Docs/Security/Vulnerability management

Vulnerability management

Beakr runs continuous automated security scanning across every layer of the stack — from application code to dependencies to infrastructure — with defined triage SLAs and annual penetration testing.

Automated scanning

Security scanning is built into the CI/CD pipeline and runs on every code change:

ScannerWhat it checksWhen it runs
Semgrep (SAST)Static application security testing with security-audit rulesets. Fails the build on high-severity findings.Every push and pull request
TruffleHogScans full commit history for leaked credentials, API keys, and secrets.Every pull request
GitHub DependabotMonitors all Python packages and GitHub Actions for known vulnerabilities (CVEs). Automatically opens pull requests to remediate.Weekly
AWS GuardDutyRuntime threat detection including malware protection (EBS volume scanning) and ECS Fargate runtime monitoring.Continuous
AWS WAFOWASP Top 10, SQL injection, Log4j, and known bad input patterns blocked at the edge.Continuous

Vulnerability triage SLAs

When a vulnerability is identified — whether through automated scanning, GitHub security advisories, CVE database monitoring, AWS security bulletins, or penetration testing — it is triaged by severity and remediated on a defined schedule:

SeverityRemediation timeline
Critical24–48 hours
High7 days
Medium30 days
Low90 days

Vulnerability identification

New vulnerabilities are identified through multiple channels:

Penetration testing

Penetration testing is conducted on an annual basis by a qualified third party against the external attack surface of the application. Findings are documented, triaged by severity, and remediated according to the triage SLAs above.

Questions about our vulnerability management?

For details on our most recent penetration test or vulnerability management procedures, contact security@thebeakr.com.