<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security on wriotsec</title><link>https://www.wriotsecurity.com/tags/security/</link><description>Recent content in Security on wriotsec</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 31 Jan 2023 22:12:00 +0000</lastBuildDate><atom:link href="https://www.wriotsecurity.com/tags/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Exploring Windows Event Logs and Elastic Security for Incident Response</title><link>https://www.wriotsecurity.com/posts/exploring-windows-event-logs-for-incident-response/</link><pubDate>Tue, 31 Jan 2023 22:12:00 +0000</pubDate><guid>https://www.wriotsecurity.com/posts/exploring-windows-event-logs-for-incident-response/</guid><description>
&lt;p&gt;Elastic Security is incredibly useful for threat hunting especially with the success of tools like RockNSM and the HELK project. But what about hunting through old logs aided by detection tools that threat hunters use? How feasible is it to use Elastic Security if just want to stand it up the tool and throw some data at it? In this blog we we will explore how to take advantage of Elastic Security and the open source detection rules that are bundled in each release.&lt;/p&gt;</description></item></channel></rss>