Organization policies and Config prerequisites
AWS Firewall Manager centrally manages security policies across an AWS Organizations organization, so teams do not have to configure every account separately. A policy sets the accounts and resources in scope.
How it works
- Set up an organization and a Firewall Manager administrator account.
- Enable AWS Config in each member account, including the administrator, and each Region containing resources to protect. Config records resource configuration changes. Use continuous recording for protected resources and enable the resource types required by the policy.
- Choose a policy and its scope. A security groupA set of rules controlling network traffic to and from associated resources. is a set of network traffic rules. Common policies apply groups; content audits check rules; usage audits find unused or redundant groups.
- Choose automatic remediationAutomatic corrective action taken when a resource does not meet a policy., meaning automatic corrective action, only after reviewing its effects. AWS recommends starting content and usage audits with it disabled. Firewall Manager maintains security group policies as accounts and resources change.
- For Network Firewall or DNS Firewall policies, enable organization resource sharing and create the rule groupsA reusable collection of filtering rules. in the administrator account first. DNS Firewall policies associate groups of DNS filtering rules with in-scope virtual private clouds (VPCs).
| Network Firewall model | Firewall Manager action |
|---|---|
| Distributed | Creates a firewall for each in-scope account and VPC. |
| Centralized | Creates one firewall in one VPC. |
| Import existing | Imports existing firewalls into a policy. |
Exam cues
- If the question says apply security groups across accounts, think common security group policy, because it applies selected groups to in-scope resources.
- If the question says find noncompliant rules or unused groups, think content audit or usage audit respectively, because they inspect different properties.
- If the question says centrally manage DNS filtering in multiple VPCs, think DNS Firewall policy, because it manages rule group associations across the organization.
- If the question says retain existing Network Firewall firewalls under central management, think import existing firewalls, because that model brings them into a policy.
Remember
- AWS Config continuous recording is the default and is required for compliance monitoring.
- DNS first rule groups use priorities 1 through 99; account-managed groups follow; last rule groups use 9901 through 10000.
- Firewall Manager supports AWS WAF, Shield Advanced, network ACL and security group policies as well as Network Firewall and DNS Firewall policies.
Trap: AWS Config enabled with daily recording does not satisfy Firewall Manager compliance monitoring. Protected resources need continuous recording.
From the AWS docs (15)
- Firewall Manager centrally manages security policies for an organization or selected accounts and resources.
- Firewall Manager requires an AWS Organizations organization and a Firewall Manager administrator account.
- AWS Config must be enabled in each member account including the administrator account and in each Region with resources to protect.
- Compliance monitoring requires continuous Config recording for protected resources; continuous is the default recording frequency.
- When not recording all resource types, enable the Config resource types required by each policy type.
- Firewall Manager continuously maintains security group policies as accounts and resources are added or updated.
- Common security group policies apply groups; content audits find and remediate noncompliant rules; usage audits identify unused and redundant groups.
- AWS recommends starting content and usage audits with automatic remediation disabled and reviewing the proposed effects.
- Network Firewall policies support distributed firewalls per in-scope account and VPC, a centralized firewall in one VPC, or importing existing firewalls.
- Network Firewall rule groups must already exist in the Firewall Manager administrator account before they can be included in a policy.
- DNS Firewall policies manage associations between DNS Firewall rule groups and in-scope VPCs across an organization.
- DNS Firewall rule groups must already exist in the Firewall Manager administrator account before they can be included in a policy.
- Network Firewall and DNS Firewall policies require resource sharing enabled for AWS Organizations.
- DNS Firewall evaluates Firewall Manager first rule groups at priorities 1 through 99, account-managed groups next, and Firewall Manager last rule groups at priorities 9901 through 10000.
- Firewall Manager supports AWS WAF, Shield Advanced, security group, network ACL, Network Firewall and DNS Firewall policies.
Flashcards
Nothing to review here right now. Pick other topics or another filter.
·
All 9 cards as a list
Which service centrally manages AWS WAF, Shield Advanced, security group, network ACL and Network Firewall policies across an organization?
AWS Firewall Manager. Configure AWS Config and the policy scope for the accounts and resources to protect.
What prerequisites allow AWS Firewall Manager to monitor policy compliance across accounts?
An AWS Organizations organization, a Firewall Manager administrator, and AWS Config enabled in each member account and relevant Region with continuous recording of protected resources.
A team wants to find unused and redundant security groups across accounts with AWS Firewall Manager. Which policy should it use?
A security group usage audit policy.
A team wants to check security group rules against standards with AWS Firewall Manager. Which policy should it use?
A security group content audit policy. Start with automatic remediation disabled to review its effects.
How can AWS Firewall Manager apply the same security groups to selected resources across accounts?
Use a common security group policy.
Which AWS Firewall Manager Network Firewall management models are available?
Distributed, centralized, and import existing firewalls.
A team wants centrally managed DNS filtering associations in VPCs across accounts. What should it configure in AWS Firewall Manager?
A DNS Firewall policy with existing DNS Firewall rule groups and organization resource sharing enabled.
Does enabling daily AWS Config recording suffice for AWS Firewall Manager compliance monitoring?
No. Protected resources must be recorded continuously.
In an AWS Firewall Manager DNS Firewall policy, when are first and last rule groups evaluated?
First groups use priorities 1 through 99, before account-managed groups; last groups use priorities 9901 through 10000, after them.