white2hack 📚 – Telegram
white2hack 📚
12.4K subscribers
4.8K photos
135 videos
1.96K files
2.26K links
Кибербез. Книги, гайды, how to, ликбез. Аналитика, тренды, карьера, эвенты. Этичный хакинг и защита своих данных

🔊 Связь @w2hack_feed_bot
💬 Чат https://news.1rj.ru/str/+VdkEIWudTi5m3dsA
💡 Консультация https://forms.gle/iB9iX3BwyxJM4Ktx5
🏛 Обмен -- private --
Download Telegram
🧱 IPTables, Demystified — Linux Firewall Fundamentals for Blue Teams

If you’re in SysAdmin, DevSecOps, Cloud, SOC, or Network Security, this is core knowledge for traffic control, segmentation, and incident response on Linux hosts.

🧠 What the Guide Breaks Down

1️⃣ Firewall Architecture 101
External vs internal firewalls and where IPTables fits
Stateful inspection & connection tracking in plain language

2️⃣ How IPTables Is Structured
Tables: filter, nat, mangle, raw, security
Chains: INPUT, OUTPUT, FORWARD, etc.
How a packet actually travels through the kernel routing path

3️⃣ Building Real Rules (Not Just Copy-Paste)
Why a default DROP policy is your safest baseline
Letting only ESTABLISHED and RELATED traffic through
Handling loopback, DHCP, SSH, FTP/TFTP the right way
From zero to “basic firewall deployed & persistent”

4️⃣ Advanced Topics for Practitioners
Connection tracking with conntrack
Passive vs active FTP nuances
Tuning modules and limits (e.g. nf_conntrack_max, timeouts, NAT helpers)

#linux #defensive
1
IPTables,_Demystified_—_Linux_Firewall_Fundamentals_for_Blue_Teams.pdf
781.4 KB
🧱 IPTables, Demystified — Linux Firewall Fundamentals for Blue Teams
🤝1
The board won’t fund cyber brilliance.
They fund what they understand.


Because when security works, nothing happens. When it fails, you make headlines.
Security should be boring. But leadership needs to know the value...

#management
1
Real-World Cybersecurity Scenario-Based Questions SOC.pdf
217.8 KB
Real-World Cybersecurity Scenario-Based Questions SOC
1
Real-World Cybersecurity Scenario-Based Questions SOC

SOC Interviews Aren’t About Tools — They’re About Thinking Under Pressure

If you’re preparing for SOC Analyst interviews, this resource is gold. I came across a Scenario-Based Cybersecurity Interview Guide that uses the S.T.E.P. method (Situation → Triage → Evaluation → Prevention/Response) — and it perfectly reflects how real SOC work is assessed today.

This isn’t theory. It’s real-world incident thinking.

📘 What’s inside the guide:

🔐 Credential & Identity Attacks
• Suspicious foreign logins
• MFA fatigue attacks
• Azure AD / IAM compromise scenarios

🦠 Endpoint & Malware Incidents
• Obfuscated PowerShell via Office macros
• C2 beaconing & EDR response
• Post-exploitation detection

🔄 Lateral Movement & Privilege Abuse

• SMB / WMI attacks
• Kerberos anomalies & Mimikatz
• Domain admin misuse

📤 Data Exfiltration Scenarios
• HTTPS + DNS tunneling
• 7z staging & off-hours transfers
• DLP and egress control decisions

📧 Business Email Compromise (BEC)
• Mailbox rule abuse
• Auto-forwarding & vendor fraud
• SOC–Finance incident coordination

☁️ Cloud & Supply Chain Attacks
• Compromised IAM roles
• API abuse & cryptomining
• Malicious software updates

#defensive
4
Methods for Stealing Passwords in Browser

The document provides details on tables and columns in the Chrome and Firefox browsers that may contain sensitive user information like saved passwords, browsing history, cookies, and more.

