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

Chapter 3: Linux Basic Commands

3.9 Getting help

By Last updated:

Friends, you don't need to memorise every command – help is built into Linux. Learn to use man, --help and apropos, and you can teach yourself any new command.

man ls              # full manual page (q to quit, /word to search)
ls --help           # short usage summary
whatis chmod        # one-line description
apropos network     # search manual pages by keyword
type cd             # is it a built-in, alias or program?
which nginx         # full path of a command

Ravindra Bagale's Tip

Take a backup before editing any important config file: sudo cp /etc/nginx/nginx.conf /etc/nginx/nginx.conf.bak. If something breaks, one command brings it back. This small habit will save your lab server again and again.

Ravindra Bagale's Tip

Many students rush to the internet for copy-paste fixes as soon as an error appears. First look for the option in man or --help – inside man ls, type /sort to search. And if which nginx shows nothing, nginx is either not installed or not in the PATH.

Lab

Chala, whatis chmod, type cd aani which nginx chalva aani pratyekacha output ek line madhe samjavun liha. Mag man tail madhe -f cha arth shodha aani q ne baher ya.

Extended teaching notes

Why this lesson matters

Cloud security is mostly IAM, network exposure, logging and secure defaults. The shared responsibility model means the provider patches the metal; you patch what you configure.

  • No public databases or public admin panels.
  • Roles / OIDC instead of long-lived access keys.
  • CloudTrail / Activity Logs / Audit Logs on and retained.
  • S3/Blob/GCS: Block Public Access; encrypt; least privilege.

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.