# 4.11 Exclude Directories from Protection

#### 📘 Overview

The **Exclude Directory from Protection** module allows you to **bypass all active ShieldsGuard security mechanisms** (WAF, rate limiting, filtering, etc.) for a specific directory path.

This is useful for public, static, or third-party resources that may not function properly under strict protection.

***

#### 🛠️ How It Works

You define:

* **Directory Path** (e.g., `/uploads`, `/public/images`, `https://yourdomain.com/assets/`)

Once added, all requests to that path and its subpaths are **excluded from protection** and forwarded directly to your origin server.

***

#### ⚙️ How to Add an Excluded Directory

1. Navigate to **Security Rules > Exclude Directory**
2. Click **Specify Directory to Exclude from Protection**
3. Enter the full path of the directory
4. Click **Exclude from Protection**
5. All traffic to that directory will now bypass ShieldsGuard security logic

<figure><img src="/files/WUVS0salfJuT4gYICa1i" alt=""><figcaption></figcaption></figure>

***

#### ✅ Example Use Cases

* Static file directories (JS, CSS, fonts, images)
* File upload areas with large payloads
* Public folders for client download access

***

#### ⚠️ Important Notes

* No security filtering will apply to excluded directories
* Use only for **safe, public, and static content**
* Avoid excluding sensitive areas such as `/admin`, `/api`, or dynamic logic handlers

***

🎯 **This feature is designed for performance and compatibility — only use it where security impact is minimal.**


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.shieldsguard.com/getting-started/4.-security-rules/4.11-exclude-directories-from-protection.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.