Assessment Goal

This assessment evaluates Vagrant CLI, Vagrantfile, Boxen, Single-VM-Workflow und sichere Lab-Bedienung. Answers must be justified with Vagrantfile snippets, commands, risks and recovery.

Questions

Question 01: Check the box source in the HCP Vagrant Registry or an internal registry

Which box is used, who maintains it and which version is approved?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 02: Version the Vagrantfile and review changes like infrastructure code

Which provider is required and which host permissions does it need?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 03: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

Which forwarded ports, private networks or public networks are opened?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 04: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

Which files are synced between host and guest?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 05: Write provisioners idempotently and keep package installation reproducible

Which provisioners run with root privileges and are they idempotent?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 06: Limit synced folders to the minimum required paths and never sync secrets

Which plugins are required and how are they versioned?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 07: Roll out box updates through controlled testing instead of implicit team upgrades

Which host resources are consumed during vagrant up?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 08: Treat plugins as supply-chain components and document their versions

What is the recovery path for a broken VM, box regression or SSH failure?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 09: Use snapshots as lab helpers, not as a backup replacement

Which box is used, who maintains it and which version is approved?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 10: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

Which provider is required and which host permissions does it need?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 11: Check the box source in the HCP Vagrant Registry or an internal registry

Which forwarded ports, private networks or public networks are opened?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 12: Version the Vagrantfile and review changes like infrastructure code

Which files are synced between host and guest?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 13: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

Which provisioners run with root privileges and are they idempotent?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 14: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

Which plugins are required and how are they versioned?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 15: Write provisioners idempotently and keep package installation reproducible

Which host resources are consumed during vagrant up?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 16: Limit synced folders to the minimum required paths and never sync secrets

What is the recovery path for a broken VM, box regression or SSH failure?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 17: Roll out box updates through controlled testing instead of implicit team upgrades

Which box is used, who maintains it and which version is approved?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 18: Treat plugins as supply-chain components and document their versions

Which provider is required and which host permissions does it need?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 19: Use snapshots as lab helpers, not as a backup replacement

Which forwarded ports, private networks or public networks are opened?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 20: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

Which files are synced between host and guest?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 21: Check the box source in the HCP Vagrant Registry or an internal registry

Which provisioners run with root privileges and are they idempotent?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 22: Version the Vagrantfile and review changes like infrastructure code

Which plugins are required and how are they versioned?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 23: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

Which host resources are consumed during vagrant up?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 24: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

What is the recovery path for a broken VM, box regression or SSH failure?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 25: Write provisioners idempotently and keep package installation reproducible

Which box is used, who maintains it and which version is approved?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 26: Limit synced folders to the minimum required paths and never sync secrets

Which provider is required and which host permissions does it need?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 27: Roll out box updates through controlled testing instead of implicit team upgrades

Which forwarded ports, private networks or public networks are opened?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 28: Treat plugins as supply-chain components and document their versions

Which files are synced between host and guest?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 29: Use snapshots as lab helpers, not as a backup replacement

Which provisioners run with root privileges and are they idempotent?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 30: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

Which plugins are required and how are they versioned?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 31: Check the box source in the HCP Vagrant Registry or an internal registry

Which host resources are consumed during vagrant up?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 32: Version the Vagrantfile and review changes like infrastructure code

What is the recovery path for a broken VM, box regression or SSH failure?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 33: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

Which box is used, who maintains it and which version is approved?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 34: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

Which provider is required and which host permissions does it need?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 35: Write provisioners idempotently and keep package installation reproducible

Which forwarded ports, private networks or public networks are opened?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 36: Limit synced folders to the minimum required paths and never sync secrets

Which files are synced between host and guest?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 37: Roll out box updates through controlled testing instead of implicit team upgrades

Which provisioners run with root privileges and are they idempotent?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 38: Treat plugins as supply-chain components and document their versions

Which plugins are required and how are they versioned?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 39: Use snapshots as lab helpers, not as a backup replacement

Which host resources are consumed during vagrant up?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 40: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

What is the recovery path for a broken VM, box regression or SSH failure?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 41: Check the box source in the HCP Vagrant Registry or an internal registry

Which box is used, who maintains it and which version is approved?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 42: Version the Vagrantfile and review changes like infrastructure code

Which provider is required and which host permissions does it need?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 43: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

Which forwarded ports, private networks or public networks are opened?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 44: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

Which files are synced between host and guest?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 45: Write provisioners idempotently and keep package installation reproducible

Which provisioners run with root privileges and are they idempotent?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 46: Limit synced folders to the minimum required paths and never sync secrets

Which plugins are required and how are they versioned?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 47: Roll out box updates through controlled testing instead of implicit team upgrades

Which host resources are consumed during vagrant up?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 48: Treat plugins as supply-chain components and document their versions

What is the recovery path for a broken VM, box regression or SSH failure?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 49: Use snapshots as lab helpers, not as a backup replacement

Which box is used, who maintains it and which version is approved?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 50: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

Which provider is required and which host permissions does it need?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 51: Check the box source in the HCP Vagrant Registry or an internal registry

Which forwarded ports, private networks or public networks are opened?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 52: Version the Vagrantfile and review changes like infrastructure code

Which files are synced between host and guest?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 53: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

Which provisioners run with root privileges and are they idempotent?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 54: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

Which plugins are required and how are they versioned?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 55: Write provisioners idempotently and keep package installation reproducible

Which host resources are consumed during vagrant up?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 56: Limit synced folders to the minimum required paths and never sync secrets

What is the recovery path for a broken VM, box regression or SSH failure?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 57: Roll out box updates through controlled testing instead of implicit team upgrades

Which box is used, who maintains it and which version is approved?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 58: Treat plugins as supply-chain components and document their versions

Which provider is required and which host permissions does it need?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 59: Use snapshots as lab helpers, not as a backup replacement

Which forwarded ports, private networks or public networks are opened?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Question 60: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

Which files are synced between host and guest?

Assess the situation through box trust, provider assumption, network, sync path, provisioner, plugin risk and rollback.

Practice Appendix: Fundamentals assessment review

The following cards are intended for repetition, review and coaching. Each card has a concrete Vagrant angle and can be used as a short exercise, pairing prompt or pull-request comment.

Card 001: Check the box source in the HCP Vagrant Registry or an internal registry

• Context: Check the box source in the HCP Vagrant Registry or an internal registry is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant init.
• Review question: Which box is used, who maintains it and which version is approved?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 002: Version the Vagrantfile and review changes like infrastructure code

• Context: Version the Vagrantfile and review changes like infrastructure code is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant validate.
• Review question: Which provider is required and which host permissions does it need?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 003: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

• Context: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant up.
• Review question: Which forwarded ports, private networks or public networks are opened?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 004: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

• Context: Bind forwarded ports to 127.0.0.1 by default and review public networks separately is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant status.
• Review question: Which files are synced between host and guest?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 005: Write provisioners idempotently and keep package installation reproducible

• Context: Write provisioners idempotently and keep package installation reproducible is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant ssh.
• Review question: Which provisioners run with root privileges and are they idempotent?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 006: Limit synced folders to the minimum required paths and never sync secrets

• Context: Limit synced folders to the minimum required paths and never sync secrets is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant ssh-config.
• Review question: Which plugins are required and how are they versioned?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 007: Roll out box updates through controlled testing instead of implicit team upgrades

• Context: Roll out box updates through controlled testing instead of implicit team upgrades is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant provision.
• Review question: Which host resources are consumed during vagrant up?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 008: Treat plugins as supply-chain components and document their versions

• Context: Treat plugins as supply-chain components and document their versions is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant reload.
• Review question: What is the recovery path for a broken VM, box regression or SSH failure?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 009: Use snapshots as lab helpers, not as a backup replacement

• Context: Use snapshots as lab helpers, not as a backup replacement is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant halt.
• Review question: Which box is used, who maintains it and which version is approved?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 010: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

• Context: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant destroy.
• Review question: Which provider is required and which host permissions does it need?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 011: Check the box source in the HCP Vagrant Registry or an internal registry

• Context: Check the box source in the HCP Vagrant Registry or an internal registry is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant box list.
• Review question: Which forwarded ports, private networks or public networks are opened?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 012: Version the Vagrantfile and review changes like infrastructure code

• Context: Version the Vagrantfile and review changes like infrastructure code is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant box update.
• Review question: Which files are synced between host and guest?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 013: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

• Context: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant plugin list.
• Review question: Which provisioners run with root privileges and are they idempotent?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 014: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

• Context: Bind forwarded ports to 127.0.0.1 by default and review public networks separately is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant snapshot save.
• Review question: Which plugins are required and how are they versioned?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 015: Write provisioners idempotently and keep package installation reproducible

• Context: Write provisioners idempotently and keep package installation reproducible is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant init.
• Review question: Which host resources are consumed during vagrant up?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 016: Limit synced folders to the minimum required paths and never sync secrets

