Skip to main content

AWS Firewall Manager

Page topics

General
6
Enabling AWS Firewall Manager
9
Dashboard and Visibility
3

General

Open all

AWS Firewall Manager is a security management service which allows you to centrally configure and manage firewall rules across your accounts and applications in AWS Organization. As new applications are created, Firewall Manager makes it easy to bring new applications and resources into compliance by enforcing a common set of security rules. Now you have a single service to build firewall rules, create security policies, and enforce them in a consistent, hierarchical manner across your entire infrastructure.

AWS Firewall Manager is integrated with AWS Organizations so you can enable AWS WAF rules, AWS Shield Advanced protections, VPC security groups, AWS Network Firewalls, and HAQM Route 53 Resolver DNS Firewall rules across multiple AWS accounts and resources from a single place. Firewall Manager monitors for new resources or accounts created to ensure they comply with a mandatory set of security policies from day one. You can group rules, build policies, and centrally apply those policies across your entire infrastructure. For example, you can delegate the creation of application-specific rules within an account while retaining the ability to enforce global security policies across accounts. Your security team can be notified of threats to the organization so they can respond and rapidly mitigate an attack.

Firewall Manager also integrates with Managed Rules for AWS WAF, which gives you an easy way to deploy pre-configured WAF rules in front of your applications.

Security administrators can leverage Firewall Manager to apply a baseline set of security group rules for EC2 instances, Application Load Balancers and Elastic Network Interfaces (ENIs) in your HAQM VPCs. At the same time, you can also audit any existing security groups in your VPCs for over permissive rules and remediate them from a single place.

You can leverage Firewall Manager to centrally deploy AWS Network Firewall endpoints and associated rules across your VPCs in your organization, to control traffic leaving and entering your network. At the same time, you can also use Firewall Manager to associate your VPCs across your accounts with Route 53 Resolver DNS Firewall rules to block DNS queries made for known malicious domains and to allow queries for trusted domains.

Using AWS Firewall Manager, you can centrally configure AWS WAF rules, AWS Shield Advanced protections, HAQM Virtual Private Cloud (VPC) security groups and network access control lists (ACLs), AWS Network Firewalls, and HAQM Route 53 Resolver DNS Firewall rules across accounts and resources in your organization.

Using AWS Firewall Manager, you can 

  • Easily roll out AWS WAF rules across Application Load Balancer, API Gateways and HAQM CloudFront distributions. 
  • You can create AWS Shield Advanced protections for your Application Load Balancers, ELB Classic Load Balancers, Elastic IP Addresses and CloudFront distributions. 
  • You can configure new HAQM Virtual Private Cloud (VPC) security groups and audit any existing security groups for your HAQM EC2, Application Load Balancers (ALBs) and ENI resource types. 
  • You can also deploy AWS Network Firewalls across accounts and VPCs in your organization.
  • Finally, with AWS Firewall Manager, you can also associate HAQM Route 53 Resolver DNS Firewall rules across VPCs in your organization.
  • You can configure new HAQM Virtual Private Cloud (VPC) network access control lists (ACLs) for your VPC subnets.

AWS Firewall Manager pricing is available here.

Please visit the AWS Region Table to see the current region availability for AWS Firewall Manager.

Enabling AWS Firewall Manager

Open all

There are three mandatory pre-requisites and one optional pre-requisite to use AWS Firewall Manager.

  • AWS Organizations - Your accounts must be part of AWS Organizations and have enabled all features. See AWS Organizations documentation for more details.
  • Set the AWS Firewall Manager Administrator Account - Firewall Manager must be associated with the management account of your AWS organization or associated with a member account that has the appropriate permissions. The account that you associate with Firewall Manager is called the Firewall Manager administrator account. See the documentation guide for more information.
  • Enable AWS Config on accounts - Enable AWS Config for each member account in your organization. See AWS Config documentation.
  • Enable AWS Resource Access Manager (Optional) - To enable Firewall Manager to centrally configure AWS Network Firewalls or associate HAQM Route 53 Resolver DNS Firewall rules across accounts and VPCs, you must first enable sharing of resources using AWS Resource Access Manager.
  • First, complete the prerequisites mentioned above.
  • Second, create a policy type for AWS WAF, AWS Shield Advanced, VPC security group, AWS Network Firewall, or HAQM Route 53 Resolver DNS Firewall.
  • Third, depending on the policy, specify the set of rules or protections. For example, for a policy for AWS WAF specify the rule groups (custom or managed) that you want to deploy across accounts. Similarly, for a VPC security group policy, reference the security group you want replicated in each resource within accounts. For AWS Network Firewall, specify the rule groups (stateful and stateless) that you want to deploy across VPCs in your accounts. For HAQM Route 53 Resolver DNS Firewall, specify the set of rules (rule groups) you want to associate with your VPCs in your accounts.
  • Fourth, specify the scope of the policy by choosing the accounts, resource type and, optionally, resource tags, where you want the policy to be deployed.
  • Finally, you can review and create the policy. Firewall Manager will automatically apply the rules and protections to all resources across accounts. Once complete, Firewall Manager also shows a compliance dashboard indicating any accounts/resources that are non-compliant and those that are compliant.

Yes, you can configure a Firewall Manager policy in two modes –

  • Automatic remediation, which allows you to automatically monitor for drift in policy and apply rules on non-compliant resources
  • Manual remediation, which creates a new policy and the associated rules/protections in each account but does not enforce the rules on the resources in the account. After the policy is created with manual remediation, you can choose to take manual action for each local account, or at any point you can edit the policy to automatically remediate.

Each Firewall Manager policy can be scoped to have at most 2,500 accounts, which is the default limit for number of accounts in AWS Organizations.

There is not a limit on the number of resources managed by Firewall Manager at this time.

No, AWS Firewall Manager security policies are region specific. Each Firewall Manager policy can only include resources available in that specified AWS Region. You can create a new policy for each region where you operate.

Yes. You can exclude accounts. You can also use tags to specify the resources that should be excluded from the policy scope.

Firewall Manager security policy is a set of configurations that allow customers to specify the accounts and resources that need to be associated a set of firewall rules, with additional configurations customized for each firewall type. Firewall Manager today supports AWS WAF, AWS Shield Advanced, VPC security groups, AWS Network Firewall, HAQM Route 53 Resolver DNS Firewall and AWS Marketplace third-party firewalls.

Firewall Manager security policy is a set of configurations that allow customers to specify the accounts and resources that need to be associated a set of firewall rules, with additional configurations customized for each firewall type. Firewall Manager today supports AWS WAF, AWS Shield Advanced, VPC security groups, AWS Network Firewall, HAQM Route 53 Resolver DNS Firewall and AWS Marketplace third-party firewalls.

Dashboard and Visibility

Open all

With Firewall Manager you can quickly view the compliance status for each policy by looking at how many accounts are included in the scope of the policy and how many out of those are compliant. Further, for each policy configured on Firewall Manager, you get a compliance dashboard. The central compliance dashboard allows you to view which accounts are non-compliant to a given policy, which specific resources are non-compliant, and also provides information about the reason why a particular resource is not compliant. You can also view non-compliant events for each account on AWS Security Hub.

Yes, you can create new SNS notification channels to receive real-time notifications when new non-compliant resources are discovered. Similarly, each account scoped as part of a Firewall Manager policy is notified for non-compliant events on AWS Security Hub.

For each Firewall Manager policy created, you can aggregate CloudWatch metrics for each Rule in the Rule Group, indicating how many requests were allowed or blocked across the entire organization. This gives you a central place to set up alerts for threats across your organization.