Skip to content

Soften Security Center "continuous" scanning language #4297

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AmberAlston merged 1 commit into from
Jul 23, 2026
Merged

Soften Security Center "continuous" scanning language #4297

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/vendor/security-center-about.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ You can explicitly include or exclude images from being scanned by the Security

### How cve scanning works

The Security Center is powered by Replicated's [SecureBuild](https://securebuild.com/) technology. With SecureBuild, every image is scanned continuously (not just at release time) using the open source vulnerability scanner [Grype](https://github.com/anchore/grype). This means that, as new CVEs are disclosed, they automatically appear in your Security Center without requiring a new release.
The Security Center is powered by Replicated's [SecureBuild](https://securebuild.com/) technology. With SecureBuild, images are scanned on a recurring schedule using the open source vulnerability scanner [Grype](https://github.com/anchore/grype), not only at release time. Newly promoted images are scanned as soon as they are identified, and previously scanned images are rescanned periodically, with more recently promoted images scanned more frequently than older ones. This means that, as new CVEs are disclosed, they surface in your Security Center over time without requiring a new release.
Comment thread
AmberAlston marked this conversation as resolved.
Comment thread
AmberAlston marked this conversation as resolved.
Comment thread
AmberAlston marked this conversation as resolved.
Comment thread
AmberAlston marked this conversation as resolved.
Comment thread
AmberAlston marked this conversation as resolved.
Comment thread
AmberAlston marked this conversation as resolved.
Comment thread
AmberAlston marked this conversation as resolved.
Comment thread
AmberAlston marked this conversation as resolved.

The following describes the Security Center CVE scanning process:

Expand Down