Ravindra BagaleCourses & study guides मराठी Track your progress

25. Wireless Security

25.2 Monitor Mode and the Aircrack-ng Suite

By Last updated:

In short: The Aircrack-ng suite is the standard toolkit: airmon-ng (monitor mode), airodump-ng (capture), aireplay-ng (inject/deauth), aircrack-ng (crack the captured handshake).

Wi-Fi capture sathi tumcha wireless card monitor mode madhe pahije – tyane javalche sagle Wi-Fi packets aikta yetat (normal "managed" mode madhe fakt tumchya network che). Yasathi monitor mode support karnara adapter lagto (bahutek laptop che internal card lab sathi purese nastat).

sudo airmon-ng                       # list wireless interfaces
sudo airmon-ng check kill            # stop processes that interfere
sudo airmon-ng start wlan0           # put wlan0 into monitor mode (becomes wlan0mon)
sudo airodump-ng wlan0mon            # scan: list nearby networks (BSSID, channel, encryption)
sudo airmon-ng stop wlan0mon         # return to normal mode when done

The Aircrack-ng suite is the standard toolkit: airmon-ng (monitor mode), airodump-ng (capture), aireplay-ng (inject/deauth), aircrack-ng (crack the captured handshake).

Ravindra Bagale's Tip

Students struggle because monitor mode won't work – the reason is that a laptop's internal card or a VM's virtual adapter does not support monitor mode. For the lab you need an external USB Wi-Fi adapter (one that supports monitor mode and injection). Check this first, then start.

Lab

(Needs a monitor-mode adapter.) Put your adapter in monitor mode and run airodump-ng for one minute. In your notes, list only your own network's BSSID, channel and encryption type. Do not record or target any other network.

Extended teaching notes

Why this lesson matters

Use this lesson to strengthen systems you own: understand the risk, practise safely in a lab, then write and apply the fix.

Apply the fix across stacks

Same class of bug, same idea in every language.

Java / Spring Boot

Parameterise queries, encode output, CSRF tokens, limited Actuator, dependency scanning.

ASP.NET Core

EF Core / parameterised SQL, Razor encoding, HTTPS, Data Protection.

Node.js / Express

helmet, parameterised SQL, npm audit, avoid eval and shell concat.

Python / Django / Flask / FastAPI

ORM, autoescape, pip-audit, Bandit; never shell=True with user input.

PHP / Laravel

PDO/Eloquent, Blade escaping, composer audit.

Go / Ruby

database/sql placeholders / ActiveRecord; html/template / ERB escaping; govulncheck / Brakeman.

nginx / Apache / Tomcat

Hide versions, TLS, security headers, least-open ports.

MySQL / PostgreSQL / MongoDB / Redis

Private networks, auth on, least-privilege users, no 0.0.0.0/0.

AWS / Azure / GCP

Roles not long-lived keys, private data stores, cloud audit logs on.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.