Overview
The Fastly Next-Gen WAF (powered by Signal Sciences) is a web application firewall that monitors for suspicious and anomalous web traffic and protects, in real-time, against attacks directed at the applications and origin servers that you specify.
Feature | Details |
---|---|
Allow parallel downloading ( |
|
Running environments |
|
Populated Devo events |
|
Flattening preprocessing |
|
Allowed source events obfuscation |
|
Data sources
Data source | Description | API endpoint | Collector service name | Devo table | Available from release |
---|---|---|---|---|---|
List corp activity events | Lists activity events for a corporation. |
|
|
| v1.0.0 |
List site activity events | Lists activity events of a corporation for a given site. |
|
|
| v1.0.0 |
List corp events. | Lists all events of a corporation for a given site. |
|
|
| v1.0.0 |
Get request feed. | Lists all of a corporation's request feed data for a given site. |
|
|
| v1.0.0 |
For more information on how the events are parsed, visit our page.
Vendor setup
You must have a Fasly Next-Gen WAF account. For information on how to create an account check this guide.
With the creation of the account you will get:
User email: The user's email to configure the collector.
Corporation: It is a necessary parameter to configure the collector. It is provided by the Fastly Next-Gen WAF team during account creation.
Site: It is a necessary parameter to configure the collector. It is provided by the Fastly Next-Gen WAF team during account creation.
To generate the required API access token, follow these steps:
Log in to the Fastly console here.
From the My Profile menu, select API access tokens.
Click Add API access token.
In the Token name field, enter a name to identify the access token.
Click Create API access token.
Record the token in a secure location for your use.
Note that this is the only time the token will be visible. Record the token and keep it secure. For your security, it will not appear in the console.
Click Continue to finish creating the token.
Copy the token to set the collector's
api_token
parameter.
For more information check this article.
Minimum configuration required for basic pulling
Although this collector supports advanced configuration, the fields required to retrieve data with basic configuration are defined below.
This minimum configuration refers exclusively to those specific parameters of this integration. There are more required parameters related to the generic behavior of the collector. Check setting sections for details.
Setting | Details |
---|---|
| The username for the Next-Gen WAF API. |
| The API Token for the Next-Gen WAF API.. To find out how to get it, see the Vendor Setup guide. |
See the Accepted authentication methods section to verify what settings are required based on the desired authentication method.
Accepted authentication methods
Authentication method | API Token |
| Required |
| Required |
Run the collector
Once the data source is configured, you can either send us the required information if you want us to host and manage the collector for you (Cloud collector), or deploy and host the collector in your own machine using a Docker image (On-premise collector).
Collector services detail
This section is intended to explain how to proceed with specific actions for services.
Events service
Collector operations
This section is intended to explain how to proceed with specific operations of this collector.
Change log
Release | Released on | Release type | Details | Recommendations |
---|---|---|---|---|
| INITIAL RELEASE | Deployed the first Beta version of the Fastly Next-Gen WAF with the following services:
|
|