A standard of security requirements for web applications and APIs, three levels from L1 to L3.
Standards, guides, cheat sheets and videos on secure development: 20 documents. Each has a short assessment: when to apply it and where to start.
Selection and assessments: Amir Akimbayev
A standard of security requirements for web applications and APIs, three levels from L1 to L3.
A mobile application security standard.
A guide to security testing of Android and iOS mobile applications.
A guide to security testing of web applications.
The whole series: 133 short OWASP cheat sheets on topics from authentication to AI agents. Table of contents in alphabetical order.
Open the document →Secure building and running of containers.
Typical vulnerabilities in Java code and how to avoid them.
Secure configuration of Kubernetes clusters.
How to store and issue passwords, tokens and keys.
Risks of code written with an AI assistant: invented and outdated dependencies, instruction injection, MCP, deleted tests, code leaking into prompts.
Open the document →Security of AI agents: permissions, tools, isolation and control of actions.
Open the document →Security of MCP servers and the tools connected to AI agents.
Open the document →Protecting LLM applications from instruction injection through user input and external data.
Open the document →Protecting pipelines, runners and build tokens.
Open the document →The software supply chain: dependencies, build, signatures and artifact provenance.
Open the document →The ten most critical risks of web applications.
The main API risks.
The main risks of applications built on large language models.
A secure development maturity model for self-assessment and a roadmap.
A study of what large companies actually do in secure development.