<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>SOC Lab Investigations on Lorenzo Swany — Website Portfolio</title>
    <link>https://www.lorenzoswany.com/docs/projects/</link>
    <description>Recent content in SOC Lab Investigations on Lorenzo Swany — Website Portfolio</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://www.lorenzoswany.com/docs/projects/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Case A – Authentication Abuse &amp; Brute Force Detection</title>
      <link>https://www.lorenzoswany.com/docs/projects/project-1-authentication-failures/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.lorenzoswany.com/docs/projects/project-1-authentication-failures/</guid>
      <description>&lt;h1 id=&#34;case-a--authentication-abuse--brute-force-detection&#34;&gt;Case A – Authentication Abuse &amp;amp; Brute Force Detection&lt;a class=&#34;anchor&#34; href=&#34;#case-a--authentication-abuse--brute-force-detection&#34;&gt;#&lt;/a&gt;&lt;/h1&gt;&#xA;&lt;hr&gt;&#xA;&lt;h3 id=&#34;mitre-attck&#34;&gt;MITRE ATT&amp;amp;CK&lt;a class=&#34;anchor&#34; href=&#34;#mitre-attck&#34;&gt;#&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tactic:&lt;/strong&gt; Initial Access&lt;br&gt;&#xA;&lt;strong&gt;Technique:&lt;/strong&gt; T1110.003 – Brute Force: Password Spraying&lt;/p&gt;&#xA;&lt;p&gt;This project demonstrates detection and investigation of repeated failed network authentication attempts using Windows Security logs and Splunk.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;scenario&#34;&gt;Scenario&lt;a class=&#34;anchor&#34; href=&#34;#scenario&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;A Windows host begins receiving multiple failed remote logon attempts from a single source IP within a short period of time. The objective is to determine whether the activity represents brute-force behavior, password spraying, or benign misconfiguration.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Case B - Suspicious PowerShell Execution</title>
      <link>https://www.lorenzoswany.com/docs/projects/project-2-suspicious-powershell-execution/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.lorenzoswany.com/docs/projects/project-2-suspicious-powershell-execution/</guid>
      <description>&lt;h1 id=&#34;case-b--suspicious-powershell-execution&#34;&gt;Case B – Suspicious PowerShell Execution&lt;a class=&#34;anchor&#34; href=&#34;#case-b--suspicious-powershell-execution&#34;&gt;#&lt;/a&gt;&lt;/h1&gt;&#xA;&lt;hr&gt;&#xA;&lt;h3 id=&#34;mitre-attck&#34;&gt;MITRE ATT&amp;amp;CK&lt;a class=&#34;anchor&#34; href=&#34;#mitre-attck&#34;&gt;#&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tactic:&lt;/strong&gt; Execution&lt;br&gt;&#xA;&lt;strong&gt;Technique:&lt;/strong&gt; T1059.001 – Command and Scripting Interpreter: PowerShell&lt;/p&gt;&#xA;&lt;p&gt;This project demonstrates detection and investigation of suspicious PowerShell activity using Windows Security process creation logs and Splunk.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;scenario&#34;&gt;Scenario&lt;a class=&#34;anchor&#34; href=&#34;#scenario&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;PowerShell execution was observed on a Windows endpoint from a standard user account. Because PowerShell is frequently abused by attackers for script execution, payload retrieval, and system reconnaissance, the activity was reviewed to determine whether the behavior represented legitimate administrative use or potentially malicious script execution.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Case C – Unexpected Scheduled Task Creation</title>
      <link>https://www.lorenzoswany.com/docs/projects/project-3/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.lorenzoswany.com/docs/projects/project-3/</guid>
      <description>&lt;h1 id=&#34;case-c--unexpected-scheduled-task-creation&#34;&gt;Case C – Unexpected Scheduled Task Creation&lt;a class=&#34;anchor&#34; href=&#34;#case-c--unexpected-scheduled-task-creation&#34;&gt;#&lt;/a&gt;&lt;/h1&gt;&#xA;&lt;hr&gt;&#xA;&lt;h3 id=&#34;mitre-attck&#34;&gt;MITRE ATT&amp;amp;CK&lt;a class=&#34;anchor&#34; href=&#34;#mitre-attck&#34;&gt;#&lt;/a&gt;&lt;/h3&gt;&#xA;&lt;p&gt;&lt;strong&gt;Tactic:&lt;/strong&gt; Persistence&lt;br&gt;&#xA;&lt;strong&gt;Technique:&lt;/strong&gt; T1053.005 – Scheduled Task/Job: Scheduled Task&lt;/p&gt;&#xA;&lt;p&gt;This project demonstrates detection and investigation of a suspicious scheduled task created on a Windows endpoint, using Windows Security logs and Splunk.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;h2 id=&#34;scenario&#34;&gt;Scenario&lt;a class=&#34;anchor&#34; href=&#34;#scenario&#34;&gt;#&lt;/a&gt;&lt;/h2&gt;&#xA;&lt;p&gt;A scheduled task was created on a Windows endpoint outside of expected administrative activity. Because scheduled tasks are frequently used by attackers to maintain persistent access across reboots, the activity was reviewed to determine whether the task was legitimate or a potential persistence mechanism.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
