Pricing Insights
Book a demo

Quest Loot

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

where to startas you growfor mature teams

Videos and channels

What to watch about AI and InfoSec without the noise

Requirements standards

What a secure application must have
OWASP ASVS 5.0 where to start

A standard of security requirements for web applications and APIs, three levels from L1 to L3.

Amir's assessmentStart with L1 as a checklist for an architecture review once per release. L2 is a reasonable goal for banks and fintech. Full L3 is needed by few; do not try to cover it all at once.
Open the document →
OWASP MASVS 2.1 as you grow

A mobile application security standard.

Amir's assessmentMandatory if a mobile app is your main product: banks, microfinance organizations, super apps. Use it together with MASTG: MASVS says what to check, MASTG says how.
Open the document →

Testing guides

How to check
OWASP MASTG 2.0 as you grow

A guide to security testing of Android and iOS mobile applications.

Amir's assessmentA workbook for those who test mobile apps. Developers should read at least the sections on data storage and network communication, where the most common mistakes are.
Open the document →
OWASP WSTG 4.2 for mature teams

A guide to security testing of web applications.

Amir's assessmentUseful for understanding what exactly a pentester and a DAST scanner do. As a process for a small team it is heavy; take individual chapters.
Open the document →

Cheat sheets

Short practical advice on a technology

Secure building and running of containers.

Amir's assessmentThe fastest benefit of the whole list: not root, a minimal base image, no secrets in the image. This covers most container findings.
Open the document →
Java Security Cheat Sheet where to start

Typical vulnerabilities in Java code and how to avoid them.

Amir's assessmentGive it to Java teams before turning on SAST blocking: injections, deserialization, logging. A developer who has read the cheat sheet argues less with findings.
Open the document →

How to store and issue passwords, tokens and keys.

Amir's assessmentSecrets in .env and in git history are among the most frequent findings. This explains how to build secrets management so they do not end up there.
Open the document →

Threat rankings

A common language for InfoSec and development
OWASP Top 10 2025 where to start

The ten most critical risks of web applications.

Amir's assessmentA decent working document: the main risks of web applications and a common language for security specialists and developers. For deep understanding, use ASVS.
Open the document →

The main API risks.

Amir's assessmentIf your product is an API and a mobile app, start with this list, not the web Top 10. The most common one is access to other users' objects (BOLA/IDOR).
Open the document →

Maturity models

Where you are now and where to grow
OWASP SAMM 2.2 as you grow

A secure development maturity model for self-assessment and a roadmap.

Amir's assessmentHandy for showing management where you are now and where you are heading. Do a self-assessment every six months and compare.
Open the document →
BSIMM for mature teams

A study of what large companies actually do in secure development.

Amir's assessmentUseful for comparing yourself with the market. As a plan for a small team it does not fit: these are practices of companies with hundreds of developers.
Open the document →