Pricing Insights
Book a demo

AppSec Engineer

The path into application security: from programming languages and typical vulnerabilities to pipeline checks, processes and your own expertise.

40 topics7 stages stagetopicalso in another route
Start
1.1How the web works

HTTP requests and responses, headers, cookies, CORS and the same-origin policy. Without this you cannot understand XSS, CSRF or half of the DAST findings.

1.2Linux and networks

Processes, file permissions, ports, DNS, TLS. The level of "run an application in a container and look at its traffic" is enough.

1.3Several programming languages

A basic level in two or three of the languages most common in companies: Java or C#, Python, JavaScript/TypeScript, Go. Enough to read code, understand frameworks and build a project; without this you cannot make sense of scanner findings.

1.4Git and merge request

Branches, merge requests, history. Security checks live in the MR, and leaked secrets stay in the repository history.

Stage 1Foundation4 topics
2.1OWASP Top 10 2

OWASP Top 10 is a regularly updated list of the most critical web application security risks from the OWASP community.

2.2CWE

CWE is a catalog of software weakness types that lead to vulnerabilities, maintained by MITRE. For example, CWE-89 is SQL injection, CWE-79 is XSS, CWE-798 is hardcoded credentials.

2.3API security 2

API security is the protection of the programming interfaces through which mobile apps, frontends and services communicate.

2.4AI and LLM vulnerabilities 2

Prompt injection, data leakage through the model, data poisoning, unsafe output. If a product uses LLMs or agents, this is an attacker's input like any other.

2.5Labs 2

Breaking practice applications is the fastest way to understand a vulnerability. Free: OWASP Juice Shop and PortSwigger Web Security Academy; then HackTheBox, TryHackMe and CTFs.

Stage 2Vulnerabilities5 topics
3.1ARDFM No. 53 3

Secure development requirements for banks and financial organizations of Kazakhstan. A point-by-point breakdown: what is mandatory and what is checked.

3.2Unified Requirements 3

Government Resolution No. 832 of the Republic of Kazakhstan for the public sector and those who integrate with it: software development, acceptance and testing.

3.3OWASP ASVS 3

ASVS is an OWASP standard with verifiable security requirements for web applications and APIs. The current version is 5.0 (2025).

Stage 3Requirements3 topics
4.1SAST 3

SAST is a check of source code for vulnerabilities without running the application.

4.2Secrets in code 23

Secret detection is a check of code and repository history for passwords, tokens, API keys, connection strings and private keys that ended up there.

4.3SCA 23

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.

4.4DAST

DAST is testing of an already running application "from outside": the scanner walks through the web interface and API, sends specially crafted requests and analyzes the responses.

4.5IaC and containers

IaC scanning is a check of infrastructure descriptions (Terraform, CloudFormation, Kubernetes manifests, Helm charts, Dockerfile) for insecure settings before they reach the cloud or cluster.

4.6Fuzzing

Fuzzing is a testing method in which a program is fed a huge number of malformed, unexpected or random inputs and watched to see whether it crashes or behaves incorrectly.

4.7Mobile applications

MAST is security testing of mobile applications: analysis of APK and IPA builds and their behavior on a device.

4.8False positives 2

A false positive is a scanner finding that is not actually a vulnerability: the data is already validated, the code is unreachable or the context makes the attack impossible.

4.9Triage

Triage is the review of findings: whether it is a real vulnerability, how dangerous it is in this particular application, who fixes it and by when.

Stage 4Checks9 topics
5.1CI/CD

GitLab CI, GitHub Actions, Jenkins: where to run checks, how to cache them and not slow down the build.

5.2Quality gate 23

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.

5.3SARIF

SARIF is an OASIS standard for exchanging static analysis results in JSON format. Version 2.1.0 is supported by most modern scanners.

5.4SBOM

An SBOM is a machine-readable list of everything a program consists of: libraries, their versions, suppliers, licenses.

5.5Supply chain

A supply chain attack compromises not the application itself but what and with what it is built: libraries, build tools, package repositories, updates.

5.6Security of CI/CD itself

The pipeline is a target too: secrets in variables, third-party actions and plugins, runner permissions. An attack on the build reaches all releases at once.

5.7A single entry point for components 3

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.

Stage 5Pipeline7 topics
6.1SSDLC

SSDLC is a development lifecycle in which every stage has its own security actions: from requirements and architecture to release and maintenance.

6.2Security champions 3

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.

6.3Vulnerability management 3

Vulnerability management is a continuous process: find, assess, prioritize, fix and confirm the fix.

6.4CVSS, EPSS, KEV

CVSS says how dangerous a vulnerability is in theory, EPSS says how likely it is to be exploited in the next 30 days, KEV says it is already being exploited. Together they decide what to fix first.

6.5Threat modeling 3

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.

6.6Architecture review 3

Once per release or quarter: a system diagram and five questions: authorization, logs, encryption, access, backups. OWASP ASVS level L1 works as a checklist.

6.7OWASP SAMM 3

SAMM is an open OWASP model for assessing and developing secure development maturity. The current version is 2.x.

6.8OWASP DSOMM 3

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.

Stage 6Process8 topics
7.1Triage 10,000 vulnerabilities

An eye for it comes only with volume. After 10,000 reviewed SAST and SCA findings from real projects, you tell a real vulnerability from a false one in minutes, and write rules and exclusions deliberately.

7.2Explain simply

Half of AppSec work is reaching agreement with development. The ability to explain a vulnerability in plain language, speak at a meetup or write a clear breakdown is valued no less than knowledge of tools.

7.3Communities

OWASP Almaty, conferences and meetups in Central Asia: where to ask a question and where to speak.

7.4Books

A short AppSec shelf with reviews: what to read after the first projects.

Stage 7Expertise4 topics