Network Security Channel
2.76K subscribers
5.35K photos
3.42K videos
5.59K files
4.45K links
⭕️Start Channel From 2017⭕️
Security Operation Center (SOC)
Bug Bounty
Vulnerability
Pentest
Hardening
Linux
Reasearch
Security Network
Security Researcher
DevSecOps
Blue Team
Red Team
Download Telegram
1780220276768.pdf
3.1 MB
🔹 Share & Support Us 🔹
📱 Channel : @Engineer_Computer
1
Network Security Channel
1780220276768.pdf
🛡 "Never trust, always verify." — Zero Trust, demystified
I just went through the NSA's "Zero Trust Implementation Guideline (ZIG) Primer" (Jan 2026) — a clear entry point into how large, high-stakes organizations actually operationalize Zero Trust, not just talk about it. Sharing a few takeaways 👇
🔑 The core mindset: Drop perimeter-based thinking. Continuously authenticate and authorize every user, device, and application — built on two assumptions: "never trust, always verify" and "assume breach."
🧱 It's structured around the DoW ZT Framework's seven pillars: User, Device, Application & Workload, Data, Network & Environment, Automation & Orchestration, and Visibility & Analytics — each broken into Capabilities → Activities you can actually implement.
🪜 A phased, modular roadmap instead of "boil the ocean":
Discovery — inventory your Data, Applications, Assets & Services (DAAS) and identities
Phase One & Two — Target-level capabilities (think MFA, identity lifecycle, EDR/XDR, comply-to-connect, data tagging)
Phase Three & Four — Advanced-level maturity
📚 What I appreciated: it ties together the big reference points — NIST SP 800-207, the CISA Zero Trust Maturity Model 2.0, and the DoW ZT Strategy — so you see how the standards fit into one implementation path.
💡 Biggest reminder for me: Zero Trust is a journey of capabilities, not a product you buy. Start with visibility and identity, then build outward.
A great vendor-neutral read for anyone working in security architecture, identity, or critical infrastructure. Credit to the NSA Cybersecurity Directorate for publishing it openly. 🙏
What's the hardest pillar to get right in practice — Identity, Data, or Visibility & Analytics? 💬

#ZeroTrust #CyberSecurity #NIST80027 #ZTA #IdentitySecurity #NSA #SecurityArchitecture #DefenseInDepth #InfoSec #CriticalInfrastructure

🔹 Share & Support Us 🔹
📱 Channel : @Engineer_Computer
1
🔹 Share & Support Us 🔹
📱 Channel : @Engineer_Computer
Network Security Channel
🔹 Share & Support Us 🔹 📱 Channel : @Engineer_Computer
A FREE 25+-hour course on getting started in OT/ICS cybersecurity?

Over 110,000 people have watched my course on YouTube.

At least the first part 🙂

Over 2,000+ people have taken my course live.

Here are a few of the nice things some students have said:

"I got the job because of your course!"

"The contents covered during this week were amazing and insightful, and I learned so much from it."

"This was by far the best training that I have ever received on OT/ICS Cybersecurity. Your teaching style is absolutely top notch."

"It was interesting to learn from your unique and insightful perspectives. Not many folks have a strong exposure to Industry and OT Security experience."

"It is really useful and beneficial course. I really appreciate your time that you sacrifice for us to make we more understand about the ICS Cyber Security especially in a way of view from the IT perspective in OT environment."

"It helped me have a much greater understanding of the environment, technologies and strategies to secure ICS/OT facilities!"

"I just wanted to express my gratitude and appreciation for the amazing course! The contents covered during this week were amazing and insightful, and I learned so much from it."

"I really enjoyed the class and learned quite a lot of new information, including how much I don't know about the topic.  It was really fascinating to me.  And of course, you are an excellent teacher."

"You have a horrible singing voice, Grandpa!"

Want to learn more about OT/ICS cybersecurity?

The complete course is now available!

With 200+ review questions to test your knowledge!

You can find the entire course on my YouTube channel at https://www.youtube.com/@utilsec

Here's the section list:

Part 1: Introduction to Getting Started in ICS/OT Cyber Security
Part 2: ICS/OT Cyber Security Overview
Part 3: Control Systems & Protocols
Part 4: Secure Network Architecture
Part 5: Asset Registers & Control Systems Inventory
Part 6: Threat & Vulnerability Management
Part 7: OSINT for Industrial Controls
Part 8: Incident Detection & Response
Part 9: Industry Standards & Regulations
Part 10: Introduction to ICS/OT Penetration Testing
Part 11: Review Questions

