Playing Safely in the...

on YouTube ↗34m

" summary

WASM modules ship as OCI artifact blobs that reveal imports/exports so tools can inspect capabilities before execution; runtimes like WasmEdge and wasmCloud enforce a per-module sandbox and teams run fuzzers and sanitizers against runtimes. The component model lets engineers choose shared or isolated linear memory to shrink blast radii and apply least privilege. A current proposal adds no-read-no-write pages to give static read‑only regions without heavy OS support, reducing common attack surfaces.

AI-written summary · about

" chapters (7)

1. 0:00Introduction
2. 2:06Containers to WebAssembly security
3. 7:07Engineering mistakes in WebAssembly
4. 16:40Memory safety and component model
5. 25:22WebAssembly sandboxing in practice
6. 28:12WebAssembly isn't just containers
7. 30:38Security best practices

" related talks

• 39mWhat is Wasm A Non Experts OpinionKelsey Hightower · KCD Ukraine 2023
• 38mWebAssembly beyond the browserMete Atamel · Voxxed Days Thessaloniki 2023
• 36mSandboxing Your Sandbox: Leveraging Hypervisors for WebAssembly SecurityDanilo (Dan) Chiarlone · WasmCon 2023
• 31mHow We Can Create a Thriving Wasm EcosystemTaylor Thomas, Matt Butcher · Cloud Native Rejekts NA 2021
• 35mModern Sandboxing: Using Web Assembly in JavaFrank Lyaruu · Voxxed Days Crete 2025
• 48mDon't Trust Anything! Real-world Uses For WebAssemblyKatie Bell · YOW! Perth 2023
• 17mA case for Web AssemblyElvina Valieva · BDX I/O 2018
• 33mZero Trust in the Cloud with WebAssembly and WasmCloudKevin Hoffman · CloudNativeSecurityCon North America 2023