> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/pt-br/web/access-control.md).
# Controle de acesso
Controle de acesso quebrado, IDOR, escalonamento de privilégios, manipulação de funções, bypass de autorização e exposição de painel de administração.
Notas de controle de acesso para os labs da PortSwigger Web Security Academy, com foco em etapas práticas de teste, validação no Burp Suite, comportamento de payloads e fluxo de exploração.
## Fluxo de teste
1. Identifique a funcionalidade vulnerável e a requisição, parâmetro, cabeçalho, cookie ou sink do lado do navegador relevantes.
2. Reproduza o comportamento no Burp Suite com um payload mínimo antes de escalar o ataque.
3. Valide o impacto com uma prova de conceito clara, como acesso à conta, divulgação de dados, execução de código, SSRF ou alteração de estado.
4. Mantenha os payloads, URLs, tokens e credenciais do laboratório inalterados ao documentar o caminho de exploração.
## Laboratórios
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/pt-br/web/access-control.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.