<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Threat-Hunting — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/threat-hunting/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 18 Mar 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/threat-hunting/feed.xml" rel="self" type="application/rss+xml"/><item><title>SOC Analyst Toolkit with Threat Hunting Queries</title><link>https://feed.craftedsignal.io/briefs/2026-03-soc-analyst-hub/</link><pubDate>Wed, 18 Mar 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-soc-analyst-hub/</guid><description>A free, offline SOC toolkit aimed at Tier 1 analysts includes IR checklists, triage playbooks, and threat hunting guides mapped to MITRE ATT&amp;CK, with Splunk and Elastic queries for threats such as Kerberoasting, Pass-the-Hash, LOLBAS, scheduled task persistence, and C2 on non-standard ports.</description><content:encoded><![CDATA[<p>A security practitioner has released a free, offline SOC toolkit intended for Tier 1 analysts and those new to blue team operations. This toolkit, contained within a single HTML file, provides resources for incident response, alert triage, threat hunting, and analyst onboarding. Released in March 2026, the toolkit includes interactive IR checklists for common incident types (Phishing, Malware, Brute Force, Data Exfil, Suspicious PowerShell), alert triage playbooks with decision trees, threat hunting guides mapped to MITRE ATT&amp;CK, and a structured curriculum for new Tier 1 hires. The threat hunting guides are noteworthy, as they include Splunk and Elastic queries for specific attack techniques like Kerberoasting, Pass-the-Hash, LOLBAS abuse, scheduled task persistence, and C2 communication on non-standard ports. Defenders can leverage the shared hunting queries to enhance their detection capabilities.</p>
<h2 id="attack-chain">Attack Chain</h2>
<p>This toolkit is designed to aid in the <em>detection</em> of the following attack chains:</p>
<ol>
<li><strong>Initial Access:</strong> (Phishing, Malware) An attacker gains initial access through methods such as phishing emails or malware-infected attachments.</li>
<li><strong>Credential Access:</strong> (Kerberoasting, Pass-the-Hash) After gaining initial access, the attacker attempts to harvest credentials using techniques like Kerberoasting to target service accounts or Pass-the-Hash to reuse existing credentials.</li>
<li><strong>Lateral Movement:</strong> (Pass-the-Hash) Using compromised credentials, the attacker moves laterally within the network, accessing additional systems and resources.</li>
<li><strong>Execution:</strong> (LOLBAS) The attacker utilizes Living-Off-The-Land Binaries and Scripts (LOLBAS) to execute malicious commands and evade detection.</li>
<li><strong>Persistence:</strong> (Scheduled Task Persistence) The attacker establishes persistence by creating scheduled tasks that execute malicious code at regular intervals.</li>
<li><strong>Command and Control:</strong> (C2 on non-standard ports) The attacker establishes a command and control channel, communicating with compromised systems over non-standard ports to evade detection.</li>
<li><strong>Exfiltration:</strong> (Data Exfil) The attacker exfiltrates sensitive data from the compromised systems.</li>
<li><strong>Impact:</strong> (Data Exfil) The attacker achieves their final objective of data exfiltration, resulting in data loss or exposure.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The toolkit helps defenders to mitigate the impact of attacks by providing resources for incident response, alert triage, and threat hunting. Successful implementation of the toolkit&rsquo;s recommendations can lead to faster detection and containment of security incidents, reducing the potential for data breaches, financial losses, and reputational damage.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Review the threat hunting guides within the toolkit and adapt the provided Splunk and Elastic queries for Kerberoasting, Pass-the-Hash, LOLBAS, scheduled task persistence, and C2 on non-standard ports to your environment.</li>
<li>Utilize the provided IR Checklists (Phishing, Malware, Brute Force, Data Exfil, Suspicious PowerShell) to standardize and improve incident response procedures.</li>
<li>Customize and integrate the Alert Triage Playbooks into your existing security operations workflows to assist with the analysis of alerts related to impossible travel, lateral movement, and DNS beaconing.</li>
</ul>
]]></content:encoded><category domain="severity">low</category><category domain="type">advisory</category><category>soc</category><category>blueteam</category><category>threat-hunting</category></item><item><title>Impact of Poor Security Operation Center (SOC) Metrics</title><link>https://feed.craftedsignal.io/briefs/2024-01-02-soc-metrics/</link><pubDate>Tue, 02 Jan 2024 10:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-01-02-soc-metrics/</guid><description>Poorly chosen performance metrics can significantly impair a SOC's ability to detect and respond to threats, leading to ineffective security operations and potential compromise.</description><content:encoded><![CDATA[<p>The National Cyber Security Centre (NCSC) blog post highlights the detrimental effects of using inappropriate metrics to evaluate SOC performance. Focusing on easily quantifiable metrics like &rsquo;number of tickets processed&rsquo;, &rsquo;time taken to close a ticket&rsquo;, &rsquo;number of detection rules written&rsquo;, and &lsquo;volume of logs collected&rsquo; can incentivize analysts to prioritize metric optimization over effective threat detection. These perverse incentives can lead to a high number of false positives, alert fatigue, and a failure to identify genuine security incidents. The blog emphasizes the importance of focusing on metrics that truly reflect a SOC&rsquo;s efficacy in detecting and responding to attacks in a timely manner, using red and purple teaming to simulate attacks.</p>
<h2 id="attack-chain">Attack Chain</h2>
<p>This attack chain describes how an attacker might evade detection in a SOC environment using ineffective metrics.</p>
<ol>
<li><strong>Initial Foothold:</strong> An attacker gains initial access via a vulnerability or credential compromise. This is not directly measured by common SOC metrics.</li>
<li><strong>Internal Reconnaissance:</strong> The attacker performs internal reconnaissance, such as <code>searching for passwords in a SharePoint</code>.</li>
<li><strong>Lateral Movement:</strong> The attacker uses discovered credentials to move laterally within the network.</li>
<li><strong>Data Access:</strong> The attacker accesses sensitive data, potentially including intellectual property or personal information.</li>
<li><strong>Exfiltration Preparation:</strong> The attacker prepares the data for exfiltration, such as compressing or encrypting it.</li>
<li><strong>Exfiltration:</strong> The attacker exfiltrates the data to an external server.</li>
<li><strong>Persistence:</strong> The attacker establishes persistence mechanisms to maintain access for future operations.</li>
<li><strong>Impact:</strong> The attacker achieves their objective, which could be data theft, system disruption, or financial gain. The lack of focus on TTD/TTR means the breach goes unnoticed until significant damage is done.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>The use of poor metrics can lead to a significant increase in dwell time, allowing attackers more time to achieve their objectives. Organizations may experience data breaches, financial losses, reputational damage, and regulatory fines. The NCSC observed SOCs with great potential rendered entirely ineffective through poor choice and application of metrics. If &ldquo;time to close a ticket&rdquo; is prioritized, analysts may quickly dismiss alerts as false positives, missing crucial indicators of a real attack.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Implement TTD/TTR as primary metrics to measure SOC effectiveness, using red/purple teaming to generate data.</li>
<li>Prioritize hypothesis-led threat hunting to proactively identify potential threats and improve detection capabilities.</li>
<li>Establish and maintain hard thresholds for false positive rates to minimize alert fatigue and ensure analysts focus on genuine threats.</li>
<li>Evaluate and refine detection rules to maximize true positives and minimize false positives.</li>
<li>Focus on the value of collected logs rather than sheer volume to ensure relevant data is available for threat detection.</li>
<li>Develop detection rules based on understanding likely attackers and their techniques mentioned in the overview.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>soc</category><category>metrics</category><category>threat-hunting</category><category>detection</category></item></channel></rss>