# Security

This section defines the parameters with which Reblaze scrubs traffic.&#x20;

The user interface is divided into these sections:

1. [Dynamic Rules](https://waap.docs.link11.com/v2.18/product-walkthrough/security/dynamic-rules):  Thresholds for banning sources of hostile traffic.
2. [Quarantined](https://waap.docs.link11.com/v2.18/product-walkthrough/security/quarantined): The "warehouse" of traffic sources that are currently banned. This contains blacklists and whitelists, allowing you to manually control quarantines when necessary.&#x20;
3. [Profiles](https://waap.docs.link11.com/v2.18/product-walkthrough/security/profiles): Creation of security rule sets for assignment to specific resources, locations, and applications.&#x20;
4. [Args Analysis](https://waap.docs.link11.com/v2.18/product-walkthrough/security/args-analysis): Settings for allowing requests based on their arguments, in a procedure that occurs before normal WAF inspection and filtering.
5. [Session Profiling](https://waap.docs.link11.com/v2.18/product-walkthrough/security/session-profiling): Settings for assigning [tags](https://waap.docs.link11.com/v2.18/reference-information-1/tags) to incoming requests.
6. [Rate Limiting](https://waap.docs.link11.com/v2.18/product-walkthrough/security/rate-limiting): Settings for rate limits and the actions that will be performed when a rate limit is violated.
7. [Cloud Functions](https://waap.docs.link11.com/v2.18/product-walkthrough/security/cloud-functions): Custom code that can be executed at specified times during traffic processing.

The Security section is where you define the "under the hood" settings for Reblaze. When defining or editing the information in this section, careful consideration is necessary.&#x20;

Before investigating each section of the interface, it's recommended to read the "[Security Concepts](https://waap.docs.link11.com/v2.18/product-walkthrough/security/concepts)" discussion on the next page of this Manual.

Some security entities (Profiles, Rate Limits, etc.) are marked with ![](https://1443104804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYa27AYz47cZTEzJZB1vy%2Fuploads%2FCPsFpis59pBJru0HcStC%2Fimage.png?alt=media\&token=328f62b7-7df8-423b-bbc7-2aebe9b27d94) icons. That means it is a Reblaze-managed default entity, and it cannot be edited or deleted. If you do not wish to see these in the interface, you can hide them with the![](https://1443104804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYa27AYz47cZTEzJZB1vy%2Fuploads%2FVvAWLVadU7SijAVjgzwW%2Fimage.png?alt=media\&token=bfb9f6bd-7e35-48ae-8a25-cc63b6abbbe2) checkbox at the top of a page.


---

# 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://waap.docs.link11.com/v2.18/product-walkthrough/security.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.
