Prerequisites
- Git and access to the Laser repository.
- Mirror installed and on
PATH. - A Reflection API key with Beam access.
- Bash, Python 3, cURL,
readlink -f, tmux, and a running Docker daemon. GNU coreutils (timeoutorgtimeout) enables host command timeouts.
1
Install the launcher
Clone Laser and configure your current shell. Create an API key in the Reflection platform.Add the clone’s absolute
bin path to your shell configuration to keep it available. The launcher installs the extension into each workspace automatically.2
For the demo, start a local vulnhub target
docker logs laser-demo.3
Launch Laser
Choose one launch method:Both methods lock scope and start Mirror in tmux.
- Web UI
- CLI
From the checkout, in the shell configured above, start the server:Open
http://127.0.0.1:8875 and click New engagement. Keep Run on set to Host and enter:Click Launch engagement. Web launches allow unattended tool execution.
4
Inspect progress and results
Select
laser-demo in the web UI. For a CLI-launched run, start the server using the Web UI tab above, then select the existing engagement.Overview summarizes progress; Live shows the terminal and accepts follow-up input. Inspect saved support in Evidence, Findings, and Attack graph. Keep the listener bound to loopback.Evidence and reports remain in the workspace’s .laser/ directory. Review them before accepting the outcome: a stop or report file does not prove success, and an agent’s verified finding is not independent reproduction.5
Finish the lab
In Live, choose Stop engagement to terminate verified main and worker sessions. Check for a partial stop, then remove the target:Detached host processes remain outside these controls. The lab means the disposable host or VM running Laser and Docker, not just the target container. Copy out the engagement workspace before shutting down or deleting that environment. See Stop a run for manual shutdown.