<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Windows on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/windows/</link>
    <description>Recent content in Windows on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 16 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/windows/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Windows Hello for Business – Full Report Has Been Released</title>
      <link>https://insinuator.net/2026/07/windows-hello-for-business-full-report-has-been-released/</link>
      <pubDate>Thu, 16 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/07/windows-hello-for-business-full-report-has-been-released/</guid>
      <description>&lt;p&gt;Yesterday, the BSI (the German Federal Office for Information Security, or Bundesamt für Sicherheit in der Informationstechnik in German) published the first result document from the “Windows dissected” (ger.: “Windows seziert”) project: our analysis of Windows Hello for Business (WHfB). If you have followed this blog over the past year, you have seen the pieces. The full 170-page report has now been published. And it can be downloaded from the &lt;a href=&#34;https://www.bsi.bund.de/DE/Service-Navi/Publikationen/Studien/Windows-seziert/windows-seziert_node.html&#34;&gt;project page&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Early Boot Configuration: The CmControlVector and PspSystemMitigationOptions</title>
      <link>https://insinuator.net/2026/04/windows-early-boot-configuration-the-cmcontrolvector-and-pspsystemmitigationoptions/</link>
      <pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/04/windows-early-boot-configuration-the-cmcontrolvector-and-pspsystemmitigationoptions/</guid>
      <description>&lt;p&gt;While investigating how process mitigation settings are initialized, I&#xA;encountered the global variable &lt;code&gt;PspSystemMitigationOptions&lt;/code&gt;. Tracing how this&#xA;value is populated led me to the &lt;code&gt;CmControlVector&lt;/code&gt;. In this blog post, we take a&#xA;look at the Windows kernel land configuration manager, especially its global&#xA;&lt;code&gt;CmControlVector&lt;/code&gt; variable. Quick note: the kernel’s configuration manager is&#xA;not related to Microsoft Intune’s&#xA;&lt;a href=&#34;https://learn.microsoft.com/en-us/intune/configmgr/core/understand/introduction&#34;&gt;Configuration Manager&lt;/a&gt;.&#xA;In short, the configuration manager is responsible for managing and implementing&#xA;the registry. However, it is also responsible for setting up parts of the system&#xA;during early boot.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Release of ERNW White Paper 73: Analyzing WinpMem Driver Vulnerabilities</title>
      <link>https://insinuator.net/2025/10/release-of-ernw-white-paper-73-analyzing-winpmem-driver-vulnerabilities/</link>
      <pubDate>Thu, 02 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/10/release-of-ernw-white-paper-73-analyzing-winpmem-driver-vulnerabilities/</guid>
      <description>&lt;p&gt;Today we are releasing a new white paper that delivers a technical analysis of&#xA;security weaknesses discovered in WinpMem, an open-source Windows memory&#xA;acquisition driver widely used in digital forensics.&lt;/p&gt;&#xA;&lt;p&gt;After a concise primer on relevant Windows internals (virtual vs. physical&#xA;memory, page tables and PTEs, CR3 context switching, and kernel and user memory&#xA;separation), the report examines how both the fundamental design of WinpMem and&#xA;specific implementation choices create severe risk.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Hello for Business - Faceplant: Planting Biometric Templates</title>
      <link>https://insinuator.net/2025/08/windows-hello-for-business-faceplant-planting-biometric-templates/</link>
      <pubDate>Fri, 29 Aug 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/08/windows-hello-for-business-faceplant-planting-biometric-templates/</guid>
      <description>&lt;p&gt;We are back from Black Hat USA, where we presented our research on&#xA;&lt;a href=&#34;https://www.blackhat.com/us-25/briefings/schedule/index.html#windows-hell-no-for-business-45865&#34;&gt;Windows Hello for Business&lt;/a&gt;&#xA;(&lt;a href=&#34;http://i.blackhat.com/BH-USA-25/Presentations/US-25-David-Windows-Hello-No-for-Business-Wendsday.pdf&#34;&gt;Slides&lt;/a&gt;)&#xA;once more. In the last two blog posts, we have discussed the&#xA;&lt;a href=&#34;https://insinuator.net/2025/06/windows-hello-for-business-past-and-present-attacks/&#34;&gt;architecture of WHfB and past attacks&lt;/a&gt;,&#xA;as well as how the&#xA;&lt;a href=&#34;https://insinuator.net/2025/07/windows-hello-for-business-the-face-swap/&#34;&gt;database works and how to swap identities&lt;/a&gt; in&#xA;the database.&lt;/p&gt;&#xA;&lt;p&gt;First, a few words regarding my experience at Black Hat: for me, it was the&#xA;first time attending the conference and then directly as a speaker. I thoroughly&#xA;enjoyed Black Hat. It took a while to get used to the size of the conference and&#xA;the vibe of Las Vegas. What was especially interesting for me was connecting&#xA;with other researchers. One thing that stood out was meeting with the team from&#xA;MSRC and putting faces to the team itself. It feels way more personal to know&#xA;who you’re talking to when you know the people handling your cases. During&#xA;TROOPERS I typically have the chance to connect with many researchers, mainly&#xA;from Europe. At Black Hat US, on the other hand, it is possible to connect more&#xA;with the US scene and meet people you haven’t seen in a long time! Seeing&#xA;familiar faces again is always nice, as opposed to putting them into your&#xA;biometric template database. One nice detail was that some international&#xA;researchers are aware of the research BSI (German: “Bundesamt für Sicherheit in&#xA;der Informationstechnik” – “German federal office for IT security”) is&#xA;facilitating. The results of our presentation stem from the “Windows Dissected”&#xA;project we are performing on behalf of the BSI.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Hello for Business - The Face Swap</title>
      <link>https://insinuator.net/2025/07/windows-hello-for-business-the-face-swap/</link>
      <pubDate>Tue, 15 Jul 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/07/windows-hello-for-business-the-face-swap/</guid>
      <description>&lt;p&gt;In the&#xA;&lt;a href=&#34;https://insinuator.net/2025/06/windows-hello-for-business-past-and-present-attacks/&#34;&gt;last blog post&lt;/a&gt;,&#xA;we discussed the full authentication flow using Windows Hello for Business&#xA;(WHfB) with face recognition to authenticate against an Active Directory with&#xA;Kerberos and showcased existing and new vulnerabilities. In this blog post, we&#xA;dive into the architectural challenges WHfB faces and explore how we can exploit&#xA;them.&lt;/p&gt;&#xA;&lt;p&gt;The majority of the work was conducted in the context of the “Windows Dissected”&#xA;project. This project, funded by the BSI (German: “Bundesamt für Sicherheit in&#xA;der Informationstechnik” – the German Federal Office for Information Security),&#xA;has the goal to perform ” various in-depth security analyses of&#xA;security-critical components and functions in Windows.” Over the next years we&#xA;will discuss these results here once they are published.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Hello for Business – Past and Present Attacks</title>
      <link>https://insinuator.net/2025/06/windows-hello-for-business-past-and-present-attacks/</link>
      <pubDate>Fri, 20 Jun 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/06/windows-hello-for-business-past-and-present-attacks/</guid>
      <description>&lt;p&gt;Windows Hello for Business is a key component of Microsoft’s passwordless&#xA;authentication strategy. It enables user authentication not only during system&#xA;sign-in but also in conjunction with new and advanced features such as Personal&#xA;Data Encryption, Administrator Protection, and Recall. Rather than depending on&#xA;traditional passwords, Windows Hello leverages a PIN or biometric methods – such&#xA;as fingerprint or facial recognition – to unlock cryptographic keys protected by&#xA;the Trusted Platform Module (TPM).&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>CrowdStrike: What is the worldwide BSOD all about?</title>
      <link>https://insinuator.net/2024/08/crowdstrike-what-is-the-worldwide-bsod-all-about/</link>
      <pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2024/08/crowdstrike-what-is-the-worldwide-bsod-all-about/</guid>
      <description>&lt;p&gt;&lt;em&gt;This article is about the massive BSOD triggered by CrowdStrike worldwide on July 19. Analysis and information from CrowdStrike or other sources are regularly published, completing what is expressed here. Updates may also be provided in the future.&lt;/em&gt;&lt;/p&gt;&#xA;&lt;p&gt;Friday, July 19, is a day to be remembered in computing history as the day of one of the biggest BSODs (Blue Screens of Death). We have seen air traffic come to a standstill over the USA and people climbing ladders with USB sticks to update giant screens. The impact was still measurable over many days. The question on everyone’s lips is how that all happened. CrowdStrike provided, on a regular basis, an explanation for people to understand what happened. But explanations can be hard to understand, especially for one who would like to read directly within CrowdStrike’s internal wording in their publications and regarding technical driver implementation details. Also, the analysis misses some points we consider relevant for secure software development. This article discusses conclusions from this massive crash, especially the necessity to change our mindset about software. This means we should understand, document, and evaluate independently software provided by vendors to know exactly what we install on our systems and to figure out the risk that may be taken by using the software. The time of naive belief in software magic must end with a third party’s independent review of the software, analysing its reliability, security, and stability. This is an activity we have been doing at ERNW for years, especially for e.g. the German Federal Office for Information Security (BSI)&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>BSI Publishes Windows 10 SiSyPHuS Reports: Application Compatibility Infrastructure, Microsoft Defender Antivirus ETW Usage and Device Setup Manager Service</title>
      <link>https://insinuator.net/2024/04/bsi-publishes-windows-10-sisyphus-reports-application-compatibility-infrastructure-microsoft-defender-antivirus-etw-usage-and-device-setup-manager-service/</link>
      <pubDate>Tue, 16 Apr 2024 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2024/04/bsi-publishes-windows-10-sisyphus-reports-application-compatibility-infrastructure-microsoft-defender-antivirus-etw-usage-and-device-setup-manager-service/</guid>
      <description>&lt;p&gt;The German Federal Office for Information Security (BSI – Bundesamt für Sicherheit in der Informationstechnik) has published several papers ERNW created as part of the long-term &lt;a href=&#34;https://www.bsi.bund.de/DE/Service-Navi/Publikationen/Studien/SiSyPHuS_Win10/SiSyPHuS_node.html&#34;&gt;SiSyPHuS Win10-Project&lt;/a&gt;. This project focuses on system analysis of selected parts of the Windows 10 operating system performed by ERNW.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.bsi.bund.de/DE/Service-Navi/Publikationen/Studien/SiSyPHuS_Win10/AP3/SiSyPHuS_AP3_node.html&#34;&gt;Analysis of the Application Compatibility Infrastructure (ACI)&lt;/a&gt;: In this work we present an overview of the ACI technology along with a technical analysis of the compatibility protocol which is used first to determine if a compatibility solution needs to be applied, and second, to apply said compatibility solution. Furthermore, threats and mitigation in the context of the technology are presented a long with a monitoring approach. Finally, configuration and logging capabilities are discussed.&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>Microsoft Office Telemetry: Report Release</title>
      <link>https://insinuator.net/2020/11/microsoft-office-telemetry-report-release/</link>
      <pubDate>Tue, 17 Nov 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/11/microsoft-office-telemetry-report-release/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://www.bsi.bund.de/&#34;&gt;German Federal Office for Information Security&lt;/a&gt; (orig., ger., Bundesamt für Sicherheit in der Informationstechnik – BSI) has published our report on Microsoft Office Telemetry.&lt;/p&gt;&#xA;&lt;p&gt;Microsoft has released a set of &lt;a href=&#34;https://docs.microsoft.com/en-us/deployoffice/privacy/manage-privacy-controls&#34;&gt;privacy settings&lt;/a&gt; for Office, one of which enables users to configure the type and amount of diagnostic (i.e., telemetry) data that Office may send to Microsoft. When deployed, it is available in the form of a group policy setting. It allows users to configure one of the following diagnostic data levels: &lt;em&gt;required&lt;/em&gt;, &lt;em&gt;optional&lt;/em&gt;, or &lt;em&gt;neither&lt;/em&gt;.  The report we produced:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Insight: The Windows Telemetry ETW Monitor</title>
      <link>https://insinuator.net/2020/01/windows-insight-the-windows-telemetry-etw-monitor/</link>
      <pubDate>Tue, 14 Jan 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/01/windows-insight-the-windows-telemetry-etw-monitor/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/ernw/Windows-Insight&#34;&gt;Windows Insight&lt;/a&gt; repository now hosts the &lt;a href=&#34;https://github.com/ernw/Windows-Insight/tree/master/files/wintel_etwmonitor&#34;&gt;Windows Telemetry ETW Monitor&lt;/a&gt; framework. The framework monitors and reports on Windows Telemetry ETW (Event Tracing for Windows) activities – ETW activities for providing data to Windows Telemetry. It consists of two components:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;the Windbg Framework: a set of scripts for monitoring Windows Telemetry ETW activities. The scripts are fed to a running windbg instance, connected to the Windows instance whose Windows Telemetry ETW activities are monitored.&lt;/li&gt;&#xA;&lt;li&gt;the Telemetry Information Visualization (TIV) framework for visualization of information and statistics. The TIV framework is a set of Python scripts that visualize information and statistics based on the data produced by the Windbg Framework. The output of the TIV framework is a report in the form of a web page.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://insinuator.net/2020/01/windows-insight-the-windows-telemetry-etw-monitor/wintel/&#34;&gt;&lt;img src=&#34;wintel-1024x575.png&#34; alt=&#34;wintel&#34;&gt;&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>TROOPERS20 Training Teaser: Insight Into Windows Internals</title>
      <link>https://insinuator.net/2019/11/troopers20-training-teaser-insight-into-windows-internals/</link>
      <pubDate>Mon, 25 Nov 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/11/troopers20-training-teaser-insight-into-windows-internals/</guid>
      <description>&lt;p&gt;Windows 10 is one of the most commonly deployed operating systems at this time. Knowledge about its components and internal working principles is highly beneficial. Among other things, such a knowledge enables:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;in-depth studies of undocumented, or poorly documented, system functionalities;&lt;/li&gt;&#xA;&lt;li&gt;development of performant and compatible software to monitor or extend the activities of the operating system itself; and&lt;/li&gt;&#xA;&lt;li&gt;analysis of security-related issues, such as persistent malware.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The “Insight into Windows Internals” training offered at TROOPERS20 delivers knowledge on the core components and inner working principles of Windows 10. For example, the training provides knowledge on how Windows 10 uses virtualization to isolate security-critical functionalities from attackers that have managed to compromise the system. The training includes a variety of practical exercises allowing attendees to observe first-hand the operation of Windows 10.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Insight: Code integrity and WDAC</title>
      <link>https://insinuator.net/2019/10/windows-insight-code-integrity-and-wdac/</link>
      <pubDate>Wed, 30 Oct 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/10/windows-insight-code-integrity-and-wdac/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/ernw/Windows-Insight&#34;&gt;Windows Insight&lt;/a&gt; repository now hosts three articles on Windows code integrity and WDAC (Windows Defender Application Control):&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Device Guard Image Integrity: Architecture Overview&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;, &lt;em&gt;Dominik Phillips&lt;/em&gt;): In this work, we present the high-level architecture of the code integrity mechanism implemented as part of Windows 10.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Windows Defender Application Control: Initialization&lt;/strong&gt; (&lt;em&gt;Dominik Phillips&lt;/em&gt;, &lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): This work describes the process for initializing WDAC performed by the Windows loader and the kernel when Windows 10 is booted.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Windows Defender Application Control: Image verification&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): This work discusses the workflow of WDAC for verifying images.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;– Aleksandar Milenkoski&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Insight: Virtual Secure Mode</title>
      <link>https://insinuator.net/2019/06/windows-insight-virtual-secure-mode/</link>
      <pubDate>Wed, 12 Jun 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/06/windows-insight-virtual-secure-mode/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/ernw/Windows-Insight&#34;&gt;Windows Insight&lt;/a&gt; repository currently hosts four articles on VSM (Virtual Secure Mode):&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Virtual Secure Mode: Architecture Overview&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): In this work, we discuss the architecture of a virtualized Windows environment.&lt;/li&gt;&#xA;&lt;li&gt;**Virtual Secure Mode: Communication Interfaces **(&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): In this work, we discuss the communication interfaces that VSM implements: Isolated User Mode (IUM) system calls, normal-mode services, secure services, and hypercalls.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Virtual Secure Mode: Protections of Communication Interfaces&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): This work discusses implemented mechanisms for securing the above VSM communication interfaces. This includes restrictions on issuing hypercalls, data marshalling and sanitization, and secure data sharing.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Virtual Secure Mode: Initialization&lt;/strong&gt; (&lt;em&gt;Dominik Phillips, Aleksandar Milenkoski&lt;/em&gt;): This work describes the process for VSM initialization activities performed by the Windows loader and the Windows kernel when Windows 10 is booted.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;– Aleksandar Milenkoski&lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Insight: The TPM</title>
      <link>https://insinuator.net/2019/05/windows-insight-the-tpm/</link>
      <pubDate>Mon, 27 May 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/05/windows-insight-the-tpm/</guid>
      <description>&lt;p&gt;The &lt;a href=&#34;https://github.com/ernw/Windows-Insight&#34;&gt;Windows Insight&lt;/a&gt; repository currently hosts three articles on the TPM (Trusted Platform Module):&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;The TPM: Communication Interfaces&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): In this work, we discuss how the different components of the Windows 10 operating system deployed in user-land and in kernel-land, use the TPM. We focus on the communication interfaces between Windows 10 and the TPM. In addition, we discuss the construction of TPM usage profiles, that is, information on system entities communicating with the TPM as well as on communication patterns and frequencies;&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;The TPM: Integrity Measurement&lt;/strong&gt; (&lt;em&gt;Aleksandar Milenkoski&lt;/em&gt;): In this work, we discuss the integrity measurement mechanism of Windows 10 and the role that the TPM plays&lt;br&gt;&#xA;as part of it. This mechanism, among other things, implements the production of measurement data. This involves calculation of hashes of relevant executable files or of code sequences at every system startup. It also involves the storage of these hashes and relevant related data in log files for later analysis;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt; &lt;/p&gt;</description>
    </item>
    <item>
      <title>Windows Insight: A New ERNW Repository</title>
      <link>https://insinuator.net/2019/05/windows-insight-a-new-ernw-repository/</link>
      <pubDate>Thu, 23 May 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/05/windows-insight-a-new-ernw-repository/</guid>
      <description>&lt;p&gt;We are glad to announce the &lt;a href=&#34;https://github.com/ernw/Windows-Insight&#34;&gt;Windows Insight&lt;/a&gt; repository. The content of this repository aims to assist efforts on analysing inner working principles, functionalities, and properties of the Microsoft Windows operating system. This repository stores relevant documentation as well as executable files needed for conducting analysis studies.&lt;/p&gt;&#xA;&lt;p&gt;Some of the content of this repository has been created in the course of a project named ‘Studie zu Systemaufbau, Protokollierung, Härtung und Sicherheitsfunktionen in Windows 10 (SiSyPHuS Win10)’ (ger.) – ‘Study of system design, logging, hardening, and security functions in Windows 10’ (eng.). This project has been contracted by the &lt;a href=&#34;https://www.bsi.bund.de/EN/TheBSI/thebsi_node.html&#34;&gt;German Federal Office for Information Security&lt;/a&gt; (ger., Bundesamt für Sicherheit in der Informationstechnik – BSI). The work planned as part of the project is conducted by ERNW GmbH, starting in May 2017.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Troopers &amp;amp; Chill…</title>
      <link>https://insinuator.net/2019/04/troopers-amp-chill/</link>
      <pubDate>Fri, 26 Apr 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/04/troopers-amp-chill/</guid>
      <description>&lt;p&gt;As promised in my &lt;a href=&#34;https://insinuator.net/2019/03/the-mmm-in-community/&#34;&gt;previous post&lt;/a&gt;, I am back for an overview of the &lt;strong&gt;Troopers19 – Active Directory&lt;/strong&gt; related talks… Videos have been published and it’s popcorn time… So if you are into stories about Kingdoms and Crown Jewels, grab your loved one [or a drink…] and turn the lights down low, ’cause tonight it’s “Troopers &amp;amp; Chill…”&lt;/p&gt;&#xA;&lt;p&gt;Warning: Don’t watch it all in one go… or you will start to feel some anxiety and pain…&lt;br&gt;&#xA;and then the Flying Dutchman will move to the cloud… And at that point we are not insured anymore.&lt;/p&gt;</description>
    </item>
    <item>
      <title>TROOPERS19 Training Teaser: Insight Into Windows Internals</title>
      <link>https://insinuator.net/2019/01/troopers19-training-teaser-insight-into-windows-internals/</link>
      <pubDate>Tue, 15 Jan 2019 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2019/01/troopers19-training-teaser-insight-into-windows-internals/</guid>
      <description>&lt;p&gt;Windows 10 is one of the most commonly deployed operating systems at this time. Knowledge about its components and internal working principles is highly beneficial. Among other things, such a knowledge enables:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;in-depth studies of undocumented, or poorly documented, system functionalities;&lt;/li&gt;&#xA;&lt;li&gt;development of performant and compatible software to monitor or extend the activities of the operating system itself; and&lt;/li&gt;&#xA;&lt;li&gt;analysis of security-related issues, such as persistent malware.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The “Insight into Windows Internals” training offered at TROOPERS’19 delivers knowledge on the core components and inner working principles of Windows 10. For example, the training provides knowledge on how Windows 10 uses virtualization to isolate security-critical functionalities from attackers that have managed to compromise the system. The training includes a variety of practical exercises allowing attendees to observe first-hand the operation of Windows 10.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Dog Whisperer’s Handbook</title>
      <link>https://insinuator.net/2018/11/the-dog-whisperers-handbook/</link>
      <pubDate>Mon, 19 Nov 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/11/the-dog-whisperers-handbook/</guid>
      <description>&lt;p&gt;Generally speaking, I’m more of a Cat type of guy, but I have to say I really love BloodHound. And if you do too, you are in for a treat…&lt;br&gt;&#xA;Last week, the &lt;a href=&#34;https://twitter.com/ERNW_Insight&#34;&gt;ERNW Insight&lt;/a&gt; &lt;strong&gt;Active Directory Security Summit&lt;/strong&gt; took place in Heidelberg. (&lt;a href=&#34;https://insinuator.net/2018/11/active-directory-security-summit-2018-slides-online/&#34;&gt;More Info&lt;/a&gt;)&lt;br&gt;&#xA;For this occasion, &lt;a href=&#34;https://twitter.com/Enno_Insinuator&#34;&gt;@Enno_Insinuator&lt;/a&gt; asked me if I would like to deliver a &lt;strong&gt;BloodHound Workshop&lt;/strong&gt;, and of course I accepted the challenge…&lt;/p&gt;&#xA;&lt;p&gt;We had a full class, I had a blast training it, and I hope the trainees enjoyed it as much as I did.&lt;br&gt;&#xA;But that’s not all…&lt;br&gt;&#xA;Another part of the deal was that I had to write a &lt;strong&gt;Training Guide&lt;/strong&gt; that we would then &lt;strong&gt;share with the Community&lt;/strong&gt; (aka you).&lt;br&gt;&#xA;So here it is, fresh from the Heidelberg press and available for download:&lt;/p&gt;</description>
    </item>
    <item>
      <title>#TR18 Defense &amp; Management Summaries</title>
      <link>https://insinuator.net/2018/03/%23tr18-defense-management-summaries/</link>
      <pubDate>Fri, 23 Mar 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/03/%23tr18-defense-management-summaries/</guid>
      <description>&lt;p&gt;This blogpost contains summaries of talks from this year’s &lt;a href=&#34;https://www.troopers.de/troopers18/&#34;&gt;TROOPERS18&lt;/a&gt; Defense &amp;amp; Management Track.&lt;/p&gt;&#xA;&lt;h1 id=&#34;all-your-cloud-are-belong-to-us&#34;&gt;All Your Cloud Are Belong to Us&lt;/h1&gt;&#xA;&lt;p&gt;The talk “All Your Cloud Belong Are Belong to Us” was held by &lt;a href=&#34;https://twitter.com/dk_effect&#34;&gt;Nate Warfield&lt;/a&gt;, who is a Senior Security Program Manager for the Microsoft Security Response Center (MSRC).&lt;br&gt;&#xA;Before Microsoft he worked as a network engineer about 18 years and 10 of this for a large amount of cell phone companies.&lt;br&gt;&#xA;Nate gives an overview about the state of the cloud solution provided by Microsoft, Azure, and how he hunts vulnerabilities in this environment.&lt;br&gt;&#xA;Finally he concludes that the giving up your infrastructure to the cloud doesn’t mean that you give up your responsibility.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Creating Static Binaries for Nmap, Socat and other Tools</title>
      <link>https://insinuator.net/2018/02/creating-static-binaries-for-nmap-socat-and-other-tools/</link>
      <pubDate>Fri, 23 Feb 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/02/creating-static-binaries-for-nmap-socat-and-other-tools/</guid>
      <description>&lt;p&gt;In various scenarios it might be helpful or even required to have a statically compiled version of Nmap available. This applies to e.g. scenarios where only limited user privileges are available and installing anything to the system might not be desirable.&lt;/p&gt;&#xA;&lt;p&gt;For such cases I’ve started to create recipes to build such binaries. Similar projects are already available on GitHub, but there are several reasons why I chose to create my own tools:&lt;/p&gt;</description>
    </item>
    <item>
      <title>White Paper on Multi-Factor Authentication in Microsoft Windows Environments</title>
      <link>https://insinuator.net/2018/01/white-paper-on-multi-factor-authentication-in-microsoft-windows-environments/</link>
      <pubDate>Mon, 29 Jan 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/01/white-paper-on-multi-factor-authentication-in-microsoft-windows-environments/</guid>
      <description>&lt;p&gt;A new ERNW whitepaper was just published. I wrote this whitepaper in the course of my bachelor thesis and it examines multi-factor authentication in Microsoft Windows environments:&lt;/p&gt;&#xA;&lt;blockquote&gt;&#xA;&lt;p&gt;Credential theft and the subsequent reuse of stolen credentials are a significant problem in today’s information security. To counter the associated risks, a planned approach is required as part of a comprehensive security architecture program. This includes the implementation of multi-factor authentication as an important building block. This whitepaper covers the relevant steps of implementing a multi-factor authentication system in an enterprise environment and closes with a security evaluation.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPv6 Properties of Windows Server 2016 / Windows 10</title>
      <link>https://insinuator.net/2017/01/ipv6-properties-of-windows-server-2016-/-windows-10/</link>
      <pubDate>Mon, 30 Jan 2017 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2017/01/ipv6-properties-of-windows-server-2016-/-windows-10/</guid>
      <description>&lt;p&gt;In this post we’ll take a detailed look at the properties of the Windows Server 2016 IPv6 stack.&lt;br&gt;&#xA;I perform(ed) this exercise for several reasons:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Server 2016 is the latest OS released by Microsoft so this might give an indication as for their plans &amp;amp; strategy when it comes to supporting certain specifications.&lt;br&gt;&#xA;(here you may keep in mind that the ~50 IETF meetings having passed since the publication of RFC 2460 provided ample opportunity for creative minds to come up with ever new ideas for “enhancing” IPv6, without too much real-life feedback/reality checks from enterprise space though, as simply not many of such organizations have deployed it at scale… or are incentivized to send their employees to week-long meetings in expensive hotels on other continents twice a year…).&lt;/li&gt;&#xA;&lt;li&gt;as I laid out &lt;a href=&#34;https://insinuator.net/2016/12/ipv6-configuration-approaches-for-servers/&#34;&gt;in this post&lt;/a&gt; the configuration approach an organization takes for their servers might depend on the support of specific features.&lt;/li&gt;&#xA;&lt;li&gt;obviously for both IPv6 planning and operations it might be helpful to understand the respective behavior of individual operating systems (which is why we researched stuff like &lt;a href=&#34;https://www.ernw.de/download/ERNW_Whitepaper_IPv6_RAs_RDNSS_DHCPv6_Conflicting_Parameters.pdf&#34;&gt;this&lt;/a&gt; or &lt;a href=&#34;https://www.ernw.de/download/newsletter/ERNW_Whitepaper57_IPv6_lab_source_address_selection_signed.pdf&#34;&gt;this&lt;/a&gt; in the past).&lt;/li&gt;&#xA;&lt;li&gt;many years ago Microsoft published white papers with details as for the TCP/IP parameters of their OSs (incl. stuff like registry parameters to control it etc.) but I’m not aware of such a document for Server 2016 or Windows 10. I hence hope this post can somewhat contribute to public knowledge of the intricacies of their latest IPv6 stack.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;&lt;strong&gt;Version&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Diving into EMET</title>
      <link>https://insinuator.net/2016/09/diving-into-emet/</link>
      <pubDate>Mon, 26 Sep 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/09/diving-into-emet/</guid>
      <description>&lt;p&gt;Last week, we decided to take a look onto the EMET library provided by Microsoft. This library is intended to introduce several security features to applications which are not explicitly compiled to use them.&lt;/p&gt;&#xA;&lt;p&gt;It also adds an additional layer to protect against typical exploiting techniques by filtering library calls, preventing usage of dangerous functions/components and inserting mitigation technologies.&lt;/p&gt;&#xA;&lt;p&gt;As EMET is already a target for many researchers, we currently only started to get an overview of it’s structure and how the different components are interacting with each other. Today we would like to share some of our results with you.&lt;/p&gt;</description>
    </item>
    <item>
      <title>PFX Profiles in Microsoft’s System Management Server</title>
      <link>https://insinuator.net/2016/08/pfx-profiles-in-microsofts-system-management-server/</link>
      <pubDate>Fri, 05 Aug 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/08/pfx-profiles-in-microsofts-system-management-server/</guid>
      <description>&lt;p&gt;In a recent assessment, we had to evaluate how Microsoft’s System Management Server (SMS) certificate management solution (CMS) stores and handles certificates. This question came up because sensitive, encrypted user certificates were to be stored in the SMS CMS. Due to the sensitivity of the handled certificates, we assessed the protection capabilities of the certificate management solution against extraction attempts from a local attacker with administrative privileges.&lt;/p&gt;&#xA;&lt;h2 id=&#34;how-did-we-do-it&#34;&gt;How did we do it?&lt;/h2&gt;&#xA;&lt;p&gt;We determined a five steps approach to gain access to the certificates and be able to decrypt the accessed certificate material:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Your Mouse Got Sick and You Don’t Know it. aka “Reverse Shell via Mouse”</title>
      <link>https://insinuator.net/2016/07/your-mouse-got-sick-and-you-dont-know-it.-aka-reverse-shell-via-mouse/</link>
      <pubDate>Fri, 29 Jul 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/07/your-mouse-got-sick-and-you-dont-know-it.-aka-reverse-shell-via-mouse/</guid>
      <description>&lt;p&gt;Ever got a backdoor installed on your computer by your beloved mouse? Here’s the story of a poor mouse that got really, really sick.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://www.insinuator.net/wp-content/uploads/2016/07/mouse-300x169.jpg&#34; alt=&#34;Agent &amp;ldquo;Danger Mouse&amp;rdquo;&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Agent “Danger Mouse”&lt;/p&gt;&#xA;&lt;p&gt;Do you remember the times where people put Teensy-boards and USB hubs in their mouses? [Chris? ;)] Their aim was to attach an additional &lt;a href=&#34;https://en.wikipedia.org/wiki/Human_interface_device&#34;&gt;Human Interface Device&lt;/a&gt; (HID, like keyboards or mouses) with some payload in kind of e.g. keystrokes or mouse movements. Also, there are devices available like the USB Rubber Ducky in the housing of a USB thumb drive.&lt;br&gt;&#xA;The principle is easy: The tools are using a programmable microcontroller with the capability to emulate USB HID. That’s it. Just program your board of choice with the payload fitting your needs and plug it in at the target computer. The latter will recognize it as a keyboard/mouse and the payload-keystrokes will be entered.&lt;br&gt;&#xA;But why should external hardware be used? Many modern gaming peripherals provide functions to store macros on them, including enough onboard memory for little payloads.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How ‘security’ black boxes might corrupt your investment</title>
      <link>https://insinuator.net/2016/04/how-security-black-boxes-might-corrupt-your-investment/</link>
      <pubDate>Fri, 29 Apr 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/04/how-security-black-boxes-might-corrupt-your-investment/</guid>
      <description>&lt;p&gt;Usually I’m not the kind of guy who talks about such economic topics. Because I’m an engineer / security researcher who is exclusively concerned with understanding technical problems and if possible, solving them accordingly. My whole education is based on this and contains predominantly technical aspects of information security. This sometimes makes it difficult to understand what the market cares about (and why some products are being developed / exist on the market 😉 ). Nevertheless, a current engagement for one of our customers made me stumble upon such a product.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Assessment of Microsoft DirectAccess</title>
      <link>https://insinuator.net/2016/04/security-assessment-of-microsoft-directaccess/</link>
      <pubDate>Wed, 06 Apr 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/04/security-assessment-of-microsoft-directaccess/</guid>
      <description>&lt;p&gt;A &lt;a href=&#34;https://www.troopers.de/events/ipv6-security-summit-2016/698_security_assessment_of_microsoft_directaccess/&#34;&gt;talk&lt;/a&gt; about DirectAccess (an IPv6-only VPN solution) was given by our colleague Ali Hardudi during IPv6 summit. Ali has recently finished his master thesis on this topic.&lt;/p&gt;&#xA;&lt;p&gt;The DirectAccess VPN technology was introduced by Microsoft starting from Windows server 2008. It allows users remotely, seamlessly and securely connect to their internal network resources without a need to provide user credentials, which is done using different technologies such as Windows domain group policies.&lt;/p&gt;</description>
    </item>
    <item>
      <title>I Have the Power(View): Offensive Active Directory with PowerShell</title>
      <link>https://insinuator.net/2016/03/i-have-the-powerview-offensive-active-directory-with-powershell/</link>
      <pubDate>Thu, 31 Mar 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/03/i-have-the-powerview-offensive-active-directory-with-powershell/</guid>
      <description>&lt;p&gt;In his talk &lt;a href=&#34;https://www.troopers.de/events/troopers16/604_i_have_the_powerview_offensive_active_directory_with_powershell/&#34;&gt;I have the Power(View): Offensive Active Directory with PowerShell&lt;/a&gt; Will Schroeder, a researcher and Red teamer in Veris Group´s Adaptive Thread Division, presented offensive Active Directory information gathering technics using his Tool PowerView.&lt;/p&gt;&#xA;&lt;p&gt;PowerView does not use the built in AD cmdlets to be independent from the Remote Server Administration Tools (RSAT)-AD PowerShell Module which is only compatible with PowerShell 3.0+ and by default only installed on servers that have Active Directory services roles. PowerView, however, is compatible with PowerShell 2.0 and has no outer dependencies. Furthermore, it does not require any installation process.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Joy of Sandbox Mitigations</title>
      <link>https://insinuator.net/2016/03/the-joy-of-sandbox-mitigations/</link>
      <pubDate>Mon, 28 Mar 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/03/the-joy-of-sandbox-mitigations/</guid>
      <description>&lt;p&gt;This year at TROOPERS16 in Heidelberg we welcomed James Forshaw for his talk about “&lt;a href=&#34;https://www.troopers.de/events/troopers16/644_the_joy_of_sandbox_mitigations/&#34;&gt;The Joy of Sandbox Mitigations&lt;/a&gt;“.&lt;/p&gt;&#xA;&lt;p&gt;He is a security researcher in Google’s Project Zero. He has been involved with computer hardware and software security for over 10 years looking at a range of different platforms and applications. With a great interest in logical vulnerabilities he has numerous disclosures in a wide range of products from web browsers to virtual machine breakouts as well as being a Pwn2Own and Microsoft Mitigation Bypass bounty winner. He has spoken at a number of security conferences including Black Hat USA, CanSecWest, Bluehat, HITB, and Infiltrate.&lt;/p&gt;</description>
    </item>
    <item>
      <title>TROOPERS16 Training Teaser: Dos and Don’ts of Secure Active Directory Administration</title>
      <link>https://insinuator.net/2016/01/troopers16-training-teaser-dos-and-donts-of-secure-active-directory-administration/</link>
      <pubDate>Wed, 27 Jan 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/01/troopers16-training-teaser-dos-and-donts-of-secure-active-directory-administration/</guid>
      <description>&lt;p&gt;In the last few years, attack techniques which fall in the categories of “Credential Theft” or “Credential Reuse” have grown into one of the biggest threats to Microsoft Windows environments. Microsoft has stated more than one time, that nearly almost all of their customers that run Active Directory have experienced “Pass-the-Hash” (PtH) attacks recently.&lt;a href=&#34;#_ftn1&#34;&gt;[1]&lt;/a&gt; Once an attacker gains an initial foothold on a single system in the environment it takes often less than 48 hours until the entire Active Directory infrastructure is compromised. To defend against this kind of attacks, a well-planned approach is required as part of a comprehensive security architecture and operations program. As breach has to be assumed&lt;a href=&#34;#_ftn2&#34;&gt;[2]&lt;/a&gt;, this includes a preventative mitigating control strategy, where technical and organizational controls are implemented, as well as preparations against insider attacks. This is mainly achieved by partitioning the credential flow in order to firstly limit their exposure and secondly limit their usefulness if an attacker was able to get them. Although we spoke last year at Troopers 15 about “How to Efficiently Protect Active Directory from Credential Theft &amp;amp; Large Scale Compromise”&lt;a href=&#34;#_ftn3&#34;&gt;[3]&lt;/a&gt;, we would like to summarize exemplary later in this post Active Directory pentest findings that we classified in four categories in order to better understand what goes typically wrong and thus has to be addressed. For a better understanding of the overall security goals, we classified the findings as to belonging as a security best practice violation of the following categories:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Investigating Memory Analysis Tools – SSDT Hooking via Pointer Replacement</title>
      <link>https://insinuator.net/2015/12/investigating-memory-analysis-tools-ssdt-hooking-via-pointer-replacement/</link>
      <pubDate>Sun, 13 Dec 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/12/investigating-memory-analysis-tools-ssdt-hooking-via-pointer-replacement/</guid>
      <description>&lt;p&gt;In this blogpost we will briefly explain a well known Syscall hooking technique (a more detailed explanation can be gathered from e.g.  http://resources.infosecinstitute.com/hooking-system-service-dispatch-table-ssdt/) used by multiple malware samples (like the laqma trojan) and right after discuss how some memory analysis tools have trouble in the analysis and/or reporting of these.&lt;/p&gt;&#xA;&lt;p&gt;Before we go further, I just shortly wanted to say, that this post is not intended to be a bashing of any tool. We have the greatest respect for all the effort and work which has been and most probably will be done in the future.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Black Hat Talks &amp; Papers related to Windows/Active Directory Security</title>
      <link>https://insinuator.net/2015/08/black-hat-talks-papers-related-to-windows/active-directory-security/</link>
      <pubDate>Fri, 07 Aug 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/08/black-hat-talks-papers-related-to-windows/active-directory-security/</guid>
      <description>&lt;p&gt;This year’s Black Hat US saw a number of quite interesting talks in the context of Windows or Active Directory Security. For those of you too lazy to search for themselves 😉 and for our own Windows/AD Sec team (who couldn’t send anyone to Vegas due to heavy project load) I’ve compiled a little list of those.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://twitter.com/pdjstone&#34;&gt;Paul Stone&lt;/a&gt; &amp;amp; &lt;a href=&#34;https://twitter.com/NoxrNet&#34;&gt;Alex Chapman&lt;/a&gt;: WSUSPect – Compromising the Windows Enterprise via Windows Update&lt;br&gt;&#xA;Slides &lt;a href=&#34;https://www.blackhat.com/docs/us-15/materials/us-15-Stone-WSUSpect-Compromising-Windows-Enterprise-Via-Windows-Update.pdf&#34;&gt;here&lt;/a&gt;.&lt;br&gt;&#xA;Whitepaper &lt;a href=&#34;http://www.contextis.com/media/documents/CTX_WSUSpect_White_Paper.pdf&#34;&gt;here&lt;/a&gt;. (Attention: on the BH website there’s an older this. the above link leads to the latest one).&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to go ahead with future end of life Windows (2003) Servers</title>
      <link>https://insinuator.net/2015/02/how-to-go-ahead-with-future-end-of-life-windows-2003-servers/</link>
      <pubDate>Thu, 12 Feb 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/02/how-to-go-ahead-with-future-end-of-life-windows-2003-servers/</guid>
      <description>&lt;p&gt;Server operating systems with an OS, for which vendor support has ended, come with many risks that have to be considered and addressed. The primary goal should be always to decommission or migrate the majority of end-of-life (EoL) servers to OS versions, supported by the vendor. Here it should be noted that a migration to an up-to-date OS should be preferably done before your organization enters the end of life of that software 😉&lt;/p&gt;</description>
    </item>
    <item>
      <title>Skeleton Key – a Nasty Piece of Malware. Some Remarks.</title>
      <link>https://insinuator.net/2015/01/skeleton-key-a-nasty-piece-of-malware.-some-remarks./</link>
      <pubDate>Thu, 15 Jan 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/01/skeleton-key-a-nasty-piece-of-malware.-some-remarks./</guid>
      <description>&lt;p&gt;Just recently, Dell SecureWorks Counter Threat Unit(TM) (CTU) researchers published details (see &lt;a href=&#34;http://www.secureworks.com/cyber-threat-intelligence/threats/skeleton-key-malware-analysis/&#34;&gt;http://www.secureworks.com/cyber-threat-intelligence/threats/skeleton-key-malware-analysis/&lt;/a&gt; ) on a especially nasty piece of malware that bypasses authentication on Active Directory (AD) systems which implement single-factor (password only) authentication. Once deployed the malware stays quite noiseless in the Domain Controller´s (DC) RAM, and the DC´s replication issues caused by it weren´t interpreted – in this case – during months as a hint for system compromise. Probably the malware´s modification on the LSASS process reduced the DC´s ability to perform DC-to-DC authentication, but this is only speculation and not where we would like to go today.&lt;/p&gt;</description>
    </item>
    <item>
      <title>IPv6 Hardening Guide for Windows Servers</title>
      <link>https://insinuator.net/2014/12/ipv6-hardening-guide-for-windows-servers/</link>
      <pubDate>Mon, 22 Dec 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/12/ipv6-hardening-guide-for-windows-servers/</guid>
      <description>&lt;p&gt;After we recently released the “&lt;a href=&#34;http://www.insinuator.net/2014/12/ipv6-hardening-guide-for-linux-servers/&#34;&gt;Linux IPv6 Hardening Guide&lt;/a&gt;” we got a number of suggestions “could you pls provide a similar document for $OS?” (btw: thanks to you all for the overwhelming interest in the Linux document and the active discussion of ip6tables rule approaches on the &lt;a href=&#34;http://lists.si6networks.com/listinfo/ipv6hackers/&#34;&gt;&lt;em&gt;ipv6hackers&lt;/em&gt; mailing list&lt;/a&gt;).&lt;/p&gt;&#xA;&lt;p&gt;Hence Antonios thankfully decided to put together a list of configuration steps for Windows servers. It &lt;a href=&#34;https://www.ernw.de/download/ERNW_Guide_to_Configure_Securely_Windows_Servers_For_IPv6_v1_0.pdf&#34;&gt;can be found here&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;Once more we’d like to emphasize that the approach described is only suited for very specific environments with high security requirements and an associated ratio of “generous operational resources”. From our perspective this guide is intended mostly to serve as a source of inspiration (“what could be done”) and for documentation purposes (“how to do it”). Everything described should be carefully tested in your specific environment.&lt;br&gt;&#xA;For example, we were recently involved in IPv6 security planning in an organization where the Windows guys (completely legitimately) came up with a stance of “before we fully accept and ratify the strategy and policy just discussed, we’d like to get feedback from Microsoft, if we still have full support once we follow this path”.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some Things to Consider when Using EMET</title>
      <link>https://insinuator.net/2014/08/some-things-to-consider-when-using-emet/</link>
      <pubDate>Fri, 08 Aug 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/08/some-things-to-consider-when-using-emet/</guid>
      <description>&lt;p&gt;In the light of the recent release of version 5.0 of Microsoft’s Enhanced Mitigation Experience Toolkit (EMET) on July 31, it seems to be more than appropriate to talk a bit about the new features and some general things to take into account when using EMET (for the new certificate pinning feature of EMET 4.0, see &lt;a href=&#34;http://www.insinuator.net/2013/07/emet-v4-0-with-new-certificate-trust-feature-released/&#34; title=&#34;Certificate Pinning&#34;&gt;Friedwart’s comment&lt;/a&gt;). For all of you who don’t know EMET, in short, it’s a free mitigation tool for Windows developed by Microsoft, helping the user by preventing vulnerabilities in software from being successfully exploited. The tool works by protecting applications via a number of security mitigation technologies, vastly extending Windows operating system mitigation capabilities as Data Execution Prevention (DEP) and Address Space Layout Randomization (ASLR).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Skype GPO</title>
      <link>https://insinuator.net/2014/07/skype-gpo/</link>
      <pubDate>Thu, 03 Jul 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/07/skype-gpo/</guid>
      <description>&lt;p&gt;Hi all,&lt;/p&gt;&#xA;&lt;p&gt;regularly we get requests from customers where the idea of using Skype as a VoIP solution in their corporate environment is brought up. There are a lot of eavesdropping and more conceptual concerns (e.g. refer to &lt;a href=&#34;http://arstechnica.com/security/2014/05/encrypted-or-not-skype-communications-prove-vital-to-nsa-surveillance/&#34;&gt;this&lt;/a&gt; or &lt;a href=&#34;http://www.h-online.com/news/item/Skype-with-care-Microsoft-is-reading-everything-you-write-1862870.html&#34;&gt;this&lt;/a&gt;, and of course the legendary “&lt;a href=&#34;http://www.blackhat.com/presentations/bh-europe-06/bh-eu-06-biondi/bh-eu-06-biondi-up.pdf&#34;&gt;Silver Needle in the Skype&lt;/a&gt;” paper from Black Hat EU 2006), but those won’t be covered in this post (just to say this: at ERNW the use of Skype is strictly prohibited at by policy).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Windows Update over IPv6 (or not?)</title>
      <link>https://insinuator.net/2014/05/microsoft-windows-update-over-ipv6-or-not/</link>
      <pubDate>Wed, 21 May 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/05/microsoft-windows-update-over-ipv6-or-not/</guid>
      <description>&lt;p&gt;Hello everyone,&lt;/p&gt;&#xA;&lt;p&gt;I recently stumbled over a &lt;a href=&#34;http://technet.microsoft.com/en-us/network/hh994905.aspx&#34;&gt;document&lt;/a&gt; from Microsoft which lists all services/applications that support IPv6. Most of the content wasn’t new for me, but one item caught my attention. &lt;em&gt;Windows Update&lt;/em&gt;. I haven’t heard before that Windows Update can be done over IPv6 (but this could just be me not looking hard enough ;)), so I was eager to test it out seeing if this is really the case. I was also curious why Microsoft referenced this &lt;a href=&#34;http://blogs.msdn.com/b/b8/archive/2012/06/05/connecting-with-ipv6-in-windows-8.aspx&#34;&gt;document&lt;/a&gt; in the respective column.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Role of VGX.DLL in the Context of the Latest IE 0-Day</title>
      <link>https://insinuator.net/2014/05/the-role-of-vgx.dll-in-the-context-of-the-latest-ie-0-day/</link>
      <pubDate>Tue, 13 May 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/05/the-role-of-vgx.dll-in-the-context-of-the-latest-ie-0-day/</guid>
      <description>&lt;p&gt;On Saturday, April 26 Microsoft announced that Internet Explorer version 6 until version 11 is under potential risk against drive-by attacks from malicious websites, regardless of the underlying Microsoft operating system and the associated memory protection features integrated with the operating system. Microsoft has assigned CVE-2014-1776 to this unknown use-after-free vulnerability, which in the worst case could allow remote code execution if a user views a specially crafted website. If an attacker successfully exploits this vulnerability, s/he will gain the same rights and privileges as the current user (once again, activated User Account Control [UAC] helps keeping privileges of the user low).&lt;/p&gt;</description>
    </item>
    <item>
      <title>EMET v4.0 with New Certificate Trust Feature Released</title>
      <link>https://insinuator.net/2013/07/emet-v4.0-with-new-certificate-trust-feature-released/</link>
      <pubDate>Mon, 01 Jul 2013 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2013/07/emet-v4.0-with-new-certificate-trust-feature-released/</guid>
      <description>&lt;p&gt;Microsoft released &lt;a href=&#34;http://www.microsoft.com/en-us/download/details.aspx?id=39273&#34;&gt;EMET v4.0&lt;/a&gt;  with a new (security) feature that enables protection against fraudulent websites or compromised root certification authorities (do you remember Comodo, DigiNotar, DigiCert, Turktrust et al. ;-)?)&lt;/p&gt;&#xA;&lt;p&gt;EMET defines via “certificate trust“ a trust chain between the domain name of a website (and its associated website certificate) and a root CA certificate. This is done through so called “pinning rules”. Here is one of the default pinning rules of EMET 4.0 for the domain name &lt;em&gt;login.live.com&lt;/em&gt;:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Loki for Windows released</title>
      <link>https://insinuator.net/2012/11/loki-for-windows-released/</link>
      <pubDate>Thu, 08 Nov 2012 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2012/11/loki-for-windows-released/</guid>
      <description>&lt;p&gt;Today is a great day, its the day, Loki finally runs on all big operating systems. Im proud to announce the first Loki release for Windows!&lt;/p&gt;&#xA;&lt;p&gt;There are a few things not working (yet / at all) under Windows. Those are:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;The WLCCP Module – ive not yet managed to build and link against asleap on windows [but time may help (-; ]&lt;/li&gt;&#xA;&lt;li&gt;TCP-MD5 Auth for BGP – This will never work, as Windows has no TCP-MD5 impl. in the kernel&lt;/li&gt;&#xA;&lt;li&gt;The MPLS Module – Had some hassle here with WinPcap, may be working in the future&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;The most testing so far was done on Windows 7 were all the other functions work as they do on Linux and Mac.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Advisory 2757760: Windows Internet Explorer Zero-Day Vulnerability</title>
      <link>https://insinuator.net/2012/09/microsoft-advisory-2757760-windows-internet-explorer-zero-day-vulnerability/</link>
      <pubDate>Wed, 19 Sep 2012 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2012/09/microsoft-advisory-2757760-windows-internet-explorer-zero-day-vulnerability/</guid>
      <description>&lt;p&gt;Actually a Windows Vulnerability (&lt;a href=&#34;http://technet.microsoft.com/en-us/security/advisory/2757760&#34;&gt;Microsoft Advisory 2757760&lt;/a&gt;) related to the Internet Explorer Version 7, 8 and 9 is in the news. Microsoft is aware of the problem, but there’s no patch available yet. We call this a 0-Day :-). Making the problem even worse, on monday reliable &lt;a href=&#34;https://community.rapid7.com/community/metasploit/blog/2012/09/17/lets-start-the-week-with-a-new-internet-explorer-0-day-in-metasploit&#34;&gt;exploit code&lt;/a&gt; was released within the Metasploit project, so exploit code is already in the wild.&lt;/p&gt;&#xA;&lt;p&gt;Basically Microsoft suggests two workarounds:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Usage of EMET &lt;a href=&#34;http://support.microsoft.com/kb/2458544&#34;&gt;(Enhanced Mitigation Experience Toolkit&lt;/a&gt;)&lt;/li&gt;&#xA;&lt;li&gt;Disabling Active X and Active Scripting in the Internet Settings&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;But both of them have some impact: EMET must be deployed before any usage (btw. EMET can be configured via Group Policies) and disabling Active X and Active Scripting might break some business relevant web sites (that can be added to the “Trusted Sites” Zone, but might produce major operational effort).&lt;/p&gt;</description>
    </item>
    <item>
      <title>MS10-063, Prevention</title>
      <link>https://insinuator.net/2010/09/ms10-063-prevention/</link>
      <pubDate>Wed, 15 Sep 2010 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2010/09/ms10-063-prevention/</guid>
      <description>&lt;p&gt;One of the four vulnerabilities rated “critical” from yesterday’s MS patchday, that is &lt;a href=&#34;http://www.microsoft.com/technet/security/bulletin/MS10-063.mspx&#34;&gt;MS10-063&lt;/a&gt;, has an interesting “Workarounds” section as for MS Internet Explorer. There it’s stated:&lt;/p&gt;&#xA;&lt;p&gt;“Disabling the support for the parsing of embedded fonts in Internet Explorer prevents this application from being used as an attack vector.”&lt;/p&gt;&#xA;&lt;p&gt;which, according to the advisory, should/can be done by setting the “Font Downloading” parameter to “Disable”.&lt;/p&gt;&#xA;&lt;p&gt;Which is exactly what &lt;a href=&#34;http://www.ernw.de/content/e15/e28/e1497/download1499/ERNW_Newsletter_31_Secure_IE8_Configuration_en_ger.pdf&#34;&gt;this document&lt;/a&gt; suggests. So taking a preventive approach, once more, might have saved some concerns (“Will we be targeted by this one”) and patch/testing time…&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
