@hamidou.hollanda: #blida09_tiktok_algérie❤️🇩🇿 #البليدة_حنوني09🌹❤🇩🇿💖✌ #algeria #ministere #fyp

hamidou hollanda ⚕️

Open In TikTok:

Region: DZ

Tuesday 30 June 2026 08:22:22 GMT

38411

1559

36

77

Music

Download

No Watermark .mp4 (1.34MB) No Watermark(HD) .mp4 (0.99MB) Watermark .mp4 (0MB) Music .mp3

Comments

Youcef Hamlat :

الله يسترك وخلاص واعرة تبقا ساكت ربي يحفظك

2026-06-30 11:25:35

29

user4729112125310 :

هذي فيها قصة كبيرة ربي يجب لخير

2026-06-30 15:11:56

6

Moh Azaro dz :

أهدر حتي عام جاي 😂😂

2026-06-30 19:49:28

0

rahim🇲🇽 :

علاه حبست؟؟

2026-06-30 19:59:33

0

user4965691311477 :

يعطيك صحة

2026-06-30 19:36:16

0

Abdelwahab Bouchlaghem :

هدر برك

2026-06-30 19:17:28

0

Zaki vip :

برتاج برتاج

2026-06-30 18:28:33

0

Issam Bezalla :

أزمة مالية

2026-06-30 17:17:41

0

ابو زياد ☝️💪🇩🇿09 :

جات الشتاء و جات السخانة و حنا مشفناش

2026-06-30 16:57:01

0

Chouaib Alger :

يعطيك صحا على المعلومة♥️

2026-06-30 15:16:04

1

mehdi :

منا على 20 سنة ان شاء الله

2026-06-30 16:12:40

0

vts 🇩🇿 :

إنشاء الله يخلوها

2026-06-30 15:16:55

0

abderrahman. Hadji :

راني معاك

2026-06-30 19:44:01

0

Oussama Mamèche :

تلفريك و مخطط السير الجديد وفتح مدالحواجز المغلقة تاع السكك الحديدية مبان والو

2026-06-30 19:06:12

0

sidahmedboukourba :

واش هلوندي هادي غيبة

2026-06-30 14:16:18

0

fontom 300.300.300 :

صحبي حميد بعتلي بريفي كاين جديد ليك و

2026-06-30 15:43:32

0

fleurheureuse09 :

والله نتأسفو على بليدة

2026-06-30 16:21:52

0

Fõûád 09 :

كون في عاصمة راهي تخدمت الله غالب البليدة 🤐

2026-06-30 18:41:06

0

tchiro :

علاش ماراهيش تخدم

2026-06-30 12:56:36

1

magheraoimohamed :

🥰🥰🥰🥰🥰🥰🥰🥰🥰

2026-06-30 09:59:21

1

🧔‍♂️قمر الزمان🏃‍♂️ :

❤️❤️❤️

2026-06-30 10:06:46

1

zi zõũ :

🥰🥰

2026-06-30 16:50:44

0

dyydo6qrmj1a :

😇😇😇

2026-06-30 17:03:41

0

🤍Abdou09💚 :

🥰🥰🥰

2026-06-30 17:41:23

0

SidaLi_Guedouar :

🥰🥰🥰

2026-06-30 12:15:50

0

To see more videos from user @hamidou.hollanda, please go to the Tikwm homepage.

Other Videos

Most breaches are not detected because organizations lack tools. They are detected late because teams are *drowning in logs that do not matter* while ignoring the ones attackers actually leave behind. In incident response, logs are your forensic truth. But not all logs are equal. The difference between rapid containment and weeks of blind investigation often comes down to *which logs you prioritized before the attack happened*. Below is a practitioner-focused breakdown of the logs that truly matter during real-world attacks. 1. Authentication & Identity Logs (High Priority) Attackers almost always touch identity first. Why they matter: * Credential stuffing * Brute-force attempts * Account takeovers * Privilege escalation Key signals to watch: * Multiple failed logins followed by a success * Logins from new geolocations or impossible travel * Authentication outside normal business hours * MFA bypass or MFA fatigue patterns Sources: * Active Directory / Azure AD * IAM providers (Okta, AWS IAM, Entra ID) 2. Endpoint & EDR Logs Endpoints are where execution happens. Why they matter: * Malware execution * Living-off-the-land attacks (PowerShell, WMI, LOLBins) * Persistence mechanisms Key signals: * Suspicious process creation * Script execution from temp or user directories * Unusual parent-child process relationships * Disabled security tools Sources: * EDR/XDR platforms * Windows Event Logs (Sysmon if configured) * Linux audit logs 3. Network & Firewall Logs Attackers must move, scan, and exfiltrate. Why they matter: * Lateral movement * Command-and-control (C2) traffic * Data exfiltration Key signals: * Internal scanning behavior * Outbound traffic to rare or newly registered domains * Large data transfers at odd hours * Repeated blocked connection attempts Sources: * Firewalls * IDS/IPS * Proxy and VPN logs * DNS logs (extremely valuable) 4. Web Server & Application Logs Most breaches begin at the application layer. Why they matter: * Exploitation of vulnerabilities * Abuse of business logic * Web shells and backdoors Key signals: * SQL injection patterns * Directory traversal attempts * Abnormal HTTP status codes (500s, 403s, 401s) * Requests to unexpected endpoints Sources: * Web servers (Apache, Nginx, IIS) * Application logs * API gateway logs 5. Privilege & Administrative Activity Logs Attackers aim for control. Why they matter: * Detection of privilege escalation * Abuse of admin accounts * Creation of backdoor users Key signals: * New admin accounts created * Changes to group memberships * Service accounts used interactively * Privileged actions without change tickets Sources: * Directory services * Cloud control plane logs * PAM solutions 6. Database & Data Access Logs Breaches are about *data*. Why they matter: * Data theft * Insider threats * Compliance impact analysis Key signals: * Mass queries or exports * Access from unfamiliar applications or IPs * Reads without corresponding application activity Sources: * Database audit logs * Cloud storage access logs What Most Organizations Get Wrong * Logging *everything* without context * No centralized log management (no SIEM correlation) * No baseline of “normal” behavior * Logs retained for too short a period Logs only become powerful when they are: * Centralized * Correlated * Retained long enough * Actively monitored with detection use cases Final Takeaway Logs do not prevent attacks. They explain attacks, reduce dwell time, and make recovery possible. If you had only 24 hours of logs after a breach, would they tell you *what actually happened*? If not, log management is not a compliance task — it is a security risk. If this helped, share it with someone building a SOC, running Splunk/ELK, or responsible for incident response in 2025.

