AWS WAF Logging Configured

Severity: high
Compliance: PCI 10.5.5
Tags: AWS, Monitoring, Logging, Security Control, Defense Evasion:Impair Defenses
Reference: https://docs.aws.amazon.com/waf/latest/developerguide/logging.html
Source: github.com/panther-labs/panther-analysis

Ensures that AWS WAF logging is enabled and that the logs are being sent to a valid destination (S3, CloudWatch, or Kinesis Firehose). Without logging, visibility into WAF activity is severely limited, increasing the risk of undetected attacks.

MITRE ATT&CK coverage

Tactic	Techniques
Stealth	`T1562` Impair Defenses

Rule body yaml

AnalysisType: policy
Filename: aws_waf_logging_configured.py
PolicyID: "AWS.WAF.LoggingConfigured"
DisplayName: "AWS WAF Logging Configured"
Enabled: true
ResourceTypes:
  - AWS.WAF.Regional.WebACL
  - AWS.WAF.WebACL
Tags:
  - AWS
  - Monitoring
  - Logging
  - Security Control
  - Defense Evasion:Impair Defenses
Reports:
  PCI:
    - 10.5.5
  MITRE ATT&CK:
    - TA0005:T1562
Severity: High
Description: >
  Ensures that AWS WAF logging is enabled and that the logs are being sent to a valid destination (S3, CloudWatch, or Kinesis Firehose). Without logging, visibility into WAF activity is severely limited, increasing the risk of undetected attacks.
Runbook: >
  Ensure AWS WAF logging is configured to at least one valid destination such as an Amazon S3 bucket, Amazon CloudWatch Logs, or Amazon Kinesis Data Firehose. Refer to the AWS WAF logging documentation for setup instructions.
Reference: https://docs.aws.amazon.com/waf/latest/developerguide/logging.html
Tests:
  - Name: WAF Logging Configured to CloudWatch Logs
    ExpectedResult: true
    Resource:
      LoggingConfiguration:
        LogDestinationConfigs:
          - "arn:aws:logs:us-west-2:123456789012:log-group:example-log-group"
        RedactedFields: null

  - Name: WAF Logging Configured to S3
    ExpectedResult: true
    Resource:
      LoggingConfiguration:
        LogDestinationConfigs:
          - "arn:aws:s3:::example-bucket/waf-logs/"
        RedactedFields: null

  - Name: WAF Logging Configured to Kinesis Firehose
    ExpectedResult: true
    Resource:
      LoggingConfiguration:
        LogDestinationConfigs:
          - "arn:aws:firehose:us-west-2:123456789012:deliverystream/example-firehose"
        RedactedFields: null

  - Name: WAF Logging Not Configured
    ExpectedResult: false
    Resource:
      LoggingConfiguration: null

  # Edge Case 1: Malformed CloudWatch Logs ARN
  - Name: WAF Logging Configured with Malformed CloudWatch Logs ARN
    ExpectedResult: false
    Resource:
      LoggingConfiguration:
        LogDestinationConfigs:
          - "arn:aws:logs:us-west-2:123456789012"  # Incorrect ARN format
        RedactedFields: null

  # Edge Case 2: Malformed S3 ARN
  - Name: WAF Logging Configured with Malformed S3 ARN
    ExpectedResult: false
    Resource:
      LoggingConfiguration:
        LogDestinationConfigs:
          - "arn:aws:s3::example-bucket-wrong-format"  # Incorrect ARN format
        RedactedFields: null

  # Edge Case 3: Multiple Valid Logging Destinations (S3 and Kinesis Firehose)
  - Name: WAF Logging Configured to Both S3 and Kinesis Firehose
    ExpectedResult: true
    Resource:
      LoggingConfiguration:
        LogDestinationConfigs:
          - "arn:aws:s3:::example-bucket/waf-logs/"
          - "arn:aws:firehose:us-west-2:123456789012:deliverystream/example-firehose"
        RedactedFields: null

  # Edge Case 4: Malformed Kinesis Firehose ARN
  - Name: WAF Logging Configured with Malformed Kinesis Firehose ARN
    ExpectedResult: false
    Resource:
      LoggingConfiguration:
        LogDestinationConfigs:
          - "arn:aws:firehose:us-west-2"  # Incorrect ARN format
        RedactedFields: null

Detection logic

Condition

LoggingConfiguration not is_not_null

This rule also runs imperative logic the parser cannot express as a filter; the conditions above are the structured part it could extract.

Exclusions

Top-level NOT(...) conjuncts: predicates this rule actively suppresses.

Field	Kind	Excluded values
`LoggingConfiguration`	is_not_null	(no value, null check)

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)