CrowdSec scenario to partially mitigate Log4j | Dark Hacker News