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: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -250,6 +250,7 @@ _Note that Kubernetes annotation maps are all of Go type `map[string]string`. A
250
250
| <aname="enable-regex-domains"></a>deis-router | deployment |[router.deis.io/nginx.enableRegexDomains](#enable-regex-domains)|`"false"`| Whether to _enable_ application-level regex domain that can be explicitly defined for specific applications. With this option enabled, each app can have its own regex domain in server_name blocks of the nginx config. This allows for useful domains like `store-number-\d*.example.com`. |
251
251
| <aname="load-tcell-module"></a>deis-router | deployment |[router.deis.io/nginx.loadTcellModule](#load-tcell-module)|`"false"`| Whether to _enable_ the dynamic security nginx module provided by [Tcell](https://tcell.io/) as a [WAF](https://en.wikipedia.org/wiki/Web_application_firewall) on the router. Note this requires that you purchase a Tcell account and have application configured in the Tcell UI. The tcell_agent.config is passed through a configMap object through k8s. Example of the configMap can be found in this [gist](https://gist.github.com/Cryptophobia/648b23f234eeb9538c87b478de401a53). The open source alternative for this is Modsecurity dynamic module. |
252
252
| <aname="global-tcell-app-id"></a>deis-router | deployment |[router.deis.io/nginx.globalTcellAppID](#global-tcell-app-id)| N/A | This is the global app id to insert for the Tcell module in the top-most http{} block of the nginx config. To configure an individual app id for each application, you need to use the application annotation below. The application specific app id will take precedence over the global one. |
253
+
| <aname="load-modsecurity-module"></a>deis-router | deployment |[router.deis.io/nginx.loadModsecurityModule](#load-modsecurity-module)|`"false"`| Whether to _enable_ the open source dynamic security nginx module [Modsecurity](https://github.com/SpiderLabs/ModSecurity/tree/v3/master) globally for all apps as a [WAF](https://en.wikipedia.org/wiki/Web_application_firewall) on the router. The rule set that Modsecurity will use by default is the [OWASP ModSecurity Core Rule Set (CRS)](https://github.com/SpiderLabs/owasp-modsecurity-crs) and Modsecurity will be turned on to block malicious traffic on all apps if this annotation is enabled. This core rule set can be overwritten by configMap like in the example above for the Tcell module. |
253
254
| <aname="default-whitelist"></a>deis-router | deployment |[router.deis.io/nginx.defaultWhitelist](#default-whitelist)| N/A | A default (router-wide) whitelist expressed as a comma-delimited list of addresses (using IP or CIDR notation). Application-specific whitelists can either extend or override this default. |
254
255
| <aname="whitelist-mode"></a>deis-router | deployment |[router.deis.io/nginx.whitelistMode](#whitelist-mode)|`"extend"`| Whether application-specific whitelists should extend or override the router-wide default whitelist (if defined). Valid values are `"extend"` and `"override"`. |
255
256
| <aname="default-service-enabled"></a>deis-router | deployment |[router.deis.io/nginx.defaultServiceEnabled](#default-service-enabled)|`"false"`| Enables default back-end service for traffic hitting /. In order to work correctly both `defaultServiceIP` and `DefaultAppName` MUST also be set. |
0 commit comments