Transparent Security is a solution for identify the source devices of a DDoS attack and mitigates the attack in the customer premises or the access network. This solution leverages a P4 based programmable data plane for add in-band network telemetry (INT) for device identification and in-band mitigation.
Fixes #351
Adds the ability for the SimpleAE to ingest drop reports and enable it to tell the controller when the attack has ceased.
Do you have any concerns with this PR?
no
How can the reviewer verify this PR?
ensure CI passes
Any background context you want to provide?
With drop reports being properly created, we need to ensure we can act on these packets. The rules for the SimpleAE are rudimentary. When the pre-configured number of drop reports (default 3) are received without any other packets from the device to a given destination, a DELETE RESTful call is made to the same endpoint the POST was made with the same arguments.
Screenshots or logs (if appropriate)
Questions:
Have you connected this PR to the issue it resolves? yes
Does the documentation need an update? eventually if/when we document the SimpleAE
Does this add new dependencies? no
Have you added unit or functional tests for this PR? Expanded the existing pkt-flood tests to ensure packets can flow again as well as get mitigated a second time.
What does this PR do?
Fixes #351 Adds the ability for the SimpleAE to ingest drop reports and enable it to tell the controller when the attack has ceased.
Do you have any concerns with this PR?
no
How can the reviewer verify this PR?
ensure CI passes
Any background context you want to provide?
With drop reports being properly created, we need to ensure we can act on these packets. The rules for the SimpleAE are rudimentary. When the pre-configured number of drop reports (default 3) are received without any other packets from the device to a given destination, a DELETE RESTful call is made to the same endpoint the POST was made with the same arguments.
Screenshots or logs (if appropriate)
Questions: