Practical cybersecurity guides, labs & compliance
Kioptrix Labs 
Record an rpcclient access denial at the specific procedure and account context that failed. Use the evidence card to distinguish connection success from per-call permissions and keep other successful queries within their own scope.
When rpcclient connects but user enumeration fails, record the exact call, identity and status. Use the operation coverage table to distinguish narrow successful queries from denied actions and retain the authorization boundary.
Compare SMB behavior on ports 139 and 445 using the same target, client, identity and operation. Preserve transport context and the first failure before attributing different results to dialect, signing or access policy.
Diagnose SMBMap logon failures with one approved account, explicit username and domain inputs, and an attempt ceiling. Use the comparison record to preserve changed conditions without turning formatting checks into credential guessing.
Review SMBMap access denial with the accepted session identity and exact operation recorded. Distinguish share discovery from file access, retain guest-mapping uncertainty and keep write-permission checks within the agreed scope.
Review Nuclei selection filters and matcher logic with pinned engine and template revisions. Use positive and negative fixtures to examine match behavior, then distinguish a template hit from independently verified vulnerability evidence.
Compare Chisel and Ligolo-NG from the traffic, DNS path and deployment permissions your task requires. Use the traffic contract to test representative permitted flows and record operational ownership, limits and recovery.
Troubleshoot Ligolo-NG by locating the first failing hop across the control channel, routes, destination service and DNS path. Retain installed versions and one narrow permitted connection before adding routes or tunnel hops.
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.
Read a penetration-test finding through affected assets, evidence, prerequisites and confidence. Use the action card to separate demonstrated impact from assumptions, assign an owner and define a remediation acceptance check.