<style>pre { line-height: 125%; } td.linenos .normal { color: #6e7681; background-color: #0d1117; padding-left: 5px; padding-right: 5px; } span.linenos { color: #6e7681; background-color: #0d1117; padding-left: 5px; padding-right: 5px; } td.linenos .special { color: #e6edf3; background-color: #6e7681; padding-left: 5px; padding-right: 5px; } span.linenos.special { color: #e6edf3; background-color: #6e7681; padding-left: 5px; padding-right: 5px; } .codehilite .hll { background-color: #6e7681 } .codehilite .c { color: #8b949e; font-style: italic } /* Comment */ .codehilite .err { color: #f85149 } /* Error */ .codehilite .esc { color: #e6edf3 } /* Escape */ .codehilite .g { color: #e6edf3 } /* Generic */ .codehilite .k { color: #ff7b72 } /* Keyword */ .codehilite .l { color: #a5d6ff } /* Literal */ .codehilite .n { color: #e6edf3 } /* Name */ .codehilite .o { color: #ff7b72; font-weight: bold } /* Operator */ .codehilite .x { color: #e6edf3 } /* Other */ .codehilite .p { color: #e6edf3 } /* Punctuation */ .codehilite .ch { color: #8b949e; font-style: italic } /* Comment.Hashbang */ .codehilite .cm { color: #8b949e; font-style: italic } /* Comment.Multiline */ .codehilite .cp { color: #8b949e; font-weight: bold; font-style: italic } /* Comment.Preproc */ .codehilite .cpf { color: #8b949e; font-style: italic } /* Comment.PreprocFile */ .codehilite .c1 { color: #8b949e; font-style: italic } /* Comment.Single */ .codehilite .cs { color: #8b949e; font-weight: bold; font-style: italic } /* Comment.Special */ .codehilite .gd { color: #ffa198; background-color: #490202 } /* Generic.Deleted */ .codehilite .ge { color: #e6edf3; font-style: italic } /* Generic.Emph */ .codehilite .gr { color: #ffa198 } /* Generic.Error */ .codehilite .gh { color: #79c0ff; font-weight: bold } /* Generic.Heading */ .codehilite .gi { color: #56d364; background-color: #0f5323 } /* Generic.Inserted */ .codehilite .go { color: #8b949e } /* Generic.Output */ .codehilite .gp { color: #8b949e } /* Generic.Prompt */ .codehilite .gs { color: #e6edf3; font-weight: bold } /* Generic.Strong */ .codehilite .gu { color: #79c0ff } /* Generic.Subheading */ .codehilite .gt { color: #ff7b72 } /* Generic.Traceback */ .codehilite .g-Underline { color: #e6edf3; text-decoration: underline } /* Generic.Underline */ .codehilite .kc { color: #79c0ff } /* Keyword.Constant */ .codehilite .kd { color: #ff7b72 } /* Keyword.Declaration */ .codehilite .kn { color: #ff7b72 } /* Keyword.Namespace */ .codehilite .kp { color: #79c0ff } /* Keyword.Pseudo */ .codehilite .kr { color: #ff7b72 } /* Keyword.Reserved */ .codehilite .kt { color: #ff7b72 } /* Keyword.Type */ .codehilite .ld { color: #79c0ff } /* Literal.Date */ .codehilite .m { color: #a5d6ff } /* Literal.Number */ .codehilite .s { color: #a5d6ff } /* Literal.String */ .codehilite .na { color: #e6edf3 } /* Name.Attribute */ .codehilite .nb { color: #e6edf3 } /* Name.Builtin */ .codehilite .nc { color: #f0883e; font-weight: bold } /* Name.Class */ .codehilite .no { color: #79c0ff; font-weight: bold } /* Name.Constant */ .codehilite .nd { color: #d2a8ff; font-weight: bold } /* Name.Decorator */ .codehilite .ni { color: #ffa657 } /* Name.Entity */ .codehilite .ne { color: #f0883e; font-weight: bold } /* Name.Exception */ .codehilite .nf { color: #d2a8ff; font-weight: bold } /* Name.Function */ .codehilite .nl { color: #79c0ff; font-weight: bold } /* Name.Label */ .codehilite .nn { color: #ff7b72 } /* Name.Namespace */ .codehilite .nx { color: #e6edf3 } /* Name.Other */ .codehilite .py { color: #79c0ff } /* Name.Property */ .codehilite .nt { color: #7ee787 } /* Name.Tag */ .codehilite .nv { color: #79c0ff } /* Name.Variable */ .codehilite .ow { color: #ff7b72; font-weight: bold } /* Operator.Word */ .codehilite .pm { color: #e6edf3 } /* Punctuation.Marker */ .codehilite .w { color: #6e7681 } /* Text.Whitespace */ .codehilite .mb { color: #a5d6ff } /* Literal.Number.Bin */ .codehilite .mf { color: #a5d6ff } /* Literal.Number.Float */ .codehilite .mh { color: #a5d6ff } /* Literal.Number.Hex */ .codehilite .mi { color: #a5d6ff } /* Literal.Number.Integer */ .codehilite .mo { color: #a5d6ff } /* Literal.Number.Oct */ .codehilite .sa { color: #79c0ff } /* Literal.String.Affix */ .codehilite .sb { color: #a5d6ff } /* Literal.String.Backtick */ .codehilite .sc { color: #a5d6ff } /* Literal.String.Char */ .codehilite .dl { color: #79c0ff } /* Literal.String.Delimiter */ .codehilite .sd { color: #a5d6ff } /* Literal.String.Doc */ .codehilite .s2 { color: #a5d6ff } /* Literal.String.Double */ .codehilite .se { color: #79c0ff } /* Literal.String.Escape */ .codehilite .sh { color: #79c0ff } /* Literal.String.Heredoc */ .codehilite .si { color: #a5d6ff } /* Literal.String.Interpol */ .codehilite .sx { color: #a5d6ff } /* Literal.String.Other */ .codehilite .sr { color: #79c0ff } /* Literal.String.Regex */ .codehilite .s1 { color: #a5d6ff } /* Literal.String.Single */ .codehilite .ss { color: #a5d6ff } /* Literal.String.Symbol */ .codehilite .bp { color: #e6edf3 } /* Name.Builtin.Pseudo */ .codehilite .fm { color: #d2a8ff; font-weight: bold } /* Name.Function.Magic */ .codehilite .vc { color: #79c0ff } /* Name.Variable.Class */ .codehilite .vg { color: #79c0ff } /* Name.Variable.Global */ .codehilite .vi { color: #79c0ff } /* Name.Variable.Instance */ .codehilite .vm { color: #79c0ff } /* Name.Variable.Magic */ .codehilite .il { color: #a5d6ff } /* Literal.Number.Integer.Long */</style><h1>Welcome to Spooky Sweets Candy Company</h1> <p>🥳 Today is your first day as a Junior Security Operations Center (SOC) Analyst with our company. Your primary job responsibility is to defend Spooky Sweets Candy Company and our employees from malicious cyber actors.</p> <p><img alt="image" src="https://github.com/KC7-Foundation/kc7_data/assets/129029167/ff0b5325-6419-48ad-80f8-27aae7daf06e" /></p> <p>The Spooky Sweets Candy Company is a renowned confectionery enterprise with a captivating history and a substantial global following. Founded in the early 20th century by the imaginative Wilhelmina "Willy" Whipple, the company has since evolved into a Halloween sensation. Spooky Sweets is celebrated for its inventive and spooky-themed candy creations, contributing significantly to the Halloween spirit.</p> <p>Spooky Sweets Candy Company has a series of key partners who contribute to the success of our business:</p> <table> <thead> <tr> <th>Partner Name</th> <th>Relationship</th> </tr> </thead> <tbody> <tr> <td>spoopycandysupplies.com</td> <td>spoopycandysupplies.com seems like a website dedicated to offering various supplies and accessories related to Halloween or spooky-themed candy. This might include packaging, decorations, and special ingredients for making Halloween candies.</td> </tr> <tr> <td>spookycandycompliance.biz</td> <td>spookycandycompliance.biz appears to be a domain focused on ensuring compliance with regulatory and safety standards in the candy industry, particularly for spooky or Halloween-themed confectionery products. It might provide information, resources, or services for candy manufacturers to meet these standards.</td> </tr> <tr> <td>spookysweetsuppliers.shop</td> <td>spookysweetsuppliers.shop suggests a platform that connects buyers with suppliers of a wide range of spooky or Halloween-themed sweets. This domain likely hosts an online store or marketplace for purchasing candies and related products with a spooky twist.</td> </tr> <tr> <td>spoopycandydistribution.site</td> <td>spoopycandydistribution.site seems like a website involved in the distribution of Halloween or spooky-themed candies. It may function as a distributor, connecting candy producers with retailers, or as an online store where customers can purchase these candies for various occasions.</td> </tr> </tbody> </table> <p>Spooky Sweets Candy Company has been laser-focused on broadening our customer base. Recently, though, we have been getting a lot of attention. All this extra attention has brought along some unwelcome visitors- cyber attackers! That’s why we’ve hired you! To help keep us safe!</p> <p>Like all good companies, Spooky Sweets Candy Company collects log data about the activity our employees perform on the corporate network. These security audit logs are stored in Azure Data Explorer (ADX) - a data storage service in Azure (Microsoft’s cloud). You will use the Kusto Query Language (KQL) to parse through various types of security logs. By analysing these logs, you can help us determine whether we’re being targeted by malicious actors.</p> <p>You can find full documentation on ADX here: <a href="https://docs.microsoft.com/en-us/azure/data-explorer/kusto/query/tutorial?pivots=azuredataexplorer">https://docs.microsoft.com/en-us/azure/data-explorer/kusto/query/tutorial?pivots=azuredataexplorer</a></p> <h3>Objectives</h3> <p>🧠 By the end of your first day on the job, you should be able to:</p> <ul> <li>Use the Azure Data Explorer</li> <li>Use multiple data sets to answer targeted questions </li> <li>Investigate cyber activity in logs including: email, web traffic, and server logs </li> <li>Use multiple techniques to track the activity of APTs (Advanced Persistent Threats) </li> <li>Use third party data sets to discover things about your attackers</li> <li>Make recommendations on what actions a company can take to protect themselves</li> </ul> <p><strong>The attackers have gotten a head start, so let's not waste any more time... let's get to work!</strong></p> <p>You can find all the links you on the left sidebar of the the KC7 scoreboard. </p> <h3>Legend</h3> <blockquote> <p>🎯Key Point – Occasionally, you will see a dart emoji with a “key point.” These signal explanations of certain concepts that may enhance your understanding of key cybersecurity ideas that are demonstrated in the game. </p> <p>🤔Question – “Thinking” emojis represent questions that will enable you to demonstrate mastery of the concepts at hand. You can earn points by entering your responses to questions from section 3 in the scoring portal available at kc7cyber.com/scoreboard.</p> <p>🤫 Hint – “Whisper” emojis represent in-game hints. These hints will guide you in the right direction in answering some of the questions.</p> </blockquote> <h2>Section 1: The Walkthrough</h2> <h4>Getting Set Up in Azure Data Explorer (ADX)</h4> <p>ADX is the primary tool used in the Spooky Sweets Candy Company SOC for data exploration and analysis. The great thing about ADX is that it is used by cyber analysts at many of the smallest and largest organizations in the world. </p> <p>Let’s get you logged in and started with ADX:</p> <ol> <li>Look on the left sidebar of the scoreboard</li> </ol> <p>On the training module page, you’ll see a button that says <strong>Query Data (ADX)</strong>. Click this and it will redirect you to ADX! (Note: You’ll probably be asked to login with a Microsoft account. You can use an existing personal or organization-issued Microsoft account, or create a new one for free.)</p> <p>Once you login, you should see a cluster called <em>“kc7001.eastus”</em> has already been added to your account.</p> <p>Data in ADX is organized in a hierarchical structure which consists of <strong>clusters</strong>, <strong>databases</strong>, and <strong>tables</strong>.</p> <p><img alt="Untitled-8" src="https://github.com/KC7-Foundation/kc7_data/assets/31902160/fae8970c-27d9-4865-b6a3-fa97480a08e5" /></p> <p>All of Spooky Sweets Candy Company’s security logs are stored in a single database – the Spooky Sweets Candy Company database. </p> <ol> <li>Select your database. <ul> <li>Expand the dropdown arrow next to the Spooky Sweets Candy Company database.</li> <li>Click on the <strong>Spooky Sweets Candy Company</strong> database. Once you’ve done this, you should see the database highlighted- this means you’ve selected the database and are ready to query the tables inside.</li> </ul> </li> </ol> <p>Note: It’s very important that you use the Spooky Sweets Candy Company database for all questions while you’re investigating activity at Spooky Sweets Candy Company! If you choose the wrong database, you won’t be able to answer questions correctly. You can click the "favorite" button next to the query bar to highlight only the SpookySweets database.</p> <p><img alt="image" src="https://github.com/KC7-Foundation/kc7_data/assets/31902160/b246c8d1-6041-47e1-824b-d39d290319a1" /></p> <p>The big space to the right of your cluster list is the <em>query workspace</em>. That’s where you’ll actually write the queries used to interact with our log data.</p> <p><img alt="Untitled-9" src="https://github.com/KC7-Foundation/kc7_data/assets/31902160/384c3f1c-d6ed-4001-a187-6409e215a6c8" /></p> <p>Currently, you’ll see there’s a message there welcoming you to Spooky Sweets Candy Company! Click the blue Run button above the query workspace to run your first query! Once you’ve done that, you can erase the welcome message by highlighting it and pressing backspace or delete on your keyboard.</p> <p>Okay, enough introductions… let’s get your hands on the data.</p> <h4>First Look at the data...</h4> <p>The <strong>SpookySweets</strong> database contains nine tables. Tables contain many rows of similar data. For security logs, a single row typically represents a single thing done by an employee or a device on the network at a particular time.</p> <p>We currently have nine types of log data. As you’ll see in ADX, each log type corresponds to a table that exists in the <strong>SpookySweets</strong> database:</p> <table> <thead> <tr> <th><strong>Table Name</strong></th> <th><strong>Description</strong></th> </tr> </thead> <tbody> <tr> <td>Employees</td> <td>Contains information about the company’s employees</td> </tr> <tr> <td>Email</td> <td>Records emails sent and received by employees</td> </tr> <tr> <td>InboundNetworkEvents</td> <td>Records inbound network events including browsing activity from the Internet to devices within the company network</td> </tr> <tr> <td>OutboundNetworkEvents</td> <td>Records outbound network events including browsing activity from within the company network out to the Internet</td> </tr> <tr> <td>AuthenticationEvents</td> <td>Records successful and failed logins to devices on the company network. This includes logins to the company’s mail server.</td> </tr> <tr> <td>FileCreationEvents</td> <td>Records files stored on employee’s devices</td> </tr> <tr> <td>ProcessEvents</td> <td>Records processes created on employee’s devices</td> </tr> <tr> <td>PassiveDns (External)</td> <td>Records IP-domain resolutions</td> </tr> <tr> <td>SecurityAlerts</td> <td>Records security alerts from an employee’s device or the company’s email security system</td> </tr> </tbody> </table> <blockquote> <p>🎯<strong>Key Point – Over the Horizon (OTH) data</strong>: One of the tables listed above is not like the others – <strong>PassiveDns</strong>. Rather than being an internal security log, PassiveDns is a data source that we’ve purchased from a 3rd party vendor. Not all malicious cyber activity happens within our company network, so sometimes we depend on data from other sources to complete our investigations.</p> </blockquote> <p>You’ll learn more about how to use each of these datasets in just a minute. First, let’s just run some queries so you can practice using KQL and ADX.</p> <h4>KQL 101</h4> <p>Type the following query in the workspace to view the first rows in the <strong>Employees</strong> table. Press “run” or “shift + enter” to execute the query.</p> <div class="codehilite"><pre><span></span><code><span class="n">Employees</span> <span class="o">|</span><span class="w"> </span><span class="n">take</span><span class="w"> </span><span class="mi">10</span> </code></pre></div> <p>This query has a few parts. Let’s take a moment to break each of them down:</p> <p><img alt="Diagram Description automatically generated with low confidence" src="https://lh4.googleusercontent.com/y7YpmVbUlak4wMrI43nYzAqieamRnwiANLJzy8UsxHHaYJI5SlJVpTdz4EO47A-g0SVI77ehgZxHB13AZXLKKX02Yr40VZmFsb3blZgHCojeD-vS34SS24yWWqK6rnduGNdhmnXlCAQAMWETrm7_hg" /></p> <table> <thead> <tr> <th><strong>Query Component</strong></th> <th><strong>Description</strong></th> </tr> </thead> <tbody> <tr> <td>Table Name</td> <td>The table name specifies which table/data source the query will pull data from. All queries must start with a table.</td> </tr> <tr> <td>Pipe character (&#124;)</td> <td>The pipe character indicates the start of a new part of the query. A pipe will be added automatically after typing a table name and pressing enter. You can also add a pipe character manually by holding shift and pressing the backslash (&#92;) key. That’s the one just below the backspace key.</td> </tr> </tbody> </table> <p>The <strong>take</strong> operator is a powerful tool you can use to explore rows in a table, and therefore better understand what kinds of data are stored there.</p> <blockquote> <p>🎯<strong>Key Point – What to do when you don’t know what to do</strong>: Whenever you are faced with an unfamiliar database table, the first thing you should do is sample its rows using the <strong>take</strong> operator. That way, you know what fields are available for you to query and you can guess what type of information you might extract from the data source.</p> </blockquote> <p>The Employees table contains information about all the employees in our organization. In this case, we can see that the organization is named “Spooky Sweets Candy Company” and the domain is “spookysweets.xyz”.</p> <blockquote> <ol> <li>🤔 Try it for yourself! Do a <strong>take</strong> 10 on all the other tables to see what kind of data they contain.</li> </ol> </blockquote> <p>Make sure you record your answer to all the questions from KQL 101 in the scoreboard at kc7cyber.com/scoreboard</p> <p>You can easily write multiple queries in the same workspace tab. To do this, make sure to separate each query by an empty line. Notice below how we have separated the queries for the <strong>Employees</strong>, <strong>Email</strong>, and <strong>OutboundNetworkEvents</strong> tables by adding empty lines between them.</p> <div class="codehilite"><pre><span></span><code><span class="n">Email</span> <span class="o">|</span><span class="w"> </span><span class="n">take</span><span class="w"> </span><span class="mi">10</span> <span class="n">Employees</span> <span class="o">|</span><span class="w"> </span><span class="n">take</span><span class="w"> </span><span class="mi">10</span> <span class="n">OutboundNetworkEvents</span> <span class="o">|</span><span class="w"> </span><span class="n">take</span><span class="w"> </span><span class="mi">10</span> </code></pre></div> <p>When you have multiple queries, it’s important to tell ADX which query you want to run. To choose a query, just click on any line that is part of that query. </p> <p><strong>Finding Out “How Many”: The count Operator</strong></p> <p>We can use <strong>count</strong> to see how many rows are in a table. This tells us how much data is stored there.</p> <div class="codehilite"><pre><span></span><code><span class="n">Employees</span> <span class="o">|</span><span class="w"> </span><span class="k">count</span> </code></pre></div> <ol> <li>🤔How many employees are in the company?</li> </ol> <p><strong>Filtering Data With the <em>where</em> Operator</strong></p> <p>So far, we’ve run queries that look at the entire contents of the table. Often in cybersecurity analysis, we only want to look at data that meets a set of conditions or criteria. To accomplish this, we apply filters to specific columns.</p> <p>We can use the <strong>where</strong> operator in KQL to apply filters to a particular field. For example, we can find all the employees with the name “Jerry” by filtering on the name column in the Employees table.</p> <p><strong>where</strong> statements are written using a particular structure. Use this helpful chart below to understand how to structure a <strong>where</strong> statement.</p> <table> <thead> <tr> <th><strong>where</strong></th> <th><strong>field</strong></th> <th><strong>operator</strong></th> <th><strong>"value"</strong></th> </tr> </thead> <tbody> <tr> <td>where</td> <td>name</td> <td>has</td> <td>"Jerry"</td> </tr> </tbody> </table> <div class="codehilite"><pre><span></span><code><span class="n">Employees</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">name</span><span class="w"> </span><span class="n">has</span><span class="w"> </span><span class="ss">&quot;Jerry&quot;</span> </code></pre></div> <p>The <strong>has</strong> operator is useful here because we’re looking for only a partial match. If we wanted to look for an employee with a specific first and last name (an exact match), we’d use the == operator:</p> <div class="codehilite"><pre><span></span><code><span class="n">Employees</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">name</span><span class="w"> </span><span class="o">==</span><span class="w"> </span><span class="ss">&quot;Jerry Blake&quot;</span> </code></pre></div> <blockquote> <ol> <li>🤔Each employee at Spooky Sweets Candy Company is assigned an IP address. Which employee has the IP address: “10.10.0.251”?</li> </ol> </blockquote> <p>Here are some additional operators we like to use:</p> <table> <thead> <tr> <th>Operator</th> <th>Description</th> <th>Case-Sensitive</th> <th>Example (yields true)</th> </tr> </thead> <tbody> <tr> <td>==</td> <td>Equals</td> <td>Yes</td> <td>"aBc" == "aBc"</td> </tr> <tr> <td>!=</td> <td>Not equals</td> <td>Yes</td> <td>"abc" != "ABC"</td> </tr> <tr> <td>=~</td> <td>Equals</td> <td>No</td> <td>"abc" =~ "ABC"</td> </tr> <tr> <td>contains</td> <td>Right-hand-side (RHS) occurs as a subsequence of left-hand-side (LHS)</td> <td>No</td> <td>"FabriKam" contains "BRik"</td> </tr> <tr> <td>has</td> <td>RHS is a whole term in LHS</td> <td>No</td> <td>"North America" has "america"</td> </tr> <tr> <td>has_all</td> <td>Same as has but works on all of the elements</td> <td>No</td> <td>"North and South America" has_all("south", "north")</td> </tr> <tr> <td>has_any</td> <td>Same as has but works on any of the elements</td> <td>No</td> <td>"North America" has_any("south", "north")</td> </tr> <tr> <td>in</td> <td>Equals to any of the elements</td> <td>Yes</td> <td>"abc" in ("123", "345", "abc")</td> </tr> </tbody> </table> <p>While performing their day-to-day tasks, Spooky Sweets Candy Company employees send and receive emails. A record of each of these emails is stored in the <strong>Email</strong> table.</p> <blockquote> <p>🎯<strong>Key Point – User Privacy and Metadata</strong>: As you can imagine, some emails are highly sensitive. Instead of storing the entire contents of every email sent and received within the company in a database that can be easily accessed by security analysts, we only capture email metadata. </p> </blockquote> <p>Email metadata includes information like: the time the email was sent, the sender, the recipient, the subject line, and any links the email may contain. Storing only email metadata, rather than entire contents, helps protect the privacy of our employees, while also ensuring that our security analysts can keep us safe. Sometimes even metadata can reveal sensitive information, so it’s important that you don’t talk about log data with other employees outside the SOC.</p> <p>We can find information about the emails sent or received by a user by looking for their email address in the sender and recipient fields of the <strong>Email</strong> table. For example, we can use the following query to see all the emails sent by “Jerry Blake”:</p> <div class="codehilite"><pre><span></span><code><span class="n">Email</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">sender</span><span class="w"> </span><span class="o">==</span><span class="w"> </span><span class="ss">&quot;jerry_blake@spookysweets.xyz&quot;</span> </code></pre></div> <blockquote> <ol> <li>🤔How many emails did Timothy Moran receive?</li> </ol> </blockquote> <p><strong>Easy as 1, 2, 3… Compound Queries and the distinct Operator</strong></p> <p>We can use the <strong>distinct</strong> operator to find unique values in a particular column. We can use the following query to determine how many of the organization’s users sent emails.</p> <div class="codehilite"><pre><span></span><code><span class="n">Email</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">sender</span><span class="w"> </span><span class="n">has</span><span class="w"> </span><span class="ss">&quot;spookysweets.xyz&quot;</span> <span class="o">|</span><span class="w"> </span><span class="k">distinct</span><span class="w"> </span><span class="n">sender</span> <span class="o">|</span><span class="w"> </span><span class="k">count</span> </code></pre></div> <p>This is our first time using a multi-line query with multiple operators, so let’s break it down:</p> <p>In line 2, we take the Email table and filter the data down to find only those rows with “spookysweets.xyz” in the sender column.</p> <p>In line 3, we add another pipe character ( | ) and use the distinct operator to find all the unique senders. Here, we aren’t finding the unique senders for all of the email senders, but only the unique senders that are left after we apply the filter looking for rows with “spookysweets.xyz” in the sender column.</p> <p>Finally, in line 4, we add another pipe character ( | ) and then use the count operator to count the results of lines 1-3 of the query.</p> <ol> <li>🤔How many distinct senders were seen in the email logs from spoopycandysupplies.com?</li> </ol> <p><strong>Tracking Down a Click: OutboundNetworkEvents Data</strong></p> <p>When employees at Spooky Sweets Candy Company browse to a website from within the corporate network, that browsing activity is logged. This is stored in the <strong>OutboundNetworkEvents</strong> table, which contains records of the websites browsed by each user in the company. Whenever someone visits a website, a record of it is stored in the table. However, the user’s name is not stored in the table, only their IP address is recorded. There is a 1:1 relationship between users and their assigned IP addresses, so we can reference the <strong>Employees</strong> table to figure out who browsed a particular website. When a user visits a site, sometimes data from a lot of other sources are loaded as well. For example, images, assets, and other content may be hosted on content delivery network (CDN), which is used to deliver and load content quickly on a website. Sometimes, advertisements will also load from a particular website as well.</p> <p>If we want to figure out what websites Michael Dawson visited, we can find their IP address from the Employees table.</p> <div class="codehilite"><pre><span></span><code><span class="n">Employees</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">name</span><span class="w"> </span><span class="o">==</span><span class="w"> </span><span class="ss">&quot;Michael Dawson&quot;</span> </code></pre></div> <p>The query above tells us their IP address is “10.10.0.83”. We can take their IP address and look in the <strong>OutboundNetworkEvents</strong> table to determine what websites they visited.</p> <div class="codehilite"><pre><span></span><code><span class="n">OutboundNetworkEvents</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">src_ip</span><span class="w"> </span><span class="o">==</span><span class="w"> </span><span class="ss">&quot;10.10.0.83&quot;</span> </code></pre></div> <blockquote> <ol> <li>🤔How many unique websites did “Michael Dawson” visit?</li> </ol> </blockquote> <p><strong>What’s in a Name? All about Passive DNS Data</strong></p> <p>Although domain names like “google.com” are easy for humans to remember, computers don’t know how to handle them. So, they convert them to machine readable IP addresses. Just like your home address tells your friends how to find your house or apartment, an IP address tells your computer where to find a page or service hosted on the internet.</p> <blockquote> <p>🎯<strong>Key Point – Practice Good OPSEC</strong>: If we want to find out which IP address a particular domain resolves to, we could just browse to it. But, if the domain is a malicious one, you could download malicious files to your corporate analysis system or tip off the attackers that you know about their infrastructure. As cybersecurity analysts, we must follow procedures and safeguards that protect our ability to track threats. These practices are generally called operational security, or OPSEC.</p> </blockquote> <p>To eliminate the need to actively resolve (that is- directly browse to or interact with a domain to find it’s related IP address) every domain we’re interested in, we can rely on passive DNS data. Passive DNS data allows us to safely explore domain-to-IP relationships, so we can answer questions like:</p> <ul> <li><em>Which IP address does this domain resolve to?</em></li> <li><em>Which domains are hosted on this IP address?</em></li> <li><em>How many other IPs have this domain resolved to?</em></li> </ul> <p>These domain-to-IP relationships are stored in our <strong>PassiveDns</strong> table.</p> <blockquote> <ol> <li>🤔 How many domains in the PassiveDns records contain the word “Halloween”? (hint: use the contains operator instead of has. If you get stuck, do a take 10 on the table to see what fields are available.)</li> <li>🤔 What IPs did the domain “halloween-infrastructure.com” resolve to (enter any one of them)?</li> </ol> </blockquote> <p><strong>🤯Let statements – making your life a bit easier:</strong></p> <p>Sometimes we need to use the output of one query as the input for a second query. The first way we can do this is by manually typing the results into the next query.</p> <p>For example, what if we want to look at all the web browsing activity from employees named “James”?</p> <p>First, you would need to go into the <strong>Employees</strong> table and find the IP addresses used by these employees.</p> <div class="codehilite"><pre><span></span><code><span class="n">Employees</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">name</span><span class="w"> </span><span class="n">has</span><span class="w"> </span><span class="ss">&quot;James&quot;</span> </code></pre></div> <p><img alt="" src="https://lh5.googleusercontent.com/Ul2NZuxCWG8Wg3zIGBjTSrUQHeNJ7b_cPKWSqvqGrkptYJ8F0Y4-qtoTcR8OtjJGzQaCqdyDe9_fJDSXOm58hWdgvNYqvteckmtEvq51WIjYrxXIIi-rdGUSIZ0eSYon7mOoL2jFrmu-" /></p> <p>Then, you could manually copy and paste these IPs into a query against the <strong>OutboundNetworkEvents</strong> table. Note that we can use the in operator to choose all rows that have a value matching any value from a list of possible values. In other words, the == (comparison) operator looks for an exact match, while the in operator checks for any values from the list</p> <div class="codehilite"><pre><span></span><code><span class="n">OutboundNetworkEvents</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">src</span><span class="o">-</span><span class="n">ip</span><span class="w"> </span><span class="k">in</span><span class="w"> </span><span class="p">(</span><span class="ss">&quot;192.168.1.132&quot;</span><span class="p">,</span> <span class="w"> </span><span class="ss">&quot;192.168.3.128&quot;</span><span class="p">,</span> <span class="w"> </span><span class="ss">&quot;192.168.1.70&quot;</span><span class="p">,</span> <span class="w"> </span><span class="ss">&quot;192.168.1.92&quot;</span><span class="p">,</span> <span class="w"> </span><span class="ss">&quot;192.168.0.147&quot;</span><span class="p">,</span> <span class="w"> </span><span class="ss">&quot;192.168.1.50&quot;</span><span class="p">,</span> <span class="w"> </span><span class="ss">&quot;192.168.0.163&quot;</span><span class="p">,</span> <span class="w"> </span><span class="ss">&quot;192.168.2.200&quot;</span><span class="p">)</span> </code></pre></div> <p>Although this is a valid way to get the information you need, it may not be as elegant (or timely) if you had 100 or even 1000 employees named “James.”</p> <p>We can accomplish this in a more elegant way by using a <a href="https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/letstatement">let statement,</a> which allows us to assign a name to an expression or a function. We can use a let statement here to save and give a name to the results of the first query so that the values can be re-used later. That means we don’t have to manually type or copy and paste the results repeatedly.</p> <div class="codehilite"><pre><span></span><code><span class="n">let</span><span class="w"> </span><span class="n">james_ips</span><span class="w"> </span><span class="o">=</span><span class="w"> </span> <span class="n">Employees</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">name</span><span class="w"> </span><span class="n">has</span><span class="w"> </span><span class="ss">&quot;James&quot;</span> <span class="o">|</span><span class="w"> </span><span class="k">distinct</span><span class="w"> </span><span class="n">ip_addr</span><span class="p">;</span> <span class="n">OutboundNetworkEvents</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">src_ip</span><span class="w"> </span><span class="k">in</span><span class="w"> </span><span class="p">(</span><span class="n">james_ips</span><span class="p">)</span> </code></pre></div> <p>On the left of the let statement is the variable name (“james_ips” in this case). The variable name can be whatever we want, but it is helpful to make it something meaningful that can help us remember what values it is storing.</p> <div class="codehilite"><pre><span></span><code><span class="hll"><span class="n">let</span><span class="w"> </span><span class="n">james_ips</span><span class="w"> </span><span class="o">=</span><span class="w"> </span> </span><span class="n">Employees</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">name</span><span class="w"> </span><span class="n">has</span><span class="w"> </span><span class="ss">&quot;James&quot;</span> <span class="o">|</span><span class="w"> </span><span class="k">distinct</span><span class="w"> </span><span class="n">ip_addr</span><span class="p">;</span> <span class="n">OutboundNetworkEvents</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">src_ip</span><span class="w"> </span><span class="k">in</span><span class="w"> </span><span class="p">(</span><span class="n">james_ips</span><span class="p">)</span> </code></pre></div> <p>On the right side of the let statement in the expression you are storing. In this case, we use the <strong>distinct</strong> operator to select values from only one column – so they are stored in an array – or list of values.</p> <div class="codehilite"><pre><span></span><code><span class="n">let</span><span class="w"> </span><span class="n">james_ips</span><span class="w"> </span><span class="o">=</span><span class="w"> </span> <span class="hll"><span class="n">Employees</span> </span><span class="hll"><span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">name</span><span class="w"> </span><span class="n">has</span><span class="w"> </span><span class="ss">&quot;James&quot;</span> </span><span class="hll"><span class="o">|</span><span class="w"> </span><span class="k">distinct</span><span class="w"> </span><span class="n">ip_addr</span><span class="p">;</span> </span><span class="n">OutboundNetworkEvents</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">src_ip</span><span class="w"> </span><span class="k">in</span><span class="w"> </span><span class="p">(</span><span class="n">james_ips</span><span class="p">)</span> </code></pre></div> <p>The <strong>let</strong> statement is concluded by a semi-colon.</p> <div class="codehilite"><pre><span></span><code><span class="n">let</span><span class="w"> </span><span class="n">james_ips</span><span class="w"> </span><span class="o">=</span><span class="w"> </span> <span class="n">Employees</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">name</span><span class="w"> </span><span class="n">has</span><span class="w"> </span><span class="ss">&quot;James&quot;</span> <span class="hll"><span class="o">|</span><span class="w"> </span><span class="k">distinct</span><span class="w"> </span><span class="n">ip_addr</span><span class="p">;</span> </span><span class="n">OutboundNetworkEvents</span> <span class="o">|</span><span class="w"> </span><span class="k">where</span><span class="w"> </span><span class="n">src_ip</span><span class="w"> </span><span class="k">in</span><span class="w"> </span><span class="p">(</span><span class="n">james_ips</span><span class="p">)</span> </code></pre></div> <p>After we store the value of a query into a variable using the <strong>let</strong> statement, we can refer to it as many times as we like in the rest of the query. The stored query does not show any output. Remember, however, that your KQL query must have a tabular statement – which means that you must have another query following your <strong>let</strong> statement.</p> <blockquote> <ol> <li>🤔 How many unique URLs were browsed by employees named “Karen”?</li> </ol> <p>🎯<strong>Key Point – Pivoting:</strong> Part of being a great cyber analyst is learning how to use multiple data sources to tell a more complete story of what an attacker has done. We call this “pivoting.” We pivot by taking one known piece of data in one dataset and looking in a different dataset to learn something we didn’t already know. You practiced this here when we started in one dataset – the Employees table – and used knowledge from there to find related data in another source – OutboundNetworkEvents.</p> </blockquote> <h2>Section 2: Start Hunting!</h2> <p>You’ve finished your training and you’re ready to get to work protecting Spooky Sweets Candy Company. </p> <p>Work with your team to complete as many challenge questions from the remaining sections in the scoreboard as possible! The goal is to score as many points as you can. There are a lot of questions (the attackers have been busy), so you probably won’t be able to answer them all. Just do as many as you can!</p> <p>As you answer the questions, we will take you on a journey exploring the data and discovering what actions the adversaries have taken. However, you should remember that this is only one of many paths you can take through the data. As you go, don’t forget to pay attention to the details along the way. What patterns do the attackers exhibit that could help you track them better? Do they like to use certain words, themes? Or do they make mistakes? Keeping track of these patterns will help you build the full picture of what happened. </p> <p>Use the provided <a href="[https://docs.google.com/document/d/1rZR4eVG886oPziG-5nGeQ5kN_q5Bpq0m/edit?usp=sharing&amp;ouid=105873493764084037775&amp;rtpof=true&amp;sd=true](https://docs.google.com/document/d/14OMSq-CGa4K-royu3SxgKm-XKDwu15OJCKG-PHFbskI/edit?usp=sharing)">Actor Preview</a> document to keep track of what you know about the attacker. Building a good profile, timelining the attacker’s activity, and forming a list of indicators of compromise (IOCs) will help you keep track of the attacker. KC7 models some of the techniques used by these attackers from real world threat actors, so it may be a helpful resource for you in the future when you are investigating a real security incident. </p> <p><img alt="image" src="https://github.com/KC7-Foundation/kc7_data/assets/9474932/47f32215-4632-48f6-af2b-dcd00080978a" /></p> <p>Now, get out there and keep us safe! The whole company is counting on you. No pressure😊.</p> <h2>Resources</h2> <p>Understanding KQL operators: <a href="https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/datatypes-string-operators">https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/datatypes-string-operators</a></p>