Skip to content

Commit 4c3da78

Browse files
IlyesbdlalaJ12934
authored andcommitted
#1902 Replaced all occurences of OWASP ZAP to ZAP
This is due to ZAP no longer being part of OWASP Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
1 parent b3b2f19 commit 4c3da78

10 files changed

Lines changed: 15 additions & 16 deletions

File tree

‎scanners/zap-advanced/.helm-docs.gotmpl‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ optional arguments:
6060
-o OUTPUT_FOLDER, --output-folder OUTPUT_FOLDER
6161
The path to a local folder used to store the output files, eg. the ZAP Report or logfiles.
6262
-r XML,XML-plus,JSON,JSON-plus,HTML,HTML-plus,MD, --report-type XML,XML-plus,JSON,JSON-plus,HTML,HTML-plus,MD
63-
The ZAP Report Type.
63+
The ZAP Report Type.
6464
```
6565
{{- end }}
6666

@@ -91,7 +91,7 @@ Additionally, there will be some ZAP Scripts included, these are stored in the c
9191
│This CM contains ZAP session │ │ ▼ │ │A YAML configuration for ZAP that │
9292
│scripts that are already included │ │ │ ┌───────────────────┐ │ │ │relates to a single scan execution. │
9393
│within the zap-advanced scanner. │ │ │ │ │ │- can by used for selected scans │
94-
│Feel free to add your own. │────────┼─────┼─▶│ ZAP Proxy │ │ │ │- not created by default │
94+
│Feel free to add your own. │────────┼─────┼─▶│ ZAP Proxy │ │ │- not created by default │
9595
│ │ │ │ │ └───────│- add your scan target specific config │
9696
│ConfigMap: zap-scripts-session │ │ │ └───────────────────┘ │ │- needs to be referenced in Scan │
9797
└──────────────────────────────────────┘ │ │- please use SecretMap for credentials! │

‎scanners/zap-advanced/README.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Otherwise your changes will be reverted/overwritten automatically due to the bui
3535
<a href="https://infosec.exchange/@secureCodeBox"><img alt="Mastodon Follower" src="https://img.shields.io/mastodon/follow/111902499714281911?domain=https%3A%2F%2Finfosec.exchange%2F"/></a>
3636
</p>
3737

38-
## What is OWASP ZAP?
38+
## What is ZAP?
3939
:::caution Deprecation Notice
4040
The `zap-advanced` and `zap` ScanType are being deprecated in favor of the `zap-automation-framework`, which encompasses all functionalities of the previous ScanTypes. We recommend transitioning to "zap-automation-framework". This change will take effect in the upcoming release cycle. For guidance on migrating to "zap-automation-framework," please refer to [here](/docs/scanners/zap-automation-framework#migration-to-zap-automation-framework).
4141
:::
@@ -76,7 +76,7 @@ optional arguments:
7676
-o OUTPUT_FOLDER, --output-folder OUTPUT_FOLDER
7777
The path to a local folder used to store the output files, eg. the ZAP Report or logfiles.
7878
-r XML,XML-plus,JSON,JSON-plus,HTML,HTML-plus,MD, --report-type XML,XML-plus,JSON,JSON-plus,HTML,HTML-plus,MD
79-
The ZAP Report Type.
79+
The ZAP Report Type.
8080
```
8181

8282
## Requirements
@@ -109,7 +109,7 @@ Additionally, there will be some ZAP Scripts included, these are stored in the c
109109
│This CM contains ZAP session │ │ ▼ │ │A YAML configuration for ZAP that │
110110
│scripts that are already included │ │ │ ┌───────────────────┐ │ │ │relates to a single scan execution. │
111111
│within the zap-advanced scanner. │ │ │ │ │ │- can by used for selected scans │
112-
│Feel free to add your own. │────────┼─────┼─▶│ ZAP Proxy │ │ │ │- not created by default │
112+
│Feel free to add your own. │────────┼─────┼─▶│ ZAP Proxy │ │ │ │- not created by default │
113113
│ │ │ │ │ └───────│- add your scan target specific config │
114114
│ConfigMap: zap-scripts-session │ │ │ └───────────────────┘ │ │- needs to be referenced in Scan │
115115
└──────────────────────────────────────┘ │ │- please use SecretMap for credentials! │

