<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Heise on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/heise/</link>
    <description>Recent content in Heise on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 09 Aug 2019 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/heise/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Follow-Up on the Heisec Webinar on Emotet &amp;amp; Some Active Directory Security Sources</title>
      <link>https://insinuator.net/2019/08/a-follow-up-on-the-heisec-webinar-on-emotet-amp-some-active-directory-security-sources/</link>
      <pubDate>Fri, 09 Aug 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/08/a-follow-up-on-the-heisec-webinar-on-emotet-amp-some-active-directory-security-sources/</guid>
      <description>&lt;p&gt;Some weeks ago, Heinrich and I had the pleasure to participate in the heisec-Webinar &lt;a href=&#34;https://www.heise.de/security/meldung/heisec-Webinar-Emotet-bei-Heise-Lernen-aus-unseren-Fehlern-4439874.html&#34;&gt;“Emotet bei Heise – Lernen aus unseren Fehlern”&lt;/a&gt;. We really enjoyed the webinar and the (alas, due to the format: too short) discussions and we hope we could contribute to understand how to make Active Directory implementations out there a bit safer in the future.&lt;/p&gt;&#xA;&lt;p&gt;Now, I have the pleasure to announce a continuation of our talk about Active Directory security next week, Wednesday, 14^(th) of August @heisec in the format of a technical talk &lt;a href=&#34;https://www.heise-events.de/webinare/emotet_cybercrime&#34;&gt;“Emotet bei Heise – Online-Fachgespräch zum Schutz vor Cybercrime”&lt;/a&gt;. Seats are still available 😉&lt;/p&gt;</description>
    </item>
    <item>
      <title>Emotet at Heise, Emotet there, Emotet everywhere – Dissection of an Incident</title>
      <link>https://insinuator.net/2019/07/emotet-at-heise-emotet-there-emotet-everywhere-dissection-of-an-incident/</link>
      <pubDate>Thu, 18 Jul 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/07/emotet-at-heise-emotet-there-emotet-everywhere-dissection-of-an-incident/</guid>
      <description>&lt;p&gt;After the &lt;a href=&#34;https://www.heise.de/ct/artikel/Emotet-bei-Heise-4437807.html&#34;&gt;Emotet Incident at Heise&lt;/a&gt;, where &lt;a href=&#34;https://www.heise.de/security/meldung/heisec-Webinar-Emotet-bei-Heise-Lernen-aus-unseren-Fehlern-4439874.html&#34;&gt;ERNW has been consulted for Incident Response&lt;/a&gt;, we decided to start a blogpost series, in which we want to regularly report on current attacks that we observe. In particular we want to provide details about the utilized pieces of malware, different stages, and techniques used for the initial infection and lateral movement. We hope that this information might help you to detect ongoing incidents, apply countermeasures, and in the best case to figure out proactive countermeasures and security controls beforehand.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
