More versatile Custom Protection Rules setup.

Published 13 days ago

# SafeLine WAF
# ๐Ÿ’ก feature
# ๐Ÿ–ฅ๏ธ ui
# ๐Ÿ’ช improve

Published 13 days ago

profile_photo

selenium

Updated 2 months ago

0

I would like to see more versatile mechanism of customizable protection rule setup.

  1. Rules ordering. Assume lots of deny rules and allow rules, it would be better to order these rules by desire, no need of current explicit lists of rule type, for more precise access controlling. Similar to Cloudflare implementation. Build a chain of custom rules, evaluate rules by order until a custom rule hits, then decide what further action to take defined by the custom rule, allow, deny, challenge, auth, pass down to further scrutiny by built-in/managed rules, etc. For my use case, because of SafeLine blocks Git over HTTP by default, I add a custom rule to regex match Git UA string to allow Git operations. Although there are already default rules of blocking malicious IPs, defining such Allow rule, without a clearly-documented or desired order of rule evaluation, can be another spot of vulnerability, bypassing the rest part of protection under SafeLine's current WAF implementation.

  2. Selectively bypass selected built-in/managed rules while preserving other types of scrutiny in custom protection rules setup. Sometimes a HTTP request can look suspicious or be similar to attacking while is actually not, especially when internally exchanging large amount of sensitive information, in headers, query parameters or body payloads, e.g. Internal communications among Gitea/Gogs/GitLab/Jenkins/S3/OIDC/And many others wrongly blocked by SafeLine, until I manually add Allow rules.

  3. Allow Modification/Deletion of default protection rules that are for Search Engine Spider and Malicious IP. I don't want Search Engine to index and crawl my private site.

  4. More match target options in rule setup. e.g. Possible to block IP by ASN?

profile_photo
profile_photo

Carrie

Updated a month ago

0

  1. More match target options in rule setup. e.g. Possible to block IP by ASN?

Answer: We are going to add this in the next version.

profile_photo
profile_photo

Carrie

Updated a month ago

0

  1. Search Engine Spider and Malicious IP can be disabled here in the red box.
    image.png
profile_photo

selenium

Updated a month ago

Yeah, I see the disable button. But wouldn't it be better allowing deletion?

profile_photo
profile_photo

Carrie

Updated a month ago

0

1 & 2 will be discussed further within the team and will reach back if there is any update

profile_photo
profile_photo