It lists the table names and relevant column names for Chrome and Firefox that could be used to extract passwords, browsing data, autofill form information, and other private browsing data from the browsers. The tables described contain a wealth of personal data that could be abused if improperly accessed.

#web
1
Methods for Stealing Passwords in Browser.pdf
1.4 MB
Methods for Stealing Passwords in Browser
OWASP Top 10 2025 Updates: Supply Chain, Secrets, And Misconfigurations Take Center Stage

Official page

#web
👍5🔥3
Master OSINT Skills with Professional Training

15+ Training Modules
100% Free Access
24/7 Available Online


Your premier resource for Open Source Intelligence training and education, featuring professional-grade modules designed for real-world applications. Learn at your own pace with our structured curriculum.

Official page
All Modules

#OSINT #education
🔥73
Расскажи свою историю! Как ты стал частью White2Hack комьюнити или что нашел в нем? Быть может контент канала смог что-то изменить для тебя или в чем-то помог?

Курьезная история знакомства, а может быть у тебя есть интересны факт связанный с каналом, админом или в целом ИБ темой, м?

Пиши в коменты к посту! Делись всем что чувствуешь, что посчитаешь нужным.

#talk
4
Introducing Network Security

Network security isn’t just an IT responsibility anymore — it’s a business-critical priority.


From evolving threat vectors to hybrid-cloud complexity, the modern enterprise demands architecture, visibility, and resilience at a level never seen before.

That’s why we created this comprehensive Network Security Guide — a distilled view of frameworks, architectures, KPIs, governance models, and threat insights that every cybersecurity leader must keep on their radar.

Built using industry best practices and expert insights, this guide simplifies complexity so teams can build stronger, smarter, and future-ready network defenses.

📘 Explore the full guide and take a meaningful step toward stronger security maturity.


#defensive
2👍2
1764575644054.pdf
12.5 MB
Introducing Network Security
1
Linux Privilege Escalation

Linux Privilege Escalation — The Skill Every Cybersecurity Professional Must Master in 2025

I just reviewed one of the most comprehensive Linux PrivEsc guides I’ve seen and it’s packed with real techniques attackers actually use in real breaches. If you work in Red Teaming, Pentesting, Threat Hunting, SOC, DFIR or even Cloud this is the kind of knowledge that separates beginners from true professionals.

🧠 What the PDF Covers (and Why It Matters)

🔹 Deep Enumeration: kernel version, sudo rights, SUID/SGID binaries, environment variables, cronjobs, backups, hidden files, services, shells (pages 1–3)
🔹 Automated Enum: LinEnum, LinPEAS, enumy, linuxprivchecker (page 4)
🔹 Kernel Exploits: searchsploit + exploit suggester (page 4)
🔹 Weak Permissions Abuse: /etc/shadow, /etc/passwd, binary overwrites (pages 5–6)
🔹 Credential Harvesting: history grep, config leakage, memory dump tools like mimipenguin (page 6)
🔹 Docker & LXD Breakouts: mounting host FS, privilege containers (pages 7–8)
🔹 SUID/SGID Exploits: PATH hijacking, shared object injection, cron abuse (pages 9–10)
🔹 LD_PRELOAD / LD_LIBRARY_PATH attacks: hijacking libraries to spawn root shells (pages 11–13)
🔹 Python Module Hijacking: creating fake modules to escalate privileges (page 14)
🔹 GTFOBins techniques the ultimate misconfiguration weapon (multiple pages)
🔹 NFS no_root_squash exploitation (page 17)
🔹 Session Hijacking (screen/tmux) (pages 18–19)
🔹 Reverse Shell Hijacking (page 20)

This is not theory these are the exact paths attackers use after initial access. If you can’t detect or replicate them, you can’t defend against them.

My biggest takeaway:
Privilege escalation isn’t a toolset it’s a mindset of finding one misconfiguration that changes everything.

