Enhance the mission objectives

Author: aerabi

labspace/01-docker-init.md

@@ -2,6 +2,8 @@
 
 **Mission**: Docker Commandos arrive at Asgard and initiate their mission to contain the outbreak. Gord orders, "Set up a command center for us". Valkyrie and Agent Null start setting up the command center, while Jack and Evie secure the perimeter.
 
+![Docker Commandos setting up the command center](https://dockersecurity.io/commandos-asgard/asgard-init.png)
+
 **Real-world context**: Docker Init creates secure, production-ready Dockerfiles using established best practices, reducing the likelihood of security misconfigurations from day one.
 
 Docker Init is a command to initialize a Docker project with a Dockerfile and other necessary files:
@@ -13,6 +15,9 @@ Docker Init is a command to initialize a Docker project with a Dockerfile and ot
 
 ### Usage
 
+> [!NOTE]  
+> The command `docker init` is not available in the Labspace experience, so you can go to `flask-init` directly to see the generated files, and carry out the rest of the lab from there.
+
 On the repo, go to the Flask example directory:
 
 ```bash

labspace/02-sbom.md

@@ -11,18 +11,18 @@
 In the Docker Init step, we built an image with tag `flask-server:latest`. Let's check the SBOM for this image:
 
 ```bash
-docker sbom flask-server:latest
+docker scout sbom flask-server:latest --format list
 ```
 
 The output will show the SBOM in a table format. Try to export it to a SPDX file:
 
 ```bash
-docker sbom --format spdx-json flask-server:latest > sbom.spdx.json
+docker sbom flask-server:latest --format spdx --output sbom.spdx.json
 ```
 
 If you investigate the file, you will see that it contains a list of all the packages used in the image, their versions, and the licenses.
 
 ### Exercises
 
-- 2.1. Use `docker sbom --help` to check available formats for the SBOM output.
+- 2.1. Use `docker scout sbom --help` to check available formats for the SBOM output.
 - 2.2. Compare different base images: `docker sbom node:22` vs `docker sbom node:22-alpine` - which has fewer packages?

labspace/04-sbom-attestations.md

@@ -2,7 +2,7 @@
 
 **Mission**: The Valkyrie sets up a camera with face recognition and says, "I can generate an ID card for everyone in Asgard, and attach it to their database face record. That way, we can verify their identity at the checkpoints."
 
-![SBOM Attestations](https://dockersecurity.io/commandos-asgard/asgard-3.1.png)
+![SBOM Attestations](https://dockersecurity.io/commandos-asgard/asgard-checkpoint.png)
 
 **Real-world context**: SBOM attestations are SBOMs generated during build time and cryptographically signed, providing tamper-proof component information that travels with your image.
 
@@ -44,6 +44,8 @@ Check the SBOM attestations for the image again:
 docker scout cves cpp-hello:with-build-stage
 ```
 
+![SBOM Attestations](https://dockersecurity.io/commandos-asgard/asgard-3.1.png)
+
 ### Exercises
 
 - 4.1. Store the SBOM locally: `docker buildx build --sbom=true --sbom-output=type=local,dest=. -t test-image .`

labspace/07-vex-attestation.md

@@ -2,7 +2,7 @@
 
 **Mission**: The Valkyrie issues "Check Exemption" badges for the Exempted CVEs, and adds them to the checkpoints. "The Exempted CVEs can pass through the checkpoints without being flagged, as they are not a threat to us."
 
-![Mina found a new warrior when fighting CVEs](https://dockersecurity.io/commandos-asgard/asgard-4.5.png)
+![Mina issues a VEX attestation for the exempted CVE](https://dockersecurity.io/commandos-asgard/asgard-vex.png)
 
 **Real-world context**: VEX attestations are cryptographically signed exemptions that travel with your image, providing tamper-proof vulnerability exception documentation that's verified automatically.
 
@@ -23,6 +23,8 @@ Next time, you won't need to pass the VEX statement to the Scout scan, as it is
 docker scout cves aerabi/flask-hello:with-sbom
 ```
 
+![Mina found a new warrior when fighting CVEs](https://dockersecurity.io/commandos-asgard/asgard-4.5.png)
+
 ### Exercises
 
 - 7.1. Research how else can one generate VEX statements besides using `vexctl create` command.

labspace/09-cosign.md

@@ -2,6 +2,8 @@
 
 **Mission**: With the party still going, Evie steps away from the celebration and quietly gets to work. One by one, she signs each SBOM attestation and each VEX attestation with her special pen, ensuring their originality. "A document without a signature is just a rumor," she says.
 
+![Evie signing the SBOM and VEX attestations](https://dockersecurity.io/commandos-asgard/asgard-sign.png)
+
 **Real-world context**: Cosign (part of the Sigstore project) lets you cryptographically sign container images and attestations. Consumers can then verify those signatures before running anything.
 
 ### Usage

labspace/10-zero-day.md

@@ -2,6 +2,8 @@
 
 **Mission**: During the party, Artemisia and Rothütle come to Gord, "Artemisia says she senses something off with Null," Rothütle adds, "I think Null is a traitor, he might be working with the CVEs." As they are talking, they notice Null throwing a smoke bomb and disappearing.
 
+![Null throwing a smoke bomb](https://dockersecurity.io/commandos-asgard/asgard-6.png)
+
 **Real-world context**: Zero-day vulnerabilities are unknown to security systems. Defense requires proactive security measures that protect against unknown attack vectors.
 
 ### Usage

labspace/11-final-mission.md

@@ -2,6 +2,8 @@
 
 The hunt is complete, but Agent Null has escaped to the Black Forest. The Commandos have successfully defended Asgard using systematic security practices.
 
+![10 Docker Commandos in Asgard](https://dockersecurity.io/blog-img/10-commandos-asgard.png)
+
 ## Victory Conditions
 
 - ✅ All builds generate SBOM and provenance attestations