<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GRC on IRRGANG.DEV</title>
    <link>https://www.irrgang.dev/tags/grc/</link>
    <description>Recent content in GRC on IRRGANG.DEV</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-US</language>
    <copyright>© 2026 Dennis Irrgang · [Legal notice](/legal-notice/) · [Privacy](/privacy-policy/)</copyright>
    <lastBuildDate>Fri, 11 Jul 2025 18:38:23 +0000</lastBuildDate><atom:link href="https://www.irrgang.dev/tags/grc/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Information security is not an IT issue – it is a corporate responsibility</title>
      <link>https://www.irrgang.dev/information-security-is-not-an-it-issue/</link>
      <pubDate>Fri, 11 Jul 2025 18:38:23 +0000</pubDate>
      
      <guid>https://www.irrgang.dev/information-security-is-not-an-it-issue/</guid>
      <description>&lt;h2 class=&#34;relative group&#34;&gt;A call after the worst-case scenario&#xA;    &lt;div id=&#34;a-call-after-the-worst-case-scenario&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#a-call-after-the-worst-case-scenario&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h2&gt;&#xA;&lt;p&gt;A company calls. Ransomware. Production has come to a standstill. The first question: &lt;em&gt;“How could this happen?”&lt;/em&gt; A better question would have been: &lt;em&gt;“Why didn’t we do anything about it before?”&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Many companies still treat information security as a chore – something you do because you have to. It is regrettable that regulatory pressure is often needed to make this happen, but given human weaknesses in dealing with statistics and risk, it is hardly surprising.&lt;/p&gt;</description>
      
    </item>
    
    <item>
      <title>My CISSP Experience</title>
      <link>https://www.irrgang.dev/my-cissp-experience/</link>
      <pubDate>Mon, 09 Jun 2025 17:36:18 +0000</pubDate>
      
      <guid>https://www.irrgang.dev/my-cissp-experience/</guid>
      <description>&lt;h2 class=&#34;relative group&#34;&gt;Preparation&#xA;    &lt;div id=&#34;preparation&#34; class=&#34;anchor&#34;&gt;&lt;/div&gt;&#xA;    &#xA;    &lt;span&#xA;        class=&#34;absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none&#34;&gt;&#xA;        &lt;a class=&#34;text-primary-300 dark:text-neutral-700 !no-underline&#34; href=&#34;#preparation&#34; aria-label=&#34;Anchor&#34;&gt;#&lt;/a&gt;&#xA;    &lt;/span&gt;&#xA;    &#xA;&lt;/h2&gt;&#xA;&lt;p&gt;I started preparing in January and took the exam in mid-March. So it took me about two months in total, with a few interruptions. I spent about an hour a day during the week and two hours at weekends. Some weeks I did nothing at all – but I didn’t let that stress me out.&lt;/p&gt;&#xA;&lt;p&gt;My technical background allowed me to repeat familiar content instead of starting from scratch. Nevertheless, the exam was no walk in the park. It was crucial that I identified my weaknesses early on and worked on them systematically. I focussed on continuity rather than perfectionism – it was okay to skip a chapter from time to time.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