Most breaches are not detected because organizations lack tools. They are detected late because teams are *drowning in logs that do not matter* while ignoring the ones attackers actually leave behind. In incident response, logs are your forensic truth. But not all logs are equal. The difference between rapid containment and weeks of blind investigation often comes down to *which logs you prioritized before the attack happened*. Below is a practitioner-focused breakdown of the logs that truly matter during real-world attacks. 1. Authentication & Identity Logs (High Priority) Attackers almost always touch identity first. Why they matter: * Credential stuffing * Brute-force attempts * Account takeovers * Privilege escalation Key signals to watch: * Multiple failed logins followed by a success * Logins from new geolocations or impossible travel * Authentication outside normal business hours * MFA bypass or MFA fatigue patterns Sources: * Active Directory / Azure AD * IAM providers (Okta, AWS IAM, Entra ID) 2. Endpoint & EDR Logs Endpoints are where execution happens. Why they matter: * Malware execution * Living-off-the-land attacks (PowerShell, WMI, LOLBins) * Persistence mechanisms Key signals: * Suspicious process creation * Script execution from temp or user directories * Unusual parent-child process relationships * Disabled security tools Sources: * EDR/XDR platforms * Windows Event Logs (Sysmon if configured) * Linux audit logs 3. Network & Firewall Logs Attackers must move, scan, and exfiltrate. Why they matter: * Lateral movement * Command-and-control (C2) traffic * Data exfiltration Key signals: * Internal scanning behavior * Outbound traffic to rare or newly registered domains * Large data transfers at odd hours * Repeated blocked connection attempts Sources: * Firewalls * IDS/IPS * Proxy and VPN logs * DNS logs (extremely valuable) 4. Web Server & Application Logs Most breaches begin at the application layer. Why they matter: * Exploitation of vulnerabilities * Abuse of business logic * Web shells and backdoors Key signals: * SQL injection patterns * Directory traversal attempts * Abnormal HTTP status codes (500s, 403s, 401s) * Requests to unexpected endpoints Sources: * Web servers (Apache, Nginx, IIS) * Application logs * API gateway logs 5. Privilege & Administrative Activity Logs Attackers aim for control. Why they matter: * Detection of privilege escalation * Abuse of admin accounts * Creation of backdoor users Key signals: * New admin accounts created * Changes to group memberships * Service accounts used interactively * Privileged actions without change tickets Sources: * Directory services * Cloud control plane logs * PAM solutions 6. Database & Data Access Logs Breaches are about *data*. Why they matter: * Data theft * Insider threats * Compliance impact analysis Key signals: * Mass queries or exports * Access from unfamiliar applications or IPs * Reads without corresponding application activity Sources: * Database audit logs * Cloud storage access logs What Most Organizations Get Wrong * Logging *everything* without context * No centralized log management (no SIEM correlation) * No baseline of “normal” behavior * Logs retained for too short a period Logs only become powerful when they are: * Centralized * Correlated * Retained long enough * Actively monitored with detection use cases Final Takeaway Logs do not prevent attacks. They explain attacks, reduce dwell time, and make recovery possible. If you had only 24 hours of logs after a breach, would they tell you *what actually happened*? If not, log management is not a compliance task — it is a security risk. If this helped, share it with someone building a SOC, running Splunk/ELK, or responsible for incident response in 2025.

Aww hmm #elephantqueen #morda #fyp #odobroni #akosuaserwaa

Aww hmm #elephantqueen #morda #fyp #odobroni #akosuaserwaa

حسين الغزال | بين نارين #حسين_الغزال #هواجيس #fyp إعادة النشر 🔃. #fyppppppppppppppppppppppp #foryou

حسين الغزال | بين نارين #حسين_الغزال #هواجيس #fyp إعادة النشر 🔃. #fyppppppppppppppppppppppp #foryou

@Lukinha @Rafael Cabral - - - - #mjmusiccy #saojoao #lukinha #forró #artista

@Lukinha @Rafael Cabral - - - - #mjmusiccy #saojoao #lukinha #forró #artista

HUYO MBWA SIJUI AKIMKAMATA ATAMFANYA NINI WALAHI😂😂😂😂😂

HUYO MBWA SIJUI AKIMKAMATA ATAMFANYA NINI WALAHI😂😂😂😂😂

About

Robot
API

Legal

Privacy Policy