Sari la conținut

Română · beta. Traducerea a fost făcută automat și este încă în curs de revizuire. Citește pagina în engleză

perspectiva aiqbenchSiguranță AI

analiza aiqbench

This integration applies Model Context Protocol (MCP) to bridge disconnected security design artifacts with real-time AI-assisted code reviews at Dropbox. By centralizing threat models and requirements within the development workflow via an internal knowledge platform, the system reduces context switching while keeping security intent visible during implementation without automating decision-making. This represents a practical application of MCP in enterprise engineering environments where maintaining alignment between high-level design specifications and low-level code changes is critical for robust AI safety practices.
Sursă care acoperăInfoQ
Ce este aceastaLectura unui model asupra articolului și a acoperirii conexe, scrisă pentru aiqbench. Nu sunt cuvintele publicației.

Dropbox Integrates MCP and Dash to Close the Gap between Security Design and Code Review

InfoQ10 min de cititArticolul și perspectiva sunt în engleză.

Dropbox has integrated Model Context Protocol (MCP) with its internal knowledge platform, Dash, to surface security design context during AI assisted code reviews. The system retrieves threat models and security requirements for pull requests, helping reviewers validate implementation against design intent. An InfoQ Q&A explores the architecture and key lessons learned. By Leela Kumili

Dropbox has introduced a new engineering approach that connects security design artifacts directly with code review workflows using Model Context Protocol (MCP) and its internal knowledge system, Dash. The initiative aims to address a persistent gap in large engineering organizations: security requirements are typically defined during design reviews, but enforcement and verification occur much later, during code reviews, often without full context. In many teams, threat models, design documents, and security requirements are created as standalone artifacts and stored separately from the codebase. As systems evolve, these documents often become stale or disconnected from implementation details. This leads to a recurring problem where engineers and reviewers must manually trace security intent back to code changes, increasing the likelihood of missed requirements or inconsistent enforcement. Dropbox’s approach uses Dash as a centralized indexing and retrieval layer across internal documentation systems. Dash preserves existing access control policies while making organizational knowledge queryable. MCP provides a standardized protocol layer that enables AI systems to retrieve and use this context in developer workflows, such as code review. When a pull request is created, the system identifies relevant code changes and uses MCP enabled retrieval…

Extras afișat conform termenilor RSS ai publicației · 190 cuvinte · textul integral și figurile sunt pe site-ul publicației

Subiecte conexe