Thank you for taking the time to check it out!

🔹 Share & Support Us 🔹
📱 Channel : @Engineer_Computer
1
با احترام، از افراد متخصص، توانمند و باانگیزه دعوت می‌کنیم فرصت همکاری با دژپاد را بررسی نمایند.

فرصت همکاری در دژپاد
شرکت دژپاد در راستای توسعه تیم فنی و تخصصی خود، از افراد توانمند و متخصص برای موقعیت‌های زیر دعوت به همکاری می‌نماید:

🔹 کارشناس شبکه و امنیت شبکه
مسلط به مفاهیم Network & Security، مباحث CCNA، تجهیزات FortiGate، پروتکل‌های Layer 2 و Layer 3، فایروال‌های NGFW و WAF، طراحی و مدیریت شبکه‌های سازمانی و عیب‌یابی زیرساخت‌های پیچیده.

🔹 کارشناس ارشد زیرساخت مجازی‌سازی و ذخیره‌سازی
مسلط به VMware، Storage های HPE و DELL، شبکه‌های SAN Fabric، سرورهای HPE، راهکارهای Backup & Recovery و مدیریت و عیب‌یابی زیرساخت‌های مجازی‌سازی و ذخیره‌سازی سازمانی.

📍 محل کار: تهران
🕒 نوع همکاری: تمام‌وقت

📩 ارسال رزومه به ایمیل:
hr@dejpaad.com

#استخدام #فرصت_شغلی #امنیت_شبکه #زیرساخت #مجازی_سازی #Storage #VMware #Fortinet #NetworkSecurity #Infrastructure #Hiring #JobOpportunity #دژپاد #Dejpaad

🔹 Share & Support Us 🔹
📱 Channel : @Engineer_Computer
3
دو تن از بزرگان در حوزه‌ی امنیت مدل‌های یادگیری ماشین

نیکولاس کارلینی که ۳۶ سال سن دارد و هم‌اکنون در آنتروپیک مشغول به کار است، پیش از آن در دیپ‌مایند گوگل، جزو تیم تحقیقاتی بوده. ایشان لیسانس ریاضی و دکتری علوم کامپیوتر خود را از دانشگاه برکلی دریافت کرده‌اند.

خود نیکولاس می‌گوید:

من در نقطه‌ی اشتراک مدل‌های یادگیری ماشین و مباحث امنیتی کار کرده‌ام و می‌کنم.

آقای نیکولاس پیپرنات نیز در حال حاضر دانشیار دانشگاه تورنتو هستند. ایشان نیز پس از فارغ‌التحصیلی از دانشگاه پنسیلوانیا، در دیپ‌مایند گوگل مشغول شده‌اند.

خلاصه اگر در این حوزه دنبال آدم خفن می‌گردید، اشخاصی که هم صنعت را تجربه کرده‌اند و هم از دل دانشگاه بیرون آمده‌اند، این دو نفر جزو بهترین‌ها هستند.

یکی از شاخه‌هایی که بزودی در دنیا خواهد ترکاند، همین
MLSecOps
هست. چون کدهایی که با وایب‌کدینگ تولید می‌شوند، هر روز با دقت کمتر وارد بازی می‌شن و بدون اینکه خودمون خبر داشته باشیم، کلی حفره در سرویس یا مدل‌مون باز می‌گذاریم.

#MLSecOps

🔹 Share & Support Us 🔹
📱 Channel : @Engineer_Computer
2🔥1👏1
EXPLORING THE DARK WEB.pdf
14.2 MB
🔹 Share & Support Us 🔹
📱 Channel : @Engineer_Computer
❤‍🔥11🔥1👏1
Network Security Channel
EXPLORING THE DARK WEB.pdf
🔘 Everyone talks about the "dark web." Almost no one understands it.

After working through "Exploring the Dark Web," here's what actually stood out:

🔹 ~94% of the web is never indexed by Google — but most of it is harmless (email, banking, databases).
🔹 Tor wasn't built by hackers. It began as a US Naval Research project to protect intelligence communications, and went public in 2002.
🔹 Anonymity is a discipline, not a download. Tor hides your route — not the data you type into a form.
🔹 ~60% of Tor traffic is fully legitimate: journalists, whistleblowers, researchers, people escaping censorship.
🔹 The recurring lesson from every major darknet takedown: anonymity ≠ immunity. The weakest link is almost always human.

