69 lines
6.2 KiB
XML
69 lines
6.2 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||
<channel>
|
||
<title>Cybersecurity on Joren's Site</title>
|
||
<link>http://localhost:1313/categories/cybersecurity/</link>
|
||
<description>Recent content in Cybersecurity on Joren's Site</description>
|
||
<generator>Hugo</generator>
|
||
<language>en</language>
|
||
<lastBuildDate>Fri, 30 May 2025 00:00:00 +0000</lastBuildDate>
|
||
<atom:link href="http://localhost:1313/categories/cybersecurity/index.xml" rel="self" type="application/rss+xml" />
|
||
<item>
|
||
<title>Kerberos Under Siege: Abusing the Trust Backbone of Windows Domains</title>
|
||
<link>http://localhost:1313/blog/post-7/</link>
|
||
<pubDate>Fri, 30 May 2025 00:00:00 +0000</pubDate>
|
||
<guid>http://localhost:1313/blog/post-7/</guid>
|
||
<description><p>Kerberos, introduced to Windows with Active Directory in 2000, is widely seen as a secure, modern replacement for NTLM. And yet, in the hands of an attacker, it becomes a double-edged sword. This post explores how Kerberos works, and how it can be abused through techniques like <strong>Kerberoasting</strong>, <strong>delegation abuse</strong>, and <strong>ticket impersonation</strong>.</p></description>
|
||
</item>
|
||
<item>
|
||
<title>Matrix: Building a Decentralized Communication Future</title>
|
||
<link>http://localhost:1313/blog/post-6/</link>
|
||
<pubDate>Fri, 30 May 2025 00:00:00 +0000</pubDate>
|
||
<guid>http://localhost:1313/blog/post-6/</guid>
|
||
<description><p>If you’ve ever switched between Slack, WhatsApp, Discord, Teams, Signal and Telegram in a single day, you’ve felt the cost of digital fragmentation. We live in a world where communication is siloed into centralized apps, each with its own rules, limits and vulnerabilities. Matrix proposes an alternative: a universal, open, decentralized protocol for real-time communication, where users control their data and messaging isn&rsquo;t trapped in walled gardens.</p></description>
|
||
</item>
|
||
<item>
|
||
<title>Silent Interception: Exploiting LLMNR, NBT-NS, mDNS and IPv6 in Modern Networks</title>
|
||
<link>http://localhost:1313/blog/post-5/</link>
|
||
<pubDate>Fri, 30 May 2025 00:00:00 +0000</pubDate>
|
||
<guid>http://localhost:1313/blog/post-5/</guid>
|
||
<description><p>In many internal networks, outdated or misconfigured protocols silently create attack surfaces. This post explores how attackers abuse name resolution fallbacks and IPv6 autoconfiguration to capture and relay NTLM credentials using <code>Responder</code> and <code>mitm6</code>.</p></description>
|
||
</item>
|
||
<item>
|
||
<title>The Smart Home Trap: Isolate or Be Owned</title>
|
||
<link>http://localhost:1313/blog/post-10/</link>
|
||
<pubDate>Fri, 30 May 2025 00:00:00 +0000</pubDate>
|
||
<guid>http://localhost:1313/blog/post-10/</guid>
|
||
<description><h1 id="the-smart-home-trap-isolate-or-be-owned">The Smart Home Trap: Isolate or Be Owned</h1>
<p>Smart homes are convenient. But with convenience comes risk. If your doorbell runs Linux, talks to Chinese cloud servers, and sits on the same network as your work laptop, you&rsquo;ve got a problem. The fix? Segmentation. This post explores how to use VLANs and firewall rules to quarantine IoT devices and minimize lateral movement, even on a home budget.</p></description>
|
||
</item>
|
||
<item>
|
||
<title>Red Team Talk: Een Blik Achter de Schermen bij Offensive Security</title>
|
||
<link>http://localhost:1313/blog/post-4/</link>
|
||
<pubDate>Tue, 20 May 2025 00:00:00 +0000</pubDate>
|
||
<guid>http://localhost:1313/blog/post-4/</guid>
|
||
<description><p>In Red Team Talk nemen wij, Joren Schipman en Mattia Punjwani, studenten Cybersecurity aan Howest, jullie mee in een gesprek met <strong>Thomas Castronovo</strong>, ethical hacker en consultant bij Deloitte. Samen duiken we in de wereld van offensieve security, red teaming, en de realiteit van een carrière als pentester.</p></description>
|
||
</item>
|
||
<item>
|
||
<title>Cyber Defence on the Digital Frontline: A Mission with NATO</title>
|
||
<link>http://localhost:1313/blog/post-1/</link>
|
||
<pubDate>Tue, 13 May 2025 00:00:00 +0000</pubDate>
|
||
<guid>http://localhost:1313/blog/post-1/</guid>
|
||
<description><h4 id="on-a-mission-with-nato-cyber-defence-on-the-frontline">On a Mission with NATO: Cyber Defence on the Frontline</h4>
<p>Howest’s ongoing commitment to world-class cybersecurity training took center stage again as six lecturers from the Cyber Security program joined forces with experts from Latvia, Luxembourg and Belgium in one of NATO&rsquo;s most intensive simulations: the Locked Shields exercise, hosted by the Cooperative Cyber Defence Centre of Excellence (CCDCOE). Now in its fifth year of participation, the Howest team shared their firsthand experiences at a special evening talk at Howest Bruges.</p></description>
|
||
</item>
|
||
<item>
|
||
<title>Reversing, Rebuilding, and Failing Better: My Cyber Security Challenge Belgium Qualifier Experience</title>
|
||
<link>http://localhost:1313/blog/post-2/</link>
|
||
<pubDate>Sat, 15 Mar 2025 00:00:00 +0000</pubDate>
|
||
<guid>http://localhost:1313/blog/post-2/</guid>
|
||
<description><p>On March 14 and 15, I joined the Cyber Security Challenge Belgium qualifiers with three teammates. For two days, we threw ourselves at CTF challenges covering binary exploitation, Android reversing, cryptography, and more.</p></description>
|
||
</item>
|
||
<item>
|
||
<title>Securing Cyberspace: Belgian Cyber Command at Howest</title>
|
||
<link>http://localhost:1313/blog/post-3/</link>
|
||
<pubDate>Tue, 12 Nov 2024 00:00:00 +0000</pubDate>
|
||
<guid>http://localhost:1313/blog/post-3/</guid>
|
||
<description><p>On November 12, we had the opportunity to attend a Tech&amp;Meet session unlike any other. The speaker was <strong>Colonel Gunther Godefridis</strong>, Director for Development &amp; Readiness at Belgian Cyber Command, and the topic: safeguarding our country in the digital domain.</p></description>
|
||
</item>
|
||
</channel>
|
||
</rss>
|