# AWS WAF

Cloud service · AWS. Updated 2026-11-12. Page: https://blowstack.com/tools/cloud-services-hub/aws-waf

> AWS WAF (Web Application Firewall) is a web application firewall service that helps protect web applications and APIs from common web exploits and bots that may affect availability, compromise security, or consume excessive resources.

Practice exams covering AWS WAF: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [DOP-C02 AWS Certified DevOps Engineer - Professional](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional), [SCS-C03 AWS Certified Security - Specialty](https://blowstack.com/practice-exams/aws-certified-security-specialty), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate), [SAP-C03 AWS Certified Solutions Architect - Professional](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional).

## 8 key features of AWS WAF

AWS WAF provides customizable web security rules, real-time visibility into web traffic, managed rules from AWS, protection against DDoS with rate-based rules, seamless integration with AWS services, bot management, and rule prioritization for comprehensive application protection.

1. **Customizable Web Security Rules**: AWS WAF allows users to create custom security rules tailored to their application's needs to block common attack patterns, such as SQL injection or cross-site scripting (XSS).
2. **Real-Time Visibility**: Provides real-time metrics and captures detailed logs of web traffic, enabling quick identification and response to threats.
3. **Managed Rules**: Offers pre-configured rule sets from AWS security experts and AWS Marketplace sellers to protect applications against common web exploits with minimal setup.
4. **Rate-Based Rules**: Enables automatic blocking of IP addresses that send requests at a rate above a given threshold, effectively mitigating DDoS attacks and brute force attempts.
5. **Integration with AWS Services**: Seamlessly integrates with Amazon CloudFront, Application Load Balancer (ALB), Amazon API Gateway, and AWS AppSync, allowing for protection in various layers of a cloud architecture.
6. **Bot Control**: AWS WAF includes a managed rule group that helps you control bot traffic to your application, distinguishing between benign and malicious bots.
7. **Rule Prioritization**: Offers the flexibility to prioritize the order in which rules are evaluated, ensuring more critical rules are applied first for efficient threat mitigation.
8. **Custom Responses**: Based on configured request conditions, protected resources can return a custom response instead of requested content or an HTTP 403 Forbidden response.

## Where AWS WAF is used

AWS WAF is used for preventing SQL injection and XSS attacks, mitigating DDoS attacks, controlling bot traffic, and managing country-based access to web applications.

1. **Preventing SQL Injection Attacks**: AWS WAF allows users to create custom web security rules to block common web attack patterns, such as SQL injection, by inspecting elements like SQL tokens and statement structures within web requests. This can protect databases from unauthorized data exposure or corruption.
2. **Blocking Cross-Site Scripting (XSS) Attacks**: With AWS WAF, users can prevent XSS attacks where attackers inject malicious scripts into content viewed by other users. Rules can be configured to identify and block malicious scripts, safeguarding website integrity and user data privacy.
3. **Mitigating DDoS Attacks**: AWS WAF can be utilized in conjunction with AWS Shield for mitigating Distributed Denial of Service (DDoS) attacks. Users can create rules that help in filtering traffic patterns and volumes that are typically indicative of DDoS, thus preserving application availability and performance.
4. **Controlling Bot Traffic**: AWS WAF helps in distinguishing between legitimate and malicious bot traffic. Users can create rules to allow, block, or monitor web request patterns identified as automated bot interactionsâprotecting against scrapping, fraud, and abuse without impacting user experience.
5. **Country-based Access Control**: Businesses operating in multiple jurisdictions can use AWS WAF to implement geo-blocking or geo-allow policies. This enables restricting or allowing access to web applications based on the geographic location of the request, aiding in compliance with regional regulations.

## How AWS WAF is priced

AWS WAF utilizes a request-based pricing model complemented by additional fees for optional managed rules, with costs accruing based on the volume of web requests and the use of managed rule groups.

- **Web ACL, Rule, and Request Pricing**: AWS WAF charges for each web ACL created, each rule created per web ACL, and the number of web requests processed by the web ACL. Pricing may vary by AWS Region, and monthly fees are prorated hourly.
- **Managed Rules Pricing**: In addition to request-based pricing, using AWS managed rules or third-party rules from the AWS Marketplace incurs additional costs. These are typically charged on a monthly basis per rule group that you add to your web ACL.
- **Additional Capacity and Body Inspection**: AWS WAF charges an additional $0.20 per million requests for each 500 WCUs used beyond the default allocation of 1,500, and $0.30 per million requests for each additional 16 KB analyzed beyond the default body inspection limit.
- **CAPTCHA and Challenge Pricing**: CAPTCHA attempts and Challenge responses incur separate charges; standard Allow, Block, and Count actions have no additional action charge.
- **Bot Control Pricing**: Bot Control has subscription and request fees in addition to base AWS WAF charges. Common Bot Control includes the first 10 million requests per month for free, while Targeted Bot Control includes the first 1 million requests per month for free.
- **Fraud Control Pricing**: Account Takeover Prevention and Account Creation Fraud Prevention charge request fees for analyzed requests and a $10 monthly subscription per web ACL for each managed rule group used.
- **DDoS Protection Pricing**: AWS WAF Layer 7 DDoS Protection is billed per web ACL per month, prorated hourly, and per million requests.
- **CloudFront Flat-Rate Plans**: AWS WAF is also included in CloudFront flat-rate website delivery and security plans for a monthly price with no overage charges.

## Services AWS WAF works with

- **[Amazon CloudFront](https://blowstack.com/tools/cloud-services-hub/amazon-cloudfront)**: AWS WAF can be deployed with Amazon CloudFront to help protect edge locations and deliver secure content to viewers with low latency and high transfer speeds.
- **[Amazon API Gateway](https://blowstack.com/tools/cloud-services-hub/amazon-api-gateway)**: AWS WAF associates a web ACL with an API Gateway REST API stage to inspect incoming requests. Rules can block malicious payloads, restrict source IP addresses, or rate-limit requests before they reach the API.
- **[Amazon Athena](https://blowstack.com/tools/cloud-services-hub/amazon-athena)**: AWS WAF request logs stored in Amazon S3 can be queried with Athena using tables defined for the WAF log format. This lets you investigate blocked requests, identify frequently targeted paths, and evaluate rule matches with SQL.
- **[Amazon Bedrock AgentCore](https://blowstack.com/tools/cloud-services-hub/amazon-bedrock-agentcore)**: AWS WAF protects Bedrock AgentCore Gateway endpoints through an associated web ACL. Its rules inspect incoming requests and can block malicious traffic or limit excessive requests to the gateway.
- **[Amazon CloudWatch](https://blowstack.com/tools/cloud-services-hub/amazon-cloudwatch)**: AWS WAF publishes traffic and rule metrics to CloudWatch and can deliver detailed request logs to CloudWatch Logs. You can create alarms for increases in blocked requests and use Logs Insights to investigate matching traffic.
- **[Amazon Cognito](https://blowstack.com/tools/cloud-services-hub/amazon-cognito)**: AWS WAF associates a web ACL with a Cognito user pool to inspect supported requests to its endpoints. This can restrict suspicious sign-up and sign-in traffic using IP restrictions, rate-based rules, and other request filters.
- **[Amazon Data Firehose](https://blowstack.com/tools/cloud-services-hub/amazon-kinesis-data-firehose)**: AWS WAF can send request logs to a Data Firehose delivery stream. Firehose buffers and delivers those records to a configured destination for storage or security analysis.
- **[Amazon Elastic Container Service (Amazon ECS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-container-service-(amazon-ecs))**: AWS WAF protects HTTP and HTTPS traffic to ECS services through a WAF-enabled Application Load Balancer. The load balancer applies the associated web ACL before forwarding requests to the service's container tasks.
- **[Amazon Elastic Kubernetes Service (Amazon EKS)](https://blowstack.com/tools/cloud-services-hub/amazon-elastic-kubernetes-service-(amazon-eks))**: AWS WAF can protect EKS applications exposed through an Application Load Balancer managed by the AWS Load Balancer Controller. An Ingress annotation specifies the WAF web ACL that the controller associates with the load balancer.
- **[Amazon EventBridge](https://blowstack.com/tools/cloud-services-hub/amazon-eventbridge)**: AWS WAF management API activity recorded by CloudTrail can match EventBridge rules. For example, a rule can route web ACL changes to a notification or automated review workflow.
- **[Amazon OpenSearch Service](https://blowstack.com/tools/cloud-services-hub/amazon-opensearch-service)**: AWS WAF logs can be delivered through Data Firehose to OpenSearch Service for indexing and analysis. This supports dashboards and investigations of blocked requests, client IP addresses, and rule matches.
- **[Amazon S3](https://blowstack.com/tools/cloud-services-hub/amazon-s3)**: AWS WAF can deliver request logs directly to an S3 bucket. These logs provide a durable record of inspected requests for security investigations, retention, and downstream analysis.
- **[Amazon Security Lake](https://blowstack.com/tools/cloud-services-hub/amazon-security-lake)**: AWS WAF is a supported Security Lake source, allowing its request logs to be collected and normalized into the Open Cybersecurity Schema Framework format. This makes WAF activity available alongside other security data for centralized investigation.
- **[AWS Amplify](https://blowstack.com/tools/cloud-services-hub/aws-amplify)**: AWS WAF associates a web ACL with an Amplify Hosting application to inspect requests before they reach the hosted application. Managed and custom rules can filter common exploits, unwanted bots, and excessive traffic.
- **[AWS App Runner](https://blowstack.com/tools/cloud-services-hub/aws-app-runner)**: AWS WAF associates a web ACL with an App Runner service to inspect incoming web requests. You can apply managed rules, IP restrictions, and rate-based protections without changing the application code.
- **[AWS AppSync](https://blowstack.com/tools/cloud-services-hub/aws-appsync)**: AWS WAF associates a web ACL with an AppSync GraphQL API to filter requests before AppSync processes them. Rules can inspect request contents, block malicious patterns, and limit abusive traffic.
- **[AWS Audit Manager](https://blowstack.com/tools/cloud-services-hub/aws-audit-manager)**: AWS WAF configuration evaluations from AWS Config and API activity from CloudTrail can contribute evidence to Audit Manager assessments. This helps document firewall configuration and changes for applicable security controls.
- **[AWS CloudFormation](https://blowstack.com/tools/cloud-services-hub/aws-cloudformation)**: AWS WAF resources can be provisioned with CloudFormation, including web ACLs, rule groups, IP sets, regular expression pattern sets, logging configurations, and supported resource associations. Templates make firewall policies repeatable and version-controlled.
- **[AWS CloudTrail](https://blowstack.com/tools/cloud-services-hub/aws-cloudtrail)**: AWS WAF management API calls are recorded by CloudTrail. These records identify who created or changed web ACLs, rules, logging settings, and resource associations.
- **[AWS Config](https://blowstack.com/tools/cloud-services-hub/aws-config)**: AWS Config records supported AWS WAF resource configurations and evaluates them with managed or custom rules. Checks can identify issues such as missing web ACL rules or disabled request logging.
- **[AWS Control Tower](https://blowstack.com/tools/cloud-services-hub/aws-control-tower)**: AWS WAF configurations can be governed with Control Tower proactive controls that evaluate CloudFormation deployments. These controls can require supported web ACLs and rule groups to contain rules before deployment proceeds.
- **[AWS Firewall Manager](https://blowstack.com/tools/cloud-services-hub/aws-firewall-manager)**: AWS WAF protections can be centrally deployed and maintained through Firewall Manager policies across accounts in an organization. Firewall Manager can associate web ACLs with in-scope resources and remediate resources that do not comply with the policy.
- **[AWS Identity and Access Management (IAM)](https://blowstack.com/tools/cloud-services-hub/aws-identity-and-access-management-(iam))**: AWS WAF uses IAM policies to control access to its management operations and resources. Permissions can distinguish administrators who modify web ACLs from users who only inspect configurations or traffic information.
- **[AWS Key Management Service (AWS KMS)](https://blowstack.com/tools/cloud-services-hub/aws-key-management-service-(aws-kms))**: AWS WAF logs delivered to Amazon S3 can be encrypted with a customer-managed KMS key. The key policy must permit the log-delivery service to use the key for delivery.
- **[AWS Marketplace](https://blowstack.com/tools/cloud-services-hub/aws-marketplace)**: AWS WAF supports managed rule groups offered by sellers through AWS Marketplace. After subscribing, you can add a seller's rule group to a web ACL and configure how its matches affect incoming requests.
- **[AWS Resource Groups and Tag Editor](https://blowstack.com/tools/cloud-services-hub/aws-resource-groups-and-tag-editor)**: AWS WAF resources support tags that can be used with Resource Groups and Tag Editor to organize and manage supported firewall resources. For example, tags can group an application's web ACLs and rule groups by environment or owner.
- **[AWS Security Hub](https://blowstack.com/tools/cloud-services-hub/aws-security-hub)**: AWS WAF resources are evaluated by Security Hub security controls for configuration issues such as missing rules and disabled logging. The resulting findings help track firewall-related compliance problems alongside other security findings.
- **[AWS Shield](https://blowstack.com/tools/cloud-services-hub/aws-shield)**: AWS WAF works with Shield Advanced to mitigate application-layer DDoS attacks. Shield Advanced can automatically manage mitigation rules in an associated web ACL to respond to detected attacks.
- **[AWS Systems Manager](https://blowstack.com/tools/cloud-services-hub/aws-systems-manager)**: AWS WAF resources can be remediated with Systems Manager Automation runbooks, including a runbook that associates a web ACL with a supported resource. AWS Config remediation can invoke this automation when a resource lacks the required protection.
- **[AWS Verified Access](https://blowstack.com/tools/cloud-services-hub/aws-verified-access)**: AWS WAF associates a web ACL with a Verified Access instance to inspect requests to applications published through its endpoints. WAF request filtering complements Verified Access identity- and device-based access decisions.
- **[Elastic Load Balancing (ELB)](https://blowstack.com/tools/cloud-services-hub/elastic-load-balancing-(elb))**: AWS WAF associates a regional web ACL with an Application Load Balancer to inspect HTTP and HTTPS requests before they reach its targets. The web ACL can block exploits, enforce request-rate limits, and apply bot protections across applications behind the load balancer.

## AWS WAF exam questions

Real practice exam questions on AWS WAF, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A company hosts a public web application behind an Application Load Balancer. The security team has identified requests containing SQL injection attempts in URL query strings. The company needs to block these requests before they reach the application without changing the application code. Which solution best meets these requirements?

**Correct answer:** Associate an AWS WAF web ACL with the Application Load Balancer and enable SQL injection protection rules with a block action.

**Explanation:** AWS WAF can inspect web request components, including URL query strings, for SQL injection patterns. A web ACL associated with the Application Load Balancer can block matching requests before they reach the application.

### Question 2 (SOA-C03)

**Question:**

A company runs a public application behind an Application Load Balancer (ALB) in a single AWS account. The ALB is protected by AWS Shield Advanced and has an AWS WAF web ACL associated with it. Automatic application-layer DDoS mitigation is enabled in observation-only mode.

During an audit, a CloudOps engineer confirms that attack-specific rules were generated during a recent HTTP flood, but matching requests were counted rather than blocked. Company policy now requires these automatically generated mitigations to block matching requests during attacks. The company must retain its existing web ACL rules and avoid maintaining fixed request-rate thresholds.

Which change should the engineer make?

**Correct answer:** Update the ALB's Shield Advanced automatic application-layer DDoS mitigation configuration to use the Block action instead of Count.

**Explanation:** Shield Advanced automatic application-layer DDoS mitigation supports Count and Block actions. Changing its action to Block makes its automatically managed attack-specific rules enforce mitigation without requiring the company to maintain fixed rate thresholds or replace existing web ACL rules.

### Question 3 (SAP-C03)

**Question:**

A financial services company runs three independently managed web applications in one VPC. Each application has a dedicated internet-facing Application Load Balancer (ALB), EC2 application instances in private subnets, and an Amazon RDS database in isolated subnets. The application tiers share private subnets, and the databases share isolated subnets. No application requires connectivity to another application's resources.

Currently, all application instances and databases use a shared security group that allows all traffic from the VPC CIDR. An assessment finds that an attacker who exploits one application could connect directly to the other applications and databases. Moving resources to different subnets or VPCs is not permitted during the remediation window.

The company requires a design that blocks common malicious HTTP requests before they reach application instances, prevents a compromised instance from establishing connections to another application's instances or database, and records accepted and rejected network flows for investigation. Legitimate ALB-to-application and application-to-database connections must continue to work. The design must assume that some attacks can evade HTTP request filtering.

Which solution meets these requirements?

**Correct answer:** Associate an AWS WAF web ACL with each ALB. Replace the shared security group with separate ALB, application, and database security groups for each application. Permit application ingress only from its ALB security group on required ports and database ingress only from its application security group on the database port. Remove other workload ingress permissions. Enable VPC Flow Logs for accepted and rejected traffic.

**Explanation:** This combines application-layer filtering, independent workload-level segmentation, and network visibility. Dedicated security groups prevent a compromised instance from initiating connections to another application's instances or database, even if an exploit evades AWS WAF. Security group references preserve the required communication paths, and stateful filtering permits their return traffic. VPC Flow Logs provide connection metadata for investigation.

### Question 4 (SAA-C03)

**Question:**

A company runs a public ticket-sales application behind an Application Load Balancer (ALB). The ALB is protected by AWS Shield Advanced and has an associated AWS WAF web ACL. During ticket releases, legitimate request volumes increase sharply. Recent application-layer DDoS attacks have used changing source IP addresses, making manually maintained IP block lists ineffective.

The company wants a managed solution that identifies application-layer DDoS attacks, automatically deploys attack-specific blocking rules, and removes those rules when the attacks end. The operations team must not need to create rules for each attack.

Which solution meets these requirements?

**Correct answer:** Enable Shield Advanced automatic application-layer DDoS mitigation for the ALB and configure its rule action to Block.

**Explanation:** Shield Advanced automatic application-layer DDoS mitigation uses AWS WAF to deploy rules tailored to detected attacks. In Block mode, these rules mitigate matching attack traffic. Shield Advanced manages the rules throughout the attack lifecycle and removes attack-specific rules when they are no longer needed.

### Question 5 (SCS-C03)

**Question:**

A company correlates AWS WAF request logs with logs from a third-party edge firewall in a centralized security analytics platform. An AWS Lambda function converts both sources into OCSF events. The converted events pass schema validation, but an investigation finds incorrect enforcement results:

• AWS WAF blocked a request and returned a configured custom HTTP 200 response. The normalized event indicates that the request was allowed.
• The third-party firewall allowed a request that subsequently received HTTP 403 from the application. The normalized event indicates that the firewall blocked the request.

The analysts need one source-independent query that identifies requests blocked by either edge security control while preserving the actual HTTP response codes for investigation.

Which change should a security engineer make to the normalization logic?

**Correct answer:** Map both sources to an appropriate OCSF HTTP activity class. Derive the normalized action or disposition from each control's enforcement decision, and retain HTTP response codes in the HTTP response attributes.

**Explanation:** OCSF normalization must preserve source semantics, not merely satisfy schema validation. AWS WAF's Block action and the vendor's enforcement decision determine whether the edge control blocked a request. An HTTP 200 custom block response does not mean the request was allowed, and an application's HTTP 403 does not mean the edge firewall blocked it. Consistent action or disposition mappings support a common query across both sources.

### Question 6 (DOP-C02)

**Question:**

A company is deploying a partner-facing API on Amazon EC2 instances behind an internet-facing Application Load Balancer (ALB). An AWS WAF web ACL associated with the ALB blocks malicious HTTP requests. Instance security groups permit application traffic only from the ALB security group.

Partners must authenticate by presenting client certificates issued by the company's existing private certificate authority. The ALB must reject connections with untrusted or expired client certificates before forwarding requests. Partners must also be able to validate the API's server certificate by using standard public trust stores. Server certificate renewal and deployment must be automatic. Application code must remain unchanged, and authenticated partner requests must still undergo web ACL inspection.

Which solution meets these requirements with the LEAST operational overhead?

**Correct answer:** Request a DNS-validated public certificate through ACM, retain its public DNS validation records, and associate it with the ALB HTTPS listener. Configure mutual TLS verify mode with an ALB trust store containing the private CA certificate chain from Amazon S3. Retain the web ACL association and existing security group restrictions.

**Explanation:** ACM manages renewal and deployment of an eligible Amazon-issued public certificate associated with the ALB when DNS validation remains available. The public certificate authenticates the server, while the separate ALB trust store establishes which client certificate issuers are trusted. Mutual TLS verify mode validates client certificates, including their trust chain and expiration by default. Successfully authenticated requests still pass through AWS WAF, providing independent transport, client-authentication, application-filtering, and network controls.

### Question 7 (ANS-C01)

**Question:**

A company protects an HTTPS application with an AWS WAF web ACL associated with an Application Load Balancer. The web ACL evaluates the AWS Managed Rules Common Rule Set before a separate SQL injection rule group. During threat modeling, engineers identify that the POST /preview endpoint must accept user-supplied HTML, which the application sanitizes before rendering. Legitimate requests to this endpoint trigger the Common Rule Set's CrossSiteScripting_BODY rule.

The security team approves an exception only for this rule on the exact /preview URI path. Every other managed rule must retain its existing protection on all paths, and CrossSiteScripting_BODY must continue blocking matching requests on other paths. Requests to /preview must also continue through subsequent web ACL rules.

Which configuration meets these requirements?

**Correct answer:** Override only CrossSiteScripting_BODY to Count. Immediately after the Common Rule Set, add a Block rule that matches the label emitted by CrossSiteScripting_BODY AND a URI path that is not exactly /preview. Leave all other rules unchanged.

**Explanation:** The individual Count override preserves the rule's inspection and labeling without terminating evaluation. The subsequent label-based rule restores blocking for matching requests on every path except /preview. Other rules in the managed group retain their actions, and preview requests continue to subsequent rules, including SQL injection inspection.

## Practice AWS WAF in a full exam

Questions on AWS WAF in each practice exam, with every answer option and an explanation for each:

- [SCS-C03](https://blowstack.com/practice-exams/aws-certified-security-specialty): 32 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 11 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 10 questions
- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 9 questions
- [DOP-C02](https://blowstack.com/practice-exams/aws-certified-devops-engineer-professional): 6 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 5 questions
- [SAP-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-professional): 3 questions

## What is AWS WAF

AWS WAF, or Amazon Web Services Web Application Firewall, plays a pivotal role in safeguarding web applications from a myriad of threats over the internet. It serves as a formidable barrier between your web application and common threats such as SQL injection, cross-site scripting (XSS), and other exploits that could compromise the security, availability, or resilience of your application. AWS WAF is deeply integrated into the Amazon ecosystem, providing a seamless and highly customizable defense mechanism for applications hosted on services like Amazon CloudFront, the Amazon API Gateway, and AWS AppSync.

AWS WAF can also protect Amazon Cognito user pools, AWS App Runner services, Amazon Bedrock AgentCore Gateway, AWS Verified Access instances, and AWS Amplify.

One of the primary advantages of AWS WAF is its flexibility. Users can create custom security rules that precisely target and mitigate specific threats. This means that in addition to using predefined rules and rule groups that AWS provides and maintains, which cover common web vulnerabilities and attack patterns, users can tailor their security posture to meet the unique demands of their application. These custom rules can be based on a variety of conditions, including HTTP headers, IP addresses, HTTP bodies, or URI strings, enabling a granular approach to threat mitigation. AWS WAF operates at the application layer (Layer 7 in the OSI model), allowing it to inspect the content of HTTP/S traffic and make informed decisions on whether to allow, block, or count the traffic based on the conditions defined in the rules. This is instrumental in preventing the exploitation of vulnerabilities within the application or the underlying infrastructure.

A web ACL also has a default action that allows or blocks requests that its rules have not already allowed or blocked.

AWS WAF Bot Control is a managed rule group for monitoring, blocking, or rate-limiting automated traffic such as scrapers, scanners, and crawlers while allowing common bots such as status monitors and search engines.

AWS WAF Fraud Control consists of Account Takeover Prevention and Account Creation Fraud Prevention, providing managed rules that protect login and sign-up pages against credential stuffing, credential cracking, and fake account creation attacks.

AWS WAF also supports CAPTCHA and silent challenge controls for requests matching your criteria to help reduce bot traffic.

Moreover, AWS WAF is capable of providing real-time visibility into the traffic, thereby enabling timely and informed reactions to emerging threats. This visibility is not just limited to threats but extends to monitoring legitimate access, helping in understanding traffic patterns and potentially uncovering insights that can be leveraged to optimize application performance and user experience. Moreover, AWS WAF can be configured to provide automated responses to certain types of threats, thus enhancing the ability to quickly mitigate potential attacks without the need for manual intervention.

AWS WAF application layer (L7) DDoS protection is a managed rule group that establishes a normal traffic baseline and uses machine learning to detect anomalies and automatically apply mitigation rules. It protects applications on Amazon CloudFront, Application Load Balancer, and API Gateway.

The service integrates well with other AWS services such as Amazon CloudWatch for logging and monitoring and AWS Lambda for executing custom functions in response to certain triggers, offering a comprehensive security solution that is not only reactive but also proactive.

Another noteworthy aspect of AWS WAF is its cost-effectiveness. Pricing is based on the number of web access control lists (web ACLs) created, the number of rules added per web ACL, and the number of web requests received. This pay-as-you-go model ensures that businesses of all sizes can access robust web application security without a significant upfront investment.

Flat-rate pricing plans provide an alternative to pay-as-you-go, with plans selected according to the total number of requests and desired features.

In the landscape of cyber threats that evolves every day, AWS WAF stands out as a critical tool in the arsenal of web application protection. Its adaptability, integration capabilities, and cost-efficiency make it an attractive solution for businesses looking to protect their web applications from the ever-present and ever-evolving threats of the digital world.

## Learn AWS WAF in lessons

19 short lessons on AWS WAF in 6 certification courses.

- CLF-C02: AWS Firewall Manager vs AWS WAF: management and filtering (Premium), https://app.blowstack.com/lessons/aws-firewall-manager-vs-aws-waf-management-and-filtering-clf-c02
- SOA-C03: AWS Network Firewall and AWS WAF: network versus web protection (Premium), https://app.blowstack.com/lessons/aws-network-firewall-and-aws-waf-network-versus-web-protection-soa-c03
- SAP-C03: AWS Network Firewall vs AWS WAF: network and web application protection (Premium), https://app.blowstack.com/lessons/aws-network-firewall-vs-aws-waf-network-and-web-application-protection-sap-c03
- SAA-C03: AWS WAF: filtering requests with web ACLs (Premium), https://app.blowstack.com/lessons/aws-waf-filtering-requests-with-web-acls-saa-c03
- SCS-C03: AWS Shield vs AWS WAF: DDoS protection and request filtering (Premium), https://app.blowstack.com/lessons/aws-shield-vs-aws-waf-ddos-protection-and-request-filtering-scs-c03
- DOP-C02: AWS WAF: automated web ACL deployment (Premium), https://app.blowstack.com/lessons/aws-waf-automated-web-acl-deployment-dop-c02

## Concepts related to AWS WAF

- [Defense in Depth](https://blowstack.com/tools/cloud-concepts-hub/defense-in-depth): Defense in Depth is a security strategy that uses multiple complementary layers of protection so that failure of one control does not expose the entire system.
- [DDoS Mitigation](https://blowstack.com/tools/cloud-concepts-hub/ddos-mitigation): DDoS mitigation combines traffic filtering, distributed capacity, and resilient architecture to keep services available during distributed denial-of-service attacks.
- [Rate Limiting](https://blowstack.com/tools/cloud-concepts-hub/rate-limiting): Rate limiting controls how many requests or operations a client or workload can perform within a defined period.
- [Client Fingerprinting](https://blowstack.com/tools/cloud-concepts-hub/client-fingerprinting): Client fingerprinting identifies or groups requesting clients by combining observable connection, protocol, browser, or device characteristics into a recognizable signature.
- [Geofencing](https://blowstack.com/tools/cloud-concepts-hub/geofencing): Geofencing defines geographic boundaries and uses location information to control access or trigger actions when a client or device is inside or outside those boundaries.
- [SQL Injection](https://blowstack.com/tools/cloud-concepts-hub/sql-injection): SQL injection is an application vulnerability in which untrusted input changes the structure or meaning of a database query.
- [Threat Modeling](https://blowstack.com/tools/cloud-concepts-hub/threat-modeling): Threat modeling is a structured process for identifying how a system could be attacked and selecting controls and monitoring to reduce the resulting risks.
- [OWASP Top 10](https://blowstack.com/tools/cloud-concepts-hub/owasp-top-10): The OWASP Top 10 is a periodically updated awareness document describing major categories of security risk in web applications.
- [Cross-Site Scripting](https://blowstack.com/tools/cloud-concepts-hub/cross-site-scripting): Cross-site scripting is a web application vulnerability that allows attacker-controlled code to execute in a user's browser within a trusted application's security context.
- [Open Cybersecurity Schema Framework (OCSF)](https://blowstack.com/tools/cloud-concepts-hub/open-cybersecurity-schema-framework-(ocsf)): Open Cybersecurity Schema Framework (OCSF) is an open, vendor-neutral framework for representing cybersecurity events in a common schema.
- [Content Delivery Networks](https://blowstack.com/tools/cloud-concepts-hub/content-delivery-networks): Content delivery networks are geographically distributed systems that deliver content through edge locations near users, often caching responses to reduce latency and origin traffic.
- [Deep Packet Inspection](https://blowstack.com/tools/cloud-concepts-hub/deep-packet-inspection): Deep Packet Inspection is the examination of packet contents and application protocols, beyond basic network and transport headers, to identify traffic and enforce security policies.
- [Input Sanitization](https://blowstack.com/tools/cloud-concepts-hub/input-sanitization): Input sanitization is the controlled transformation of untrusted input to remove or neutralize unsafe content before an application processes it.
- [Security](https://blowstack.com/tools/cloud-concepts-hub/security): Security is the protection of systems, data, and operations against unauthorized access, misuse, disruption, and loss.
- [Trust Boundaries](https://blowstack.com/tools/cloud-concepts-hub/trust-boundaries): Trust boundaries are points where data, requests, or identities cross between environments with different security assumptions or levels of control.
