Implement AppSec
A plan for a CISO and head of InfoSec: from the list of applications and regulator requirements to the release rule, the team and process maturity.
Answer for yourself and the team: which risks are unacceptable, what the regulator requires, what we want to achieve in a year. Without an answer any tool turns into a report nobody reads.
Which applications exist, where their code lives, who the owner is and who ships releases. Without the list you cannot count coverage or answer the regulator.
Divide systems by damage: money, personal data, availability for customers. Implementation starts with the most critical.
Secure development requirements for banks and financial organizations of Kazakhstan. A point-by-point breakdown: what is mandatory and what is checked.
Government Resolution No. 832 of the Republic of Kazakhstan for the public sector and those who integrate with it: software development, acceptance and testing.
ASVS is an OWASP standard with verifiable security requirements for web applications and APIs. The current version is 5.0 (2025).
How to compare SAST, SCA and platforms: languages, false positives, work in a closed perimeter, reports for the regulator.
SAST is a check of source code for vulnerabilities without running the application.
Secret detection is a check of code and repository history for passwords, tokens, API keys, connection strings and private keys that ended up there.
SCA is a check of the libraries and dependencies an application is built from: whether the versions in use have known vulnerabilities (CVEs) and under which licenses the code is distributed.
SCA and SAST on every merge request, review of the first findings, a release rule. A 30-day plan is in the Playbook.
A significant part of code is written by outsourcers. It goes through the same pipeline and the same checks as your own, and security requirements are written into the contract.
Your own code is about 15% of a project; the rest is libraries and images. All dependencies come through your own proxy repository with checking and quarantine, not directly from the internet.
A short corporate document: what is mandatory in code and what is forbidden. The basis is the free OWASP Cheat Sheets and recommendations for your language. Secure code is a standard, not an option.
A Quality Gate is an automatic checkpoint in the pipeline: if the check results do not meet the policy, the build does not go further.
A block introduced right away gets turned off within a week. For two to four weeks only collect statistics, then block one clear class of vulnerabilities and expand as teams get ready.
A closing deadline by criticality: critical before release, the rest on a schedule. For banks the requirements are described in the ARDFM Resolution No. 53 breakdown.
Not every finding can be closed by the release. You need a clear path: who accepts the risk, for how long and where it is recorded.
A Security Champion is a developer in a product team who, besides their main work, is responsible for security: helps review findings, promotes practices, connects the team with the InfoSec department.
A short course on the team's stack and a review of findings from its own code. The route for developers is the "Secure Code" roadmap.
Vulnerability management is a continuous process: find, assess, prioritize, fix and confirm the fix.
What to do in the first hours when a critical vulnerability is found in a popular library.
Four reports in different formats and Excel do not work. SAST, SCA and DAST findings are collected in one place without duplicates, statuses are synchronized with the task tracker, and management gets one clear number.
A ban breeds shadow use. You need an allowed path that is more convenient than the workaround: a registry of tools and agents, a corporate perimeter, masking of secrets before sending, a request log.
Metrics the business understands: coverage of applications by checks, how many critical issues are closed and how fast, the number of open exceptions.
A review of the architecture with the question "what could go wrong here". You can start with three questions before a feature: where the data is stored, who gets access, what happens if it is stolen or changed. Then 30 minutes once a sprint, and for an audit a full STRIDE with a document.
Once per release or quarter: a system diagram and five questions: authorization, logs, encryption, access, backups. OWASP ASVS level L1 works as a checklist.
A pentest is a controlled simulation of a real attack: specialists look for vulnerabilities and try to exploit them to show how far an attacker can go.
SAMM is an open OWASP model for assessing and developing secure development maturity. The current version is 2.x.
A DevSecOps maturity model: which practices to introduce in the pipeline and in which order, by levels from first to fourth. Handy for showing a team a plan for the year.