This site is for education and authorized security research. We advocate a
permission-first, lab-safe, and data-minimizing approach.
Nothing here is legal advice—consult your counsel where applicable.
Purpose & Principles
Do no harm: Protect people, services, and property.
Permission-first: Obtain explicit, written authorization before any testing.
Minimize exposure: Limit power, scope, duration, and data collected.
Respect privacy: Avoid personal data; securely handle any unavoidable exposure.
Reminder: Unauthorized interception, access, or interference can violate
communications, computer misuse, and monitoring laws in many jurisdictions.
Permission & Scope
Operate only under a written agreement that clearly defines:
Who authorizes you, and who performs testing (named parties).
What assets are in scope (SSIDs, devices, networks, facilities).
When testing occurs (dates, windows), with rollback/stop conditions.
Where testing occurs (on-prem lab, shielded area, isolated VLANs).
Which techniques are allowed (passive vs. active; thresholds).
Data handling (storage, access, retention, destruction).
# Example scope (lab)
Authorized: Test SSID LAB-5G on channels 36/44 with 10 dBm max power.
Clients: Company-owned laptops listed in Appendix A.
Time: Sept 1–5, 09:00–17:00 local.
Prohibited: Production SSIDs, emergency comms, third-party systems.
Regulatory & Legal Landscape
Spectrum & power limits: Stay within ISM bands and local limits.
Interference: Jamming/deauth are illegal without authorization.
Interception laws: Capturing others’ traffic can be unlawful.
Computer misuse: Unauthorized access may carry criminal liability.
Privacy frameworks: Handle data under GDPR, CCPA, HIPAA, etc. where applicable.
Note: Always review local regulations with legal counsel.
Lab-Safe Practices
Use Faraday bags/enclosures or dummy loads for RF experiments.
Keep EIRP low; avoid bleeding into public spectrum.
Use test-only SSIDs, tags, and disposable credentials.
Start with passive capture before active tests.
Log everything: time, power, channels, and test IDs.
Data Handling & Privacy
Collect only what’s needed—avoid sensitive content.
Encrypt data at rest; restrict access.
Keep data for a fixed window (e.g., 30–90 days).
Scrub PII from examples before sharing.
Technique-Specific Boundaries
Wi-Fi
Allowed: Passive scans, handshake capture on lab SSIDs.
Avoid: Deauth/rogue APs on real networks.
BLE
Allowed: Beaconing and GATT tests on owned devices.
Avoid: Tracking/spoofing others’ devices.
RFID/NFC
Allowed: Lab tag emulation, controlled cloning demos.
Avoid: Unauthorized badge cloning.
Sub-GHz
Allowed: rtl_433 decoding of your lab sensors.
Avoid: Interfering with licensed/industrial systems.
IR
Allowed: Your own remotes + lab gear.
Avoid: Controlling others’ devices in shared spaces.
SDR
Allowed: Passive spectrum analysis; shielded signal gen.
Avoid: Over-the-air jamming without clearance.
Responsible Disclosure
Reproduce in a controlled lab first.
Notify the vendor/owner privately.
Agree on timelines and remediation windows.
Provide minimal evidence, no sensitive data.
Quick Checklist
✅ Written permission & scope
✅ Lab containment (Faraday, low power)
✅ Passive-first, active with approval only
✅ Logs & rollback plan
✅ Data encryption + retention policy
Code of Conduct
Respect people over proofs—no harassment.
Report honestly and without hype.
Prioritize safety and human impact.
Credit others, share responsibly.
FAQ
Can I test my neighbor’s Wi-Fi?
No. Only test systems you own or are contracted to assess.
Is deauth always illegal?
Usually—it’s unlawful interference unless lab-contained or authorized.
Can I publish captures?
Never raw. Redact, anonymize, and ensure you have owner permission.
