-
Notifications
You must be signed in to change notification settings - Fork 9
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.
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
Set Network Policy geolocation limitations #2534
Comments
@kevindherman given that no one (outside of colma) should be connecting to Then use my.proudcity.com to login to beta and do some content stuff. You should be able to log in without issue and edit content. On beta you will still need to use the standard auth login information to see the site first before getting the forbidden message. While this doesn't fully stop/block remote IPs hitting the page it does stop them accessing anything much sooner in the server life so it will reduce impacts of any attack greatly. Ideally we'd block any IP that hits this page, but as we don't pass IPs through to Kubernetes properly I can't. We hit the same IP issue with #2377 If this is good we can roll it out tomorrow. |
Following @curtismchale's steps I got the block on /wp-login and then logged in from my.proudcity.com and successfully add new and edited existing content. With the exception of Colma, seems good to go from my end. |
This |
We should set NetworkPolicy limitations on who can even access
my.proudcity.com
and any variation of/wp-login.php
. We should not have any access from outside the US (with an exemption for our single developer outside the US) to our login pages. Rejecting that would stop the type of credential stuffing attack we had to deal with on March 28 2024.There are likely 2 layers with this.
Customer with Cloudflare
/wp-login.php
,/wp-admin.php
from connecting at all if you're outside the USCustomer without Cloudflare
The text was updated successfully, but these errors were encountered: