The Video Signal

Topic

Security Engineering

All digests tagged Security Engineering

We let an AI agent execute Bash and lived to talk about it — Sarah Sanders, PostHog thumbnail

· 21:00

We let an AI agent execute Bash and lived to talk about it — Sarah Sanders, PostHog

The talk details the architecture and security challenges of building agentic CLI tools, exemplified by PostHog's 'Wizard.' The speaker emphasizes that an agent with command execution capabilities is essentially a 'malware starter pack.' Security must be layered, deterministic, and must account for dangerous inputs originating not only from users but also from the system's own supply chain (the 'Context Mill'). The solution involves implementing a dedicated, deterministic scanner (Warlock) and ensuring that the LLM layer acts only as an 'adviser,' never an enforcer.

Key takeaways

  1. The Danger of Agentic Tools 0:03

    An agent that can run commands is structurally similar to malware, requiring extreme caution. The threat model must account for how 'attacks compose' from multiple, seemingly innocent vulnerabilities.

  2. Context Supply Chain Risk 0:11

    The most dangerous input can come from the system's own supply chain (the Context Mill), such as a seemingly harmless prompt injection payload signed by the development team.

  3. Security Must Be Deterministic 0:15

    For enforcement, security mechanisms must be deterministic and mechanical. The LLM layer should only be an 'adviser' to reduce noise, never the primary enforcer, to prevent failure modes.

Watch on YouTube Full article

Oleg Šelajev - You're absolutely right, it was your home directory! - AI Native DevCon June 2026 thumbnail

· 33:15

Oleg Šelajev - You're absolutely right, it was your home directory! - AI Native DevCon June 2026

The session addresses the security risks posed by autonomous AI agents running locally, noting that these agents can pose significant threats by accessing sensitive data and executing arbitrary code. To mitigate this risk, Docker introduces sandboxing using MicroVMs—a hardware-level isolation primitive superior to traditional containers. This approach allows developers to run powerful AI agents in a restricted environment with controlled access to the filesystem, network, and secrets, enabling high productivity without sacrificing security.

Key takeaways

  1. The Danger of Autonomous Agents 2:00

    AI agents are highly autonomous and persistent; if given sufficient access (data, external communication, internet), they can execute malicious actions like stealing SSH keys or cloud credentials, leading to massive security incidents. The stakes are asymmetric: the attacker only needs to succeed once.

  2. MicroVMs for Hard Isolation 6:00

    Traditional containers share a kernel and are insufficient for high-stakes AI agent sandboxing due to potential container escaping exploits. Docker's solution uses MicroVMs, providing hardware-level isolation that significantly raises the security boundary.

  3. The Role of Kits (YAML) 10:00

    To improve developer experience in isolated environments, 'Kits' are introduced. These declarative YAML files define reusable configurations for a sandbox, specifying required commands, tools (e.g., programming language toolchains), file placements, and network rules.

  4. Controlled Access Mechanisms 8:00

    Sandboxes implement critical controls including networking proxies (to block specific domains/services) and secrets injection mechanisms, allowing agents to function without direct access to the host machine's private data.

Watch on YouTube Full article

Platform Engineering in the age of Generative AI - thumbnail

· 1:02:16

Platform Engineering in the age of Generative AI -

The talk argues that while Generative AI tools significantly accelerate code generation and development speed, they are not a 'silver bullet.' To harness AI effectively, organizations must first establish robust platform engineering foundations. The core focus is on implementing comprehensive 'harnessing'—a system of controls (guides and sensors) that ensure consistent behavior, mitigate security vulnerabilities, and guide agents toward high-quality outcomes. Key strategies include adopting open standards like those from the Aentic AI Foundation, utilizing Spec Driven Development (SDD), and treating the entire development environment as a codified, observable artifact.

Key takeaways

  1. Platform Engineering's Goal: Reducing Cognitive Overload 10:40

    Platform engineering should aim to make it the 'path of least resistance' for developers by building internal mechanisms and golden paths. This reduces cognitive overload, allowing teams to focus on delivering value rather than managing complex compliance, security, or deployment processes.

  2. AI is an Amplifier, Not a Solution 20:00

    Generative AI amplifies existing engineering quality. If foundational practices (like documentation and consistent tooling) are weak, AI will amplify those weaknesses, leading to basic security failures or unreliable code.

  3. The Importance of Agentic Standards 30:00

    The Aentic AI Foundation is establishing open standards (MCP servers, agent MD files, and agent skills) to standardize how agents interact with tools. MCP servers are described as a 'USB-C for AI agents,' providing a standard protocol layer.

  4. Harness Engineering: Controlling the Agent 40:00

    A robust 'harness' is the system surrounding the LLM model. It uses two types of controls: **Feed-forward guides** (anticipating and steering behavior, e.g., Agent MD files) and **Feedback sensors** (observing after action, e.g., linters, unit tests, or an 'LLM as a judge' pattern).

Watch on YouTube Full article