Skip to content

Conversation

@craig-osterhout
Copy link
Contributor

@craig-osterhout craig-osterhout commented Jan 9, 2026

Description

Added topic about scanner integrations and moved conceptual info from how to scan to that topic.
Refreshed how to scan and vex core concept topics.

Pending Wiz updates.

Related issues or tickets

ENGDOCS-3137

Reviews

  • Editorial review
  • Product review

@netlify
Copy link

netlify bot commented Jan 9, 2026

Deploy Preview for docsdocker ready!

Name Link
🔨 Latest commit 90349ae
🔍 Latest deploy log https://app.netlify.com/projects/docsdocker/deploys/69618edbf47ddc0008bcb64e
😎 Deploy Preview https://deploy-preview-23952--docsdocker.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.

Signed-off-by: Craig Osterhout <craig.osterhout@docker.com>
Copy link

@Bkblodget Bkblodget left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

made a few suggestions, overall looks great!

- Scanner flexibility: Switch between any VEX-enabled scanner (Docker Scout,
Trivy, Grype, etc.) without losing vulnerability context or rebuilding
exclusion lists.
- Consistent results: All VEX-enabled scanners interpret the same data the

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would remove "all" here.

"VEX-enabled scanners interpret the same data...."

lists to replicate what VEX statements already document.
- Higher false positive rates: Expect to see more reported vulnerabilities
that don't represent real risks.
- Increased investigation time: Security teams spend time researching why

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This may not be the right place, but when I read this bullet point, I was thinking we could add something like "security experts at docker manage this investigation for you, and thoroughly vet each justification before adding it to a VEX statement."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants