Security
Lab

Research Scope

The public lab is organized around four practical questions. What should be visible? Which controls reduce risk without making a system unusable? What evidence proves a change worked? What must stay private when the work is documented?

• Endpoint visibilityLogs, events, and signals that support useful investigation.
• Secure deploymentTrust boundaries, preflight checks, and repeatable release procedures.
• Access and hardeningLeast privilege, configuration review, and Linux system hygiene — plus professional guidance on limiting and eliminating scope creep, where colleagues accumulate more access keys and permissions than their role requires, regardless of motive, ego or otherwise.
• Safe evidenceRedacted screenshots, terminal excerpts, and notes that teach without exposing infrastructure.

Detailed procedures and evidence will be added after hostnames, usernames, addresses, repository details, and credentials are removed.