Skip to content

Soften Security Center "continuous" scanning language#4297

Merged
AmberAlston merged 1 commit into
mainfrom
amber/soften-security-center-scan-cadence
Jul 23, 2026
Merged

Soften Security Center "continuous" scanning language#4297
AmberAlston merged 1 commit into
mainfrom
amber/soften-security-center-scan-cadence

Conversation

@AmberAlston

Copy link
Copy Markdown
Member

What

Reword the "How CVE scanning works" section of the Security Center (Alpha) docs so it no longer claims every image is scanned continuously.

Why

"Continuously" reads as real-time and overstates what the system does. Scanning actually runs on a recurring schedule with variable frequency:

  • Newly promoted images that have never been scanned are prioritized and scanned right away.
  • Previously scanned images are rescanned periodically, more often for recently promoted images than for older ones.

The new wording describes a recurring schedule without committing to the exact cadence (which may change), while keeping the honest and valuable point that newly disclosed CVEs surface after release without requiring a new release.

Change

Before:

With SecureBuild, every image is scanned continuously (not just at release time) using the open source vulnerability scanner Grype. This means that, as new CVEs are disclosed, they automatically appear in your Security Center without requiring a new release.

After:

With SecureBuild, images are scanned on a recurring schedule using the open source vulnerability scanner 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.

Scope is intentionally limited to the continuous-scanning language. The SecureBuild references are left as-is.

🤖 Generated with Claude Code

The "How CVE scanning works" section claimed every image is scanned
"continuously," which reads as real-time and overstates the behavior.
Scanning actually runs on a recurring schedule with variable frequency:
newly promoted images are scanned right away, and previously scanned
images are rescanned periodically, more often for recently promoted
images than for older ones.

Reword to describe a recurring schedule without committing to the exact
cadence, which may change. Keeps the honest, valuable point that CVEs
surface after release without requiring a new release.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@AmberAlston
AmberAlston requested a review from a team as a code owner July 23, 2026 21:18
@netlify

netlify Bot commented Jul 23, 2026

Copy link
Copy Markdown

Deploy Preview for replicated-docs ready!

Name Link
🔨 Latest commit 815eeb0
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs/deploys/6a62850c5c164f000804d185
😎 Deploy Preview https://deploy-preview-4297--replicated-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify

netlify Bot commented Jul 23, 2026

Copy link
Copy Markdown

Deploy Preview for replicated-docs-upgrade ready!

Name Link
🔨 Latest commit 815eeb0
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs-upgrade/deploys/6a62850c53945f0008168916
😎 Deploy Preview https://deploy-preview-4297--replicated-docs-upgrade.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions github-actions Bot added type::docs Improvements or additions to documentation type::feature labels Jul 23, 2026
Comment thread docs/vendor/security-center-about.mdx
Comment thread docs/vendor/security-center-about.mdx
Comment thread docs/vendor/security-center-about.mdx
Comment thread docs/vendor/security-center-about.mdx
Comment thread docs/vendor/security-center-about.mdx
Comment thread docs/vendor/security-center-about.mdx
Comment thread docs/vendor/security-center-about.mdx
Comment thread docs/vendor/security-center-about.mdx
@AmberAlston
AmberAlston requested a review from divolgin July 23, 2026 21:18
@AmberAlston
AmberAlston merged commit f495afa into main Jul 23, 2026
6 checks passed
@AmberAlston
AmberAlston deleted the amber/soften-security-center-scan-cadence branch July 23, 2026 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

type::docs Improvements or additions to documentation type::feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants