# Access Control

Access control is the application of constraints on who or what is authorized to perform actions or access resources. In the context of web applications, access control is dependent on authentication and session management:

* **Authentication** confirms that the user is who they say they are.
* **Session management** identifies which subsequent HTTP requests are being made by that same user.
* **Access control** determines whether the user is allowed to carry out the action that they are attempting to perform.

#### Types Of Access Control Security Models

* ### Programmatic access control <a href="#programmatic-access-control" id="programmatic-access-control"></a>
* ### Discretionary access control (DAC) <a href="#discretionary-access-control-dac" id="discretionary-access-control-dac"></a>
* ### Mandatory access control (MAC) <a href="#discretionary-access-control-dac" id="discretionary-access-control-dac"></a>
* ### Role-based access control (RBAC) <a href="#role-based-access-control-rbac" id="role-based-access-control-rbac"></a>

To read in detail: <https://portswigger.net/web-security/access-control/security-models>


---

# 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://n0m4dsec.gitbook.io/sec-book/web-vulnerabilities/server-side-vulnerabilities/access-control.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.