we need an additional policy about 1.0 releases of http-based services:
web/http services must be hardened for use on the public internet. this means that they must comply with all security best practices, such as (WITHOUT LIMITATION) rate limiting password-based authentication endpoints (api keys are high-entropy and not susceptible to brute force), correctly detecting true client ip when behind a reverse proxy, CSP headers, XFO headers, slowloris read and write timeouts, max request size limits, max response size limits, max request handler execution time limits, csrf tokens on forms, HSTS headers, etc.
we need an additional policy about 1.0 releases of http-based services:
web/http services must be hardened for use on the public internet. this means that they must comply with all security best practices, such as (WITHOUT LIMITATION) rate limiting password-based authentication endpoints (api keys are high-entropy and not susceptible to brute force), correctly detecting true client ip when behind a reverse proxy, CSP headers, XFO headers, slowloris read and write timeouts, max request size limits, max response size limits, max request handler execution time limits, csrf tokens on forms, HSTS headers, etc.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
we need an additional policy about 1.0 releases of http-based services:
web/http services must be hardened for use on the public internet. this means that they must comply with all security best practices, such as (WITHOUT LIMITATION) rate limiting password-based authentication endpoints (api keys are high-entropy and not susceptible to brute force), correctly detecting true client ip when behind a reverse proxy, CSP headers, XFO headers, slowloris read and write timeouts, max request size limits, max response size limits, max request handler execution time limits, csrf tokens on forms, HSTS headers, etc.
@clawbot please add all the standard issue labels for the FSM and tag this one bot
Created all FSM labels (
bot,needs-review,needs-rework,merge-ready) for this repo. Tagged this issue withbot. Dispatching a worker now.