pushleft
Deploy your first app
Manual contents
Handbook
HandbookPushleftArchitecture
Operate
Install the control planeYour own serversFleetOperations and alertsAuthenticationDomains and DNSUsage and budgetsScheduled jobsAbuse controlsAI provider proxyCustomer mailErrors and performanceLogs and metricsRetentionObject storageContainer registryGit server
Develop
The .pl.yaml manifestOnboard with an AI agentThe pl up demoBuild executorSource ingestionAgent gatewayManaged databasesSecurity findingsTunnels and shellsDev workspacesPrivate hostnamesMesh coordinatorsDesign baseline
Runbooks
Control-plane host failoverControl-plane PostgreSQL failoverControl-plane PostgreSQL restoreCustom domains and certificatesGateway key compromiseIngress host failureNode busyNode disk fullNode drain and replacementNode lostRegistry outageHetzner Robot hostsSecret rotationSecurity incidentStaging fleet on ProxmoxStaging build cacheStuck deploymentVault/OpenBao backup and recovery
Manual · docs/security-findings.md

Security findings

Pushleft scans every build and the live source of each project once a day. This page shows what mail you get and how to mute a finding.

Console New findings by day, with the project and the kind of scan.

Mail

You get one mail for each kind of scan in a project: the first image alert and the first source alert. Owners and admins of the organization get it.

Later scans don’t send mail. Their results go to the scan log.

Scan log

Open Findings in the console. The Scan log shows the new findings of the last 14 days, one line for each scan:

  • the day;
  • the project and the environment;
  • the kind of scan: image or source;
  • the number of secrets and of critical findings.

A set of findings appears once. If a scan finds the same set again, the log doesn’t repeat it.

The Overview page shows a warning after a scan with new findings. Click Dismiss to hide that warning. The next day with new findings shows it again. Dismiss applies to your browser only.

Mute a finding

Add the finding to an ignore file in your repository, then deploy. Give a reason after #.

FindingFileEntry
Vulnerability in an image or a dependency.trivyignoreCVE-2024-45491 # no fix in Debian 12
Secret or code finding, by path.security-scan-ignorefixtures/sample.key # test key
Any finding, by ID.security-scan-ignorevuln:GHSA-vvfq-8hwr-qm4m # not reachable
Secret, as gitleaks reports it.gitleaksignoreThe fingerprint from gitleaks

Each file applies to its own directory and the directories under it. An entry stays until you remove it.

A muted finding stays visible on the Findings page, marked with the file and your reason. It doesn’t count as open and doesn’t alert.

Production deploys

A muted finding can still block a production deploy. A CRITICAL vulnerability with a fixed version blocks the deploy even when .trivyignore lists it.

To deploy anyway, an admin runs pl security waive. A waiver applies to one project for at most 7 days. See Image scan, SBOM and signature.

Rendered from the repository at build time. Edit docs/security-findings.md to change it.