The Video Signal

Topic

Data Security

All digests tagged Data Security

· 1:06:04

Why This Company Won't Let AI Agents Touch Bash

The presentation details the evolution of an internal AI agent platform at Cyera, transforming a personal assistant project into an enterprise-wide tool for data security and operational efficiency. The core focus is on building robust guardrails to prevent agents from becoming uncontrolled 'black boxes.' Key architectural innovations include whitelisting tools over blacklisting them, implementing a structured citation system for verifiable claims, and replacing traditional RAG with a Knowledge Graph (KG) that allows agents to navigate interconnected data like an LLM wiki. The platform emphasizes controlled deployment, allowing multiple developers to build and own specialized agents while maintaining centralized security and governance.

Key takeaways

  1. Controlled Agent Architecture

    The system prioritizes control by whitelisting specific tools rather than blacklisting forbidden actions. A critical guardrail is the use of structured, validated output, ensuring that an agent cannot execute arbitrary code (like unrestricted Bash) or leak sensitive data outside its designated context.

  2. Citation and Hallucination Mitigation 20:55

    To ensure reliability, every claim generated by the agent must be backed by a citation. This is achieved by forcing the model to output structured blocks containing both the claim and the source reference. A second model then performs clean-context verification against the raw data to drastically reduce hallucinations.

  3. Knowledge Graph over RAG 32:33

    The platform utilizes a Knowledge Graph (KG) instead of standard RAG for context retrieval. This allows agents to 'walk' connections between entities (e.g., an exception, a service, and the related pull request), providing more structured and reliable data exploration than simply dumping retrieved documents.

  4. Adoption through Platform Engineering 50:27

    To drive adoption across engineering teams, the platform was designed to be easily customizable. By allowing users to name and modify their own agents (e.g., 'It's my agent'), the barrier to entry is lowered, promoting organic growth with a strategy of 'carrots, not sticks.'

Watch on YouTube Full article

· 14:04

I Cut the Internet and Let AI Read the File I Could Never Upload. It Caught the Leak.

This video details methods for running AI models locally on sensitive documents while completely disconnected from the internet ('air-gapping'). The core problem addressed is data leakage risk when uploading proprietary or PII-containing files to cloud AI providers. Solutions range from using open-source tools like LM Studio with downloaded, local models (e.g., GPT-OSS Safeguard 20B) to sophisticated enterprise methods utilizing Azure and LoRA for fine-tuning within a controlled boundary.

Key takeaways

  1. Local AI Processing Capability

    It is possible to run downloaded, open-weight models on a laptop with Wi-Fi disabled. These local models can scan documents for private material (PII, financial data, legal notes) and mask it without sending any data over the network.

  2. Enterprise Adoption of Local AI

    Large companies like Discovery Bank and Bayer are implementing specialized, fine-tuned models (on-premise/Azure) to handle confidential information. This approach allows for faster processing while keeping proprietary data within a controlled boundary.

  3. The Risk of Cloud Dependence 5:13

    Even if an AI model claims it did not look at a file, the logs may show that the entire repository was uploaded to the provider (e.g., Grok build leak), emphasizing the need for hard guardrails like air-gapping.

  4. LoRA and Enterprise Tuning

    Microsoft uses Low-Rank Adaptation (LoRA) to fine-tune models by adjusting only a subset of parameters, allowing large clients to create highly specialized models that outperform general cloud providers for specific tasks.

Watch on YouTube Full article