Lion Cipher Lab

Set up VS Code for security work: terminal, Python, Docker and remote (WSL/SSH) in one editor

Why it matters

More than a hundred labs on this site say "open the file in VS Code" or "you'll need a text editor such as VS Code" and then carry on as though you were born knowing how. VS Code is where most security work actually happens between the terminal commands: reading a 40,000-line log with the keywords lit up, editing a YAML detection rule with the indentation checked for you, running a Python script against a packet capture, and doing all of that inside a Linux VM or WSL without leaving one window. This lab installs it properly — verified download, telemetry decision made on purpose, extensions…

What you'll learn

Steps in this lab

  1. Editor, IDE, terminal: three different tools, and which one VS Code is
  2. First, check whether it's already there (every OS)
  3. Windows: the User Installer, and prove the download is genuine
  4. macOS: drag to Applications, then install the `code` command
  5. Linux: use Microsoft's signed apt/dnf repository, not a random script
  6. Decide about telemetry on purpose — and know that VSCodium exists
  7. Open your labs folder, and meet Workspace Trust
  8. The integrated terminal, and choosing your default shell
  9. Before you install a single extension: what an extension can do to you
  10. Install the Python extension and point it at your venv
  11. Containers: the extension that used to be called "Docker" (optional now, needed soon)
  12. Why security labs live in WSL or a VM — and opening a folder inside WSL
  13. Remote - SSH: edit files on a VM or server as if they were local
  14. settings.json: user settings vs workspace settings
  15. The six keys that replace the mouse
  16. Reading JSON, YAML and logs with the colours on
  17. Prove it: run a Python file in your venv from the integrated terminal
  18. What you just did — and how a pro keeps it this clean

Open the full interactive lab →