Menu

Squid forward-proxy security depends on ACL order and a closed default
📰

Squid forward-proxy security depends on ACL order and a closed default

DEV Community: cybersecurity·OnaEiuspkz·9 days ago
#jpLbP188
#devtocybersecurity#devto#dev#proxy#squid
Reading 0:00
15s threshold

Squid forward-proxy security depends on ACL order and a closed default

A Squid forward proxy can be a controlled egress gateway or an open relay into internal networks. The difference is configuration. Squid evaluates http_access rules in order, and the first matching rule decides the request. An early allow for a broad source network can make a later authentication check irrelevant.

Build the decision chain

Start with a final deny all and add allow rules for named networks, authenticated groups and required destinations. Keep the rules small enough to explain. A proxy_auth ACL challenges the client when the request reaches that rule, so authentication should appear before any broader allowance that would bypass it.

The http_port documentation includes a NP option that disables authentication on a listening port. That may be appropriate for a tightly controlled reverse-proxy listener, but it is a poor default for a forward proxy used by people or untrusted workloads.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.