Konspekt · Xavfsizlik
Maxfiy ma'lumotlarni boshqarish
Muammo
Do'kon backend'i baza parolini repoga commit qilingan .env faylda saqlaydi, uni beshta servis bo'lishadi. Parol oqib chiqadi, shoshilinch almashtirish esa checkout'ni to'xtatib qo'yadi. Secrets manager ikkalasini ham tuzatadi: servislar o'zini workload identity bilan isbotlaydi, o'z qisqa muddatli baza foydalanuvchisini oladi, secret'lar diskda shifrlangan, kalitlar ustma-ust versiyalar bilan almashadi va har o'qish auditga yoziladi.
Nimani o'rganasiz
- Nega repo yoki env fayldagi uzoq yashovchi umumiy parol buzilishdan bitta oqish narida turadi
- Statik token o'rniga workload identity va lease'li, har servisga alohida dinamik baza foydalanuvchisi
- Diskda envelope shifrlash va ikki ustma-ust versiya orqali to'xtovsiz almashtirish
- Har secret o'qilishining audit jurnali va manager'ning o'zi ishlamay qolganda break-glass yo'li
Diagramma kod sifatida
Darsdagi yakuniy sxemani matn ko'rinishida oling va Jira, GitLab, GitHub, Notion yoki hujjatga qo'ying: Mermaid u yerlarda o'zi chiziladi. D2 va PlantUML (Confluence, IntelliJ) uchun alohida variantlar bor.
Mermaid: sxema
flowchart LR
n_orders["Buyurtma servisi"]
n_reports("Hisobot job")
n_db[("Do'kon bazasi")]
n_secrets["Secrets manager"]
n_issuer>"Identity beruvchi"]
n_kms>"KMS"]
n_partner>"Hamkor API"]
n_audit[("Audit jurnali")]
n_oncall(("Navbatchi"))
n_safe[("Muhrlangan seyf")]
n_orders --> n_db
n_reports --> n_db
n_orders --x n_secrets
n_reports --x n_secrets
n_secrets --> n_issuer
n_secrets --> n_db
n_secrets --> n_kms
n_orders --> n_partner
n_secrets --> n_partner
n_secrets --> n_audit
n_oncall --> n_safe
n_oncall -.->|"qayta urinish"| n_db
classDef down fill:#fde2e2,stroke:#c62828,color:#4a0d0d,stroke-dasharray:4 3
class n_secrets downMermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_repo as Git repo
participant n_orders as Buyurtma servisi
participant n_intruder as Buzg'unchi
participant n_db as Do'kon bazasi
participant n_secrets as Secrets manager
participant n_kms as KMS
participant n_partner as Hamkor API
participant n_audit as Audit jurnali
actor n_oncall as Navbatchi
participant n_safe as Muhrlangan seyf
Note over n_repo,n_orders: Parol repodagi faylda yashaydi
n_repo->>n_orders: $ cat services/orders/.env
Note over n_intruder,n_db: Repo zaxirasi oqib chiqdi, kimdir kirdi
n_intruder->>n_db: 02:14:07 LOG connection authorized: user=app database=shop
Note over n_orders,n_db: Shoshilinch almashtirish checkout'ni to'xtatadi
n_orders->>n_db: 02:31:00 admin ALTER ROLE app PASSWORD '***'
Note over n_orders,n_secrets: Secret'lar secrets manager'ga ko'chadi
n_orders->>n_secrets: GET /v1/secret/shop/db HTTP/1.1
n_secrets-->>n_orders: HTTP/1.1 200 OK
Note over n_orders,n_secrets: Servis o'zini isbotlaydi, saqlangan token yo'q
n_orders->>n_secrets: POST /v1/auth/workload/login HTTP/1.1
n_secrets-->>n_orders: HTTP/1.1 200 OK
Note over n_orders,n_secrets: Har servis lease'li o'z baza foydalanuvchisini oladi
n_orders->>n_secrets: GET /v1/database/creds/orders-rw HTTP/1.1
n_secrets-->>n_orders: HTTP/1.1 200 OK
Note over n_secrets,n_db: Manager bazada nima qiladi
n_secrets->>n_db: CREATE ROLE #34;v-orders-h7Kq#34; LOGIN PASSWORD '***'
n_db-->>n_secrets: CREATE ROLE
Note over n_secrets,n_kms: Diskdagi secret'lar shifrlangan, root kalit KMS'da qoladi
n_secrets->>n_kms: POST /v1/keys/secrets-root/decrypt HTTP/1.1
n_kms-->>n_secrets: HTTP/1.1 200 OK
Note over n_secrets,n_partner: To'xtovsiz almashtirish: ikki versiya ustma-ust
n_secrets->>n_partner: 03:00:00 rotate partner/api-key: created version 8
Note over n_secrets,n_audit: Har o'qish yoziladi, noto'g'ri o'qish ko'rinadi
n_secrets->>n_audit: audit.log
Note over n_oncall,n_safe: Manager ishlamay qolganda: break-glass
n_oncall->>n_safe: 04:12 BREAK-GLASS shop-db opened by oncall_1D2
direction: right
n_orders: "Buyurtma servisi" {
shape: rectangle
}
n_reports: "Hisobot job" {
shape: rectangle
style.multiple: true
}
n_db: "Do'kon bazasi" {
shape: cylinder
}
n_secrets: "Secrets manager" {
shape: rectangle
style.fill: "#fde2e2"
style.stroke: "#c62828"
style.stroke-dash: 3
}
n_issuer: "Identity beruvchi" {
shape: cloud
}
n_kms: "KMS" {
shape: cloud
}
n_partner: "Hamkor API" {
shape: cloud
}
n_audit: "Audit jurnali" {
shape: stored_data
}
n_oncall: "Navbatchi" {
shape: person
}
n_safe: "Muhrlangan seyf" {
shape: stored_data
}
n_orders -> n_db
n_reports -> n_db
n_orders -> n_secrets {
target-arrowhead.shape: cross
}
n_reports -> n_secrets {
target-arrowhead.shape: cross
}
n_secrets -> n_issuer
n_secrets -> n_db
n_secrets -> n_kms
n_orders -> n_partner
n_secrets -> n_partner
n_secrets -> n_audit
n_oncall -> n_safe
n_oncall -> n_db: "qayta urinish" {
style.stroke-dash: 3
}PlantUML: so'rovlar ketma-ketligi
@startuml
database "Git repo" as n_repo
participant "Buyurtma servisi" as n_orders
boundary "Buzg'unchi" as n_intruder
database "Do'kon bazasi" as n_db
participant "Secrets manager" as n_secrets
boundary "KMS" as n_kms
boundary "Hamkor API" as n_partner
database "Audit jurnali" as n_audit
actor "Navbatchi" as n_oncall
database "Muhrlangan seyf" as n_safe
note over n_repo, n_orders : Parol repodagi faylda yashaydi
n_repo -> n_orders : $ cat services/orders/.env
note over n_intruder, n_db : Repo zaxirasi oqib chiqdi, kimdir kirdi
n_intruder -> n_db : 02:14:07 LOG connection authorized: user=app database=shop
note over n_orders, n_db : Shoshilinch almashtirish checkout'ni to'xtatadi
n_orders -> n_db : 02:31:00 admin ALTER ROLE app PASSWORD '***'
note over n_orders, n_secrets : Secret'lar secrets manager'ga ko'chadi
n_orders -> n_secrets : GET /v1/secret/shop/db HTTP/1.1
n_secrets --> n_orders : HTTP/1.1 200 OK
note over n_orders, n_secrets : Servis o'zini isbotlaydi, saqlangan token yo'q
n_orders -> n_secrets : POST /v1/auth/workload/login HTTP/1.1
n_secrets --> n_orders : HTTP/1.1 200 OK
note over n_orders, n_secrets : Har servis lease'li o'z baza foydalanuvchisini oladi
n_orders -> n_secrets : GET /v1/database/creds/orders-rw HTTP/1.1
n_secrets --> n_orders : HTTP/1.1 200 OK
note over n_secrets, n_db : Manager bazada nima qiladi
n_secrets -> n_db : CREATE ROLE "v-orders-h7Kq" LOGIN PASSWORD '***'
n_db --> n_secrets : CREATE ROLE
note over n_secrets, n_kms : Diskdagi secret'lar shifrlangan, root kalit KMS'da qoladi
n_secrets -> n_kms : POST /v1/keys/secrets-root/decrypt HTTP/1.1
n_kms --> n_secrets : HTTP/1.1 200 OK
note over n_secrets, n_partner : To'xtovsiz almashtirish: ikki versiya ustma-ust
n_secrets -> n_partner : 03:00:00 rotate partner/api-key: created version 8
note over n_secrets, n_audit : Har o'qish yoziladi, noto'g'ri o'qish ko'rinadi
n_secrets -> n_audit : audit.log
note over n_oncall, n_safe : Manager ishlamay qolganda: break-glass
n_oncall -> n_safe : 04:12 BREAK-GLASS shop-db opened by oncall_1
@endumlPlantUML: komponentlar
@startuml
left to right direction
component "Buyurtma servisi" as n_orders
collections "Hisobot job" as n_reports
database "Do'kon bazasi" as n_db
component "Secrets manager" as n_secrets #fde2e2;line:c62828;line.dashed
cloud "Identity beruvchi" as n_issuer
cloud "KMS" as n_kms
cloud "Hamkor API" as n_partner
storage "Audit jurnali" as n_audit
actor "Navbatchi" as n_oncall
storage "Muhrlangan seyf" as n_safe
n_orders --> n_db
n_reports --> n_db
n_orders -[#c62828]-> n_secrets
n_reports -[#c62828]-> n_secrets
n_secrets --> n_issuer
n_secrets --> n_db
n_secrets --> n_kms
n_orders --> n_partner
n_secrets --> n_partner
n_secrets --> n_audit
n_oncall --> n_safe
n_oncall ..> n_db : qayta urinish
@endumlXulosa
Secret'lar uchun olti qoida.
1) Repo, image va env fayllarda secret yo'q; git'da bo'lgan narsa oqib chiqqan. 2) Servislar o'zini saqlangan token bilan emas, workload identity bilan isbotlaydi. 3) Lease'li, eng kam huquqli, har servisga alohida dinamik login afzal. 4) Diskdagi secret'larni envelope shifrlash bilan himoya qiling, root kalit KMS'da. 5) Ikki ustma-ust versiya bilan almashtiring, eskisini faqat ishlatilmay qolgach bekor qiling. 6) Har o'qishni auditga yozing, rad etishlarga signal qo'ying va sinalgan, ikki kishilik break-glass yo'lini saqlang.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| Statik secret nusxasi | 9 | 1 |
| Bir oqishda servis | 5 | 1 |
| Almashtirishda to'xtash | 0 s | 0 s |
| Auditdagi o'qishlar | 0% | 100% |
Qadamlar
- Holat Parol repodagi faylda yashaydi
Buyurtma servisi baza login'ini
.envfayldan o'qiydi. - Muammo Repo zaxirasi oqib chiqdi, kimdir kirdi
Repo bor noutbuk zaxirasi uch kun ochiq turgan.
- Muammo Shoshilinch almashtirish checkout'ni to'xtatadi
Admin parolni 02:31 da almashtiradi.
- Yechim Secret'lar secrets manager'ga ko'chadi
Parol repodan chiqariladi, git tarixi tozalanadi.
- Yechim Servis o'zini isbotlaydi, saqlangan token yo'q
Pod'larni ishga tushiradigan platforma har biriga imzolangan, qisqa muddatli token beradi: "men shop namespace'idagi buyurtma servisiman".
- Yechim Har servis lease'li o'z baza foydalanuvchisini oladi
Buyurtma servisi saqlangan parolni o'qimaydi, login so'raydi.
- Holat Manager bazada nima qiladi
Manager bazaga bitta admin login'ga ega, u faqat foydalanuvchi yaratish va o'chirish uchun.
- Yechim Diskdagi secret'lar shifrlangan, root kalit KMS'da qoladi
Manager secret'larni o'z storage'ida saqlaydi, storage'ning esa zaxirasi olinadi.
- Yechim To'xtovsiz almashtirish: ikki versiya ustma-ust
Ba'zi secret'lar dinamik bo'la olmaydi: hamkor API kalitini hamkorning o'zi beradi.
- Yechim Har o'qish yoziladi, noto'g'ri o'qish ko'rinadi
Manager'ga har so'rov audit yozuvini qoldiradi: qaysi workload, qaysi yo'l, natija va qayerdan.
- Holat Manager ishlamay qolganda: break-glass
Soat 04:12 da secrets manager ishlamayapti, servislar login ololmaydi.
- Xulosa Xulosa
Secret'lar uchun olti qoida.
Atamalar
- Secrets manager
- Secret'larni saqlaydigan, so'rovchini tekshiradigan va faqat unga ruxsat etilganini beradigan, har o'qishni auditga yozadigan servis.
- Dinamik login
- So'rov paytida servisga alohida yaratiladigan, lease tugashi bilan o'chiriladigan baza foydalanuvchisi yoki kalit.
- Workload identity
- Platforma servisga beradigan imzolangan qisqa muddatli token: servis saqlangan secret'siz o'zini isbotlaydi.