17. Why Learn All This Before Kali Linux?
17.4 From HTTP and Web Servers to Burp Suite, Nikto and Misconfigurations
Burp Suite mhanje browser aani server chya madhe basun HTTP requests pakadnara aani badalnara proxy. HTTP samjla nasel tar Burp madhe tumhala fakt text disto.
| You learnt (Parts 3, 4, 6) | You will use it for |
|---|---|
| HTTP methods, headers, status codes | Reading and editing requests in Burp Suite and OWASP ZAP |
| Cookies and sessions | Session hijacking concepts, testing HttpOnly/Secure flags |
| Nginx/Apache document root, config | Finding exposed files (.git, backups) with Gobuster/Dirb; fixing them in config |
Virtual hosts and the Host header |
Virtual host discovery, Host-header attacks |
| PHP forms and file upload | File upload and command injection tests in DVWA |
| TLS and Certbot | Testing weak protocols, missing HSTS |
| DNS and subdomains | Recon: subdomain enumeration, dangling DNS records |
curl -sI https://yourdomain.com | grep -Ei 'server|x-powered-by|strict|content-security'
That one line already tells a tester (and you) whether versions leak and whether security headers exist – no special tool needed.
Why this matters for security
A large share of real web findings are security misconfiguration (सुरक्षा चुकीचे कॉन्फिगरेशन): directory listing, default pages, verbose errors, missing headers, exposed admin panels. You configured all of these yourself in Parts 3 and 6, so you know both how they happen and how to fix them in one line of config.
Ravindra Bagale's Tip
When students open Burp Suite for the first time, all the tabs and buttons scare them. Don't worry – Burp just shows HTTP requests and responses, which we've already seen with curl -v. First learn to read requests with curl -v, and then Burp will feel very simple.
Ravindra Bagale's Tip – मराठी
Burp Suite पहिल्यांदा उघडल्यावर students ना खूप tabs आणि buttons बघून भीती वाटते. घाबरू नका – Burp फक्त HTTP request आणि response दाखवतो, जे आपण curl -v ने आधीच बघितले. आधी curl -v ने request वाचायला शिका, मग Burp एकदम simple वाटेल.
Ravindra Bagale's Tip – हिंदी
Burp Suite पहली बार खोलने पर बहुत सारे tabs और buttons देखकर students डर जाते हैं. घबराओ मत – Burp बस HTTP request और response दिखाता है, जो हम curl -v से पहले ही देख चुके हैं. पहले curl -v से request पढ़ना सीखो, फिर Burp बहुत आसान लगेगा.
Practice task
Run curl -v https://yourdomain.com and label every line: request line, request headers, status line, response headers. Then list three response headers that would interest a security tester.
Extended teaching notes
Why this lesson matters
Kali tools are dual-use. In this course every run ends with a defensive note: what config would have blocked or detected the activity on a system you own.
Rule
Host-only lab, written scope, no bridging onto real LANs.
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)
- Write the lesson title, date and the exact lab target you are allowed to use.
- List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
- Run one safe check from the lesson on a lab system only. Paste the command and output.
- Write a two-sentence fix you would give a teammate.
- 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.