Konspekt · Xavfsizlik
Shifrlash va sirlar
Muammo
Eslatmalar ilovasi odamlarning shaxsiy yozuvlarini saqlaydi. O'g'irlangan nusxa o'qiladigan har bir joyni topamiz: tarmoq, disk, backup va config fayl, keyin ularni birma-bir yopamiz.
Nimani o'rganasiz
- TLS handshake nimani tekshiradi va nega sertifikat o'zi yangilanishi kerak
- Saqlanayotgan ma'lumotni shifrlash va nega kalit ma'lumot yonida tursa hech narsani himoya qilmaydi
- Envelope shifrlash: har yozuvga data key, master key esa KMS'dan chiqmaydi
- Sirlar qisqa muddatli lease bilan secrets manager'da, kalitni hamma narsani qayta shifrlamasdan almashtirish
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_app(["Telefon ilovasi"])
n_api["Eslatmalar API"]
n_db[("Baza")]
n_attacker(("Hujumchi"))
n_backup[("Backup'lar")]
n_kms>"KMS"]
n_secrets>"Secrets manager"]
n_app --> n_api
n_api --> n_db
n_db --> n_backup
n_backup --x|"yo'qoldi"| n_attacker
n_api --x|"yo'qoldi"| n_attacker
n_api --> n_kms
n_api -.->|"qayta urinish"| n_secretsMermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_app as Telefon ilovasi
participant n_api as Eslatmalar API
participant n_ca as Sertifikat markazi
participant n_backup as Backup'lar
actor n_attacker as Hujumchi
participant n_db as Baza
participant n_kms as KMS
participant n_secrets as Secrets manager
Note over n_app,n_api: Eslatmalar ochiq matnda ketmoqda
n_app->>n_api: POST /notes HTTP/1.1
n_api-->>n_app: HTTP/1.1 201 Created
Note over n_app,n_api: TLS handshake: umumiy kalit va shaxsni isbotlash
n_app->>n_api: ClientHello
n_api-->>n_app: ServerHello + Certificate
Note over n_app,n_api: Sertifikat yarim tunda eskirdi
n_app->>n_api: ClientHello
n_api-->>n_app: ServerHello + Certificate
Note over n_api,n_ca: Sertifikat o'zi yangilanadi
n_api->>n_ca: POST /acme/new-order HTTP/1.1
n_ca-->>n_api: HTTP/1.1 201 Created
Note over n_backup,n_attacker: Backup tashqariga chiqdi, u esa ochiq matn
n_backup->>n_attacker: $ strings notes-2026-11-01.bak #124; grep -i door
Note over n_api,n_db: Eslatmani saqlashdan oldin shifrlash
n_api->>n_db: INSERT INTO notes (id, owner, text_enc, nonce)
n_db-->>n_api: INSERT 0 1
Note over n_api,n_attacker: Kalit ma'lumot yonida turibdi
n_api->>n_attacker: config/prod.json (from a leaked image)
Note over n_api,n_kms: KMS bilan envelope shifrlash
n_api->>n_kms: POST /v1/keys/notes-master:generateDataKey HTTP/1.1
n_kms-->>n_api: HTTP/1.1 200 OK
Note over n_api,n_secrets: Kodda sir yo'q: secrets manager
n_api->>n_secrets: GET /v1/secret/notes-db HTTP/1.1
n_secrets-->>n_api: HTTP/1.1 200 OK
Note over n_api,n_kms: Ma'lumotni qayta shifrlamasdan kalitni almashtirish
n_api->>n_kms: POST /v1/keys/notes-master:reEncrypt HTTP/1.1
n_kms-->>n_api: HTTP/1.1 200 OKD2
direction: right
n_app: "Telefon ilovasi" {
shape: rectangle
}
n_api: "Eslatmalar API" {
shape: rectangle
}
n_db: "Baza" {
shape: cylinder
}
n_attacker: "Hujumchi" {
shape: person
}
n_backup: "Backup'lar" {
shape: stored_data
}
n_kms: "KMS" {
shape: cloud
}
n_secrets: "Secrets manager" {
shape: cloud
}
n_app -> n_api
n_api -> n_db
n_db -> n_backup
n_backup -> n_attacker: "yo'qoldi" {
style.stroke-width: 4
target-arrowhead.shape: cross
}
n_api -> n_attacker: "yo'qoldi" {
style.stroke-width: 4
target-arrowhead.shape: cross
}
n_api -> n_kms
n_api -> n_secrets: "qayta urinish" {
style.stroke-dash: 3
}PlantUML: so'rovlar ketma-ketligi
@startuml
participant "Telefon ilovasi" as n_app
participant "Eslatmalar API" as n_api
boundary "Sertifikat markazi" as n_ca
database "Backup'lar" as n_backup
actor "Hujumchi" as n_attacker
database "Baza" as n_db
boundary "KMS" as n_kms
boundary "Secrets manager" as n_secrets
note over n_app, n_api : Eslatmalar ochiq matnda ketmoqda
n_app -> n_api : POST /notes HTTP/1.1
n_api --> n_app : HTTP/1.1 201 Created
note over n_app, n_api : TLS handshake: umumiy kalit va shaxsni isbotlash
n_app -> n_api : ClientHello
n_api --> n_app : ServerHello + Certificate
note over n_app, n_api : Sertifikat yarim tunda eskirdi
n_app -> n_api : ClientHello
n_api --> n_app : ServerHello + Certificate
note over n_api, n_ca : Sertifikat o'zi yangilanadi
n_api -> n_ca : POST /acme/new-order HTTP/1.1
n_ca --> n_api : HTTP/1.1 201 Created
note over n_backup, n_attacker : Backup tashqariga chiqdi, u esa ochiq matn
n_backup -> n_attacker : [dublikat] $ strings notes-2026-11-01.bak | grep -i door
note over n_api, n_db : Eslatmani saqlashdan oldin shifrlash
n_api -> n_db : INSERT INTO notes (id, owner, text_enc, nonce)
n_db --> n_api : INSERT 0 1
note over n_api, n_attacker : Kalit ma'lumot yonida turibdi
n_api -> n_attacker : [dublikat] config/prod.json (from a leaked image)
note over n_api, n_kms : KMS bilan envelope shifrlash
n_api -> n_kms : POST /v1/keys/notes-master:generateDataKey HTTP/1.1
n_kms --> n_api : HTTP/1.1 200 OK
note over n_api, n_secrets : Kodda sir yo'q: secrets manager
n_api -> n_secrets : GET /v1/secret/notes-db HTTP/1.1
n_secrets --> n_api : HTTP/1.1 200 OK
note over n_api, n_kms : Ma'lumotni qayta shifrlamasdan kalitni almashtirish
n_api -> n_kms : POST /v1/keys/notes-master:reEncrypt HTTP/1.1
n_kms --> n_api : HTTP/1.1 200 OK
@endumlPlantUML: komponentlar
@startuml
left to right direction
agent "Telefon ilovasi" as n_app
component "Eslatmalar API" as n_api
database "Baza" as n_db
actor "Hujumchi" as n_attacker
storage "Backup'lar" as n_backup
cloud "KMS" as n_kms
cloud "Secrets manager" as n_secrets
n_app --> n_api
n_api --> n_db
n_db --> n_backup
n_backup -[#c62828,dashed]-> n_attacker : yo'qoldi
n_api -[#c62828,dashed]-> n_attacker : yo'qoldi
n_api --> n_kms
n_api ..> n_secrets : qayta urinish
@endumlXulosa
Ma'lumot nusxasi yashaydigan har bir joyni toping va har birini yoping.
1) Har ulanishda TLS, sertifikat o'zi yangilanadi, muddatdan oldin alert. 2) Diskda shifrlash, backup'lar ham. 3) Envelope shifrlash: har yozuvga data key, master key faqat KMS'da. 4) Sirlar secrets manager'da qisqa lease bilan, hech qachon kodda emas. 5) Almashtirish ma'lumotni emas, kalitlarni qayta o'rash orqali.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| O'qiladigan nusxalar | 4 | 0 |
| Javob p95 | 120 ms | 158 ms |
| Xato so'rovlar | 0% | 0% |
Qadamlar
- Muammo Eslatmalar ochiq matnda ketmoqda
Ilova eslatmalarni oddiy HTTP orqali yuboradi.
- Yechim TLS handshake: umumiy kalit va shaxsni isbotlash
Ma'lumotdan oldin ilova va server yangi kalitga kelishadi: har biri
key_share'ning ochiq yarmini yuboradi va ikkalasi bir xil sirni hisoblaydi. - Muammo Sertifikat yarim tunda eskirdi
Sertifikatni yiliga bir marta kimdir qo'lda yangilardi.
- Yechim Sertifikat o'zi yangilanadi
Server endi CA'dan yangi sertifikatni o'zi so'raydi, ACME protokoli orqali.
- Muammo Backup tashqariga chiqdi, u esa ochiq matn
Har kecha backup storage bucket'ga tushadi.
- Yechim Eslatmani saqlashdan oldin shifrlash
API endi
INSERT'dan oldin eslatmani AES-256-GCM bilan shifrlaydi. - Muammo Kalit ma'lumot yonida turibdi
Config fayli bor container image xato bilan ochiq registry'ga chiqib ketdi.
- Yechim KMS bilan envelope shifrlash
Master key endi KMS ichida yashaydi va undan chiqmaydi.
- Yechim Kodda sir yo'q: secrets manager
Baza paroli config fayldan chiqariladi.
- Holat Ma'lumotni qayta shifrlamasdan kalitni almashtirish
Har yili KMS master key'ning yangi versiyasini yaratadi, eski versiyalar esa eski ma'lumotni ochish uchun qoladi.
- Xulosa Xulosa
Ma'lumot nusxasi yashaydigan har bir joyni toping va har birini yoping.
Atamalar
- TLS
- Ulanishni shifrlaydigan protokol: handshake'da tomonlar umumiy kalit kelishadi, server esa sertifikat bilan shaxsini isbotlaydi. Sertifikat o'zi yangilanib turishi kerak, aks holda yarim tunda eskiradi.
- Diskda shifrlash (at rest)
- Ma'lumot bazaga yozilishdan oldin shifrlanadi, shunda disk va backup'larda faqat shifrlangan matn qoladi. Kalit ma'lumot yonida tursa, bu hech narsani himoya qilmaydi.
- Envelope shifrlash (KMS)
- Har yozuv o'z data key'i bilan shifrlanadi, data key esa KMS'dan chiqmaydigan master key bilan o'raladi. Bazada faqat o'ralgan kalit saqlanadi; kalitni almashtirish ma'lumotni emas, kalitlarni qayta o'rashni talab qiladi.