DeadSwitch Ethical Hacking – Rules of the Game

The blade is legal. The hand must be clean.

Welcome to the edge.

This is not a playground. This is the wire. The digital warfront. You want to hack with purpose – then learn the rules. A blade in the dark is only justified if your hand is clean. That means ethics, permission, scope, and discipline.

Let’s break it down.


1. Ethics First

What – Ethics is your core. Without it, you’re just another attacker.
Why – Your intent defines your path. Ethical hacking is about securing, not exploiting.
How – Always ask: Does this action protect or harm? Would I be fine if this was made public?
Tools – No tool here – this one lives in your spine.


2. Permission is Everything

What – You don’t test a system unless you have explicit written permission.
Why – Testing without it is illegal. No gray area. No excuses.
How – Before any engagement, get a signed agreement or contract. Include scope, rules, and timeline.
Tools – Use GnuPG to sign agreements. Encrypt sensitive documents. Use Magic Wormhole or OnionShare to exchange permissions securely if needed.


3. Scope is Your Map

What – Scope defines what you can touch.
Why – One step outside and you’re an intruder.
How – Ask for IP ranges, domains, accounts, endpoints. Get it in writing. Stick to it.
Tools – Use Recon-ng, Amass, or OWASP Amass to map targets within scope. Tag everything. Keep logs.


4. Engagement Rules Define Survival

What – Engagement rules are the battlefield laws.
Why – They protect you and the client from accidental damage.
How – Understand rate limits, data handling rules, off-hours policy, and testing restrictions. Know when to stop.
Tools – Maintain an attack journal using Obsidian, Standard Notes, or just plain Org mode in Emacs. Log every action.


5. Responsible Disclosure

What – Reporting the vulnerability without drama.
Why – It protects users and helps patch the hole.
How – Report directly to the client or via platforms like HackerOne, Bugcrowd, or Intigriti. Include PoC, impact, and fix suggestions.
Tools – Use Markdown, Asciidoctor, or Pandoc to format clean reports. Encrypt everything. Don’t send raw.


6. Legal Shield

What – Legal protection is your armor.
Why – Without it, your skill is a weapon – not a tool.
How – Signed NDAs, contracts, disclosure agreements. Backed up and timestamped.
Tools – Use KeePassXC or Tomb to store legal files securely. Sign with OpenSSL or GnuPG. Keep multiple copies offline.


Final Note
You’re not a hacker until you know restraint. Skill without control is chaos. Ethical hacking is precision, law, and honor combined. This is the foundation. Violate it, and you vanish in the noise of the black hat crowd.

Next post – Signals in the Static (Passive Recon)

Stay sharp. Stay clean. Stay DeadSwitch.

Leave a comment