• Context: Limit synced folders to the minimum required paths and never sync secrets is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant validate.
• Review question: What is the recovery path for a broken VM, box regression or SSH failure?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 017: Roll out box updates through controlled testing instead of implicit team upgrades

• Context: Roll out box updates through controlled testing instead of implicit team upgrades is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant up.
• Review question: Which box is used, who maintains it and which version is approved?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 018: Treat plugins as supply-chain components and document their versions

• Context: Treat plugins as supply-chain components and document their versions is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant status.
• Review question: Which provider is required and which host permissions does it need?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 019: Use snapshots as lab helpers, not as a backup replacement

• Context: Use snapshots as lab helpers, not as a backup replacement is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant ssh.
• Review question: Which forwarded ports, private networks or public networks are opened?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 020: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

• Context: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant ssh-config.
• Review question: Which files are synced between host and guest?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 021: Check the box source in the HCP Vagrant Registry or an internal registry

• Context: Check the box source in the HCP Vagrant Registry or an internal registry is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant provision.
• Review question: Which provisioners run with root privileges and are they idempotent?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 022: Version the Vagrantfile and review changes like infrastructure code

• Context: Version the Vagrantfile and review changes like infrastructure code is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant reload.
• Review question: Which plugins are required and how are they versioned?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 023: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

• Context: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant halt.
• Review question: Which host resources are consumed during vagrant up?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 024: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

• Context: Bind forwarded ports to 127.0.0.1 by default and review public networks separately is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant destroy.
• Review question: What is the recovery path for a broken VM, box regression or SSH failure?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 025: Write provisioners idempotently and keep package installation reproducible

• Context: Write provisioners idempotently and keep package installation reproducible is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant box list.
• Review question: Which box is used, who maintains it and which version is approved?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 026: Limit synced folders to the minimum required paths and never sync secrets

• Context: Limit synced folders to the minimum required paths and never sync secrets is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant box update.
• Review question: Which provider is required and which host permissions does it need?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 027: Roll out box updates through controlled testing instead of implicit team upgrades

• Context: Roll out box updates through controlled testing instead of implicit team upgrades is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant plugin list.
• Review question: Which forwarded ports, private networks or public networks are opened?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 028: Treat plugins as supply-chain components and document their versions

• Context: Treat plugins as supply-chain components and document their versions is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant snapshot save.
• Review question: Which files are synced between host and guest?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 029: Use snapshots as lab helpers, not as a backup replacement

• Context: Use snapshots as lab helpers, not as a backup replacement is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant init.
• Review question: Which provisioners run with root privileges and are they idempotent?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 030: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

• Context: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant validate.
• Review question: Which plugins are required and how are they versioned?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 031: Check the box source in the HCP Vagrant Registry or an internal registry

• Context: Check the box source in the HCP Vagrant Registry or an internal registry is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant up.
• Review question: Which host resources are consumed during vagrant up?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 032: Version the Vagrantfile and review changes like infrastructure code

• Context: Version the Vagrantfile and review changes like infrastructure code is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant status.
• Review question: What is the recovery path for a broken VM, box regression or SSH failure?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 033: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

• Context: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant ssh.
• Review question: Which box is used, who maintains it and which version is approved?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 034: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

• Context: Bind forwarded ports to 127.0.0.1 by default and review public networks separately is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant ssh-config.
• Review question: Which provider is required and which host permissions does it need?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 035: Write provisioners idempotently and keep package installation reproducible

• Context: Write provisioners idempotently and keep package installation reproducible is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant provision.
• Review question: Which forwarded ports, private networks or public networks are opened?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 036: Limit synced folders to the minimum required paths and never sync secrets

• Context: Limit synced folders to the minimum required paths and never sync secrets is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant reload.
• Review question: Which files are synced between host and guest?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 037: Roll out box updates through controlled testing instead of implicit team upgrades

• Context: Roll out box updates through controlled testing instead of implicit team upgrades is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant halt.
• Review question: Which provisioners run with root privileges and are they idempotent?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 038: Treat plugins as supply-chain components and document their versions

• Context: Treat plugins as supply-chain components and document their versions is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant destroy.
• Review question: Which plugins are required and how are they versioned?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 039: Use snapshots as lab helpers, not as a backup replacement

• Context: Use snapshots as lab helpers, not as a backup replacement is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant box list.
• Review question: Which host resources are consumed during vagrant up?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 040: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