‎scanners/zap-advanced/docs/README.ArtifactHub.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The secureCodeBox project is running on [Kubernetes](https://kubernetes.io/). To
4040

4141
You can find resources to help you get started on our [documentation website](https://www.securecodebox.io) including instruction on how to [install the secureCodeBox project](https://www.securecodebox.io/docs/getting-started/installation) and guides to help you [run your first scans](https://www.securecodebox.io/docs/getting-started/first-scans) with it.
4242

43-
## What is OWASP ZAP?
43+
## What is ZAP?
4444
:::caution Deprecation Notice
4545
The `zap-advanced` and `zap` ScanType are being deprecated in favor of the `zap-automation-framework`, which encompasses all functionalities of the previous ScanTypes. We recommend transitioning to "zap-automation-framework". This change will take effect in the upcoming release cycle. For guidance on migrating to "zap-automation-framework," please refer to [here](/docs/scanners/zap-automation-framework#migration-to-zap-automation-framework).
4646
:::
@@ -81,7 +81,7 @@ optional arguments:
8181
-o OUTPUT_FOLDER, --output-folder OUTPUT_FOLDER
8282
The path to a local folder used to store the output files, eg. the ZAP Report or logfiles.
8383
-r XML,XML-plus,JSON,JSON-plus,HTML,HTML-plus,MD, --report-type XML,XML-plus,JSON,JSON-plus,HTML,HTML-plus,MD
84-
The ZAP Report Type.
84+
The ZAP Report Type.
8585
```
8686

8787
## Requirements
@@ -114,7 +114,7 @@ Additionally, there will be some ZAP Scripts included, these are stored in the c
114114
│This CM contains ZAP session │ │ ▼ │ │A YAML configuration for ZAP that │
115115
│scripts that are already included │ │ │ ┌───────────────────┐ │ │ │relates to a single scan execution. │
116116
│within the zap-advanced scanner. │ │ │ │ │ │- can by used for selected scans │
117-
│Feel free to add your own. │────────┼─────┼─▶│ ZAP Proxy │ │ │ │- not created by default │
117+
│Feel free to add your own. │────────┼─────┼─▶│ ZAP Proxy │ │ │ │- not created by default │
118118
│ │ │ │ │ └───────│- add your scan target specific config │
119119
│ConfigMap: zap-scripts-session │ │ │ └───────────────────┘ │ │- needs to be referenced in Scan │
120120
└──────────────────────────────────────┘ │ │- please use SecretMap for credentials! │

‎scanners/zap-advanced/docs/README.DockerHub-Scanner.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ This `scanner` image is intended to work in combination with the corresponding `
5151
docker pull securecodebox/scanner-zap-advanced
5252
```
5353

54-
## What is OWASP ZAP?
54+
## What is ZAP?
5555
:::caution Deprecation Notice
5656
The `zap-advanced` and `zap` ScanType are being deprecated in favor of the `zap-automation-framework`, which encompasses all functionalities of the previous ScanTypes. We recommend transitioning to "zap-automation-framework". This change will take effect in the upcoming release cycle. For guidance on migrating to "zap-automation-framework," please refer to [here](/docs/scanners/zap-automation-framework#migration-to-zap-automation-framework).
5757
:::
@@ -84,7 +84,7 @@ optional arguments:
8484
-o OUTPUT_FOLDER, --output-folder OUTPUT_FOLDER
8585
The path to a local folder used to store the output files, eg. the ZAP Report or logfiles.
8686
-r XML,XML-plus,JSON,JSON-plus,HTML,HTML-plus,MD, --report-type XML,XML-plus,JSON,JSON-plus,HTML,HTML-plus,MD
87-
The ZAP Report Type.
87+
The ZAP Report Type.
8888
```
8989

9090
## Community

‎scanners/zap-automation-framework/.helm-docs.gotmpl‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ usecase: "WebApp & OpenAPI Vulnerability Scanner"
2525
{{- end }}
2626

2727
{{- define "extra.chartAboutSection" -}}
28-
## What is OWASP ZAP?
28+
## What is ZAP?
2929

3030
The [OWASP Zed Attack Proxy (ZAP)][zap owasp project] is one of the world’s most popular free security tools and is actively maintained by hundreds of international volunteers*. It can help you automatically find security vulnerabilities in your web applications while you are developing and testing your applications. It's also a great tool for experienced pentesters to use for manual security testing.
3131

‎scanners/zap-automation-framework/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-automation-framework
7-
description: A Helm chart for the OWASP ZAP Automation Framework that integrates with the secureCodeBox.
7+
description: A Helm chart for the ZAP Automation Framework 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

‎scanners/zap-automation-framework/README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ Otherwise your changes will be reverted/overwritten automatically due to the bui
3535
<a href="https://infosec.exchange/@secureCodeBox"><img alt="Mastodon Follower" src="https://img.shields.io/mastodon/follow/111902499714281911?domain=https%3A%2F%2Finfosec.exchange%2F"/></a>
3636
</p>
3737

38-
## What is OWASP ZAP?
38+
## What is ZAP?
3939

4040
The [OWASP Zed Attack Proxy (ZAP)][zap owasp project] is one of the world’s most popular free security tools and is actively maintained by hundreds of international volunteers*. It can help you automatically find security vulnerabilities in your web applications while you are developing and testing your applications. It's also a great tool for experienced pentesters to use for manual security testing.
4141

‎scanners/zap-automation-framework/docs/README.ArtifactHub.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ The secureCodeBox project is running on [Kubernetes](https://kubernetes.io/). To
4040

4141
You can find resources to help you get started on our [documentation website](https://www.securecodebox.io) including instruction on how to [install the secureCodeBox project](https://www.securecodebox.io/docs/getting-started/installation) and guides to help you [run your first scans](https://www.securecodebox.io/docs/getting-started/first-scans) with it.
4242

43-
## What is OWASP ZAP?
43+
## What is ZAP?
4444

4545
The [OWASP Zed Attack Proxy (ZAP)][zap owasp project] is one of the world’s most popular free security tools and is actively maintained by hundreds of international volunteers*. It can help you automatically find security vulnerabilities in your web applications while you are developing and testing your applications. It's also a great tool for experienced pentesters to use for manual security testing.
4646

‎scanners/zap-automation-framework/docs/README.DockerHub-Parser.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,7 @@ This `parser` image is intended to work in combination with the corresponding se
5151
docker pull securecodebox/parser-zap-automation-framework
5252
```
5353

54-
## What is OWASP ZAP?
54+
## What is ZAP?
5555

5656
The [OWASP Zed Attack Proxy (ZAP)][zap owasp project] is one of the world’s most popular free security tools and is actively maintained by hundreds of international volunteers*. It can help you automatically find security vulnerabilities in your web applications while you are developing and testing your applications. It's also a great tool for experienced pentesters to use for manual security testing.
5757

‎scanners/zap/.helm-docs.gotmpl‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,6 @@ usecase: "WebApp & OpenAPI Vulnerability Scanner"
2727
{{- define "extra.chartAboutSection" -}}
2828
## What is ZAP?
2929

30-
3130
:::caution Deprecation Notice
3231
The `zap-advanced` and `zap` ScanType are being deprecated in favor of the `zap-automation-framework`, which encompasses all functionalities of the previous ScanTypes. We recommend transitioning to "zap-automation-framework". This change will take effect in the upcoming release cycle. For guidance on migrating to "zap-automation-framework," please refer to [here](/docs/scanners/zap-automation-framework#migration-to-zap-automation-framework).
3332
:::

0 commit comments

Comments
 (0)