Konspekt · Biznes jarayonlar
Audit jurnali
Muammo
Back-office'da kimdir mijozning bank hisobini o'zgartirdi, keyingi to'lov begona odamga ketdi va kim qilganini hech kim isbotlay olmaydi. Bu darsda kim, nima, qachon, qayerdan qilgani va oldin-keyin qanday bo'lganiga javob beradigan audit jurnali quriladi. U yiqilishga, o'sib borayotgan jadvalga va bazaga kira oladigan ichki odamga ham bardosh beradi.
Nimani o'rganasiz
- Audit hodisasida nima bo'ladi va nega u o'zgartirish bilan bitta tranzaksiyada yoziladi
- Auditni outbox orqali alohida, faqat qo'shiladigan, oylik bo'laklarga bo'lingan omborga ko'chirish
- Xesh zanjiri va imzolangan nazorat nuqtalari bilan soxtalashtirishni ko'rinadigan qilish
- Auditdagi shaxsiy ma'lumot, alohida o'qish roli, bir marta yoziladigan omborda saqlash muddati va request id bo'yicha tergov
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_admin(("Back-office xodimi"))
n_api["Back-office API"]
n_db[("Mijozlar bazasi")]
n_relay("Audit relay")
n_auditdb[("Audit ombori")]
n_signer>"Imzo xizmati"]
n_archive[("WORM arxiv")]
n_investigator(("Tergovchi"))
n_admin --> n_api
n_api --> n_db
n_db --> n_relay
n_relay --> n_auditdb
n_auditdb --> n_signer
n_auditdb --> n_archive
n_investigator --> n_auditdbMermaid: so'rovlar ketma-ketligi
sequenceDiagram
participant n_api as Back-office API
participant n_db as Mijozlar bazasi
participant n_relay as Audit relay
participant n_auditdb as Audit ombori
actor n_insider as Ichki odam
participant n_signer as Imzo xizmati
actor n_investigator as Tergovchi
participant n_archive as WORM arxiv
Note over n_api,n_db: Bank rekvizitlari o'zgardi, kim ekanini hech kim aytolmaydi
n_api->>n_db: UPDATE customers
n_db-->>n_api: UPDATE 1
Note over n_api,n_db: Har biznes harakatiga bitta audit hodisasi
n_api->>n_db: audit_event
Note over n_api,n_db: Ikki yildan keyin audit jadvali bazani egallab oldi
n_api->>n_db: db stats, two years later
Note over n_api,n_db: Bitta tranzaksiya, alohida ombor: outbox
n_api->>n_db: BEGIN#59;
n_db-->>n_api: COMMIT
Note over n_relay,n_auditdb: Faqat qo'shish, har oyga bitta bo'lak
n_relay->>n_auditdb: CREATE TABLE audit_events (... , at timestamptz)
Note over n_insider,n_auditdb: Superuser huquqi bor odam qatorni o'chiradi
n_insider->>n_auditdb: -- superuser session, 23:52
n_auditdb-->>n_insider: DELETE 1
Note over n_relay,n_auditdb: Har yozuv oldingisining xeshini saqlaydi
n_relay->>n_auditdb: audit-verify partition=2026_11 (hourly)
Note over n_auditdb,n_signer: Imzolangan nazorat nuqtalari zanjirni mahkamlaydi
n_auditdb->>n_signer: POST /v1/sign HTTP/1.1
n_signer-->>n_auditdb: HTTP/1.1 200 OK
Note over n_investigator,n_auditdb: Auditda shaxsiy ma'lumot bor: kamaytiring va o'qishni yoping
n_investigator->>n_auditdb: CREATE ROLE audit_reader#59;
Note over n_auditdb,n_archive: Saqlash muddati: eski oylar bir marta yoziladigan omborga
n_auditdb->>n_archive: export audit_events_2025_10 -#62; archive/2025/10/events.jsonl.zst
Note over n_investigator,n_auditdb: Tergov: bitta request id, butun voqea
n_investigator->>n_auditdb: SELECT at, actor_id, action, target, ip
n_auditdb-->>n_investigator: 09:41:07.312 #124; u_17 #124; customer.bank_account.update #124; customer:c_1187D2
direction: right
n_admin: "Back-office xodimi" {
shape: person
}
n_api: "Back-office API" {
shape: rectangle
}
n_db: "Mijozlar bazasi" {
shape: cylinder
}
n_relay: "Audit relay" {
shape: rectangle
style.multiple: true
}
n_auditdb: "Audit ombori" {
shape: cylinder
}
n_signer: "Imzo xizmati" {
shape: cloud
}
n_archive: "WORM arxiv" {
shape: stored_data
}
n_investigator: "Tergovchi" {
shape: person
}
n_admin -> n_api
n_api -> n_db
n_db -> n_relay
n_relay -> n_auditdb
n_auditdb -> n_signer
n_auditdb -> n_archive
n_investigator -> n_auditdbPlantUML: so'rovlar ketma-ketligi
@startuml
participant "Back-office API" as n_api
database "Mijozlar bazasi" as n_db
participant "Audit relay" as n_relay
database "Audit ombori" as n_auditdb
actor "Ichki odam" as n_insider
boundary "Imzo xizmati" as n_signer
actor "Tergovchi" as n_investigator
database "WORM arxiv" as n_archive
note over n_api, n_db : Bank rekvizitlari o'zgardi, kim ekanini hech kim aytolmaydi
n_api -> n_db : UPDATE customers
n_db --> n_api : UPDATE 1
note over n_api, n_db : Har biznes harakatiga bitta audit hodisasi
n_api -> n_db : audit_event
note over n_api, n_db : Ikki yildan keyin audit jadvali bazani egallab oldi
n_api -> n_db : db stats, two years later
note over n_api, n_db : Bitta tranzaksiya, alohida ombor: outbox
n_api -> n_db : BEGIN;
n_db --> n_api : COMMIT
note over n_relay, n_auditdb : Faqat qo'shish, har oyga bitta bo'lak
n_relay -> n_auditdb : CREATE TABLE audit_events (... , at timestamptz)
note over n_insider, n_auditdb : Superuser huquqi bor odam qatorni o'chiradi
n_insider -> n_auditdb : -- superuser session, 23:52
n_auditdb --> n_insider : DELETE 1
note over n_relay, n_auditdb : Har yozuv oldingisining xeshini saqlaydi
n_relay -> n_auditdb : audit-verify partition=2026_11 (hourly)
note over n_auditdb, n_signer : Imzolangan nazorat nuqtalari zanjirni mahkamlaydi
n_auditdb -> n_signer : POST /v1/sign HTTP/1.1
n_signer --> n_auditdb : HTTP/1.1 200 OK
note over n_investigator, n_auditdb : Auditda shaxsiy ma'lumot bor: kamaytiring va o'qishni yoping
n_investigator -> n_auditdb : CREATE ROLE audit_reader;
note over n_auditdb, n_archive : Saqlash muddati: eski oylar bir marta yoziladigan omborga
n_auditdb -> n_archive : export audit_events_2025_10 -> archive/2025/10/events.jsonl.zst
note over n_investigator, n_auditdb : Tergov: bitta request id, butun voqea
n_investigator -> n_auditdb : SELECT at, actor_id, action, target, ip
n_auditdb --> n_investigator : 09:41:07.312 | u_17 | customer.bank_account.update | customer:c_1187
@endumlPlantUML: komponentlar
@startuml
left to right direction
actor "Back-office xodimi" as n_admin
component "Back-office API" as n_api
database "Mijozlar bazasi" as n_db
collections "Audit relay" as n_relay
database "Audit ombori" as n_auditdb
cloud "Imzo xizmati" as n_signer
storage "WORM arxiv" as n_archive
actor "Tergovchi" as n_investigator
n_admin --> n_api
n_api --> n_db
n_db --> n_relay
n_relay --> n_auditdb
n_auditdb --> n_signer
n_auditdb --> n_archive
n_investigator --> n_auditdb
@endumlXulosa
Audit jurnali uchun olti qoida.
1) Har biznes harakatiga bitta hodisa: kim, harakat, nima, vaqt, oldin va keyin, request id. 2) Uni o'zgartirish bilan bitta tranzaksiyada yozing va outbox orqali yetkazing, chunki yo'qolgan yozuv sekin yozuvdan yomonroq. 3) Uni alohida, faqat qo'shiladigan, oylarga bo'lingan omborda saqlang. 4) Yozuvlarni xesh bilan zanjirlang va boshini muntazam ravishda bazadan tashqaridagi kalit bilan imzolang. 5) Shaxsiy ma'lumotni kamaytiring, o'qishga alohida, audit qilinadigan rol bering. 6) Eski oylarni nazorat nuqtalari bilan tekshirib, bir marta yoziladigan omborga ko'chiring.
Ko'rsatkichlar: boshida va oxirida
| Ko'rsatkich | Boshida | Oxirida |
|---|---|---|
| Egasiz o'zgartirishlar | 14/kun | 0/kun |
| API p95 | 45 ms | 58 ms |
| Tez diskdagi audit | 0 GB | 380 GB |
| Sezilmagan soxtalik | 0 | 0 |
Qadamlar
- Muammo Bank rekvizitlari o'zgardi, kim ekanini hech kim aytolmaydi
Mijoz shu oygi to'lov kelmaganidan shikoyat qiladi.
- Yechim Har biznes harakatiga bitta audit hodisasi
Endi har biznes harakati hodisa yozadi: kim qildi, qanday harakat, nimaga, qachon, oldingi va keyingi qiymat, qaysi so'rovdan kelgan va qaysi tarmoqdan.
- Muammo Ikki yildan keyin audit jadvali bazani egallab oldi
Har harakat qator yozadi va hech narsa o'chirilmaydi.
- Yechim Bitta tranzaksiya, alohida ombor: outbox
API hodisani hali ham biznes tranzaksiyasida yozadi, lekin kichik
audit_outboxjadvaliga. - Yechim Faqat qo'shish, har oyga bitta bo'lak
Audit omborida bitta jadval oylik bo'laklarga (partition) bo'lingan.
- Muammo Superuser huquqi bor odam qatorni o'chiradi
Ruxsatlar ilovalarni to'xtatadi, baza superuser'ini emas.
- Yechim Har yozuv oldingisining xeshini saqlaydi
Har hodisa
prev_hashni saqlaydi, o'z xeshi esa oldingi xesh va hodisaning kanonik baytlarini qamraydi. - Yechim Imzolangan nazorat nuqtalari zanjirni mahkamlaydi
Ehtiyotkor ichki odam qatorni o'chirib, keyingi har xeshni qayta qurishi mumkin.
- Yechim Auditda shaxsiy ma'lumot bor: kamaytiring va o'qishni yoping
Audit jurnali kim kimga nima qilganini yig'adi, demak o'zi ham shaxsiy ma'lumot.
- Yechim Saqlash muddati: eski oylar bir marta yoziladigan omborga
Qoidalar auditni bir necha yil saqlashni talab qiladi, lekin o'tgan yilgi hodisalar tez disklarda hech kimga kerak emas.
- Holat Tergov: bitta request id, butun voqea
To'lovga qaytamiz.
- Xulosa Xulosa
Audit jurnali uchun olti qoida.
Atamalar
- Audit jurnali
- Biznes harakatlarining faqat qo'shiladigan yozuvi: kim, nima qildi, nimaga, qachon, qayerdan, oldin va keyin.
- Xesh zanjiri
- Har bir yozuv oldingisining xeshini saqlaydi, shuning uchun bitta yozuvni o'zgartirish yoki o'chirish undan keyingi hamma bog'lanishni buzadi.
- WORM ombori
- Bir marta yoz, ko'p o'qi: object lock yoqilgan ombor. Saqlash muddati tugaguncha hech kim ma'lumotni o'chira yoki ustidan yoza olmaydi.