<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blog | Muhammad Koprawi</title>
    <link>https://example.com/post/</link>
      <atom:link href="https://example.com/post/index.xml" rel="self" type="application/rss+xml" />
    <description>Blog</description>
    <generator>Wowchemy (https://wowchemy.com)</generator><language>en-us</language><copyright>© 2026 Muhammad Koprawi</copyright>
    <image>
      <url>https://example.com/media/icon_hua2ec155b4296a9c9791d015323e16eb5_11927_512x512_fill_lanczos_center_3.png</url>
      <title>Blog</title>
      <link>https://example.com/post/</link>
    </image>
    
    <item>
      <title>Designing a Practical Cybersecurity Lab</title>
      <link>https://example.com/post/security-lab-setup/</link>
      <pubDate>Thu, 15 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://example.com/post/security-lab-setup/</guid>
      <description>&lt;p&gt;A useful cybersecurity lab should be realistic enough to make students think, but structured enough that instructors can reproduce the exercise, assess the outcome, and reset the environment quickly.&lt;/p&gt;
&lt;p&gt;The most effective labs I have run include three ingredients: a clear operational goal, observable evidence, and a written reflection. Students should know what system they are defending or investigating, what data they can trust, and how they will communicate findings.&lt;/p&gt;
&lt;p&gt;For security education, realism is not the same as complexity. A small, well-instrumented environment often teaches better judgment than a large environment that no one can explain.&lt;/p&gt;
</description>
    </item>
    
  </channel>
</rss>