The takeaway for defenders: you can't protect against a threat you refuse to understand. Dark web monitoring (OSINT) is now a core part of threat intelligence — leaked credentials and emerging threats often surface there first.

Curiosity is good. Caution is better. 🔒

What's the biggest misconception you still hear about the dark web?

#CyberSecurity #DarkWeb #OSINT #ThreatIntelligence #BlueTeam #InfoSec #Privacy

Share & Support Us 🔹
🔥 Channel : @Engineer_Computer
Please open Telegram to view this post
VIEW IN TELEGRAM
2🔥1👏1
Forwarded from DevScribe
📢 فرصت همکاری | Full Stack Developer (Python)

ما به دنبال جذب یک Full Stack Developer با تمرکز اصلی بر Python هستیم.

شرایط و مهارت‌های مورد نیاز:

• تسلط به Python و توسعه Backend
• آشنایی با طراحی و توسعه API
• تجربه کار با پایگاه داده‌های SQL و NoSQL
• آشنایی با JavaScript و حداقل یکی از فریم‌ورک‌های Frontend
• آشنایی با Git و فرآیندهای توسعه نرم‌افزار
• توانایی تحلیل، طراحی و پیاده‌سازی راهکارهای فنی

موارد زیر مزیت محسوب می‌شوند:

• تجربه کار با Docker و Containerization
• آشنایی با Linux
• تجربه کار با معماری Microservices
• آشنایی با مفاهیم Cloud و DevOps

ما به دنبال فردی مسئولیت‌پذیر، علاقه‌مند به یادگیری و توانمند در حل مسئله هستیم که بتواند در توسعه و بهبود یک محصول نرم‌افزاری مشارکت مؤثر داشته باشد.

📍 محل فعالیت: تهران

⚠️ پس از تأیید نهایی و شروع همکاری، حضور در محل کار الزامی خواهد بود.

📩 در صورت تمایل، رزومه خود را ارسال کنید.
@Re_security
2🔥1👏1
1779955060875.pdf
5.4 MB
🔘The AI security job market isn't coming. It's already here — and most career guides haven't caught up.

I went through the SANS 2026 AI Cybersecurity Careers report this week, and a few numbers stopped me cold:

→ 74% of cyber teams are restructuring because of AI
→ The skills gap now outweighs the headcount gap by 20 points (it was just 4 points a year ago)
→ AI/ML Security Engineers are earning $152K–$210K, with roughly 2,400 active listings right now

The report maps 10 roles across three tiers — the clearest signal I've seen of where this field is heading:

🟢 HIRING NOW — AI/ML Security Engineer, AI Red Team Specialist, AI GRC Lead, AI Threat Intel Analyst. 100+ live listings each. Search these titles today.

🟠 BUILDING — AI SOC Orchestrator, AI IR Orchestrator, AI Security Specialist, AI Supply Chain Engineer. Your current role is quietly turning into one of these.

🟣 HORIZON — AI Deepfake Defense Specialist, Post-Quantum Migration Specialist. Hiring ramps up in 2027–2028, so the time to build the skills is now.

The line that stuck with me: the window to establish yourself in AI security is 12–18 months.

For those of us already in SOC and blue-team work, this isn't a threat — it's the biggest opportunity in a decade. AI handles the pattern-matching; we bring the judgment, context, and defensive strategy that machines still can't.

Which of these roles are you positioning for?

#CyberSecurity #AISecurity #SOC #BlueTeam #InfoSec #CyberCareers

Share & Support Us 🔹
🔥 Channel : @Engineer_Computer
Please open Telegram to view this post
VIEW IN TELEGRAM
1🔥1👨‍💻1
NSE Train ing FortiNet 2026.pdf
3 MB
💎 Planning your cybersecurity certification roadmap for 2026?
The skills gap is real — and Fortinet's NSE program has now crossed 1.8M+ certifications issued worldwide.
Here's how the certification ladder is structured 👇
🔹 Fundamentals (NSE 1–2) — threat landscape + core concepts. A solid entry point whether your role is technical or not.
🔹 Associate / FCA (NSE 3) — hands-on FortiGate operation.
🔹 Professional / FCP (NSE 4–5) — deploy, manage & monitor across four tracks: Secure Networking, SASE, Cloud Security, and Security Operations. (NSE 4 is now the FortiOS Administrator exam.)
🔹 Solution Specialist / FCSS (NSE 6–7) — design & troubleshoot advanced solutions. The SecOps track (FortiSIEM + FortiSOAR) is gold for anyone building a SOC career.
🔹 Expert / FCX (NSE 8) — a written exam plus a 9-hour practical lab. The summit.
My takeaway: certifications don't replace experience, but a structured path keeps your learning intentional instead of scattered. If you're SOC-focused, the Security Operations tracks (FCP → FCSS) are the most direct route.
Which level are you targeting this year?

