WAFv2 WebACL Rule Group Logging Should Be Enabled

Using Console

To remediate the misconfiguration of WAFv2 WebACL Rule Group Logging not being enabled in AWS CloudWatch using the AWS Management Console, follow these steps:

Sign in to the AWS Management Console: Go to https://aws.amazon.com/ and sign in to your AWS account.
Navigate to AWS WAF & Shield console: Click on the ‘Services’ dropdown menu at the top left corner of the console, then select ‘WAF & Shield’ under the Security, Identity, & Compliance section.
Select the desired WebACL: In the AWS WAF & Shield console, click on ‘Web ACLs’ from the left-hand menu, then select the WebACL that you want to enable logging for.
Edit the WebACL: Click on the WebACL that you have selected, then click on the ‘Edit’ button to make changes to the WebACL configuration.
Enable Logging for the Rule Group: In the WebACL configuration page, scroll down to the ‘Logging configuration’ section. Ensure that ‘Log’ is enabled for the desired rule group(s) that you want to log.
Save Changes: Once you have enabled logging for the rule group(s), click on the ‘Save’ button to save the changes to the WebACL configuration.
Verify Logging Configuration: After saving the changes, you can verify that logging is enabled for the rule group(s) by checking the ‘Logging configuration’ section in the WebACL configuration page.

By following these steps, you have successfully remediated the misconfiguration of WAFv2 WebACL Rule Group Logging not being enabled in AWS CloudWatch using the AWS Management Console.

Using CLI

To remediate the misconfiguration for WAFv2 WebACL Rule Group Logging in AWS CloudWatch using AWS CLI, follow these steps:

List all the WAFv2 WebACLs in your AWS account to identify the WebACL Rule Group for which logging needs to be enabled:

aws wafv2 list-web-acls

Get the details of the specific WebACL Rule Group that needs logging enabled:

aws wafv2 get-web-acl --name <WebACL-Name>

Enable logging for the identified WebACL Rule Group by updating its configuration:

aws wafv2 update-web-acl --name <WebACL-Name> --scope REGIONAL --default-action ALLOW --visibility-config SampledRequestsEnabled=true,CloudWatchMetricsEnabled=true,ManagedByFirewallManager=false --rules 'Action=ALLOW,Priority=1,RuleLabels=[{Name=SampleRuleLabel}],Statement={ByteMatchStatement={FieldToMatch={UriPath={}},PositionalConstraint=EXACTLY,SearchString="example.com"},VisibilityConfig={SampledRequestsEnabled=true,CloudWatchMetricsEnabled=true,ManagedByFirewallManager=false}'

Verify that the logging is enabled for the WebACL Rule Group:

aws wafv2 get-web-acl --name <WebACL-Name>

By following these steps, you can successfully remediate the misconfiguration and enable logging for the WAFv2 WebACL Rule Group in AWS CloudWatch using AWS CLI.

Using Python

To remediate the misconfiguration of WAFv2 WebACL Rule Group Logging not being enabled in AWS CloudWatch using Python, you can use the AWS SDK for Python (Boto3) to programmatically enable logging for the WebACL Rule Group. Below are the step-by-step instructions to remediate this issue:

Install Boto3: Make sure you have the Boto3 library installed. You can install it using pip:

pip install boto3

Configure AWS Credentials: Ensure that you have configured your AWS credentials either by setting environment variables or using AWS CLI aws configure command.
Write a Python script: Create a Python script with the following code to enable logging for the WAFv2 WebACL Rule Group:

import boto3

# Initialize the WAFv2 client
wafv2_client = boto3.client('wafv2')

# Specify the WebACL ARN for which you want to enable logging
web_acl_arn = 'YOUR_WEB_ACL_ARN'

# Enable logging for the specified WebACL
response = wafv2_client.put_logging_configuration(
    LoggingConfiguration={
        'ResourceArn': web_acl_arn,
        'LogDestinationConfigs': [
            'arn:aws:logs:REGION:ACCOUNT_ID:log-group:LOG_GROUP_NAME'
        ],
        'RedactedFields': []
    }
)

print("Logging enabled for WebACL Rule Group with ARN:", web_acl_arn)

