<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Forensics on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/forensics/</link>
    <description>Recent content in Forensics on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 12 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/forensics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ERNW White Paper 79: Integrating Incident Analysis and Digital Forensics Tooling for Automated Compromise Detection</title>
      <link>https://insinuator.net/2026/08/ernw-white-paper-79-integrating-incident-analysis-and-digital-forensics-tooling-for-automated-compromise-detection/</link>
      <pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/08/ernw-white-paper-79-integrating-incident-analysis-and-digital-forensics-tooling-for-automated-compromise-detection/</guid>
      <description>&lt;p&gt;With this blog post I am pleased to announce the publication of a new ERNW White Paper about our incident analysis and digital forensics framework. It is available on our &lt;a href=&#34;https://ernw.de/en/whitepapers/issue-79.html&#34;&gt;website&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Due to the increasing number and impact of computer security incidents, it has become essential to develop and implement efficient measures for their investigation. However, comprehensive forensic analyses are time-consuming, and this time is often not available to security analysts during computer security incidents. As a result, automated tools are increasingly being used. These tools, however, often cover only a limited scope of the necessary analyses and typically require deep technical expertise to be used effectively.&lt;/p&gt;</description>
    </item>
    <item>
      <title>TROOPERS26: Integrating Incident Analysis and Digital Forensics Tooling for Automated Compromise Detection</title>
      <link>https://insinuator.net/2026/06/troopers26-integrating-incident-analysis-and-digital-forensics-tooling-for-automated-compromise-detection/</link>
      <pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/06/troopers26-integrating-incident-analysis-and-digital-forensics-tooling-for-automated-compromise-detection/</guid>
      <description>&lt;p&gt;Last week I gave a talk at #TROOPERS26: &lt;a href=&#34;https://troopers.de/troopers26/talks/m7qtn7/&#34;&gt;Integrating Incident Analysis and Digital Forensics Tooling for Automated Compromise Detection&lt;/a&gt;. I discussed the challenges of incident analysis, such as increasing storage capacities and the lack of integration between tools. I presented a modular framework that integrates established forensic and analysis tools using a decision-tree-based control mechanism. A workflow was designed to control the execution of 14 integrated analysis tools in order to reproduce the manual analysis process usually performed by analysts. Moreover, the framework is capable of identifying whether a system has been compromised and compiles a analyst-oriented report. Together with the audience we took a look at the report in a live demonstration. The evaluation results of the framework were promising as it was able to identify all compromised systems. However, a significant number of false positive classifications were also observed. To improve the framework possible future extensions include functionality such as recovering already deleted files to detect missed Indicators of Compromise. Additionally, our team want to integrate artificial intelligence in the workflow to help in data processing and make more decisions automatically. The slides will be published next week on the conference website. I will add the link in this blog post when they become available. A more detailed description of the content of the talk can be found in the following sections. Looking forward to #TROOPERS27!&lt;/p&gt;</description>
    </item>
    <item>
      <title>Jigsaw RDPuzzle: Piecing Attacker Actions Together</title>
      <link>https://insinuator.net/2025/01/jigsaw-rdpuzzle-piecing-attacker-actions-together/</link>
      <pubDate>Wed, 29 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/01/jigsaw-rdpuzzle-piecing-attacker-actions-together/</guid>
      <description>&lt;p&gt;In a recent incident response project, we had the chance to virtually look over&#xA;the attackers’ shoulder and observe their activities. The attackers used the&#xA;Remote Desktop Protocol (RDP) for lateral movement within the compromized&#xA;environment and beyond (MITRE techniques&#xA;&lt;a href=&#34;https://attack.mitre.org/techniques/T1570/&#34;&gt;T1570&lt;/a&gt;,&#xA;&lt;a href=&#34;https://attack.mitre.org/techniques/T1021/001/&#34;&gt;T1021&lt;/a&gt;). As a matter of fact,&#xA;RDP creates cache files that contain tiles of the transferred screen recording&#xA;data. While this fact is well-known and there are existing tools, we found it&#xA;worth reporting because of two different aspects:&lt;/p&gt;</description>
    </item>
    <item>
      <title>BMBF UNCOVER – Monitoring von Sicherheitsvorfällen in Fahrzeugen</title>
      <link>https://insinuator.net/2024/06/bmbf-uncover-monitoring-von-sicherheitsvorf%C3%A4llen-in-fahrzeugen/</link>
      <pubDate>Fri, 21 Jun 2024 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2024/06/bmbf-uncover-monitoring-von-sicherheitsvorf%C3%A4llen-in-fahrzeugen/</guid>
      <description>&lt;h4 id=&#34;english-abstract&#34;&gt;English Abstract&lt;/h4&gt;&#xA;&lt;p&gt;For the realization and introduction of autonomous vehicles, the safe interaction of functions, systems and services as well as their monitoring over the entire product life cycle is essential. An exclusive security-by-design approach is no longer sufficient and must be continuously supported by feedback obtained from in-the-wild operation. This is where the recently successfully completed joint project BMBF UNCOVER comes into play, which targets the requirements of the standards &lt;em&gt;ISO/SAE 21434 (Road vehicles – Cybersecurity engineering)&lt;/em&gt; and &lt;em&gt;ISO 21448 (Road vehicles – Safety of the intended functionality (SOTIF))&lt;/em&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Identification of (malicious) modifications in memory-mapped image files</title>
      <link>https://insinuator.net/2023/09/identification-of-malicious-modifications-in-memory-mapped-image-files/</link>
      <pubDate>Wed, 06 Sep 2023 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2023/09/identification-of-malicious-modifications-in-memory-mapped-image-files/</guid>
      <description>&lt;p&gt;I’m happy to announce the publication of the paper&#xA;&lt;a href=&#34;https://dfrws.org/wp-content/uploads/2023/07/block-windowsmemoryforensics.pdf&#34;&gt;Windows memory forensics: Identification of (malicious) modifications in memory-mapped image files&lt;/a&gt;&#xA;at this years DFRWS USA, and the release of the corresponding&#xA;&lt;a href=&#34;https://github.com/f-block/volatility-plugins#imgmalfind&#34;&gt;volatility plugin&lt;/a&gt;.&#xA;With this research came also an update to the Ptenum family (affecting&#xA;especially the &lt;code&gt;ptemalfind&lt;/code&gt; plugin), which makes the plugins reliable in&#xA;identifying modified pages despite memory combining, so make sure to grab the&#xA;newest version from the Github repository.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IMF Conference 2023 in Munich</title>
      <link>https://insinuator.net/2023/05/imf-conference-2023-in-munich/</link>
      <pubDate>Thu, 25 May 2023 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2023/05/imf-conference-2023-in-munich/</guid>
      <description>&lt;p&gt;The IMF Conference is the &lt;em&gt;International Conference on IT Security Incident&#xA;Management &amp;amp; IT Forensics&lt;/em&gt;. This year it took place from May 23 to 24 in Munich.&#xA;The schedule lists&#xA;&lt;a href=&#34;https://imf-conference.org/imf2023/program.html&#34;&gt;a lot of interesting talks&lt;/a&gt;.&#xA;One of the talks was my presentation on a paper about Ceph forensics, based on&#xA;my Master Thesis:&lt;/p&gt;&#xA;&lt;p&gt;The concept of Software Defined Storage (SDS) has become very popular over the&#xA;last few years.  It is used in public, private, and hybrid clouds to store&#xA;enterprise, private, and other kinds of data. &lt;a href=&#34;https://ceph.io/&#34;&gt;Ceph&lt;/a&gt; is an&#xA;open-source software that implements an SDS stack.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Release of PTE Analysis plugins for Volatility 3</title>
      <link>https://insinuator.net/2021/12/release-of-pte-analysis-plugins-for-volatility-3/</link>
      <pubDate>Fri, 31 Dec 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/12/release-of-pte-analysis-plugins-for-volatility-3/</guid>
      <description>&lt;p&gt;I’m happy to announce the&#xA;&lt;a href=&#34;https://github.com/f-block/volatility-plugins&#34;&gt;release&lt;/a&gt; of several plugins for&#xA;Volatility 3 that allow you to dig deeper into the memory analysis. One of those&#xA;plugins is &lt;code&gt;PteMalfind&lt;/code&gt;, which is essentially an improved version of &lt;code&gt;malfind&lt;/code&gt;.&#xA;Another one is &lt;code&gt;PteResolve&lt;/code&gt; which, similarly to the WinDBG command &lt;code&gt;!pte&lt;/code&gt;,&#xA;allows you to inspect Page Table Entry (PTE) information for e.g., a given&#xA;virtual address. In this blog post we will have a closer look at these and more&#xA;plugins, and the &lt;code&gt;PteEnumerator&lt;/code&gt; base class and what you can do with it. The&#xA;memory dump used for this blog post is available&#xA;&lt;a href=&#34;https://ernw.de/download/blogposts/pte_analysis/mem.dump.zip&#34;&gt;here&lt;/a&gt;. Some of&#xA;the injection tools used in this blog post can be gathered from&#xA;&lt;a href=&#34;https://github.com/f-block/DFRWS-USA-2019/tree/master/tools&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Analysis of HSTS Caches of Different Browsers</title>
      <link>https://insinuator.net/2021/05/analysis-of-hsts-caches-of-different-browsers/</link>
      <pubDate>Thu, 06 May 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/05/analysis-of-hsts-caches-of-different-browsers/</guid>
      <description>&lt;p&gt;I recently stumbled upon a strange behavior in my Firefox: I visited an&#xA;HTTPS-enabled website that I had visited before and saw that my Firefox&#xA;connected insecurely via HTTP. I found that strange because nowadays, most&#xA;websites set the&#xA;&lt;a href=&#34;https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security&#34;&gt;HSTS&lt;/a&gt;&#xA;header, which is supposed to force the browser to connect via HTTPS. I checked&#xA;whether this website set the HSTS header – and it did. This means my Firefox was&#xA;ignoring/forgetting about the HSTS header right after my visit.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ERNW Whitepaper 71: Analysis of Anti-Virus Software Quarantine Files</title>
      <link>https://insinuator.net/2021/01/ernw-whitepaper-71-analysis-of-anti-virus-software-quarantine-files/</link>
      <pubDate>Wed, 27 Jan 2021 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2021/01/ernw-whitepaper-71-analysis-of-anti-virus-software-quarantine-files/</guid>
      <description>&lt;p&gt;I am glad to announce the release of the ERNW whitepaper 71 containing&#xA;information about quarantine file formats of different AV software vendors. It&#xA;is available&#xA;&lt;a href=&#34;https://static.ernw.de/whitepaper/ERNW-Whitepaper-71_AV_Quarantine_signed.pdf&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;h2 id=&#34;anti-virus-software&#34;&gt;Anti-Virus Software&lt;/h2&gt;&#xA;&lt;p&gt;I took quarantine files from real-life incidents and created some in a lab&#xA;environment. Afterwards I tried to identify metadata, like timestamps, path&#xA;names, malware names, and the actual malicious file in the quarantine files. One&#xA;goal was to use this information to support our incident analyses: Using the&#xA;results, we can now easily create timelines showing information about&#xA;quarantined files, extract the detected malware, and sometimes even find&#xA;information about processes that created the malicious files.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How can data from fitness trackers be obtained and analyzed with a forensic approach?</title>
      <link>https://insinuator.net/2020/09/how-can-data-from-fitness-trackers-be-obtained-and-analyzed-with-a-forensic-approach/</link>
      <pubDate>Thu, 10 Sep 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/09/how-can-data-from-fitness-trackers-be-obtained-and-analyzed-with-a-forensic-approach/</guid>
      <description>&lt;p&gt;The use of Internet of Things devices is continuously increasing: People buy devices, such as smart assistants, to make their lives more comfortable or fitness trackers to assess sports activities. According to the Pew Research Center [1], every fifth American wears a device to track their fitness. In Germany, the number increases likewise. The increasing number of fitness trackers in use can also be seen in criminal proceedings, as there exist more and more cases where these devices provide evidence.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dissection of an Incident – Part 2</title>
      <link>https://insinuator.net/2019/10/dissection-of-an-incident-part-2/</link>
      <pubDate>Wed, 30 Oct 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/10/dissection-of-an-incident-part-2/</guid>
      <description>&lt;p&gt;After our &lt;a href=&#34;https://insinuator.net/2019/07/emotet-at-heise-emotet-there-emotet-everywhere-dissection-of-an-incident/&#34;&gt;last blogpost&lt;/a&gt; regarding Emotet and several other Emotet and Ransomware samples that we encountered, we recently stumbled across a variant belonging to the &lt;em&gt;Gozi&lt;/em&gt;, &lt;em&gt;ISFB&lt;/em&gt;, &lt;em&gt;Dreambot&lt;/em&gt; respectively &lt;em&gt;Ursnif&lt;/em&gt; family. In this blogpost, we want to share our insights from the analysis of this malware, whose malware family is mainly known for being a banking trojan that typically tries to infect browser sessions and sniff/redirect data. In particular, we are going to provide details about the first stage Word Document, the embedded JavaScript/XSL document, an in-depth runtime analysis of the downloaded executable, and some details regarding detection.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Comparison of our tool afro (APFS file recovery) with Blackbag Blacklight and Sleuthkit</title>
      <link>https://insinuator.net/2018/10/comparison-of-our-tool-afro-apfs-file-recovery-with-blackbag-blacklight-and-sleuthkit/</link>
      <pubDate>Thu, 18 Oct 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/10/comparison-of-our-tool-afro-apfs-file-recovery-with-blackbag-blacklight-and-sleuthkit/</guid>
      <description>&lt;p&gt;At this years ARES conference, Jonas Plum (Siemens) and me (Andreas Dewald, ERNW Research GmbH) published a &lt;a href=&#34;https://dl.acm.org/citation.cfm?id=3232808&#34;&gt;paper&lt;/a&gt; about the forensic analysis of APFS, file system internals and presented different methodologies for file recovery. We also publicly released a tool implementing our presented approaches, called &lt;a href=&#34;https://github.com/cugu/afro&#34;&gt;afro&lt;/a&gt; (APFS file recovery).&lt;/p&gt;&#xA;&lt;p&gt;APFS is the file system for Apple devices that is used by default on all current iOS mobile devices, as well as macOS since High Sierra, and is thus currently rolled out on a large number of devices. By using afro, we evaluated and compared the different approaches amongst each other and identified the method that so far delivers the best results and compared it to photorec. This showed that AFRO outperforms photorec on the evaluated APFS dataset. In the presentations of this research we were often asked if other tools like Blackbags Blacklight do not already support this recovery process. So, we decided to compare the file recovery capabilities of BlackLight and afro. We wanted to compare afro to the sleuth kit as well, as at the DFRWS conference it was discussed about &lt;a href=&#34;https://www.dfrws.org/sites/default/files/session-files/pres_adding_apfs_support_to_the_sleuthkit_framework.pdf&#34;&gt;adding APFS Support to The Sleuthkit Framework&lt;/a&gt;, but no implementations are public yet.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Incident Analysis and Digital Forensics Summit 2018, 14th of November of 2018</title>
      <link>https://insinuator.net/2018/10/incident-analysis-and-digital-forensics-summit-2018-14th-of-november-of-2018/</link>
      <pubDate>Mon, 08 Oct 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/10/incident-analysis-and-digital-forensics-summit-2018-14th-of-november-of-2018/</guid>
      <description>&lt;p&gt;*This event will be held in German*&lt;/p&gt;&#xA;&lt;p&gt;Inspiriert durch die erfolgreichen Round-Table-Diskussionen der Troopers-Konferenz freuen wir uns, Ihnen heute mit dem Incident Analysis and Digital Forensics Summit 2018, eine weitere Veranstaltung in einer Reihe zu Trend-Themen im Bereich der IT-Sicherheit vorzustellen.&lt;/p&gt;&#xA;&lt;p&gt;Die Veranstaltung beginnt am Morgen mit einem Eröffnungsvortrag von Thomas Schreck (Chairman of the Board des internationalen CERT Verbunds FIRST), gefolgt von Fallstudien und Vorträgen durch weitere Referenten aus der Industrie und Strafverfolgung.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New Release of Glibc Heap Analysis Plugins</title>
      <link>https://insinuator.net/2018/06/new-release-of-glibc-heap-analysis-plugins/</link>
      <pubDate>Wed, 06 Jun 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/06/new-release-of-glibc-heap-analysis-plugins/</guid>
      <description>&lt;p&gt;After quite some time and work, I’m happy to announce the new release of the &lt;a href=&#34;https://github.com/google/rekall/blob/master/rekall-core/rekall/plugins/linux/heap_analysis.py&#34;&gt;Linux&lt;/a&gt; &lt;a href=&#34;https://github.com/google/rekall/blob/master/rekall-core/rekall/plugins/linux/keepassx.py&#34;&gt;Heap&lt;/a&gt; &lt;a href=&#34;https://github.com/google/rekall/blob/master/rekall-core/rekall/plugins/linux/zsh.py&#34;&gt;Analysis&lt;/a&gt; Plugins, which are now part of the &lt;a href=&#34;https://github.com/google/rekall&#34;&gt;Rekall&lt;/a&gt; project, but not yet part of an official Rekall release, so you have to grab them manually.&lt;br&gt;&#xA;This release fixes several bugs and adds the following features:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Support for Glibc version 2.26 (tcache chunks) and 2.27&lt;/li&gt;&#xA;&lt;li&gt;Heapsearch now includes Rekall’s yara scan functionality&lt;/li&gt;&#xA;&lt;li&gt;x86 Glibc versions with a modified MALLOC_ALIGNMENT value of 16 (as done in arch’s glibc package 2.26) are now supported&lt;/li&gt;&#xA;&lt;li&gt;Improved retrieval of main_arena and new automated retrieval of malloc_par struct; so for the majority of cases, the corresponding cmd line options are not necessary anymore and hence no debug information have to be retrieved.&lt;/li&gt;&#xA;&lt;li&gt;main_arena and malloc_par struct retrieval now also applies for statically linked binaries; there might however be cases, where it is necessary to specify the malloc_par struct offset and the used glibc version number&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;While Glibc version 2.27 does not really change much for the heap from a forensics point of view, version 2.26 introduced a new feature called tcache (per thread cache). Those caches are essentially just a new type of bin, holding freed chunks, but &lt;a href=&#34;https://sourceware.org/ml/libc-alpha/2017-01/msg00452.html&#34;&gt;seem to improve the performance&lt;/a&gt;.&lt;br&gt;&#xA;Sadly, only two days after its &lt;a href=&#34;https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=d5c3fafc4307c9b7a4c7d5cb381fcdbfad340bcc&#34;&gt;first commit&lt;/a&gt;, there was already a &lt;a href=&#34;http://tukan.farm/2017/07/08/tcache/&#34;&gt;blog post&lt;/a&gt; explaining the functionality (not so sad 😉 ) and also some discovered vulnerabilities (here we go with the sad part).&lt;br&gt;&#xA;Besides introducing a new landscape for attackers, this feature added two new heap management structs and one additional chunk per thread-heap (each thread has its own heap, up until an upper limit). This chunk is located at the beginning of each heap and hence, part of a raw heap dump (so be aware of that, if you are doing a raw analysis without the plugins).&lt;br&gt;&#xA;The chunk holds the content of the &lt;code&gt;tcache_perthread_struct&lt;/code&gt;, which has to members:&lt;/p&gt;</description>
    </item>
    <item>
      <title>DFRWS USA 2017</title>
      <link>https://insinuator.net/2017/09/dfrws-usa-2017/</link>
      <pubDate>Wed, 06 Sep 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/09/dfrws-usa-2017/</guid>
      <description>&lt;p&gt;As mentioned in my last &lt;a href=&#34;https://insinuator.net/2017/07/release-of-glibc-heap-analysis-plugins-for-rekall/&#34;&gt;blogpost&lt;/a&gt;, I had the pleasure to participate in this years DFRWS USA and present our paper. The paper and presentation can be freely viewed and downloaded &lt;a href=&#34;https://www.dfrws.org/conferences/dfrws-usa-2017/sessions/linux-memory-forensics-dissecting-user-space-process-heap&#34;&gt;here&lt;/a&gt; or &lt;a href=&#34;https://authors.elsevier.com/sd/article/S1742287617301895&#34;&gt;here&lt;/a&gt;. Note that there is also an extended version of the paper, which can be downloaded &lt;a href=&#34;https://opus4.kobv.de/opus4-fau/frontdoor/index/index/docId/8340&#34;&gt;here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;The keepassx, zsh and heap analysis plugins are now also part of the &lt;a href=&#34;https://github.com/google/rekall/releases/tag/v1.7.0rc1&#34;&gt;Rekall release candidate 1.7.0RC1&lt;/a&gt;, so it’s easier to get started.&lt;/p&gt;&#xA;&lt;p&gt;The conference had some great talks and workshops, which I’m going to briefly sum up.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Release of Glibc Heap Analysis Plugins for Rekall</title>
      <link>https://insinuator.net/2017/07/release-of-glibc-heap-analysis-plugins-for-rekall/</link>
      <pubDate>Thu, 13 Jul 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/07/release-of-glibc-heap-analysis-plugins-for-rekall/</guid>
      <description>&lt;p&gt;I’m happy to announce the release of several Glibc heap analysis plugins (for Linux), resp. plugins to gather information from keepassx and zsh, which are now included in the &lt;a href=&#34;https://github.com/google/rekall&#34;&gt;Rekall Memory Forensic Framework&lt;/a&gt;. This blogpost will demonstrate these plugins and explain how they can be used. More detailed information, including real world scenarios, will be released after the &lt;a href=&#34;https://dfrws.org/conferences/dfrws-usa-2017/sessions/linux-memory-forensics-dissecting-user-space-process-heap&#34;&gt;talk&lt;/a&gt; at this years &lt;a href=&#34;https://dfrws.org/conferences/dfrws-usa-2017&#34;&gt;DFRWS USA&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Before being able to reliably analyze the heap of a process, a profile, for the Glibc version being used, must be provided. However, this step should for most cases be fairly simple and only consist of gathering the offset for the &lt;em&gt;mp_&lt;/em&gt; and &lt;em&gt;main_arena&lt;/em&gt; variables:&lt;/p&gt;</description>
    </item>
    <item>
      <title>First dedicated Forensic Computing Training at TR17</title>
      <link>https://insinuator.net/2017/01/first-dedicated-forensic-computing-training-at-tr17/</link>
      <pubDate>Wed, 11 Jan 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/01/first-dedicated-forensic-computing-training-at-tr17/</guid>
      <description>&lt;p&gt;I am looking forward to our newly introduced dedicated Forensic Computing Training at TR17!&lt;br&gt;&#xA;We will start the first day with a detailed background briefing about Forensic Computing as a Forensic Science, Digital Evidence, and the Chain of Custody. The rest of the workshop we will follow the Order of Volatility starting with the analysis of persistent storage using file system internals and carving, as well as RAID reassembly with lots of hands-on case studies using open source tools. As a next step, we will smell the smoking gun in live forensics exercises. Depending on your preferences we will then dig a bit into memory forensics and network forensics.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New Ransomware-Wave Analysis</title>
      <link>https://insinuator.net/2016/07/new-ransomware-wave-analysis/</link>
      <pubDate>Thu, 28 Jul 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/07/new-ransomware-wave-analysis/</guid>
      <description>&lt;p&gt;In the context of a customer project, we examined a new variant of the Locky ransomware. As in the meantime stated by a law enforcement agency, this has been part of a large wave of attacks hitting various enterprises in the night from Tuesday (2016-07-26) to Wednesday.&lt;/p&gt;&#xA;&lt;p&gt;As an initial attack vector, the attackers use emails with an attachment that probably even uses a 0day exploit, that enables the payload to be executed already when displayed in the MS Outlook preview.&lt;/p&gt;</description>
    </item>
    <item>
      <title>DFRWS EU 2016 Summary</title>
      <link>https://insinuator.net/2016/03/dfrws-eu-2016-summary/</link>
      <pubDate>Thu, 31 Mar 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/03/dfrws-eu-2016-summary/</guid>
      <description>&lt;p&gt;In this article, I want to provide a concise sum-up of the (to me) most interesting talks of this year’s DFRWS EU (&lt;a href=&#34;http://www.dfrws.org/2016eu/&#34;&gt;http://www.dfrws.org/2016eu/&lt;/a&gt;).&lt;/p&gt;&#xA;&lt;p&gt;Eoghan Casey, one of most famous pioneers in digital forensics, and David-Olivier Jaquet-Chiffelle, professor in police science at University of Lausanne, gave a keynote that emphasized the need for theoretical fundamental basis research in the field of digital forensics, which I fully agreed on, as this was exactly what I addressed in some of my former research.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Generic RAID Reassembly using Block-Level Entropy</title>
      <link>https://insinuator.net/2016/03/generic-raid-reassembly-using-block-level-entropy/</link>
      <pubDate>Wed, 30 Mar 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/03/generic-raid-reassembly-using-block-level-entropy/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://www.insinuator.net/wp-content/uploads/2016/03/FullSizeRender-209x300.jpg&#34; alt=&#34;DFRWS EU 2016 Talk Forensic Raid Recovery&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;DFRWS EU 2016 Talk Forensic Raid Recovery&lt;/p&gt;&#xA;&lt;p&gt;We just presented our Paper “&lt;em&gt;Generic RAID Reassembly using Block-Level Entropy&lt;/em&gt;” at the &lt;em&gt;DFRWS EU 2016&lt;/em&gt; digital forensics conference (&lt;a href=&#34;http://www.dfrws.org/&#34;&gt;http://www.dfrws.org/&lt;/a&gt;). The article is about a new approach that we developed for forensic RAID recovery. Our technique calculates block-wise entropy all over the disks and uses generic heuristics on those to detect all the relevant RAID parameters such as stripe size, stripe map, disk order, and RAID type, that are needed to reassemble the RAID and make the data accessible again for forensic investigations (or just for data recovery).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