#CyberSecurity #Fortinet #NSE #BlueTeam #SOC #InfoSec #CareerDevelopment

Share & Support Us 🔹
🔥 Channel : @Engineer_Computer
Please open Telegram to view this post
VIEW IN TELEGRAM
1❤‍🔥1👍1
1780764206019.pdf
5.7 MB
🔘 Active Directory is the #1 target in most enterprise breaches.
Why? Because once an attacker lands a single foothold, AD becomes the highway to Domain Admin.
You can't defend what you don't understand — so here's the attacker's path through AD, and how Blue Teams shut it down 👇
🔸 Enumeration — attackers map users, groups & computers (LDAP/SID lookups) before doing anything loud.
🔸 Kerberos abuse — AS-REP Roasting (accounts with pre-auth disabled) and Kerberoasting (service accounts) let them crack weak passwords offline.
🔸 Delegation abuse — misconfigured RBCD can let a low-priv account impersonate the Domain Controller.
🔸 Credential dumping — DCSync mimics a DC to pull hashes; LAPS & gMSA misconfigs leak local/service passwords.
🔸 Persistence — Shadow Credentials inject a key into msDS-KeyCredentialLink to quietly re-authenticate as a target.
🛡 Defensive takeaways:
Enforce Kerberos pre-auth; use long service-account passwords (or gMSA).
Prefer constrained delegation over RBCD, and audit who can write it.
Monitor anomalous ticket requests (mass SPN queries, DCSync from non-DC hosts).
Deploy LAPS correctly and restrict read access.
Enable SMB signing to kill relay attacks.
The same TTPs that red teams use are what adversaries use — understanding them is what turns raw logs into real detections.
What's the first AD detection you'd build?

#ActiveDirectory #BlueTeam #SOC #ThreatDetection #Kerberos #DFIR #CyberSecurity #InfoSec

Share & Support Us 🔹
🔥 Channel : @Engineer_Computer
Please open Telegram to view this post
VIEW IN TELEGRAM
1👍1🔥1
1780652220817.pdf
1.1 MB
🔘Phishing is still the #1 initial access vector — year after year.
But strong phishing response isn't about heroics. It's about a repeatable, auditable process anyone on the team can execute under pressure.
Here's what a solid SOC phishing playbook actually looks like 👇
⏱️ Triage on the clock:
🔹 Intake (0–5 min) — log the report, pull the raw .eml, capture screenshots. Never forward it — that rewrites the headers.
🔹 Preserve (0–10 min) — extract attachments, compute SHA256, store read-only. Chain of custody from minute one.
🔹 Authenticate (0–15 min) — read Authentication-Results: SPF / DKIM / DMARC (and ARC for forwarded mail). Check the Received chain + WHOIS domain age.
🔹 Classify & escalate — Critical / High / Medium / Low, each with its own SLA.
🔐 The nuance most people miss: SPF=fail isn't always phishing (forwarding breaks it), and DKIM=pass doesn't mean "trusted" if the signing domain isn't your brand. Authentication is a signal, not a verdict — combine it with domain age, URL analysis & user behavior.
🧯 Containment by scenario:
Clicked only → block domain, quarantine similar mail, monitor 72h.
Credentials submitted → reset password, revoke tokens, force MFA re-enroll.
Malware executed → isolate host, image memory + disk, hunt for lateral movement.
📊 The metrics that matter: time-to-triage (<15 min) and time-to-contain for criticals (<2 hrs).
A playbook turns panic into procedure. Does your team have one documented?

#SOC #IncidentResponse #Phishing #BlueTeam #DFIR #DMARC #ThreatHunting #CyberSecurity

Share & Support Us 🔹
🔥 Channel : @Engineer_Computer
Please open Telegram to view this post
VIEW IN TELEGRAM
1👍1🔥1👏1