Skip to content

Update botstopper standard policy #530

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dominik-matic wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update botstopper standard policy #530

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/hypernode-platform/botstopper/how-to-use-botstopper.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -97,6 +97,7 @@ The standard policy does the following:

1. Allows Hypernode platform services, payment providers, monitoring tools, and common e-commerce integrations.
1. Allows IP addresses on the Hypernode WAF allowlist.
1. Allows requests that your Hypernode, or any other node in your cluster, sends to itself, for example an extension that fetches WordPress content from your own domain, or a cache warmer requesting storefront pages.
1. Runs your custom pre-policy from `/data/web/botstopper/pre.policy.yml`.
1. Denies sensitive Magento media paths, such as `/media/customer/`, `/media/import/`, and `/media/downloadable/`.
1. Allows storefront assets, such as `/static/`, normal `/media/` files, etc.
Expand Down
Loading