Prompt

Fortinet FortiWeb is blocking too much traffic

Technology / Cybersecurity1 observationLast seen Oct 29, 2026

Latest observation

Oct 29, 2026OpenAI APIWeb search: off

If FortiWeb is blocking legitimate traffic, the goal is usually to identify which protection is firing, confirm whether it’s a false positive, and then tune the policy safely rather than just disabling protections.

Quick things to check

  1. Find the block reason

    • Review FortiWeb logs for the blocked requests.
    • Note the policy, signature/attack category, source IP, URL, and rule name.
  2. Determine if it’s a false positive

    • Compare blocked requests with normal application behavior.
    • Check if the app sends unusual query strings, JSON bodies, special characters, large headers, or file uploads.
  3. Tune the relevant protection Common causes:

    • OWASP signature/attack signatures
    • Parameter validation
    • Bot mitigation
    • CSRF protection
    • IP reputation / geo blocking
    • Rate limiting
    • File upload controls
  4. Use exceptions instead of global disable

    • Exempt specific URLs, parameters, clients, or source IPs.
    • Narrow exceptions to the smallest possible scope.
  5. Test in monitor/log-only mode if possible

    • For the affected policy, temporarily switch certain checks to monitoring so you can observe impact before enforcing changes.
  6. Check learning/auto-learning settings

    • If FortiWeb is using learned profiles, retrain or update the baseline after app changes.

Practical troubleshooting flow

  • Pick one blocked request from the logs.
  • Identify the exact rule that matched.
  • Reproduce the request in a test environment.
  • Decide whether to:
    • relax the rule,
    • add an exception,
    • adjust a threshold,
    • or keep the block if it’s real malicious traffic.

Safe tuning suggestions

  • Whitelist by URL path + parameter, not entire site, when possible.
  • Raise thresholds gradually for rate-based protections.
  • For APIs, verify JSON schema/expected methods/headers.
  • For uploads, ensure allowed file types and size limits match the application.

If you want, I can help you narrow it down

Send me any of these and I’ll help interpret them:

  • the FortiWeb log entry
  • the attack/signature name
  • the URL or parameter being blocked
  • whether this is a web app, API, or upload form

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.