envoyproxy/envoy

Holistic approach to WAF

Open

#7,918 opened on Aug 14, 2019

View on GitHub
 (7 comments) (5 reactions) (1 assignee)C++ (5,373 forks)batch import
design proposalenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

In the wake of the recent CVEs, it's become more clear that we need a holistic approach to WAF, primarily allowing for both blocking, blackholing, etc. both L4 and L7 traffic based on various input parameters.

We have various bits and pieces of this today including RBAC, IP tagging, but we need to look through the type of blocking actions that users want to perform and likely build explicit L4 and L7 WAF filters. We also need to think about how these filters would be dynamically populated with block rules via config, streaming API, etc.

Contributor guide

Research direction
Investigate existing WAF related components in Envoy (RBAC, IP tagging) and design a unified filter architecture for L4 and L7 traffic with dynamic rule population.
Tech stack
ccpp
Domain
backendinfrastructuresecurity
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++EnvoyNetworkingSecurity concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20