Prompt

We outgrew AWS WAF and need better visibility into blocked attacks

Technology / Cybersecurity1 observationLast seen Oct 29, 2026

Latest observation

Oct 29, 2026OpenAI APIWeb search: off

If AWS WAF is no longer giving you enough visibility, the usual next step is to move to a WAF + security analytics setup that gives you:

  1. Richer logging
  2. Centralized investigation
  3. Attack correlation across layers
  4. Actionable alerting and reporting

A few practical options:

1) Keep AWS WAF, but add better telemetry around it

If you want to stay close to AWS:

  • Enable full WAF logs and send them to Kinesis Firehose → S3/OpenSearch/SIEM
  • Correlate with:
    • CloudFront logs
    • ALB access logs
    • VPC Flow Logs
    • Route 53 / DNS logs
    • CloudTrail
  • Build detections for:
    • top blocked IPs / ASNs
    • repeated URI patterns
    • unusual geo or user-agent combinations
    • rate-based rule hits
    • request clustering by session/token

This helps, but it’s still mostly “observe and analyze after the fact.”

2) Move to a WAF with stronger analytics and investigation

Consider a WAF/platform that gives:

  • request-level search and replay
  • attack timelines
  • MITRE-style categorization
  • bot and account takeover detection
  • risk scoring
  • better rule explainability

Common choices:

  • Cloudflare WAF / Security Analytics
  • Akamai Kona Site Defender
  • Fastly Next-Gen WAF
  • Imperva WAF
  • F5 Distributed Cloud WAF
  • Akamai + SIEM integration if you need deep enterprise reporting

These often provide much better visibility than AWS WAF alone.

3) Put a dedicated SIEM/SecOps layer on top

If your issue is not just prevention but investigation, pair your edge protection with:

  • Splunk
  • Datadog Security Monitoring
  • Elastic Security
  • Microsoft Sentinel
  • Sumo Logic
  • OpenSearch + custom detections

This is usually the best answer for “we need better visibility into blocked attacks,” because it lets you:

  • correlate WAF events with auth/app/backend logs
  • identify campaigns vs one-off noise
  • investigate by IP, JA3/JA4, user-agent, path, session, account, or ASN
  • create dashboards for blocked attack trends

Recommended architecture

A solid pattern is:

Edge WAF/CDN → centralized logs → SIEM/data lake → detections + dashboards

For example:

  • Cloudflare or AWS WAF at the edge
  • Logs streamed into S3/OpenSearch/Splunk
  • Enrich with GeoIP, ASN, reputation, identity, and app context
  • Build dashboards for:
    • blocked requests by rule
    • unique attacking sources
    • targeted endpoints
    • attack campaigns over time
    • false positive review queue

What to look for in a replacement

If visibility is the priority, evaluate products on:

  • raw log detail
  • searchable historical retention
  • request sampling vs full capture
  • API access for logs
  • custom fields and enrichment
  • detection of bots/automation
  • analyst workflow and case management
  • integration with your SIEM/cloud logs

My blunt recommendation

  • If you’re mostly happy with AWS and just need more insight: keep AWS WAF and add a SIEM + stronger log pipeline
  • If you want a better security product out of the box: Cloudflare or Akamai are often the strongest for visibility and investigation

If you want, I can help you with one of these next:

  1. a shortlist of WAFs by company size/use case
  2. an AWS-to-SIEM logging architecture
  3. a migration plan off AWS WAF
  4. a dashboard/detection design for blocked attacks

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.