Objective & prerequisites
Write a controlled response without exposing more data. Prerequisites: basic Python expressions and files; use a disposable local practice folder and fictional data. This shared workshop complements the existing data/AI tracks and does not create a second progress system.
Understand the concept
Secrets belong in approved configuration outside public code and uploads. Logs should help investigate failures without collecting resume content, tokens or credentials. A dependency needs a reviewed source, pinned version, license and maintenance plan. Suspected exposure calls for containment, owner notification and evidence preservation under an authorized process, not public experimentation.
Worked example
The Git fixture uses an obviously fake .env value, ignores it before committing and verifies it is untracked. This demonstrates prevention only. It does not prove that a real credential in history has been removed or rotated.
Try it yourself
Write an incident note for a fictional credential accidentally committed: identify scope, stop sharing, contact the responsible owner through the approved channel, rotate under authorization and review history/backups. Do not create or expose a real key. Record your prediction before running the supplied reference, then compare the observed result and explain any difference.
Worked solution
A revert is not enough to remove a leaked secret. Avoid copying the secret into the incident ticket. Record a reference and access scope, preserve necessary evidence privately and document corrective actions and remaining uncertainty.
Knowledge check
Should you test a suspected production vulnerability without authorization? Try answering without rereading the example.
Check and explain
No. Use the approved reporting process and controlled local fixtures.
Mini-project, mistakes & handover
Produce a short README with the question, exact local command, input meaning, checks and actual results. Include one failure case and its explanation. Never silently turn an exception into a passing result. Mark simulated behavior explicitly, credit the supplied teaching code and identify your own contribution. These activities are unsaved self-practice, not certification.
Authoritative reference
— consulted for the underlying interface/concept. The lesson and fictional examples are original teaching material. Python reference tested with 3.12; designed for 3.10+. Git lab requires Git 2.28+.
Try the activity before reading its reference. Keep your sources, commands and assumptions with your work. Companion activities are unsaved self-practice and do not award a certificate or change lesson progress.