How Anthropic Secures Its AI-Native Software Development Lifecycle

This article details how Anthropic has adapted its security processes to manage an AI-native software development lifecycle (SDLC) where Claude now authors approximately 80% of the code merged into its codebase, and over half of all code is merged by an internal version of Claude Tag. The company's security strategy involves several key principles: shifting security left by encoding guidelines directly into agent instructions (CLAUDE.md) to prevent vulnerabilities at creation; using hard identity and access boundaries and remote virtual machines to contain blast radius and limit agent egress; combining automated deterministic and agentic reviews at the code review and CI stages while keeping humans accountable for critical approvals and sampling a percentage of automated decisions; and implementing continuous AI-powered dynamic testing to match deployment cadence. The article also covers monitoring practices where agents triage alerts, root-cause bugs, and draft fixes, but cannot deploy automatically due to strict permission boundaries, as well as governance measures like logging all agent actions to the SIEM and monitoring dashboards to oversee automated loops. The overarching theme is that security engineering shifts from reviewing individual bugs to managing and securing agentic loops, requiring continuous adaptation as model capabilities rapidly evolve. 

https://claude.com/blog/how-anthropic-secures-its-ai-native-software-development-lifecycle

Comments

Post a Comment

Popular posts from this blog

Prompt Engineering Demands Rigorous Evaluation

In the blog post “Prompt Engineering Requires Evaluation” on the Shostack + Associates website, the author argues that treating prompts for large language models (LLMs) merely as creative artefacts is insufficient. Engineering prompts properly demands structured evaluation frameworks — what the AI community calls “evals” — to test which prompt versions work better, with which models, and under which conditions. The post highlights that simply assuming a prompt is “good enough” creates risks when LLMs are integrated into production systems (e.g., for threat modeling). It advocates for measuring prompt performance, variation effects, and tool-chain dependencies (model, context, ancillary materials).  Ultimately the message is: prompt engineering should borrow disciplined practices from software engineering (versioning, testing, benchmarking) rather than relying on informal experimentation.  https://shostack.org/blog/prompt-enignieering-requires-evaluation/
Read more

Open-SPDD proposes an open framework for Spec-Driven Development workflows

Open-SPDD is an open-source project focused on Spec-Driven Product Development, aiming to formalize how software specifications, requirements, architecture, and implementation interact throughout the development lifecycle. The project promotes structured specification management, traceability, and AI-assisted engineering workflows, positioning itself as a foundation for “SpecOps”-style development practices. Its GitHub materials describe SPDD as a way to reduce ambiguity between planning and execution by treating specifications as first-class operational artifacts that can drive automation, validation, and collaboration across engineering teams  https://github.com/gszhangwei/open-spdd
Read more

OWASP ASVS 5.0 Released - Key Updates and What You Need to Know

The OWASP Foundation has released version 5.0 of the Application Security Verification Standard (ASVS), a major update to their security framework for web applications. This new version features restructured security requirements for better clarity, expanded guidance for cloud and API security, improved DevSecOps integration for CI/CD pipelines, updated threat modeling support, and enhanced compliance mapping with standards like NIST and PCI DSS. ASVS serves as a critical benchmark for developers building secure applications, penetration testers conducting security assessments, and auditors performing compliance reviews.  The standard is available for download from the OWASP ASVS project page, with organizations encouraged to integrate it into their software development lifecycles through code reviews and security testing tools. As a vendor-neutral, community-driven project, OWASP continues to welcome contributions to further develop the standard. This release represents an importa...
Read more