Replace the placeholders:
- Replace YOUR_WEB_ACL_ARN with the ARN of the WebACL Rule Group for which you want to enable logging.
- Replace REGION, ACCOUNT_ID, and LOG_GROUP_NAME in the LogDestinationConfigs with your AWS region, account ID, and the name of the CloudWatch Logs log group where you want to store the logs.
Run the Python script: Execute the Python script to enable logging for the specified WebACL Rule Group. Make sure the script runs successfully without any errors.

By following these steps and running the Python script, you can remediate the misconfiguration of WAFv2 WebACL Rule Group Logging not being enabled in AWS CloudWatch.

Using Terraform

# Kinesis Data Firehose delivery stream that sends WAF logs to CloudWatch Logs
resource "aws_cloudwatch_log_group" "waf_logs" {
  name              = "/aws/waf/WAF_LOG_GROUP_NAME" # replace with desired log group name
  retention_in_days = 30                            # adjust as needed
}

resource "aws_iam_role" "firehose_role" {
  name = "FIREHOSE_ROLE_NAME" # replace with a unique role name

  assume_role_policy = jsonencode({
    Version = "2012-10-17"
    Statement = [{
      Effect = "Allow"
      Principal = {
        Service = "firehose.amazonaws.com"
      }
      Action = "sts:AssumeRole"
    }]
  })
}

resource "aws_iam_role_policy" "firehose_to_cloudwatch" {
  name = "FIREHOSE_TO_CLOUDWATCH_POLICY_NAME" # replace with a unique policy name
  role = aws_iam_role.firehose_role.id

  policy = jsonencode({
    Version = "2012-10-17"
    Statement = [
      {
        Effect = "Allow"
        Action = [
          "logs:PutLogEvents",
          "logs:CreateLogStream",
          "logs:DescribeLogStreams"
        ]
        Resource = "${aws_cloudwatch_log_group.waf_logs.arn}:*"
      },
      {
        Effect = "Allow"
        Action = [
          "logs:DescribeLogGroups"
        ]
        Resource = "*"
      }
    ]
  })
}

resource "aws_kinesis_firehose_delivery_stream" "waf_to_cloudwatch" {
  name        = "WAF_FIREHOSE_STREAM_NAME" # replace with a unique stream name
  destination = "cloudwatch_logs"

  cloudwatch_logging_options {
    enabled         = true
    log_group_name  = aws_cloudwatch_log_group.waf_logs.name
    log_stream_name = "firehose-delivery"
  }

  cloudwatch_logs_configuration {
    role_arn        = aws_iam_role.firehose_role.arn
    log_group_name  = aws_cloudwatch_log_group.waf_logs.name
  }
}

# Enable WAFv2 Web ACL logging to the Kinesis Data Firehose stream above
resource "aws_wafv2_web_acl_logging_configuration" "waf_logging" {
  resource_arn = "WEB_ACL_ARN" # replace with the ARN of your existing WAFv2 Web ACL

  # This overwrites any existing WAF logging configuration; review current settings first.
  log_destination_configs = [
    aws_kinesis_firehose_delivery_stream.waf_to_cloudwatch.arn
  ]
}

This Terraform enables WAFv2 Web ACL logging by attaching a logging configuration that sends logs to a Kinesis Data Firehose stream, which in turn delivers them to CloudWatch Logs (matching the CLI behavior of using a Firehose destination).No existing aws_wafv2_web_acl resource will be replaced; the change adds or updates the separate aws_wafv2_web_acl_logging_configuration resource. Be aware that any existing logging configuration for that Web ACL will be overwritten.For CloudFront‑scope Web ACLs, ensure your provider "aws" is configured with region = "us-east-1".Verification: terraform plan should show aws_wafv2_web_acl_logging_configuration.waf_logging (and the Firehose/CloudWatch resources, if new) being created or updated, with log_destination_configs set to the Firehose stream ARN.

AWS Introduction

AWS Pricing

AWS Threats

AWS Misconfigurations

WAFv2 WebACL Rule Group Logging Should Be Enabled

More Info:

Risk Level

Address

Compliance Standards

Triage and Remediation

Remediation

​More Info:

​Risk Level

​Address

​Compliance Standards

​Triage and Remediation

​Remediation

​