| Releases | Author |
|---|---|
| Changelog - Features | David Krohn Linkedin - Blog |
AWS Web Application Firewalls (WAFs) protect web applications and APIs from typical attacks from the Internet that can compromise security and availability, and put undue strain on servers and resources. The AWS WAF provides prebuilt security rules that help control bot traffic and block attack patterns. You can also create your own rules based on your own requirements. In simple scenarios and for smaller applications, this is very easy to implement on an individual basis. However, in larger environments with tens or even hundreds of applications, it is advisable to aim for central governance and automation. This simple solution helps you deploy, update and stage your Web Application Firewalls while managing them centrally via AWS Firewall Manager.
If you want to learn more about the AWS Firewall Factory feel free to look at the following media resources.
-
📺 Webinar: Web Application Firewalls at Scale - Language: 🇩🇪
-
📺 Webinar: Managing AWS Web Application Firewalls at Scale - Language: 🇺🇸
-
📊 Slides: Managing AWS Web Application Firewalls at Scale - Language: 🇺🇸
- 🐦🤖 Twitter Bot to get Notified for Managed Rules Updates
- 🔔 Slack automation to get Notified for Managed Rules Updates
- 🏫 AWS WAF Workshop
-
Automated capactiy calculation via API - CheckCapacity
-
Algorithm to split Rules into RuleGroups
-
Automated update of RuleGroup if capacity changed
-
Add ManagedRuleGroups via configuration file
-
Automated generation of draw.io diagram for each WAF
-
Checking of the softlimit quota for WCU set in the AWS account (stop deployment if calculated WCU is above the quota)
-
Easy configuration of WAF rules trough JSON file.
-
Deployment hash to deploy same WAF more than once for testing and/or blue/green deployments.
-
Stopping deployment if soft limit will be exceeded: Firewall Manager policies per organization per Region (L-0B28E140) - Maximum number of web ACL capacity units in a web ACL in WAF for regional (L-D9F31E8A)
-
RegexMatchStatement and IPSetReferenceStatement is working now 🚀
-
You can name your rules. If you define a name in your RulesArray, the name + a Base36 timestamp will be used for the creation of your rule - otherwise a name will be generated. This will help you to query your logs in Athena. The same rule name also applies to the metric by adding "-metric" to the name.
-
Support for Captcha - You can add Captcha as an action to your WAFs. This helps you block unwanted bot traffic by requiring users to successfully complete challenges before their web request are allowed to reach AWS WAF protected resources. AWS WAF Captcha is available in the US East (N. Virginia), US West (Oregon), Europe (Frankfurt), South America (Sao Paulo), and Asia Pacific (Singapore) AWS Regions and supports Application Load Balancer, Amazon API Gateway, and AWS AppSync resources.
-
Added S3LoggingBucketName to JSON. You need to specify the S3 Bucket where logs should be placed in. We also added a prefix for the logs to be AWS conform (Prefix: AWSLogs/AWS_ACCOUNTID/FirewallManager/AWS_REGION/).
-
Added testing your WAF with GoTestWAF. To be able to check your WAF we introduced the SecuredDomain parameter in the JSON (which should be your domain) which will be checked using the WAF tool.
-
TaskFileParameters:
Parameter Value SKIP_QUOTA_CHECK true (Stop deployment if calculated WCU is above the quota)
false (Skipping WCU Check)WAF_TEST true (testing your waf with GoTestWAF)
false (Skipping WAF testing)CREATE_DIAGRAM true (generating a diagram using draw.io)
false (Skipping diagram generation)CDK_DIFF true (generating a cdk before invoking cdk deploy)
false (Skipping cdk diff) -
Validation of your ConfigFile using schema validation - if you miss a required parameter in your config file the deployment will stop automatically and show you the missing path.
-
PreProcess- and PostProcessRuleGroups - you can decide now where the Custom or ManagedRules should be added to.
- New Structure see example json.
-
RuleLabels - A label is a string made up of a prefix, optional namespaces and a name. The components of a label are delimited with a colon. Labels have the following requirements and characteristics:
-
Labels are case-sensitive.
-
Each label namespace or label name can have up to 128 characters.
-
You can specify up to five namespaces in a label.
-
Components of a label are separated by a colon ( : ).
-
-
While Deployment the Price for your WAF will be calculated using the Pricing API
-
Dashboard - The Firewall Factory is able to provision a CloudWatch Dashboard per Firewall. The Dashboard shows:
- Where the WAF is deployed to [AWS Region and Account(s)]
- Which resource type you are securing
- Which Managed Rule Groups in which version are in use
- Link to Managed Rule Groups documentation
- Direct Link to your secured Application / Endpoint
- AWS Firewall Factory version
- Check if the AWS Firewall Factory version is the latest or not during rollout
- Allowed / Blocked and Counted Requests
- Bot vs Non-bot Requests
See example:
-
An central S3 Bucket with write permission for the security account needs to be in place.
-
(Optional) If you want to use the CreateDashboard Feature to get a Dashboard deployed for your Firewall in the central Security Account, the cross-account functionality in CloudWatch must be enabled. To enable enable your account to share CloudWatch data with the central security account follow this how to.
- Create new json file for you WAF and configure Rules in the JSON (see example.json to see structure)
- Assume AWS Profile
awsume PROFILENAME - (Optional) Enter
task generateconfig - Enter
task deploy config=NAMEOFYOURCONFIGFILE
Any form of contribution is welcome. The above contributors have been officially released by globaldatanet.
Want to contribute to AWS FIREWALL FACTORY? Check out the Contribution docs
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent