Autentifikatsiya, avtorizatsiya va xavfsizlik
Omborchi brauzer manzilidagi /invoices/45 ni /invoices/46 ga o‘zgartirdi. Tizim nima qilishi kerak?
Hozircha javob bermang. Avval bu so‘rovni kim va qayerda to‘xtatishi kerakligini o‘ylab ko‘ring.
Bu ma’ruza oxirida siz quyidagilarni bajara olasiz...
Autentifikatsiya: foydalanuvchini aniqlash
Kim? Nima mumkin? Nima qildi?
Autentifikatsiya (AuthN)
401 yoki login sahifasi.Avtorizatsiya (AuthZ)
orders.confirm, OrderPolicy. Ruxsat yo‘q — 403.Audit
audit_logs jadvalida.password_hash va password_verify
$hash = password_hash('Ombor#2026', PASSWORD_BCRYPT, ['cost' => 10]); echo substr($hash, 0, 7), PHP_EOL; // algoritm va cost echo strlen($hash), PHP_EOL; // bcrypt xeshi uzunligi var_dump(password_verify('Ombor#2026', $hash)); var_dump(password_verify('ombor#2026', $hash)); // cost oshirilgan bo'lsa, keyingi loginda qayta xeshlash kerak echo password_needs_rehash($hash, PASSWORD_BCRYPT, ['cost' => 12]) ? 'qayta xeshlash' : 'yaxshi';
$2y$10$ 60 bool(true) bool(false) qayta xeshlash
2y = bcrypt), cost va tuz saqlanadi — alohida ustun kerak emasHash::make, Hash::check, Hash::needsRehash — xuddi shu funksiyalar ustidagi qobiqLoginController: xavfsiz kirish
public function store(Request $request): RedirectResponse { $credentials = $request->validate([ 'email' => ['required', 'email'], 'password' => ['required', 'string'], ]); $credentials['is_active'] = true; // bloklangan xodim kirmaydi if (! Auth::attempt($credentials, $request->boolean('remember'))) { throw ValidationException::withMessages([ 'email' => 'Email yoki parol noto‘g‘ri.', ]); } $request->session()->regenerate(); // session fixation return redirect()->intended(route('dashboard')); }
POST /login (to‘g‘ri) → 302 Location: /dashboard POST /login (xato) → 302 back, errors.email is_active = false → xuddi “parol noto‘g‘ri” kabi
Hash::check qiladi va sessiyaga yozadiwhere is_active = true bo‘lib qo‘shiladiKirish so‘rovining xavfsiz yo‘li
Cheklov
RateLimiter: email|ip kaliti bo‘yicha 5 ta urinishdan keyin 429 va kutish vaqtiValidatsiya
email formati, password mavjudligi — $request->validate()Tekshirish
Auth::attempt: e-mail + parol xeshi + is_activeSessiya
session()->regenerate(), cookie: HttpOnly, Secure, SameSite=LaxAudit
Login va Failed hodisalari audit_logs ga yoziladi (IP bilan)RateLimiter::clear($key) bilan hisoblagich nolga tushiriladi.1-bo‘lim yakuni: Autentifikatsiya: foydalanuvchini aniqlash
sha256 bilan saqlash ham xavfli?session()->regenerate() chaqirilmasa, qanday hujum mumkin?1-topshiriq: Parol mustahkamligi
Ro‘yxatdan o‘tishda parol korxona siyosatiga mos kelishini tekshiring. Qoidalar (shu tartibda tekshiriladi): uzunligi kamida 10 belgi (uzunlik), kamida bitta katta lotin harfi (katta_harf), kamida bitta kichik harf (kichik_harf), kamida bitta raqam (raqam), kamida bitta harf-raqam bo‘lmagan belgi (belgi). Agar e-mailning @ gacha bo‘lgan qismi (login) kamida 3 belgidan iborat bo‘lsa va parol ichida u katta-kichik harfdan qat’i nazar uchrasa — email xatosi. @ bo‘lmasa, login — butun satr. Parol faqat ASCII belgilardan iborat deb hisoblang.
Imzo: function parol_tekshir(string $parol, string $email): array
Qaytaradi: Buzilgan qoidalar kodlari ro‘yxati, yuqoridagi tartibda: masalan ['uzunlik', 'raqam']. Parol mustahkam bo‘lsa — [].
parol_tekshir('Ombor#2026x', 'ali@omborpro.test')[]
Avtorizatsiya: Gate va Policy
Avtorizatsiya vositalari
| Vosita | Qachon | OmborPro misoli |
|---|---|---|
Gate::define | modelga bog‘lanmagan amal | view-reports — hisobotlar sahifasi |
| Policy | aniq model obyekti ustidagi amal | OrderPolicy::confirm($user, $order) |
Gate::before | hamma tekshiruvdan oldin | admin — har doim true |
permission: / can: middleware | marshrut yoki guruh darajasida | /invoices/* → permission:invoices.view |
Gate::authorize() | controller yoki servis ichida | ruxsat yo‘q → AuthorizationException → 403 |
@can (Blade) | faqat interfeys | “Tasdiqlash” tugmasini ko‘rsatish/yashirish |
OrderPolicy: ruxsat + biznes holat
class OrderPolicy { public function update(User $user, Order $order): bool { return $user->can('orders.create') && $order->status === OrderStatus::Draft && (int) $order->created_by === $user->id; } public function confirm(User $user, Order $order): Response { if (! $user->can('orders.confirm')) { return Response::deny('Tasdiqlash huquqingiz yo‘q.'); } return $order->status === OrderStatus::Draft ? Response::allow() : Response::deny('Faqat qoralama tasdiqlanadi.'); } }
omborchi → POST /orders/124/confirm → 403 Tasdiqlash huquqingiz yo‘q. menejer, status=confirmed → 403 Faqat qoralama tasdiqlanadi. menejer, status=draft → 302 (tasdiqlandi)
Gate::before, Gate::authorize va marshrut
// AppServiceProvider::boot() — admin uchun hamma narsa Gate::before(fn (User $user, string $ability) => $user->hasRole('admin') ? true : null); // OrderController::confirm(Order $order, OrderService $orders) Gate::authorize('confirm', $order); // yo'q bo'lsa — 403 $orders->confirm($order); // istalgan joyda: true / false $canEdit = $request->user()->can('update', $order); // routes/web.php — marshrut darajasida Route::post('/orders/{order}/confirm', [OrderController::class, 'confirm'])->middleware('auth')->can('confirm', 'order');
Gate::before → true : admin, tekshiruv shu yerda tugaydi Gate::before → null : Policy::confirm() chaqiriladi AuthorizationException → HTTP 403 Forbidden
null — “men qaror qilmayman, Policy hal qilsin”; false hammani bloklaydi$this->authorize() yo‘q — shu usul ishonchlibool qaytaradi2-bo‘lim yakuni: Avtorizatsiya: Gate va Policy
$this->authorize() nima uchun ishlamasligi mumkin va o‘rniga nima yoziladi?2-topshiriq: OrderPolicy qarori
OrderPolicy mantiqini sof PHP da yozing. $user = ['id' => int, 'roles' => [...]], $order = ['status' => string, 'created_by' => int]. Amallar: view — menejer, omborchi yoki buxgalter roli bo‘lsa; update — menejer, buyurtma draft va uni shu foydalanuvchi yaratgan bo‘lsa; confirm — menejer va holat draft; cancel — menejer va holat draft, confirmed yoki reserved. admin roli har qanday ma’lum amalga ruxsat oladi (Gate::before kabi). Noma’lum amal uchun (hatto admin uchun ham) InvalidArgumentException tashlang.
Imzo: function buyurtma_ruxsat(array $user, string $amal, array $order): bool
Qaytaradi: true — ruxsat berilgan, false — rad etilgan (403).
buyurtma_ruxsat(['id' => 5, 'roles' => ['menejer']], 'update', ['status' => 'draft', 'created_by' => 5])
true
RBAC: rollar va ruxsatlar
OmborPro: modul × rol
| Modul | menejer | omborchi | buxgalter |
|---|---|---|---|
| Mahsulotlar | products.view | products.view, products.manage | — |
| Buyurtmalar | orders.view, create, confirm, cancel | orders.view | orders.view |
| Ombor | stock.view | stock.view, stock.move | — |
| Hisob-fakturalar | — | — | invoices.view, invoices.create |
| To‘lovlar | — | — | payments.create |
| Hisobotlar | reports.view | — | reports.view |
| Foydalanuvchilar, audit | — | — | — |
admin — barcha 14 ta ruxsat (users.manage, audit.view faqat unda) va Gate::before.RolesAndPermissionsSeeder::run()
app()[PermissionRegistrar::class]->forgetCachedPermissions(); $matrix = [ 'admin' => ['users.manage', 'audit.view'], // + hammasi pastda 'menejer' => ['orders.view', 'orders.create', 'orders.confirm', 'orders.cancel', 'products.view', 'stock.view', 'reports.view'], 'omborchi' => ['stock.view', 'stock.move', 'products.view', 'products.manage', 'orders.view'], 'buxgalter' => ['invoices.view', 'invoices.create', 'payments.create', 'reports.view', 'orders.view'], ]; foreach ($matrix as $role => $permissions) { foreach ($permissions as $name) { Permission::findOrCreate($name, 'web'); } Role::findOrCreate($role, 'web')->syncPermissions($permissions); } Role::findByName('admin', 'web')->syncPermissions(Permission::all()); $user->assignRole('menejer'); // foydalanuvchiga rol
php artisan db:seed --class=RolesAndPermissionsSeeder roles: 4 · permissions: 14 admin: 14 · menejer: 7 · omborchi: 5 · buxgalter: 5
HasRoles trait i bergan metod; syncRoles() — rollarni almashtiradiRBAC tekshiruvi qanday ishlaydi
$roles = [ 'menejer' => ['orders.view', 'orders.create', 'orders.confirm'], 'omborchi' => ['stock.view', 'stock.move', 'orders.view'], 'buxgalter' => ['invoices.create', 'payments.create'], ]; function can(array $userRoles, string $perm, array $roles): bool { if (in_array('admin', $userRoles, true)) { return true; // Gate::before analogi } $lists = array_map(fn ($r) => $roles[$r] ?? [], $userRoles); return in_array($perm, array_merge([], ...$lists), true); // rad } foreach ([[['omborchi'], 'stock.move'], [['omborchi'], 'orders.create'], [['menejer', 'buxgalter'], 'payments.create'], [[], 'orders.view'], [['admin'], 'users.manage']] as [$userRoles, $perm]) { echo can($userRoles, $perm, $roles) ? 'ha' : 'yo\'q', PHP_EOL; }
ha yo'q ha yo'q ha
Gate::before kabi: tekshiruv boshidayoq true3-bo‘lim yakuni: RBAC: rollar va ruxsatlar
hasRole() emas, can() ni tekshirish afzal?3-topshiriq: Ruxsat: aniq nom va wildcard
RBAC tekshiruvini yozing. $rollar — rol nomi → ruxsatlar ro‘yxati. Ruxsat namunasi aniq nom (orders.view), modul bo‘yicha wildcard (orders.* — orders. bilan boshlanadigan har qanday ruxsat) yoki * (hammasi) bo‘lishi mumkin. Foydalanuvchi rollaridan kamida bittasida mos namuna bo‘lsa — ruxsat bor. admin roli xaritada bo‘lmasa ham har doim ruxsat oladi. Foydalanuvchida xaritada yo‘q (va admin bo‘lmagan) rol bo‘lsa — DomainException.
Imzo: function ruxsat_bormi(array $foydalanuvchiRollari, string $ruxsat, array $rollar): bool
Qaytaradi: true yoki false.
ruxsat_bormi(['omborchi'], 'stock.move', ['omborchi' => ['stock.*', 'orders.view']])
true
Audit jurnali: kim, qachon, nimani o‘zgartirdi
Har bir yozuv oltita savolga javob beradi
1Kim?
user_id — tizim jarayoni (navbat, scheduler) bo‘lsa null2Nima?
action: created, updated, deleted, login, login_failed, role_changed3Qaysi obyekt?
auditable_type + auditable_id: App\Models\Product #124Oldin → keyin
old_values, new_values — faqat o‘zgargan maydonlar, JSON5Qayerdan?
ip — request()->ip(); kerak bo‘lsa user agent6Qachon?
created_at UTC da; updated_at yo‘q — yozuv o‘zgarmaydiAuditable: updated hodisasi
trait Auditable { public static function bootAuditable(): void { static::updated(function (Model $model) { $hide = ['password', 'remember_token', 'updated_at']; $new = Arr::except($model->getChanges(), $hide); $old = Arr::only($model->getOriginal(), array_keys($new)); AuditLog::create([ 'user_id' => auth()->id(), 'action' => 'updated', 'auditable_type' => $model->getMorphClass(), 'auditable_id' => $model->getKey(), 'old_values' => $old, 'new_values' => $new, 'ip' => request()->ip(), ]); }); } }
audit_logs #981: user_id=7, action=updated
auditable = App\Models\Product #12
old_values = {"price":"125000.00"}
new_values = {"price":"119000.00"}
ip = 10.0.5.23boot + trait nomi ko‘rinishidagi statik metodni avtomatik chaqiradisave() da haqiqatan o‘zgargan maydonlarupdated hodisasida hali eski qiymatlarauditable_type ustuni uchunO‘zgarishlar farqi va maxfiy maydonlar
function auditDiff(array $old, array $new, array $hidden): array { $diff = ['old' => [], 'new' => []]; foreach ($new as $key => $value) { if (array_key_exists($key, $old) && $old[$key] === $value) { continue; // o'zgarmagan } $mask = in_array($key, $hidden, true); $diff['old'][$key] = $mask ? '***' : ($old[$key] ?? null); $diff['new'][$key] = $mask ? '***' : $value; } return $diff; } $old = ['price' => '125000.00', 'name' => 'Un', 'password' => 'h1']; $new = ['price' => '119000.00', 'name' => 'Un', 'password' => 'h2']; echo json_encode(auditDiff($old, $new, ['password']));
{"old":{"price":"125000.00","password":"***"},"new":{"price":"119000.00","password":"***"}}'10' va 10 farq qiladi — Eloquent cast larini hisobga olingnull qiymatli maydon ham “bor” hisoblanadi (isset dan farqi)Audit jurnali: xato va to‘g‘ri yondashuv
✗ Noto‘g‘ri
- Auditni faqat
laravel.logga yozish — 14 kunda aylanib o‘chadi old_valuesga parol xeshi va tokenlarni ham yozish- Admin uchun “jurnalni tozalash” tugmasi
Product::where(...)->update()bilan narxlarni ommaviy o‘zgartirish — iz qolmaydi- Faqat muvaffaqiyatli amallarni yozish
✓ To‘g‘ri
- Alohida
audit_logsjadvali, indekslar va saqlash muddati siyosati password,remember_token—***yoki umuman yozilmaydi- Faqat qo‘shish (append-only): DB da
REVOKE UPDATE, DELETE - Ommaviy o‘zgarish servis orqali — har bir model
save()yoki aniq audit yozuvi login_failedva 403 urinishlari ham yoziladi
4-bo‘lim yakuni: Audit jurnali: kim, qachon, nimani o‘zgartirdi
Product::where('category_id', 3)->update(['price' => ...]) audit jurnaliga tushmaydi?OWASP Top 10 va Laravel himoya vositalari
A01–A05: OmborPro da qanday ko‘rinadi
| Kod | Xavf | OmborPro misoli | Laravel himoyasi |
|---|---|---|---|
| A01 | Broken Access Control | omborchi /invoices/46 ni ochadi (IDOR) | Policy, permission: middleware, Gate::authorize |
| A02 | Cryptographic Failures | parol md5, STIR ochiq matnda | bcrypt/argon2id, encrypted cast, HTTPS |
| A03 | Injection (SQL, XSS) | whereRaw("sku = '$sku'"), {!! $name !!} | binding, Rule::in ustunlar, {{ }} |
| A04 | Insecure Design | manfiy qoldiq, tasdiqsiz bekor qilish | invariantlar, holat mashinasi (4-mavzu) |
| A05 | Security Misconfiguration | production da APP_DEBUG=true | .env nazorati, Telescope o‘chiq |
A06–A10: davomi
| Kod | Xavf | OmborPro misoli | Laravel himoyasi |
|---|---|---|---|
| A06 | Vulnerable and Outdated Components | eski paket versiyasidagi ma’lum zaiflik | composer audit, muntazam yangilash |
| A07 | Identification and Authentication Failures | cheksiz login urinishlari, zaif parol | RateLimiter, parol qoidalari, 2FA |
| A08 | Software and Data Integrity Failures | imzosiz webhook, soxtalashtirilgan havola | hash_hmac imzo, signed middleware |
| A09 | Security Logging and Monitoring Failures | kim narxni o‘zgartirgani noma’lum | audit_logs, login_failed, monitoring |
| A10 | Server-Side Request Forgery | URL bo‘yicha rasm yuklash ichki serverga boradi | host ro‘yxati, ichki IP larni taqiqlash |
Xavfli va xavfsiz yozuv
✗ Noto‘g‘ri
DB::select("select * from products where sku = '$sku'")->orderByRaw($request->input('sort')){!! $product->name !!}— mahsulot nomida<script>bo‘lsa ishlaydiUser::create($request->all())if ($signature == $expected)
✓ To‘g‘ri
Product::where('sku', $sku)->first()— binding'sort' => Rule::in(['name', 'price', 'sku'])+orderBy($sort){{ $product->name }}— avtomatik ekranlash$fillable+User::create($request->validated())hash_equals($expected, $signature)— vaqtga chidamli
ProductController::index — validatsiya va binding
public function index(Request $request) { $data = $request->validate([ 'q' => ['nullable', 'string', 'max:100'], 'sort' => ['nullable', Rule::in(['name', 'price', 'sku'])], ]); return Product::query() ->when($data['q'] ?? null, fn ($query, $term) => $query->where('name', 'ilike', "%{$term}%")) ->orderBy($data['sort'] ?? 'name') ->paginate(20); }
?q=un&sort=price → select * from "products" where "name"::text ilike ? and "products"."deleted_at" is null order by "price" asc limit 20 offset 0 bindings: ["%un%"] ?sort=id;drop table users → validatsiya xatosi, SQL bajarilmaydi
? binding ga tushadiSoftDeletes (3-mavzu) o‘chirilganlarni avtomatik chiqarib tashlaydi5-bo‘lim yakuni: OWASP Top 10 va Laravel himoya vositalari
orderBy($request->sort) binding bo‘lsa ham xavfli va qanday tuzatiladi?{{ }} va {!! !!} ning farqi nimada?Asosiy xulosalar
1Uch savol: kim, nima mumkin, nima qildi
2Parol — faqat sekin, tuzli xesh
Hash::make, password_verify; login dan keyin session()->regenerate().3Policy — obyekt darajasidagi qoida
Gate::authorize, ->can(), Gate::before da null.4RBAC — ruxsatni tekshiring, rolni emas
HasRoles, seeder, permission: middleware, keshni tozalash.5Audit — faqat qo‘shish mumkin
***, ommaviy update() ga e’tibor.6OWASP Top 10 — tekshiruv yo‘nalishi
{{ }}, $fillable, @csrf, APP_DEBUG=false, composer audit, imzolangan havolalar.Yakunlashdan oldin sakkizta savol
Auth::attempt ga 'is_active' => true qo‘shish nima beradi?Gate::before admin bo‘lmaganlar uchun nima qaytarishi kerak?5-amaliy mashg‘ulot: 5 ta PHP topshiriq va loyiha bosqichi
Ruxsatlarni modullar bo‘yicha guruhlash
Audit: o‘zgargan maydonlar
Login urinishlarini cheklash
Imzolangan havola (signed URL)
O‘zgartirib bo‘lmaydigan audit zanjiri
Darsni tark etishdan oldin
Javoblaringizni yozing (✎ Javob yozish) yoki qog‘ozga yozib topshiring.