Skip to content

Commit c3a70d6

Browse files
Merge pull request #94829 from GroceryBoyJr/OSDOCS-9981
OSDOCS-9981:OpenShift doc references 3rd party tools instead of RH tools
2 parents 37a6327 + 836af96 commit c3a70d6

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

modules/security-build-once.adoc

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,8 +24,7 @@ image::trustedsupplychain.png["", align="center"]
2424
and development platforms (such as Che) for creating and managing secure code.
2525
Unit testing could rely on
2626
link:https://cucumber.io/[Cucumber] and link:https://junit.org/[JUnit].
27-
You could inspect your containers for vulnerabilities and compliance issues
28-
with link:https://anchore.com[Anchore] or Twistlock,
29-
and use image scanning tools such as AtomicScan or Clair.
30-
Tools such as link:https://sysdig.com[Sysdig] could provide ongoing monitoring
31-
of your containerized applications.
27+
28+
You can inspect your containers for vulnerabilities and configuration issues at build, deploy, or runtime with https://www.redhat.com/en/technologies/cloud-computing/openshift/advanced-cluster-security-kubernetes[Red Hat Advanced Cluster Security for Kubernetes]. For images stored in Quay, you can use the https://access.redhat.com/products/red-hat-quay[Clair scanner] to inspect images at rest. In addition, there are https://catalog.redhat.com/software/vulnerability-scanner/search[certified vulnerability scanners] available in the Red Hat ecosystem catalog.
29+
30+
Tools such as link:https://sysdig.com[Sysdig] can provide ongoing monitoring of your containerized applications.

0 commit comments

Comments
 (0)