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
Originally posted by brianehlert February 22, 2024
Customers use the readOnlyRootFileSystem capability to align with security policy and customers would like to also use this when NAP WAF is included with NIC.
The current implementation of readOnlyRootFileSystem does not support the NAP WAF module and thus the capability needs to be extended to support NAP WAF module behavior and paths necessary.
Notes:
this can take the v4 / v5 work into consideration
when originally written the focus was v4
unknown how this impacts v5 considering new enforcer container is introduced
The content you are editing has changed. Please copy your edits and refresh the page.
Discussed in #5156
Originally posted by brianehlert February 22, 2024
Customers use the readOnlyRootFileSystem capability to align with security policy and customers would like to also use this when NAP WAF is included with NIC.
The current implementation of readOnlyRootFileSystem does not support the NAP WAF module and thus the capability needs to be extended to support NAP WAF module behavior and paths necessary.
Notes:
Tasks
WAF v5 considerations
The text was updated successfully, but these errors were encountered: