You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/app-protect-waf/configuration.md
<
8000
div class="DiffFileHeader-module__hide-on-mobile--dxRfz">
+1-24Lines changed: 1 addition & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ The NGINX Ingress Controller has a set of global configuration parameters that a
19
19
20
20
You can enable and configure NGINX App Protect WAF on the Custom Resources (VirtualServer, VirtualServerRoute) or on the Ingress-resource basis.
21
21
22
-
To configure NGINX App Protect WAF on a VirtualServer resource, you would create a Policy Custom Resource referencing the `APPolicy` Custom Resource or `APPolicy` Bundle, and add this to the VirtualServer definition. Additional information can be found in the [Policy resource documentation](/nginx-ingress-controller/configuration/policy-resource/#waf).
22
+
To configure NGINX App Protect WAF on a VirtualServer resource, you would create a Policy Custom Resource referencing the APPolicy Custom Resource, and add this to the VirtualServer definition. See the documentation on the [App Protect WAF Policy](/nginx-ingress-controller/configuration/policy-resource/#waf).
23
23
24
24
To configure NGINX App Protect WAF on an Ingress resource, you would apply the [App Protect annotations](/nginx-ingress-controller/configuration/ingress-resources/advanced-configuration-with-annotations/#app-protect) to each desired resource.
25
25
@@ -209,29 +209,6 @@ spec:
209
209
tag: Fruits
210
210
```
211
211
212
-
## App Protect WAF Bundles
213
-
214
-
You can define App Protect WAF bundles for VirtualServers by creating policy bundles and putting them on a mounted volume accessible from NGINX Ingress Controller.
215
-
216
-
217
-
For example, you can configure a policy by referencing generated WAF Policy Bundle:
218
-
219
-
> **Note**: Currently we do not support `securityLogs` for policy bundles.
220
-
221
-
```yaml
222
-
apiVersion: k8s.nginx.org/v1
223
-
kind: Policy
224
-
metadata:
225
-
name: <policy_name>
226
-
spec:
227
-
waf:
228
-
enable: true
229
-
apBundle: "<policy_bundle_name>.tgz"
230
-
```
231
-
232
-
> **Note**: Before applying the policy, a WAF Policy Bundle must be created, copied to a volume, and the volume must be mounted to `/etc/nginx/waf/bundles`.
233
-
234
-
235
212
## OpenAPI Specification in NGINX Ingress Controller
236
213
237
214
The OpenAPI Specification defines the spec file format needed to describe RESTful APIs. The spec file can be written either in JSON or YAML. Using a spec file simplifies the work of implementing API protection. Refer to the [OpenAPI Specification](#https://github.com/OAI/OpenAPI-Specification) (formerly called Swagger) for details.
Copy file name to clipboardExpand all lines: docs/content/app-protect-waf/installation.md
-32Lines changed: 0 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -60,39 +60,7 @@ Take the steps below to set up and deploy the NGINX Ingress Controller and App P
60
60
> **Important**: You must have an admin role to configure RBAC in your Kubernetes cluster.
61
61
62
62
2. [Create the common Kubernetes resources](/nginx-ingress-controller/installation/installation-with-manifests/#2-create-common-resources).
63
-
64
63
3. Enable the App Protect WAF module by adding the `enable-app-protect` [cli argument](/nginx-ingress-controller/configuration/global-configuration/command-line-arguments/#cmdoption-enable-app-protect) to your Deployment or DaemonSet file.
65
-
66
-
If you intend to use the NGINX Ingress Controller with the AppProtect WAF module and policy bundles, follow these additional steps:
67
-
68
-
- Skip configuring custom resource definition for `APPolicy` `APLogConf` and `APUserSig`.
69
-
70
-
- Create and configure [Persistent Volume and Persistent Volume Claim](https://kubernetes.io/docs/concepts/storage/persistent-volumes/) in your Kubernetes cluster.
71
-
72
-
- Modify NGINX Ingress Controller Deployment or DaemonSet file to include volumes and volume mounts.
73
-
74
-
Make the following changes:
75
-
76
-
Add `volumes` section to deployment template spec:
77
-
```yaml
78
-
...
79
-
volumes:
80
-
- name: <volume_name>
81
-
persistentVolumeClaim:
82
-
claimName: <claim_name>
83
-
...
84
-
```
85
-
Add volume mounts to `containers` section:
86
-
```yaml
87
-
...
88
-
volumeMounts:
89
-
- name: <volume_mount_name>
90
-
mountPath: /etc/nginx/waf/bundles
91
-
...
92
-
```
93
-
94
-
> **Important**: NGINX Ingress Controller requires the volume mount path to be `/etc/nginx/waf/bundles`
95
-
96
64
4. [Deploy the Ingress Controller](/nginx-ingress-controller/installation/installation-with-manifests/#3-deploy-the-ingress-controller).
97
65
98
66
For more information, see the [Configuration guide](/nginx-ingress-controller/app-protect/configuration) and the NGINX Ingress Controller with App Protect example resources on GitHub [for VirtualServer resources](https://github.com/nginxinc/kubernetes-ingress/tree/v3.0.2/examples/custom-resources/app-protect-waf) and [for Ingress resources](https://github.com/nginxinc/kubernetes-ingress/tree/v3.0.2/examples/ingress-resources/app-protect-waf).
0 commit comments