• Context: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant box update.
• Review question: What is the recovery path for a broken VM, box regression or SSH failure?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 041: Check the box source in the HCP Vagrant Registry or an internal registry

• Context: Check the box source in the HCP Vagrant Registry or an internal registry is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant plugin list.
• Review question: Which box is used, who maintains it and which version is approved?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 042: Version the Vagrantfile and review changes like infrastructure code

• Context: Version the Vagrantfile and review changes like infrastructure code is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant snapshot save.
• Review question: Which provider is required and which host permissions does it need?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 043: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

• Context: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant init.
• Review question: Which forwarded ports, private networks or public networks are opened?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 044: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

• Context: Bind forwarded ports to 127.0.0.1 by default and review public networks separately is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant validate.
• Review question: Which files are synced between host and guest?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 045: Write provisioners idempotently and keep package installation reproducible

• Context: Write provisioners idempotently and keep package installation reproducible is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant up.
• Review question: Which provisioners run with root privileges and are they idempotent?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 046: Limit synced folders to the minimum required paths and never sync secrets

• Context: Limit synced folders to the minimum required paths and never sync secrets is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant status.
• Review question: Which plugins are required and how are they versioned?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 047: Roll out box updates through controlled testing instead of implicit team upgrades

• Context: Roll out box updates through controlled testing instead of implicit team upgrades is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant ssh.
• Review question: Which host resources are consumed during vagrant up?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 048: Treat plugins as supply-chain components and document their versions

• Context: Treat plugins as supply-chain components and document their versions is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant ssh-config.
• Review question: What is the recovery path for a broken VM, box regression or SSH failure?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 049: Use snapshots as lab helpers, not as a backup replacement

• Context: Use snapshots as lab helpers, not as a backup replacement is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant provision.
• Review question: Which box is used, who maintains it and which version is approved?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 050: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

• Context: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant reload.
• Review question: Which provider is required and which host permissions does it need?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 051: Check the box source in the HCP Vagrant Registry or an internal registry

• Context: Check the box source in the HCP Vagrant Registry or an internal registry is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant halt.
• Review question: Which forwarded ports, private networks or public networks are opened?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 052: Version the Vagrantfile and review changes like infrastructure code

• Context: Version the Vagrantfile and review changes like infrastructure code is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant destroy.
• Review question: Which files are synced between host and guest?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 053: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt

• Context: Document provider assumptions explicitly, especially VirtualBox, Docker, Hyper-V, VMware and libvirt is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant box list.
• Review question: Which provisioners run with root privileges and are they idempotent?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 054: Bind forwarded ports to 127.0.0.1 by default and review public networks separately

• Context: Bind forwarded ports to 127.0.0.1 by default and review public networks separately is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant box update.
• Review question: Which plugins are required and how are they versioned?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 055: Write provisioners idempotently and keep package installation reproducible

• Context: Write provisioners idempotently and keep package installation reproducible is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant plugin list.
• Review question: Which host resources are consumed during vagrant up?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 056: Limit synced folders to the minimum required paths and never sync secrets

• Context: Limit synced folders to the minimum required paths and never sync secrets is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant snapshot save.
• Review question: What is the recovery path for a broken VM, box regression or SSH failure?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 057: Roll out box updates through controlled testing instead of implicit team upgrades

• Context: Roll out box updates through controlled testing instead of implicit team upgrades is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant init.
• Review question: Which box is used, who maintains it and which version is approved?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 058: Treat plugins as supply-chain components and document their versions

• Context: Treat plugins as supply-chain components and document their versions is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant validate.
• Review question: Which provider is required and which host permissions does it need?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 059: Use snapshots as lab helpers, not as a backup replacement

• Context: Use snapshots as lab helpers, not as a backup replacement is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant up.
• Review question: Which forwarded ports, private networks or public networks are opened?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.

Card 060: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs

• Context: Start troubleshooting with vagrant status, ssh-config, port, provision and provider-specific logs is always part of a local infrastructure contract in Vagrant. A Vagrantfile describes not only a VM but also provider assumptions, box provenance, networks, sync paths, provisioning and the allowed host working area. Changes should therefore be handled like infrastructure code: reproducible, reviewable, reversible and without hidden secrets.
• Check command: vagrant status.
• Review question: Which files are synced between host and guest?
• Evidence: Record the Vagrantfile snippet, expected state, observed output and rollback decision.
• Risk: Document whether host resources, network exposure, secrets, box trust or plugin supply chain are affected.