Skip to content

Commit efa2971

Browse files
Reet00Reet00
committed
#2024 Changed remaining occcurances from OWASP ZAP in the documentation
This commit also includes the removal of OWASP in the auto-discovery, blog and how-tos Signed-off-by: Samreet Singh <samreet.singh@iteratec.com>
1 parent 696df85 commit efa2971

16 files changed

Lines changed: 309 additions & 309 deletions

‎auto-discovery/kubernetes/.helm-docs.gotmpl‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ The Kubernetes AutoDiscovery needs to be deployed along side the secureCodeBox O
2323

2424
The AutoDiscovery controller will automatically detect these new resources (services and containers) and start secureCodeBox _scans_ for them:
2525

26-
1. A ZAP Baseline Scan to detect basic web vulnerabilities in the service. (Using OWASP ZAP)
26+
1. A ZAP Baseline Scan to detect basic web vulnerabilities in the service. (Using ZAP)
2727
2. An image scan scanning for vulnerable libraries in the docker / container image of the deployment. (Using trivy)
2828
3. (WIP) A TLS Scan against the certificate of the ingress for the host. (Using SSLyze)
2929

@@ -43,7 +43,7 @@ The AutoDiscovery automatically tracks the lifecycle of the kubernetes resources
4343
This example deploys [JuiceShop](https://owasp.org/www-project-juice-shop/) to a new Kubernetes Namespace.
4444
(You can find the kubernetes manifests for the deployment [here](./demo/juice-shop.yaml))
4545

46-
The AutoDiscovery will automatically pick up this new deployment and then starts a OWASP ZAP Scan against it.
46+
The AutoDiscovery will automatically pick up this new deployment and then starts a ZAP Scan against it.
4747
The scan created uses our `zap-advanced` ScanType by default, this can be changed with the `config.serviceAutoDiscovery.scanConfig.scanType` config on the autoDiscovery helm release.
4848

4949
When the ContainerAutoDiscovery is enabled, the AutoDiscovery can also create a trivy scan for each unique container image (having multiple pods with the same container will only create one scan). The scan type can be defined with `config.containerAutoDiscovery.scanConfig.scanType`.

‎auto-discovery/kubernetes/README.md‎

Lines changed: 49 additions & 49 deletions
Large diffs are not rendered by default.

‎auto-discovery/kubernetes/docs/README.ArtifactHub.md‎

Lines changed: 48 additions & 48 deletions
Large diffs are not rendered by default.

‎auto-discovery/kubernetes/docs/README.DockerHub-Core.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,7 @@ docker pull securecodebox/auto-discovery-kubernetes
5656
This example deploys [JuiceShop](https://owasp.org/www-project-juice-shop/) to a new Kubernetes Namespace.
5757
(You can find the kubernetes manifests for the deployment [here](./demo/juice-shop.yaml))
5858

59-
The AutoDiscovery will automatically pick up this new deployment and then starts a OWASP ZAP Scan against it.
59+
The AutoDiscovery will automatically pick up this new deployment and then starts a ZAP Scan against it.
6060
The scan created uses our `zap-advanced` ScanType by default, this can be changed with the `config.serviceAutoDiscovery.scanConfig.scanType` config on the autoDiscovery helm release.
6161

6262
When the ContainerAutoDiscovery is enabled, the AutoDiscovery can also create a trivy scan for each unique container image (having multiple pods with the same container will only create one scan). The scan type can be defined with `config.containerAutoDiscovery.scanConfig.scanType`.

‎auto-discovery/readme.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,4 +17,4 @@ The scans it would start:
1717

1818
1. A image scan scanning for vulnerable libraries in the docker / container image of the deployment. (Using trivy)
1919
2. A TLS scan against the certificate of the ingress for the host. (Using SSLyze)
20-
3. A ZAP scan to detect basic web vulnerabilities in the service. (Using OWASP ZAP)
20+
3. A ZAP scan to detect basic web vulnerabilities in the service. (Using ZAP)

‎documentation/blog/2023-09-01-automate-zap-with-authentication.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ authors:
1515
image_url: https://avatars.githubusercontent.com/u/1688580?v=4
1616
tags:
1717
- secureCodeBox
18-
- OWASP ZAP automation
18+
- ZAP automation
1919
- Authentication
2020
description: This post describes how to automate ZAP to authenticate against an API
2121
---

‎documentation/docs/auto-discovery/overview.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,6 @@ sidebar_position: 0
1313

1414
The secureCodeBox (SCB) AutoDiscovery is an optional component that automates the process of setting up scheduled scans for Kubernetes resources inside a cluster. The AutoDiscovery will observe the scanned Kubernetes resources over their whole lifecycle. It will automatically create, update and delete scans when necessary. Currently the SCB AutoDiscovery supports two modes that can be enabled independently:
1515

16-
- [Service AutoDiscovery](./service-auto-discovery): Creates scans for (http) services inside a kubernetes cluster. With it you can automatically start scanners like OWASP ZAP or nuclei for all web applications inside the cluster.
16+
- [Service AutoDiscovery](./service-auto-discovery): Creates scans for (http) services inside a kubernetes cluster. With it you can automatically start scanners like ZAP or nuclei for all web applications inside the cluster.
1717

1818
- [Container AutoDiscovery](./container-auto-discovery): Creates scans for containers running inside a kubernetes cluster. This allows you to automatically create trivy container image scans for all container images inside a cluster.

‎documentation/docs/how-tos/scanning-web-applications.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
# SPDX-License-Identifier: Apache-2.0
55

66
title: "Scanning Web Applications"
7-
description: "Automating OWASP ZAP with the secureCodeBox"
7+
description: "Automating ZAP with the secureCodeBox"
88
sidebar_position: 3
99
---
1010

‎scanners/zap-advanced/Chart.yaml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
apiVersion: v2
66
name: zap-advanced
7-
description: A Helm chart for the OWASP ZAP (extended with advanced authentication features) security scanner that integrates with the secureCodeBox.
7+
description: A Helm chart for the ZAP (extended with advanced authentication features) security scanner that integrates with the secureCodeBox.
88
type: application
99
# version - gets automatically set to the secureCodeBox release version when the helm charts gets published
1010
version: v3.1.0-alpha1

0 commit comments

Comments
 (0)