arXiv (All)
open access
Applying Security by Design at the Point of Execution: How Governed Security Requirements Affect the Security of AI-Generated Code
Security by design asks that security requirements are defined before code is written. Secure-code benchmarks typically measure the opposite situation: the agent receives the task without requirements and is scored with security tests it has not seen. We measured what changes when security requireme
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- Applying Security by Design at the Point of Execution: How Governed Security Requirements Affect the Security of AI-Generated Code#1242722
- An Empirical Case Study of Prompt Engineering Strategies for Bypassing Multi-Layer Agent Security Defenses#1324717
- From Requirements to Attack Trees: Grounded LLM Agents for Design-Time Security Review#1199094
- SoK: AI Secure Code Generation: Progress, Pitfalls, and Paths Forward#306972
- BAITBENCH: Measuring Agent Reward Hacking with Optional Shortcuts Planted in ML Tasks#818778
Record · ID 1247586
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive