Secure development in Kazakhstan
What regulators require, which checks are needed, how to implement them, and what is happening right now. Everything on the topic on one page, details via links.
Who is obliged and to what
Two main documents: for banks, ARDFM Resolution No. 53; for the public sector and those who integrate with it, the Unified Requirements.
What checks exist
Each check looks at its own thing. The banking regulator explicitly requires the first two; the others cover what they do not see.
28 more terms (DevSecOps, SSDLC, Quality Gate, KEV, EPSS, OWASP ASVS) are in the AppSec glossary. Which technologies work against which attacks is in the attack log matrix.
How to implement
Practical step-by-step guides: from the first scan to working with vulnerabilities and choosing a tool.
All materials are in the Playbook. OWASP standards and cheat sheets, with a suggestion of where to start, are in the Quest Loot.
What is happening now
Requirements are a minimum. Attackers go after what is vulnerable today.
Analysis of the loud vulnerability of the month: CVE of the month: GitLab CVE-2026-85706, reading server files without login.
Where the people are
Conferences, meetups and chats where application security is discussed in Central Asia.
In short
Is SAST mandatory for banks in Kazakhstan?
Yes, for remote service software: ARDFM Resolution No. 53 (clause 148) names static source code analysis and third-party library analysis as mandatory stages of security testing.
What software development requirements apply to the public sector?
The Unified Requirements in the field of ICT and information security (Government Resolution No. 832 of the Republic of Kazakhstan): software development and acceptance process, tests for information security compliance before commissioning. The term SAST is not used in them directly.
Where to start with secure development?
With a list of systems and owners, then automatic scanning of code (SAST) and libraries (SCA) on every change, and a rule that does not let new critical vulnerabilities into a release. A step-by-step plan is in the article "SAST and SCA in a Bank: the First 30 Days".