> 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/hacking-wifi/introduction/wifi-hacking-overview.md).

# WiFi Hacking Overview

A guided path for authorized WiFi security labs, from wireless fundamentals to WPA/WPA2 PSK and legacy WEP assessments.

Start here to build a safe, practical wireless security workflow. Begin with authorization, scope, and fundamentals. Then move into WPA/WPA2 PSK and legacy WEP assessments.

{% hint style="warning" %}
Wireless tests can affect nearby devices. Define written permission, target equipment, channels, and a recovery plan before active testing.
{% endhint %}

### Learning path

<table data-view="cards" data-full-width="false" data-search="false"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-list-check" style="color:$primary;">:list-check:</i></h3></td><td><h4>Prepare your lab</h4></td><td>Confirm compatible hardware, required tools, permissions, and lab boundaries.</td><td><a href="/hacking-wifi/introduction/prerequisites-before-starting.md">Prerequisites Before Starting</a></td></tr><tr><td><h3><i class="fa-wifi" style="color:$primary;">:wifi:</i></h3></td><td><h4>Learn the fundamentals</h4></td><td>Understand wireless clients, access points, channels, and network behavior.</td><td><a href="/hacking-wifi/basic-concepts.md">Basic Concepts</a></td></tr><tr><td><h3><i class="fa-shield-halved" style="color:$primary;">:shield-halved:</i></h3></td><td><h4>Assess modern PSK networks</h4></td><td>Explore WPA/WPA2 PSK security with documented scope.</td><td><a href="/hacking-wifi/wpa-wpa2-psk-network-attacks.md">WPA/WPA2 PSK Network Attacks</a></td></tr><tr><td><h3><i class="fa-triangle-exclamation" style="color:$primary;">:triangle-exclamation:</i></h3></td><td><h4>Review legacy WEP risks</h4></td><td>Understand why WEP is obsolete and unsuitable for real networks.</td><td><a href="/hacking-wifi/wep-networks.md">WEP Networks</a></td></tr></tbody></table>

### What you will learn

{% columns %}
{% column %}

#### Wireless foundations

Learn how clients, access points, channels, and wireless protocols interact.

#### Security assessment concepts

Review WPA/WPA2 PSK weaknesses, authentication evidence, and legacy WEP exposure.
{% endcolumn %}

{% column %}

#### Controlled threat scenarios

Explore client disconnection, Evil Twin, and traffic analysis with a documented target list and recovery window.

#### Defensive validation

Identify controls that reduce exposure to common wireless attacks.
{% endcolumn %}
{% endcolumns %}

### Practice responsibly

{% stepper %}
{% step %}

#### Define the scope

Document approved targets, devices, channels, and testing hours before starting.
{% endstep %}

{% step %}

#### Isolate the lab

Use your own equipment. Reduce impact on nearby networks whenever possible.
{% endstep %}

{% step %}

#### Validate and report

Preserve relevant evidence. Document findings and recommended mitigations.
{% endstep %}
{% endstepper %}


---

# 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/hacking-wifi/introduction/wifi-hacking-overview.md?ask=<question>&goal=<user_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.