#linux
🔥5👍32
Linux Privilege Escalation.pdf
1.3 MB
Linux Privilege Escalation
👍71
Please open Telegram to view this post
VIEW IN TELEGRAM
1🔥1
Friends, colleagues, like-minded people. This message is more than just an announcement. It's the outcome of long reflection and an evolution of views that I want to share with you, with those who make up our community.

Since 2018, this channel has been more than just a platform for me. We've grown together from the first few hundred subscribers to 17k, and during that time, a lot has appeared here: my original articles, useful links, books, courses, repositories, job market reports, analysis on relocation and salaries. This included "leaks" / pirated copies of books, paid courses, and software. My reasoning back then was simple: I was once a student myself with no money and limited access to knowledge, and I wanted to help others in a similar situation — to give people a chance to study, enter the industry, and earn a living. I went through that journey as a student from a town where it was hard to even get physical books, and I understood the value of having access to knowledge "here and now." My motives then were help, sharing, and the idea that information should be free in the sense of being accessible.

Today, my views have changed. I've come to think differently about ideas of scarcity and abundance, about respect for others' work, and about how knowledge is created. From my own experience writing brochures and a book, I know how much effort goes into it from the author, editor, layout designer, and publisher. Piracy, even with "good intentions," ultimately doesn't help authors or the industry: it's rooted in a mindset of lack, in the habit of taking others' work for free and considering that normal. I am increasingly convinced that work should be paid for, and that a legal purchase is a real contribution to the development of a product, course, or book. By respecting others' work, we respect our own (after all, you also work, create something, and of course want to be paid fairly for your labor). Buying a licensed copy isn't just a transaction; it's a signal to the author: "Your work is valuable, keep going." It's what gives projects a longer life, stimulates the creation of new courses, updates to books, and the development of tools.

Therefore, starting some time this year, pirated materials have stopped appearing on the channel: books, paid courses, software, leaks, and any other content that violates copyright. Only legal resources will remain here: officially free books and brochures, open reports, articles, repositories, and materials that rights holders themselves permit to be freely distributed. Everything that was ever posted here, I used and offered to you precisely as a tool for self-education, skill improvement, and growing expertise — to later convert that knowledge into decent work and legal income — but from now on, I want to move forward in a different, more honest and transparent format.

I still believe knowledge should be accessible. But "accessible" doesn't mean "stolen / obtained for free." By disrespecting others' work, we essentially agree that our own work can also be disrespected and unpaid. I no longer want to support that logic, either for myself or for this community.

I don't condemn my past, and I understand this content won't disappear from the internet. But my personal path and my responsibility now lie on a different plane. I no longer want to be a conduit for that model. This isn't about trying to become an "angel." It's about growing up. It's about building an industry where work is valued and quality knowledge is fairly rewarded.

If this approach resonates with you — stay. If not — that's okay too: everyone chooses their own path. In any case, thank you to everyone who has been with me all these years, learning, sharing, debating, and growing together with the channel.

I am endlessly grateful for your trust and for our growth to 17,000 readers. This channel has been our shared space for learning. Now I invite you into the next phase — a phase of more conscious and respectful consumption of content.

#info
5💅3🤷‍♂1
🔐 CIA vs DAD in Cybersecurity — The Battle of Intentions 🔥

In cybersecurity, motivation matters — and so do acronyms.

We often talk about the CIA Triad:
Confidentiality – Keep data secret
Integrity – Keep data accurate
Availability – Keep systems running

It’s the backbone of every security programme. It’s what defenders strive to protect every single day.

But on the other side?
Attackers have their own model — DAD:
Disclosure – Expose your data
Alteration – Manipulate your information
Denial – Disrupt your access

It’s literally the inverse of CIA — the attacker’s playbook.

👉 CIA = Protect
👉 DAD = Destroy


Understanding both sides helps us build stronger, smarter, more resilient security controls.

#defensive
🔥3😁21