Practical AppSec guides: what to do, in what order and why. Regulator requirements, adoption and incidents, step by step and with links to sources.
New to the topic? Start with the guide “Secure development in Kazakhstan” →
November 2026: CVE-2026-123158, CVSS 8.1. On Linux with musl without PAM, accounts without a password accept any long password. Who is affected, Alpine packages, the temporary mitigation, signs of compromise, the attack timeline, CISA's position.
Open →Night of 2 November 2026: at three EFS sites the setpoints of plasma freezers were changed remotely. Statements from EFS, the ministry and the contractor, the CERT-FR alert, the link to the supermarket attacks, lessons for any equipment with remote control.
Open →29 October 2026: about $6.3 billion from hot wallets. Statements from Binance, estimates from Elliptic, Chainalysis and TRM Labs, two versions of the cause, four Ethereum transactions verified by the editors, and lessons for any payment service.
Open →October 2026: two vulnerabilities in PHP itself, CVSS 9.2, no login needed. What KZ-CERT and CISA recommend, vulnerable versions and packages, what companies in Kazakhstan did, sites on 1C-Bitrix.
Open →A week-by-week plan: a list of systems and owners, a first “as is” scan, triage of findings by priority, integration into development and release control. Day-30 metrics and ARDFM No. 53 clauses.
Open →The decision order in one review: whether it affects you, how urgent it is (KEV, EPSS, exposure), how to update a transitive dependency, when to replace a library and how to accept the risk in writing.
Open →September 2026: CVSS 10 in the GitLab CE/EE commits API, in the exploited-vulnerabilities catalog one day after the patch. Affected versions, 13 days without a patch on older branches, what to check in the logs.
Open →What the resolution that replaced NBK No. 48 requires from banks in software development: mandatory SAST and library analysis, fixing critical vulnerabilities before release, code storage, pentest. A checklist and quotes by clause.
Open →Government of Kazakhstan Resolution No. 832: who it applies to, the software development and acceptance process, testing for information security compliance, the single repository of the “e-government”. A checklist and quotes by clause.
Open →All ten categories of the 2025 edition in Russian: the new A10, the software supply chain, SSRF inside Broken Access Control. What to check for each and with which tools.
Open →24 questions for any vendor: stack coverage, noise and false positives, CI/CD integration, On-Premise, regulator requirements, total cost. And how to run a pilot so the comparison is fair.
Open →