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

45. Practice Exercises with Hints

45.9 Advanced Defensive Drills – AD to Mobile

By Last updated:

Chapters 38–44 themes: AD hygiene, malware handling mindset, DoS awareness, session security, evasion awareness, IoT default passwords, mobile sideload – defence drills, OWN lab only.

Exercise Task Hint
E1 AD: why Kerberoast matters to Blue – fix name two SPN + weak service password; gMSA / long password + monitor 4769
E2 Malware: first Blue steps on a suspected Windows lab VM Isolate network; snapshot/image policy; do not "clean in place" first if IR matters
E3 DoS: rate-limit idea for public login – one control WAF / reverse-proxy limits / CAPTCHA class; ISP/cloud shields for volumetric
E4 Session: steal cookie idea on OWN HTTP lab → fix flags Secure + HttpOnly + HTTPS; short TTL
E5 IoT: Raja-Rani camera default admin/admin – Blue checklist Change password; segment VLAN; update firmware; never expose to WAN
E6 Mobile: three staff rules for Sahyadri phones Store installs only; screen lock; no unknown APK
Red team (attacker) does Blue team (defender) detects / stops
Roasts weak SPN in OWN AD lab gMSA; AES; Tier model; audit
Speaks "cryptolocker" scare without isolate IR playbook: contain → evidence → eradicate → recover
Evil-twin demo on OWN lab AP only Staff VPN/HTTPS habits; no public evil-twin practice

Ravindra Bagale's Tip

The advanced chapters seem scary. One defence line: least privilege + patch + segment + monitor. Tools later. Next up: the capstone!

Lab

Pick one track: (A) AD lab pre-auth fix re-verify, or (B) mobile emulator permission revoke, or (C) IoT VM password change. Write 8-line Blue report for owner Rani.

Extended teaching notes

Why this lesson matters

Phones hold mail, MFA and business apps. Hardening is mostly updates, store-only installs, careful permissions, MDM for company data, and scepticism toward unknown Bluetooth pairings and captive portals.

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.

Extra depth

Re-read the original short section at the top of the page, then this expansion. Together they should exceed a solid lesson length. If anything still feels thin, add your own lab screenshot and a paragraph in your notebook — that personal evidence is what interviews ask for.

  • Permission before tools.
  • Patch and config before exploits.
  • Logs and backups before blame.
  • Teach one junior the warning from this page.