1~
2Uyazvimost, obnaruzhennaya vo vremya napisaniya koda, stoit razrabotchiku minut na ispravlenie. Ta zhe uyazvimost, vyyavlennaya v produktsii, stoit tsely sprint. A yesli eye pervym naydet zlolmyshlennik, ona stoit milliony. Eto glavny argument v polzu **shift-left security**  -  perenosa proverok bezopasnosti kak mozhno ranshe v zhiznennom tsikle razrabotki.
3~
4DevSecOps beryot etu ideyu i prevrashchaet eye v praktiku: bezopasnost  -  eto ne otdelnaya faza v kontse, a nepreryvny protsess, vpletyonny v kazhdy etap razrabotki  -  ot pervoy stroki koda do razvertyvaniya v produktsii.
5~
6## Stoimost pozdney bezopasnosti
7~
8Otchyot IBM Cost of a Data Breach stabilno pokazyvaet, chto stoimost ispravleniya problem bezopasnosti rastyot eksponentsialno, chem pozhe oni obnaruzhivayutsya:
9~
10| Etap | Stoimost ispravleniya | Vremya ispravleniya |
11|------|----------------------|---------------------|
12| **IDE / Lokalnaya razrabotka** | Minuty | Sekundy do minut |
13| **Code Review / PR** | Chasy | Minuty do chasov |
14| **Pipeline CI/CD** | Dni | Chasy do dney |
15| **Staging / QA** | Nedeli | Dni |
16| **Produktsiya** | Mesyatsy | Nedeli do mesyatsev |
17| **Posle utechki dannykh** | Milliony ($) | Mesyatsy do let |
18~
19Vyvod ocheviden: kazhdy etap, na kotory vy sdvigaete bezopasnost ranshe, ekonomit poryadok velichiny v zatratakh i vremeni.
20~
21## Pipeline DevSecOps
22~
23Zrely pipeline DevSecOps integriruet proverki bezopasnosti na kazhdom etape:
24~
25```mermaid
26graph LR
27    IDE[IDE / Editor] --> PC[Pre-commit Hooks]
28    PC --> PR[Pull Request]
29    PR --> CI[CI Pipeline]
30    CI --> Build[Build / Package]
31    Build --> Deploy[Deploy]
32    Deploy --> Runtime[Runtime / Production]
33~
34    IDE -.- S1[SAST\nSecret Detection\nLinting]
35    PC -.- S2[Secrets Scan\nFormat Check]
36    PR -.- S3[Code Review\nDependency Audit]
37    CI -.- S4[SAST\nSCA\nContainer Scan\nSBOM]
38    Build -.- S5[Image Signing\nArtifact Verification]
39    Deploy -.- S6[Policy Enforcement\nAdmission Control]
40    Runtime -.- S7[DAST\nWAF\nMonitoring]
41```
42~
43Razberem kazhdy etap s konkretnymi instrumentami i konfiguratsiyey.
44~
45## Etap 1: Bezopasnost v IDE
46~
47Samaya bystraya petlya obratnoy svyazi. Lovite uyazvimosti eshchyo do togo, kak sokhranite fayl.
48~
49### Rekomenduyemye instrumenty
50~
51- **Semgrep**: lyogky staticheskiy analizator s pravilami soobshchestva dlya uyazvimostey OWASP
52- **Snyk IDE Extension**: skanirovanie uyazvimostey zavisimostey v realnom vremeni
53- **GitLens + GitLeaks**: obnaruzhenie sekretov v vashem redaktore
54- **ESLint Security Plugins**: `eslint-plugin-security` dlya Node.js, `eslint-plugin-no-unsanitized` dlya DOM XSS
55~
56### Primer: Konfiguratsiya ESLint Security
57~
58```json
59{
60  "extends": ["eslint:recommended"],
61  "plugins": ["security", "no-unsanitized"],
62  "rules": {
63    "security/detect-object-injection": "warn",
64    "security/detect-non-literal-regexp": "warn",
65    "security/detect-unsafe-regex": "error",
66    "security/detect-buffer-noassert": "error",
67    "security/detect-eval-with-expression": "error",
68    "security/detect-no-csrf-before-method-override": "error",
69    "security/detect-possible-timing-attacks": "warn",
70    "no-unsanitized/method": "error",
71    "no-unsanitized/property": "error"
72  }
73}
74```
75~
76## Etap 2: Pre-commit Hooks
77~
78Vtoraya liniya oborony. Zapuskayutsya avtomaticheski pered kazhdym commitom, blokiruya opasny kod ot popadaniya v repozitoriy.
79~
80### Gitleaks: Lovite sekrety do togo, kak oni popadut v Git
81~
82Samaya rasprostranennaya oshibka bezopasnosti v kodovykh bazakh  -  eto commit sekretov  -  API-klyuchey, paroley baz dannykh, tokenov. Kak tolko sekret popadaet v istoriyu git, yego kraynaznachitelno trudno polnostyu udalit (dazhe pri force push forki i keshi mogut yego sokhranit).
83~
84```yaml
85# .pre-commit-config.yaml
86repos:
87  - repo: https://github.com/gitleaks/gitleaks
88    rev: v8.21.0
89    hooks:
90      - id: gitleaks
91~
92  - repo: https://github.com/semgrep/semgrep
93    rev: v1.90.0
94    hooks:
95      - id: semgrep
96        args: ['--config', 'auto']
97```
98~
99Ustanovka i aktivatsiya:
100~
101```bash
102pip install pre-commit
103pre-commit install
104```
105~
106Teper kazhdy `git commit` avtomaticheski skaniruet na utechku sekretov i rasprostranyonnye uyazvimosti. Yesli chto-to obnaruzheno, commit blokiruetsya.
107~
108### Polzovatelskie pravila Gitleaks
109~
110Vy mozhete dobavit polzovatelskie shablony dlya sekretov vashey organizatsii:
111~
112```toml
113# .gitleaks.toml
114title = "Custom Gitleaks Config"
115~
116[[rules]]
117id = "internal-api-key"
118description = "Internal API key detected"
119regex = '''INTERNAL_KEY_[A-Za-z0-9]{32}'''
120tags = ["key", "internal"]
121```
122~
123## Etap 3: Bezopasnost pipeline CI/CD
124~
125Zdes proiskhodit osnovnaya rabota. Vash CI pipeline dolzhen zapuskat neskolko skanirovaniy bezopasnosti pri kazhdom pull requeste.
126~
127### SAST (Static Application Security Testing)
128~
129Instrumenty SAST analiziruyut iskhodny kod bez yego vypolneniya, isha shablony, ukazyvayushchiye na uyazvimosti.
130~
131```yaml
132# .github/workflows/security.yml
133name: Security Scan
134on:
135  pull_request:
136    branches: [main]
137~
138jobs:
139  sast:
140    name: Static Analysis
141    runs-on: ubuntu-latest
142    steps:
143      - uses: actions/checkout@v4
144~
145      - name: Run Semgrep
146        uses: semgrep/semgrep-action@v1
147        with:
148          config: >-
149            p/owasp-top-ten
150            p/typescript
151            p/nodejs
152            p/react
153          generateSarif: true
154~
155      - name: Upload SARIF
156        uses: github/codeql-action/upload-sarif@v3
157        with:
158          sarif_file: semgrep.sarif
159```
160~
161Nabor pravil `p/owasp-top-ten` ot Semgrep lovit naibolee rasprostranyonnye uyazvimosti: SQL injection, XSS, SSRF, path traversal, insecure deserialization i drugie.
162~
163### SCA (Software Composition Analysis)
164~
165SCA skaniruet vashi zavisimosti na izvestnye uyazvimosti. Eto kriticheski vazhno  -  bolee 80% koda sovremennykh prilozheniy postepaet iz zavisimostey open-source.
166~
167```yaml
168  dependency-scan:
169    name: Dependency Audit
170    runs-on: ubuntu-latest
171    steps:
172      - uses: actions/checkout@v4
173~
174      - name: Run Snyk
175        uses: snyk/actions/node@master
176        env:
177          SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}
178        with:
179          args: --severity-threshold=high
180~
181      - name: npm audit
182        run: npm audit --audit-level=high
183```
184~
185### Bezopasnost konteinerov s Trivy
186~
187Yesli vy sozdayote obrazy Docker, ikh skanirovanie na uyazvimosti neobkhodimo. **Trivy**  -  samyy populyarny open-source skaner konteinerov.
188~
189```yaml
190  container-scan:
191    name: Container Security
192    runs-on: ubuntu-latest
193    steps:
194      - uses: actions/checkout@v4
195~
196      - name: Build image
197        run: docker build -t my-app:${{ github.sha }} .
198~
199      - name: Run Trivy
200        uses: aquasecurity/trivy-action@master
201        with:
202          image-ref: my-app:${{ github.sha }}
203          format: 'sarif'
204          output: 'trivy-results.sarif'
205          severity: 'CRITICAL,HIGH'
206          exit-code: '1'
207~
208      - name: Upload Trivy SARIF
209        uses: github/codeql-action/upload-sarif@v3
210        with:
211          sarif_file: trivy-results.sarif
212```
213~
214### Generatsiya SBOM
215~
216**Software Bill of Materials (SBOM)**  -  eto polny perechen kazhdogo komponenta v vashem prilozhenii. Vsyo chashche trebuyetsya ramkami sootvetstviya i gosudarstvennymi regulyatsiyami (Ispolnitelny ukaz prezidenta SSHA po kiberbezopasnosti predpisyvaet SBOM dlya federalnogo programmnogo obespecheniya).
217~
218```yaml
219  sbom:
220    name: Generate SBOM
221    runs-on: ubuntu-latest
222    steps:
223      - uses: actions/checkout@v4
224~
225      - name: Generate SBOM with Syft
226        uses: anchore/sbom-action@v0
227        with:
228          format: spdx-json
229          output-file: sbom.spdx.json
230~
231      - name: Upload SBOM
232        uses: actions/upload-artifact@v4
233        with:
234          name: sbom
235          path: sbom.spdx.json
236```
237~
238## Etap 4: Bezopasnye obrazy Docker
239~
240Produktsionny obraz Docker dolzhen sledovat prinsipu naimenshikh privilegiy. Vot kak vyglyadit ukrplyonny Dockerfile:
241~
242```dockerfile
243# Build stage
244FROM node:22-alpine AS builder
245WORKDIR /app
246COPY package.json package-lock.json ./
247RUN npm ci
248COPY . .
249RUN npm run build
250~
251# Production stage
252FROM node:22-alpine AS runner
253WORKDIR /app
254~
255# Install dumb-init before dropping root
256RUN apk add --no-cache dumb-init
257~
258# Don't run as root
259RUN addgroup -S app && adduser -S app -G app
260~
261# Copy only what's needed
262COPY --from=builder --chown=app:app /app/dist ./dist
263COPY --from=builder --chown=app:app /app/node_modules ./node_modules
264COPY --from=builder --chown=app:app /app/package.json ./
265~
266# Drop to non-root user
267USER app
268ENTRYPOINT ["dumb-init", "--"]
269~
270# Health check
271HEALTHCHECK --interval=30s --timeout=3s --retries=3 \
272  CMD wget -qO- http://localhost:3000/health || exit 1
273~
274EXPOSE 3000
275CMD ["node", "dist/server.js"]
276```
277~
278Klyuchevye praktiki:
279~
2801. **Ispolzuyte multi-stage builds**: etap builder soderzhit zavisimosti razrabotki; etap runner soderzhit tolko produktsionny kod
2812. **Ne zapuskayte ot imeni root**: sozdayte ne-root polzovatelya i pereydite na nego
2823. **Ispolzuyte obrazy Alpine**: menshaya poverkhnost ataki (menshe paketov, ustanovlennykh po umolchaniyu)
2834. **Fiksiryte versii obrazov**: `node:22-alpine` vmesto `node:latest` dlya predotvrashcheniya atak na tsepochku postavok
2845. **Ispolzuyte `npm ci`**: deterministicheskaya ustanovka iz lock-fayla, a ne `npm install`
285~
286## Etap 5: Upravlenie sekretami
287~
288Zhyostko zakodirovannye sekrety  -  prichina nomer odin utechek dannykh v intsidentakh, vyzvannykh razrabotchikami.
289~
290### Chego NE delat
291~
292```typescript
293// NEVER do this
294const API_KEY = "sk-1234567890abcdef";
295const DB_PASSWORD = "supersecret123";
296~
297const client = new Client({
298  connectionString: `postgres://admin:${DB_PASSWORD}@db.example.com/prod`
299});
300```
301~
302### Chto delat vmesto etogo
303~
304```typescript
305// Use environment variables
306const client = new Client({
307  connectionString: process.env.DATABASE_URL
308});
309~
310// Or use a secret manager
311import { SecretManagerServiceClient } from '@google-cloud/secret-manager';
312~
313const client = new SecretManagerServiceClient();
314const [version] = await client.accessSecretVersion({
315  name: 'projects/my-project/secrets/db-password/versions/latest',
316});
317const dbPassword = version.payload?.data?.toString();
318```
319~
320### Ierarkhiya upravleniya sekretami
321~
322```mermaid
323graph TD
324    A[Secret Manager\nAWS Secrets Manager\nGCP Secret Manager\nHashiCorp Vault] --> B[Best: Rotated, audited, centralized]
325    C[Environment Variables\nInjected at deploy time] --> D[Good: Not in code, but static]
326    E[.env files\nWith .gitignore] --> F[Acceptable: Local development only]
327    G[Hard-coded in source] --> H[NEVER: Instant breach risk]
328~
329    style A fill:#d4edda
330    style C fill:#fff3cd
331    style E fill:#ffeeba
332    style G fill:#f8d7da
333```
334~
335## OWASP Top 10: Kratkaya spravka
336~
337Kazhdy razrabotchik dolzhen znat OWASP Top 10. Szhatataya versiya:
338~
339| # | Uyazvimost | Chto eto | Predotvrashchenie |
340|---|-----------|---------|-------------------|
341| 1 | **Broken Access Control** | Polzovateli poluchayut dostup k resursam, k kotorym ne dolzhny | Zapret po umolchaniyu, validatsiya na storone servera |
342| 2 | **Cryptographic Failures** | Slaboye shifrovanie, dannyye v otkrytom vide | Silnye algoritmy (AES-256, bcrypt), TLS vezde |
343| 3 | **Injection** | SQL, NoSQL, OS command injection | Parametrizovannye zaprosy, validatsiya vkhodnykh dannykh |
344| 4 | **Insecure Design** | Oshibochnaya arkhitektura | Modelirovanie ugroz, bezopasnye shablony proektirovaniya |
345| 5 | **Security Misconfiguration** | Uchyotnye dannyye po umolchaniyu, otkrytye cloud buckety | Ukrplyonnye nastroyki po umolchaniyu, avtomatizirovannye audity konfiguratsii |
346| 6 | **Vulnerable Components** | Izvestnye CVE v zavisimostyakh | Skanirovanie SCA, regulyarnye obnovleniya |
347| 7 | **Auth Failures** | Slabye paroli, narushennye sessii | MFA, rate limiting, bezopasnoye upravlenie sessiyami |
348| 8 | **Data Integrity Failures** | Nepodpisannye obnovleniya, nedoveryonnye CI/CD | Podpis koda, SBOM, tselostnost pipeline |
349| 9 | **Logging Failures** | Net auditorskogo sleda | Strukturirovannoye logirovaniye, opoveshcheniya ob anomaliyakh |
350| 10 | **SSRF** | Server-side request forgery | Allowlist iskhodyashchikh URL, validatsiya vkhodnykh dannykh |
351~
352## Polny workflow bezopasnosti GitHub Actions
353~
354Polny, gotovy k produktsii workflow, obedinyayushchiy vsyo vysheukazannoye:
355~
356```yaml
357# .github/workflows/security.yml
358name: Security Pipeline
359on:
360  pull_request:
361    branches: [main]
362  push:
363    branches: [main]
364~
365permissions:
366  contents: read
367  security-events: write
368~
369jobs:
370  secrets-scan:
371    name: Secret Detection
372    runs-on: ubuntu-latest
373    steps:
374      - uses: actions/checkout@v4
375        with:
376          fetch-depth: 0
377      - uses: gitleaks/gitleaks-action@v2
378        env:
379          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
380~
381  sast:
382    name: Static Analysis (SAST)
383    runs-on: ubuntu-latest
384    steps:
385      - uses: actions/checkout@v4
386      - uses: semgrep/semgrep-action@v1
387        with:
388          config: p/owasp-top-ten p/typescript p/nodejs
389~
390  dependency-audit:
391    name: Dependency Scan (SCA)
392    runs-on: ubuntu-latest
393    steps:
394      - uses: actions/checkout@v4
395      - uses: actions/setup-node@v4
396        with:
397          node-version: 22
398      - run: npm ci
399      - run: npm audit --audit-level=high
400      - uses: snyk/actions/node@master
401        env:
402          SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}
403        with:
404          args: --severity-threshold=high
405        continue-on-error: true
406~
407  container-scan:
408    name: Container Scan
409    runs-on: ubuntu-latest
410    needs: [sast, dependency-audit]
411    steps:
412      - uses: actions/checkout@v4
413      - run: docker build -t app:${{ github.sha }} .
414      - uses: aquasecurity/trivy-action@master
415        with:
416          image-ref: app:${{ github.sha }}
417          severity: CRITICAL,HIGH
418          exit-code: '1'
419~
420  sbom:
421    name: SBOM Generation
422    runs-on: ubuntu-latest
423    needs: [container-scan]
424    steps:
425      - uses: actions/checkout@v4
426      - uses: anchore/sbom-action@v0
427        with:
428          format: spdx-json
429          output-file: sbom.spdx.json
430```
431~
432```mermaid
433graph TD
434    PR[Pull Request] --> S1[Secret Detection]
435    PR --> S2[SAST - Semgrep]
436    PR --> S3[SCA - Snyk + npm audit]
437    S2 --> S4[Container Scan - Trivy]
438    S3 --> S4
439    S4 --> S5[SBOM Generation]
440    S5 --> Deploy[Deploy]
441~
442    S1 -.- F1[Block if secrets found]
443    S2 -.- F2[Block on critical vulns]
444    S3 -.- F3[Block on high severity]
445    S4 -.- F4[Block on critical CVEs]
446```
447~
448## Metriki dlya otslezhivaniya
449~
450Kak uznat, chto vasha programma DevSecOps rabotaet? Otslezhivayte eti metriki:
451~
452- **Mean time to remediate (MTTR)**: kak bystro vy ispravlyaete uyazvimosti posle ikh obnaruzheniya
453- **Vulnerability escape rate**: protsent uyazvimostey, dostigshikh produktsii
454- **False positive rate**: slishkom mnogo lozhnykh srabatyvaniy privodit k ustalosti ot opoveshcheniy i ignorirovaniyu preduprezhdeniy
455- **Dependency freshness**: sredniy vozrast vashikh zavisimostey (starshe = vyshe veroyatnost izvestnykh CVE)
456- **SBOM coverage**: protsent proektov s aktualnymi SBOM
457~
458## Nachalo raboty: Prakticheskaya dorozhnaya karta
459~
460Ne pytaytes vnedrit vsyo srazu. Poetapny podkhod rabotaet luchshe:
461~
462```mermaid
463flowchart TD
464    A[Week 1-2: Foundations] --> B[Week 3-4: CI/CD Integration]
465    B --> C[Month 2: Container Security]
466    C --> D[Month 3+: Advanced]
467~
468    A --> A1[Add Gitleaks pre-commit hooks]
469    A --> A2[Enable npm audit in CI]
470    A --> A3[Add .gitignore for .env files]
471~
472    B --> B1[Add Semgrep to GitHub Actions]
473    B --> B2[Add Snyk dependency scanning]
474    B --> B3[Set up SARIF upload to GitHub]
475~
476    C --> C1[Add Trivy container scanning]
477    C --> C2[Harden Dockerfiles]
478    C --> C3[Generate SBOMs]
479~
480    D --> D1[Secret manager integration]
481    D --> D2[Runtime protection - DAST]
482    D --> D3[Policy as code - OPA]
483```
484~
485## Zaklyuchenie
486~
487DevSecOps  -  eto ne pro dobavlenie bolshego kolichestva instrumentov v vash pipeline  -  eto pro to, chtoby sdelat bezopasnost yestestvenoy chastyu togo, kak vy sozdayote programmnoe obespechenie. Tsel  -  ne blokirovat kazhdy PR preduprezhdeniyami bezopasnosti, a davat razrabotchikam bystruyu obratnuyu svyaz, chtoby oni mogli ispravlyat problemy, poka kod yeshchyo svezh v ikh pamyati.
488~
489Nachnite s osnov: pre-commit hooks dlya sekretov, skanirovanie zavisimostey v CI i skanirovanie konteinerov dlya obrazov Docker. Zatem iteriryte na osnove togo, chto nuzhno vashey komande.
490~
491Bezopasnost  -  eto ne funktsiya, kotoruyu vy vypuskayete odin raz. Eto praktika, kotoruyu vy vstraivayete v kazhdy commit.
492~
493> **Chek-list DevSecOps dlya starta:**
494>
495> - [x] Ustanovleny pre-commit hooks Gitleaks
496> - [x] Fayly .env i fayly s sekretami v .gitignore
497> - [x] Semgrep SAST v CI pipeline
498> - [x] Snyk ili npm audit dlya skanirovaniya zavisimostey
499> - [x] Trivy dlya skanirovaniya obrazov konteinerov
500> - [x] Ne-root polzovatel v Dockerfile
501> - [x] Sekrety v peremennykh okruzheniya ili secret manager
502> - [x] Generatsiya SBOM pri kazhdom relize
503> - [x] Osvedomlyonnost ob OWASP Top 10 vo vsey komande
504~