0.6 Safety rules for this course
Threat talk in chapter 3 is for learning only, and only inside a system you are allowed to test. Say that line before you draw a payment path for anyone else.
- Name a threat in one plain sentence.
- Name a fix in one plain sentence.
- Do not write a recipe someone could copy to harm a system.
- Do not run tests against a bank, a friend's app, or a company API you do not own.
- Paper is the lab in this volume.
- If a page feels like an attack guide, you have left the lesson. Come back to the one-sentence threat and the fix.
Guru-ji's rule in the library: a pencil is enough. A stolen login is not a lesson.
Keep these lines
- This is Volume 1: story, cost, culture, and a threat model on paper.
- Raju learns without a degree. You can too.
- DevOps on this site is the tool path. This volume is the safety story beside it.
- Steps stay vertical. Tables are for cost and for DORA only.
- Threat talk is for learning only, and only inside a system you are allowed to test.
If the map is still fuzzy, read 0.4 and 0.6 again. Samajla ka? अगर नक्शा अभी साफ नहीं है, तो 0.4 और 0.6 फिर से पढ़ो.