Udemy - DevSecOps Masterclass for Gaming Studios - Embedding Security torrent

DevSecOps Masterclass for Gaming Studios: Embedding Security
https://WebToolTip.com
Published 9/2026

MP4 | Video: h264, 1920x1080 | Audio: AAC, 44.1 KHz, 2 Ch

Language: English | Duration: 20h 33m | Size: 928.39 MB
From a leaky CI pipeline to a signed, scanned, sovereign release process — built entirely in GitHub Actions.
What you'll learn

Architect a full security control plane inside GitHub Actions — branch protection, CODEOWNERS, least-privilege tokens, and reusable security workflows.

Embed SAST across your codebase and your pipeline itself with CodeQL and Semgrep, including custom rules for gaming-specific risks.

Detect and rotate exposed credentials with Gitleaks, pre-commit hooks, and a documented secret-rotation runbook, then eliminate long-lived cloud keys.

Engineer full dependency and supply-chain security — OSV-Scanner, Dependabot, CycloneDX/SPDX SBOMs, Grype scanning, license policy.

Harden containerized game services — multi-stage Dockerfiles, non-root runtime, Trivy image and config scanning, and SARIF-based findings surfaced directly.

Deploy securely to Kubernetes with hardened security contexts, resource limits, OPA/Conftest policy-as-code, GitOps design via Argo CD, and Falco-based runtime.

Orchestrate scanners into one coherent system — severity policy, warn-only rollout for new tools, PR step summaries, and evidence bundle.

Govern player data and AI-assisted workflows — data classification, privacy-by-design telemetry rules, GDPR/DORA/NIS2/EU AI Act-aware compliance mapping.

Design for sovereignty — region-aware deployment matrices, data residency boundaries, and a sovereign release checklist that ties every release to jurisdiction.

Deliver a capstone-grade Secure Gaming Studio Release Control Plane — a portfolio repository with real branch protection, real scanner output, real SBOMs.
Requirements

Knowledge: Basic Git usage (clone, commit, push, branch). No prior DevSecOps, security, or CI/CD experience required — every lab builds from a pre-flight check up. Basic familiarity with any programming language helps (the course uses a small Node.js API and C# placeholder), but you don't need to know either language deeply — every script is explained before you run it. No prior GitHub Actions experience needed; Module 1 builds your first workflow from scratch. Software (all free/open-source): Git, Docker, GitHub CLI (gh), Node.js LTS. A free GitHub account with Actions enabled (used extensively — this course lives inside real GitHub Actions workflows, not simulations). Open-source security tooling used via Docker containers or GitHub Actions: CodeQL, Semgrep, Gitleaks, OSV-Scanner, Trivy, Syft, Grype, Checkov, OPA/Conftest, Cosign — no licenses or paid accounts required. Optional for Module 8: kind and kubectl for local Kubernetes labs — a lightweight local cluster, not a cloud account. Hardware: 15GB+ free disk space, 8GB+ RAM recommended (Docker containers for multiple scanners plus an optional local Kubernetes cluster). No real game codebase, no production infrastructure, and no cloud account required — every lab builds a small, safe, synthetic game-service repository from Lab 2 onward.