Practical cybersecurity guides, labs & compliance
Explain expected and observed behavior, identify one assumption, and choose a test that distinguishes possible causes. Follow five debugging steps, a worked example, and an editable experiment card for your own notes.
Retest a specific vulnerability after an authorized change. Five checks cover deployment, comparable conditions, secure behavior and closure evidence. Includes a worked inconclusive result and an editable record for remediation, mitigation or unresolved status.
Build an Nmap command you can explain: targets, discovery, ports, service probes and saved output. Includes a flag reference, isolated-lab command ladder and five review questions before rerunning a scan.
Trace one NoSQL input from its parser and expected type to the database query. Use the query-boundary review and worked example to document observed behavior, remaining uncertainty and repair checks.
Define a permitted web-lab exercise and the security boundary you expect. Use the boundary record and worked example to preserve controlled observations, compare explanations and avoid unsupported vulnerability claims.
Review a proposed privilege-escalation path against the identity, permissions and prerequisites actually observed. Use the hypothesis filter to choose the next authorized check and document absent evidence or an unchanged boundary.
Check a suspected Nmap version false positive using probe context, XML output and authorized package evidence. Use the verification record to separate a service clue from confirmed vulnerability prerequisites.
Troubleshoot SMB enumeration by separating transport, negotiation, session setup, tree connect and file operations. Use the permission matrix and working record to document the last successful stage, exact error and next controlled check.
Review a PHP-style application by recording routes, inputs, account context and state transitions. Use the task record to separate implementation hints from demonstrated authentication, authorization or injection behavior.
Prepare vulnerability-disclosure intake with a monitored reporting route, an owner and a publication review. Use the record to separate contact-file checks from policy scope, response commitments and authorization to test.