<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jasmehr Kaur on Medium]]></title>
        <description><![CDATA[Stories by Jasmehr Kaur on Medium]]></description>
        <link>https://medium.com/@jasmehrkaur?source=rss-98137d69ded4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*cAiXP7WUctTr_r6iwEG2rg@2x.jpeg</url>
            <title>Stories by Jasmehr Kaur on Medium</title>
            <link>https://medium.com/@jasmehrkaur?source=rss-98137d69ded4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 23:11:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jasmehrkaur/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How Does Your Email Prove It’s Really From You?]]></title>
            <link>https://medium.com/@jasmehrkaur/how-does-your-email-prove-its-really-from-you-d85495e57d7e?source=rss-98137d69ded4------2</link>
            <guid isPermaLink="false">https://medium.com/p/d85495e57d7e</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cisco]]></category>
            <category><![CDATA[email-security]]></category>
            <category><![CDATA[dmarc]]></category>
            <category><![CDATA[phishing-email]]></category>
            <dc:creator><![CDATA[Jasmehr Kaur]]></dc:creator>
            <pubDate>Wed, 15 Jul 2026 16:07:22 GMT</pubDate>
            <atom:updated>2026-07-15T16:07:22.505Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Understanding SPF, DKIM &amp; DMARC through a Real Email Journey</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Aw4BmH-SDvfrn6Ws5E7hsw.png" /></figure><p>In the previous article, we followed an email from the moment you clicked <strong>“Send”</strong> until it finally reached the recipient’s inbox.</p><p>Along the way, we explored SMTP, DNS, MX records, mail servers, and how protocols like STARTTLS help protect emails while they’re travelling across the Internet.</p><p>In this article, we will address an important question- “<strong>How does the recipient’s mail server know that an email claiming to be from </strong><strong>ceo@company.com was actually sent by the CEO—and not by an attacker pretending to be them?”</strong></p><h3>Step 1: The Problem — SMTP Doesn’t Verify Identity</h3><pre>From: ceo@company.com<br><br>Subject: Share client documents urgently<br><br>Hi,<br><br>Please send me all the documents with client data before 3PM<br><br>Thanks,<br>CEO</pre><p>At first glance, everything looks legitimate.</p><p>The sender appears to be your CEO, the email address looks correct, and there’s nothing obviously suspicious.</p><p>So how do modern mail servers separate legitimate emails from impersonated ones?</p><blockquote>The original <strong>Simple Mail Transfer Protocol (SMTP)</strong> was designed to <strong>deliver</strong> emails — not to <strong>verify who sent them</strong>. Its primary job is simply to accept the message and deliver it to the next server.</blockquote><p>That’s where <strong>SPF</strong>, <strong>DKIM</strong>, and <strong>DMARC</strong> come in.</p><p>Together, they provide a way to verify the identity of the sender before an email is trusted.</p><h3>Step 2: One Email, Two Different Sender Identities</h3><p>Let’s take this example for an instance:</p><pre>From: support@amazon.com<br><br>Subject: Your package has shipped</pre><p>To you, the sender is clearly <strong>support@amazon.com</strong>.</p><p>During the SMTP conversation, the sending server says something like:</p><pre>MAIL FROM:&lt;bounce@amazonses.com&gt;<br>RCPT TO:&lt;alice@example.com&gt;</pre><p>The address used during SMTP (<strong>MAIL FROM</strong>) is <strong>not the same</strong> as the address you see in your inbox (<strong>From:</strong>).</p><h3>The two identities are:</h3><p><strong>1. Envelope Sender (MAIL FROM)</strong></p><p>This exists only during SMTP transmission.</p><p>Mail servers use it for:</p><ul><li>Bounce messages</li><li>Delivery status notifications</li><li>SPF validation</li></ul><p>Users normally never see it.</p><p><strong>2. Header From</strong></p><p>This is the address displayed in your email client.</p><p>It’s what you see in Gmail, Outlook, Apple Mail, etc.</p><p>It represents the sender’s identity from the user’s perspective.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eTNjIYtHEmL3E4pnmAEvfA.png" /></figure><blockquote>Many organizations use third-party services like Amazon SES, SendGrid, or Microsoft 365 to send emails on their behalf. So, having a different email in Mail From part could be completely normal.</blockquote><p>Without additional verification, SMTP alone has no way to answer if it should trust the mail or not.</p><p>That’s exactly why modern email authentication standards exist.</p><blockquote><strong>SPF</strong> checks whether the server sending the email is allowed to send on behalf of a domain.</blockquote><blockquote><strong>DKIM</strong> verifies that the message hasn’t been modified.</blockquote><blockquote><strong>DMARC</strong> ensures these authentication checks align with the sender you actually see.</blockquote><p>We’ll start with <strong>SPF</strong>, because it’s the first check most receiving mail servers perform.</p><h3>Step 3: SPF — Is This Server Allowed to Send This Email?</h3><p>Since email has an <strong>Envelope Sender (MAIL FROM), </strong>suppose an email arrives from:<br>MAIL FROM: <a href="/service/mailto:bounce@example.com">bounce@example.com</a></p><p>So how do you know the server that sent this email is actually authorized by <strong>example.com</strong>?<br>That’s exactly what <strong>SPF (Sender Policy Framework)</strong> does.</p><blockquote>SPF is an email authentication standard that allows a domain owner to specify <strong>which mail servers are permitted to send email for their domain</strong>.</blockquote><p>This information is published as a <strong>DNS TXT record</strong>, making it publicly available for any receiving mail server to verify.</p><pre>example.com<br><br>TXT &quot;v=spf1 ip4:192.0.2.10 include:_spf.google.com -all&quot;</pre><p>To break it down:<br>v= spf1 (spf version)<br>ip4:192.0.2.10 (This IP is allowed to send mail)<br>include:_spf.google.com (Google Workspace servers are also allowed)<br>-all (reject every other servers)</p><p>Now when the mail comes from support@example.com, the receiving server performs a DNS lookup for the SPF record of <strong>example.com</strong>.</p><p>If the sender’s IP matches one of the authorized entries, the SPF check passes, otherwise it fails.</p><p>But there’s a catch- SPF verifies <strong>where the email came from</strong>. It does <strong>not</strong> verify what users actually see in their inbox.</p><p>For example:</p><pre>MAIL FROM: attackerdomain.com<br>From: support@example.com</pre><p>If <strong>attackerdomain.com</strong> has a valid SPF record, SPF may still pass — even though the visible sender is pretending to be <strong>example.com</strong>. That’s because SPF checks the <strong>Envelope Sender</strong>, not the <strong>Header From</strong>.</p><p>This is where <strong>DKIM</strong> enters the picture.</p><h3>Step 4: DKIM — Has This Email Been Tampered With?</h3><p>Suppose you receive an email that appears to come from your bank.</p><p>The sender’s mail server is authorized by SPF, so the SPF check passes.</p><p>But how do you know nobody modified the email while it was travelling across the Internet?</p><blockquote><strong>DKIM</strong> allows the sending mail server to <strong>digitally sign</strong> every outgoing email. It generates a unique cryptographic signature based on selected parts of the message — such as the body and important headers.</blockquote><p>Example:</p><pre>DKIM-Signature:<br>v=1;<br>d=example.com;<br>s=selector1;<br>bh=...<br>b=...</pre><p>When the email reaches the recipient’s mail server, it performs these steps:<br>1. Reads the <strong>DKIM-Signature</strong> header.<br>2. Extracts the domain (<strong>d=example.com</strong>).<br>3. Performs a DNS lookup to retrieve the public key.<br>4. Uses that key to verify the digital signature.<br>If everything matches, the message hasn’t been modified. If even a single signed character changes, the signature becomes invalid.</p><p>But <strong>DKIM</strong> proves that:<br>the message wasn’t modified after it was signed, and it was signed using the sending domain’s private key.</p><p>There’s still another question:<br><strong>Is the domain that signed the email the same domain the user actually sees in the “From” field?</strong></p><p>That’s where the last step <strong>DMARC </strong>comes into play.</p><pre>Sender<br>   │<br>   ▼<br>Sign Email 🔑<br>   │<br>   ▼<br>Email Travels<br>   │<br>   ▼<br>Receiver<br>   │<br>   ▼<br>Verify Signature<br>   │<br> ┌───────┴────────┐<br> │                │<br>✔ Signature OK   ✖ Signature Invalid<br>Email Trusted    Email Modified</pre><h3>Step 5: DMARC — Bringing SPF and DKIM Together</h3><p>From the previous examples:<br>If you receive email from:<br>From: <a href="/service/mailto:support@amazon.com">support@amazon.com</a></p><p>Behind the scenes the email contains:<br>MAIL FROM: attackerdomain.com</p><p>and</p><p>DKIM d=attackerdomain.com<br>So techincally,<br>DKIM passes and<br>SPF passes</p><blockquote><strong>DMARC (Domain-based Message Authentication, Reporting and Conformance)</strong> doesn’t replace SPF or DKIM.</blockquote><p>Instead, it adds:<br>Do the authenticated domains match the domain the user actually sees in the “From” address?<br>This is called alignment</p><p><strong>Alignment </strong>refers to at least <strong>one</strong> of SPF or DKIM must align with the visible <strong>From</strong> domain:</p><p>Example:</p><p>Suppose if user sees:<br>From: <a href="/service/mailto:support@example.com">support@example.com</a></p><p>A valid email might look like this:</p><pre>Header From:<br>support@example.com<br><br>MAIL FROM:<br>bounce@example.com<br><br>DKIM d=example.com</pre><p>Since everything belongs to <strong>example.com</strong>, so DMARC passes.</p><p>So if DMARC fails, it has 3 policies:</p><blockquote>✅ p=none (Monitor only. Deliver the email but generate reports.)<br>⚠ p=quarantine (Treat the email as suspicious, usually sending it to Spam.)<br>❌ p=reject (Reject the email before it reaches the recipient.)</blockquote><p>Without DMARC, attackers could easily spoof well-known brands by displaying a trusted <strong>From</strong> address while authenticating with their own domain.</p><blockquote>Enterprise email security solutions — such as Cisco Secure Email, Microsoft Defender for Office 365, and Proofpoint — use these authentication results as one of the first trust signals before performing deeper analysis of phishing attempts, malware, URL, and attachment analysis.</blockquote><p>So to summarise:</p><pre>                Incoming Email<br>                      │<br>        ┌─────────────┴─────────────┐<br>        ▼                           ▼<br>     SPF Pass                  DKIM Pass<br>        │                           │<br>        └─────────────┬─────────────┘<br>                      ▼<br>           Does it match the<br>          visible From domain?<br>                      │<br>              ┌───────┴────────┐<br>              ▼                ▼<br>           YES ✅            NO ❌<br>      Deliver Email      Reject / Spam</pre><p>In Part 3, we’ll follow an email after authentication and explore how modern email security solutions detect phishing, malware, and other threats before they ever reach the user.</p><p>Thank you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d85495e57d7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Really Happens After You Click “Send”?]]></title>
            <link>https://medium.com/@jasmehrkaur/what-really-happens-after-you-click-send-2f03db52063c?source=rss-98137d69ded4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f03db52063c</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[smtp]]></category>
            <category><![CDATA[email-security]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Jasmehr Kaur]]></dc:creator>
            <pubDate>Sat, 11 Jul 2026 17:27:47 GMT</pubDate>
            <atom:updated>2026-07-11T17:27:47.343Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Following an Email Across the Internet, from SMTP to Inbox</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YW7VyrDZS-X_xMV13vmsTg.png" /></figure><p>Every day, billions of emails are sent across the Internet.</p><p>Whether it’s a meeting invitation, a password reset link, an online shopping receipt, or a simple message to a friend, we send emails with a single click on <strong>“Send.”</strong></p><p>Within a few seconds, the message appears in the recipient’s inbox — almost as if it travelled there instantly.</p><p>But did it?</p><p>Behind that single click lies an entire ecosystem of protocols, DNS lookups, mail servers, routing decisions, and transport encryption working together to deliver one simple message.</p><p>In this article, we’ll follow the complete journey of an email — from the moment you click <strong>Send</strong> until it finally reaches the recipient’s inbox.</p><h3>Step 1: You Click “Send”</h3><p>Imagine you’ve just finished writing an important email to your manager. You attach the presentation, review the recipient’s email address one last time, and finally click <strong>“Send.”</strong></p><p>From your perspective, the job is done.</p><p>Within a fraction of a second, the email disappears from the compose window and moves to your <strong>Sent</strong> folder (or <strong>Outbox</strong>, depending on your email client).</p><p>The first stop on its journey isn’t the recipient’s inbox — it’s your <strong>Mail User Agent (MUA)</strong>.</p><blockquote>A <strong>Mail User Agent (MUA)</strong> is simply the application you use to compose, send, receive, and organize emails. Whether you’re using <strong>Gmail</strong>, <strong>Microsoft Outlook </strong>or<strong> Apple Mail</strong>, you’re interacting with an MUA.</blockquote><p>Its responsibility is limited to creating the email and handing it over to the next component in the email delivery chain — the <strong>Mail Submission Agent (MSA)</strong>.</p><p>The <strong>MSA</strong> acts as the first server responsible for accepting your email and preparing it for delivery. From this point onward, the email leaves your device and enters the global email infrastructure, where a series of servers and protocols work together to deliver it to the correct destination.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0t1kD6Tgjic2dVdVkoAfbQ.png" /></figure><h3>Step 2: The First Conversation — SMTP Takes Over</h3><p>Once the Mail Submission Agent (MSA) accepts your email, it needs a standardized way to communicate with other mail servers.</p><p>This is where <strong>Simple Mail Transfer Protocol (SMTP)</strong> comes into play.</p><blockquote><strong>SMTP</strong> is the application-layer protocol responsible for sending emails across the Internet. Think of it as the common language that mail servers use to exchange messages. Regardless of who your email provider is, every outgoing email relies on SMTP to begin its journey.</blockquote><p>A simplified SMTP conversation looks like this:</p><pre>Client: EHLO mail.example.com<br>Server: 250 Hello<br><br>Client: MAIL FROM:&lt;alice@example.com&gt;<br>Server: 250 OK<br><br>Client: RCPT TO:&lt;bob@company.com&gt;<br>Server: 250 OK<br><br>Client: DATA<br>Server: 354 Start mail input<br><br>Client: [Email Body]<br>Server: 250 Message accepted for delivery<br><br>Client: QUIT</pre><blockquote><strong>EHLO</strong> Introduces the sending server and advertises supported SMTP features. <br><strong>MAIL FROM</strong> Specifies the sender’s email address (the SMTP envelope sender).<br><strong>RCPT TO</strong> Identifies the intended recipient. Multiple recipients can be specified by repeating this command.<br><strong>DATA</strong> Indicates that the email headers and body are about to be transmitted.<br><strong>QUIT</strong> Gracefully terminates the SMTP session.</blockquote><h3>Step 3: Finding the Recipient — The Role of DNS and MX Records</h3><p>At this point, your email has been accepted by the Mail Submission Agent (MSA) and is ready to leave your email provider.</p><p>But there’s one problem- The sending server knows <strong>who</strong> the recipient is (bob@company.com), but it doesn&#39;t yet know <strong>where</strong> to deliver the email.</p><p>Mail servers rely on the <strong>Domain Name System (DNS)</strong> to discover where an email should be delivered.</p><p>The sending mail server extracts the domain name:</p><pre>company.com</pre><p>It then performs a <strong>DNS lookup</strong> to ask “Which mail server is responsible for receiving emails for company.com?”</p><p>The answer comes in the form of an <strong>MX (Mail Exchange) record</strong>.</p><blockquote>An MX record tells the sending server which mail server is responsible for accepting emails on behalf of a domain. It can also specify multiple mail servers with different priorities, allowing email delivery to continue even if one server becomes unavailable.</blockquote><p>Example MX record:</p><pre>company.com<br><br>MX 10 mail1.company.com<br>MX 20 mail2.company.com</pre><p>Since <strong>mail1.company.com</strong> has the lower priority value, the sending server attempts to deliver the email there first. If that server is unavailable, it automatically retries using <strong>mail2.company.com</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zo1TIY7PY6qAGKj0kKfuMg.png" /></figure><h3>Step 4: Travelling Through Mail Transfer Agents (MTAs)</h3><p>With the destination mail server identified through DNS, the email is ready to begin its journey across the Internet.</p><p>But contrary to what many people imagine, an email doesn’t always travel directly from the sender’s mail server to the recipient’s mail server.</p><p>Instead, it may pass through one or more <strong>Mail Transfer Agents (MTAs)</strong> before reaching its destination.</p><blockquote>An <strong>MTA</strong> is a mail server responsible for receiving emails from another mail server and forwarding them closer to their final destination. In other words, MTAs act like relay stations, ensuring that emails are routed efficiently and reliably across the Internet.</blockquote><p>Each <strong>MTA</strong> performs basic checks before forwarding the email, such as validating the SMTP conversation, ensuring the next destination is reachable, and determining the best route toward the recipient’s mail server.</p><p>Only after successfully passing through these relay servers does the email arrive at the recipient’s mail infrastructure, where it is prepared for final delivery into the recipient’s mailbox.</p><p>At this point, the email has successfully reached the recipient’s mail server. The only thing left is to place it into the correct mailbox so the recipient can finally read it.</p><h3>Step 5: The Final Stop — Delivering the Email to the Inbox</h3><p>After successfully travelling across the Internet, the email finally arrives at the recipient’s mail server.</p><p>However, reaching the destination server doesn’t immediately mean the email appears in the recipient’s inbox.</p><p>The final responsibility belongs to the <strong>Mail Delivery Agent (MDA)</strong>.</p><blockquote>An <strong>MDA</strong> is responsible for taking an incoming email and placing it into the correct mailbox. It determines where the recipient’s mailbox is located, stores the message, and makes it available for the recipient to access using their preferred email client.</blockquote><p>From the user’s perspective, the email has finally completed its journey.</p><p>For a quick visual recap:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sHrZ6w6qg2gZ47vELLR3dQ.png" /></figure><p>But there’s one important question we haven’t answered yet…</p><blockquote>What prevents someone from intercepting your email while it’s travelling across the Internet?</blockquote><h3>Step 6: Securing the Journey — How STARTTLS Protects Your Email</h3><p>When SMTP was originally introduced in the early 1980s, security wasn’t a primary concern. The protocol was designed for a much smaller and more trusted Internet, meaning emails were transmitted in <strong>plain text</strong>.</p><p>Anyone capable of intercepting the traffic could potentially read the contents of the email.</p><p>To address this, modern mail servers support <strong>STARTTLS</strong>.</p><p>Rather than creating a separate protocol, <strong>STARTTLS</strong> is an extension to SMTP that upgrades an existing connection from <strong>unencrypted</strong> to <strong>encrypted</strong> using <strong>Transport Layer Security (TLS)</strong>.</p><pre>Client: EHLO mail.example.com<br>Server: 250-STARTTLS<br><br>Client: STARTTLS<br>Server: 220 Ready to start TLS<br><br>🔒 Encrypted connection established<br><br>MAIL FROM:<br>RCPT TO:<br>DATA</pre><p>However, there’s an important limitation-</p><p><strong>STARTTLS encrypts the communication channel — it does not verify who actually sent the email.</strong></p><p>That raises another important question.</p><blockquote>How does a mail server know that an email claiming to be from bank@example.com was actually sent by that organization—and not by an attacker pretending to be them?</blockquote><p>We’ll answer that in the Part 2 of this series, where we’ll explore <strong>SPF, DKIM, and DMARC</strong>, the technologies that make modern email authentication possible!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f03db52063c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Malware Analysis]]></title>
            <link>https://medium.com/@jasmehrkaur/malware-analysis-0516a082690b?source=rss-98137d69ded4------2</link>
            <guid isPermaLink="false">https://medium.com/p/0516a082690b</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[malicious-software]]></category>
            <category><![CDATA[threat-detection]]></category>
            <category><![CDATA[malware-analysis]]></category>
            <dc:creator><![CDATA[Jasmehr Kaur]]></dc:creator>
            <pubDate>Mon, 25 Aug 2025 11:59:29 GMT</pubDate>
            <atom:updated>2025-08-25T12:09:50.382Z</atom:updated>
            <content:encoded><![CDATA[<p>Analysing malicious files as a malware/SOC analyst</p><p>Let’s start with an example. Ever heard of <strong>STUXNET</strong>?</p><p>The US and Israeli intelligence services created Stuxnet to disrupt Iran’s nuclear work. This malware, which was first detected in 2010, remains a complex structure even today.</p><p>Let’s look at the diagram below to understand how it worked:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*jlZiB7i3Bg2b8jOB.jpg" /><figcaption>source: letsdefend.io</figcaption></figure><p>Impact of malware is very high even if you are not very close to technology.</p><h4>What is Malware and its types:</h4><p>The term <em>Malware</em> comes from combining the words <strong>MALicious</strong> and <strong>softWARE</strong>. It refers to software designed with harmful intent, aiming to compromise the security and integrity of systems.</p><p>Once the malware is analyzed, it can be classified under one of these categories based on its purpose, functionality, or characteristics:</p><ul><li><strong>Backdoor</strong>- A backdoor is created on the infected device, giving the attacker a hidden entry point into the system. For instance, by opening a network port linked to a shell, the attacker can use this port to establish a connection and gain access to the system.</li><li><strong>Adware- </strong>This usually accompanies downloaded programs and displays unwanted advertisements on the device. Although not all adware is malicious, certain variants can modify settings such as the default search engine.</li><li><strong>Ransomware- </strong>This type of malware has become very common in the past few years. It locks or steals the files on your device by encrypting them and then asks you to pay money (a ransom) to get them back.</li><li><strong>Virus- </strong>One of the earliest forms of malware, viruses are so common that people often use the word “virus” to describe all kinds of malware. A key feature of a virus is its ability to replicate itself by infecting other files on the device, which helps it stay active and spread.</li><li><strong>Worm- </strong>This type of malware is called a worm because it spreads from one infected device to many others on its own. A well-known example is <em>WannaCry</em>, which took advantage of the MS17–010 vulnerability and created worldwide panic.</li><li><strong>Rootkit- </strong>This malware hides itself while giving attackers high-level control or administrative access to the device.</li><li><strong>RAT (Remote Access Trojan):</strong> This type of malware lets an attacker take complete control of the infected device, allowing them to use it as if it were their own.</li><li><strong>Keylogger:</strong> This malware records every keystroke made on the device and secretly sends that information to the attacker.</li></ul><blockquote>A malware may contain more than one feature, so a malware can belong to more than one category. For example, WannaCry malware includes features of both worm and ransomware malware</blockquote><h4>Approaches that can be taken to analyse a malware:</h4><p>While working in the defensive field, malware analysis becomes a regular task</p><p>Different approaches to analyse malware are:</p><ol><li>Static Analysis</li><li>Dynamic Analysis</li></ol><h4>What is Static Analysis?</h4><p>This approach utilises reverse engineering to analyse malicious software without actually running them.</p><p>This is generally done by decompiling the malware, analysing each step when the malware is executed, hence observing its behaviour.</p><blockquote>This process does not affect the device as malware is not run in static analysis, however it is not recommended to run it on your host device; run it in a virtual machine</blockquote><p>Information analysed in static analysis:</p><ul><li>P.E. (Portable Executable) Headers</li><li>Imported DLL’s (Dynamic Link Libraries)</li><li>Exported DLL’s</li><li>Strings in binary</li><li>CPU instructions</li></ul><blockquote>It is advisable to go through the Operating System Architecture and Fundamentals for better understanding of malware analysis</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hh6jCTb1wnIQrfYD.gif" /><figcaption>source:<a href="https://docs.hex-rays.com/release-notes/6_0">https://docs.hex-rays.com/release-notes/6_0</a></figcaption></figure><h4>What is Dynamic Analysis?</h4><p>In this approach, software is analysed by running it on the operating system.</p><p>Applications that can examine registry, file, network and process events are installed in the system, and their behaviour is examined by running malicious software.</p><p>Information analysed should be:</p><ul><li>Network connections</li><li>File Events</li><li>Process Events</li><li>Registry Events</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/961/0*o6OZDhqlL5y8GQEp.png" /><figcaption>Eg. of Process Events</figcaption></figure><blockquote>There is no preferrable method, as a full analysis is important for a full report. But in case of faster results, you can opt for dynamic analysis.</blockquote><p>We can use AnyRun (an interactive sandbox) to analyse malware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AC__Pgi3fJm9fNr2.png" /><figcaption>AnyRun interface for uploading</figcaption></figure><p>A file containing malware can be uploaded on the “Choose a file” option. After it’s done, we can select parameters such as operating system and 32/64 bit of OS we want to run. Finally, we can click on “Run” to open up the virtual OS.</p><blockquote>Some malware remains inactive for a while before carrying out its harmful actions, which makes it harder to analyze. To study it properly, we need to give the malware enough time to reveal its behavior</blockquote><p>Taking the below analysis in AnyRun as an example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/862/0*_X6TqZmah9pksVEt.png" /><figcaption>source:letsdefend.io</figcaption></figure><p>We can see two child processes created, “schtasks.exe” and “agenttesla”. The second one is marked as malware on AnyRun.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/0*qJ34ZD50ThTMJxSK.png" /></figure><p>When we see detailed view of the process 2680, we see that it is marked as malicious</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/0*BElO1jCDXShAqsyx.png" /></figure><p>When we analyse the process marked as agenttesla(process 3140) by AnyRun, we observe that it steals credentials from web browsers, looks rewritten by another process, reads browser cookies, and creates files in user directory.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oovT1e08fhX-TWV0.png" /></figure><p>After checking more about the process 3140 by entering the full process name in network analysis, it is found that it exfiltrates data with SMTP protocol.</p><p>There are a lot more features to explore and many more softwares/websites that can help you!</p><p>A list of a few of them are below:</p><ul><li>Analyz</li><li>Any.run</li><li>Hybrid Anlaysis</li><li>Cuckoo</li><li>Manalyzer</li></ul><p>I hope this is something that intrigues you!</p><p>Always up to connect for further discussions :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0516a082690b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Web attacks and detection]]></title>
            <link>https://medium.com/@jasmehrkaur/web-attacks-and-detection-5504795a0105?source=rss-98137d69ded4------2</link>
            <guid isPermaLink="false">https://medium.com/p/5504795a0105</guid>
            <category><![CDATA[detecting-web-attacks]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[security-awareness]]></category>
            <category><![CDATA[web-attack]]></category>
            <dc:creator><![CDATA[Jasmehr Kaur]]></dc:creator>
            <pubDate>Fri, 04 Jul 2025 05:52:09 GMT</pubDate>
            <atom:updated>2025-07-04T16:39:59.759Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Is your internet browsing safe?</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/728/0*Hn1Q-tdqdk6F8ffP.png" /></figure><p><strong>What are web attacks?</strong></p><p>A lot of our browsing includes accessing web applications on a daily basis. Google, Facebook, YouTube, LinkedIn and many more are all accessed over the web.</p><p>Web apps are the interface to to many organisations and are one of the prime targets for attackers to exploit and steal our information.</p><p><strong>A few examples of attacks on web apps are as follows:</strong></p><ul><li>SQL Injection</li><li>Cross site scripting</li><li>Command Injection</li><li>IDOR</li><li>Local and Remote File inclusion</li><li>File Upload (web shell)</li></ul><p>Before diving deep into all of the attacks, let’s understand about OWASP</p><blockquote>The <strong>Open Worldwide Application Security Project (OWASP)</strong> is a non-profit foundation dedicated to improving software security.</blockquote><p>Every few years, <strong>OWASP</strong> publishes a list of the <strong>10 web application vulnerabilities</strong> that pose the most critical security risks. The latest release was in 2021 at the time of writing.</p><p>Kindly refer the link and image below for full information:</p><p><a href="https://owasp.org/www-project-top-ten/">OWASP Top Ten Web Application Security Risks | OWASP Foundation</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/936/0*gGPJW9NtDfHp_4kK.png" /></figure><p>Now let’s discuss about all the attacks in detail:</p><ol><li><strong><em>SQL Injection</em></strong></li></ol><p><strong>SQL Injection</strong> is a critical web vulnerability where unsanitized user input is directly embedded into <strong>SQL queries</strong>, allowing attackers to manipulate the database and potentially access sensitive data.</p><p><strong>Types of SQL Injections</strong></p><ul><li><strong>In-brand SQLi (Classic SQLi)</strong>: When an SQL query is sent and responded to on the same channel, we call this in-band SQLi.</li><li><strong>Inferential SQLi (Blind SQLi): </strong>SQL queries that receive a response that cannot be seen are called Inferential SQLi. They are also called “Blind SQLi” because the response cannot be seen.</li><li><strong>Out of band SQLi: </strong>If the response to an SQL query is communicated through another channel, this type of SQLi is called “out-of-band SQLi”.</li></ul><p>How does the attacker exploit through SQL query?</p><p>A user is typically expected to enter their <strong>username</strong> and <strong>password</strong> on a login page. The web application then uses this information to construct an SQL query like this:</p><pre>SELECT * FROM users WHERE username = &#39;USERNAME&#39; AND password = &#39;USER_PASSWORD&#39;;</pre><p>To explain the above query in simple words, it means displaying all the information from the database whose name is <strong>USERNAME </strong>and password is <strong>USER_PASSWORD</strong>. If the database matches, the attacker is successful, if not- they fail.</p><p>But what if they enter it like this:</p><pre>SELECT * FROM users WHERE username = ‘’ OR 1=1;</pre><p>The above query will mean if the username is empty or 1=1(which is always true) so this query will be executed.</p><p><strong>Detecting SQL attacks from user’s perspective:</strong></p><ul><li>Look for SQL keywords(“Insert”, “Select”, “Where”)</li><li>Check any special characters(‘),(-) or paranthesis</li><li>Familiarise with common payloads</li></ul><p><strong><em>2. Cross Site Scripting (XSS) attack</em></strong></p><p><strong>XSS</strong> is a <strong>web vulnerability</strong> where attackers inject malicious scripts (usually JavaScript) into webpages viewed by other users. These scripts can steal session cookies, redirect users, or manipulate page content — all without the user’s knowledge.</p><p><strong>Types of XSS:</strong></p><ul><li><strong>Reflected XSS(Non-Persistent)</strong>- The most common type. Payload should be present in the request</li><li><strong>Stored XSS (Persistent)- </strong>The most dangerous. Attacker can permanently upload XSS payload into web app</li><li><strong>DOM Based XSS-</strong> Attack where the malicious code runs in the victim’s browser because the website’s JavaScript changes the page content (DOM) in an unexpected way</li></ul><pre>&lt;script&gt;window.location=’https://google.com’&lt;/script&gt;</pre><p>In the above payload, attacker can enter any malicious website and redirect you to that page.</p><p>XSS is a result of lack of data sanitation. When the value entered by the user is not validated, the attacker can enter any JavaScript code and get the result they want.</p><p><strong>Detecting XSS attack from user’s perspective:</strong></p><ul><li>Look for keywords(“”alert” and “script”)</li><li>Learn about commonly used XSS payloads</li><li>Check for special characters(“&gt;”,”&lt;”)</li></ul><p><strong>3. Command Injection</strong></p><p><strong>Command injection attacks</strong> are attacks that occur when data received from a user is not sanitized and is passed directly to the operating system shell.</p><pre>cp hostsys;ls;.txt</pre><p>The above example command can be broken down into three commands:<br>1. Copy process in the host sys</p><p>2. Directory listing command</p><p>3. Tries to run a command .txt</p><p>But if in the same way the following command is written:</p><pre>hostsys;shutdown;.txt</pre><p>A command like this can shut down the Operating Sys and the web app won’t be able to function.</p><p><strong>Detecting Command Injection attacks from user’s perspective:</strong></p><ul><li>When examining a web request, look at all areas</li><li>Look for keywords related to the terminal language(“dir”,”ls”,”cp”,”cat”)</li><li>Learn about commonly used command injection payloads</li></ul><p><strong>4. Insecure Direct Object Reference (IDOR)</strong></p><p>Caused by the absence or improper use of an authorization mechanism. It allows one person to access an object that belongs to another.</p><blockquote>IDOR, or “Broken Access Control”, is the number one web application vulnerability listed in the 2021 OWASP.</blockquote><pre>https://hostsys.io/get_user_information?id=1</pre><p>In the above query, If my id is 1 then I will access my information correctly but if the id field is 2 or 3 and it is not checked, then anyone can access the information for other users.</p><p><strong>Detecting IDOR attacks from user’s perspective:</strong></p><ul><li>Check all the parameters</li><li>Look at the number of requests made to the same page (Check for brute-force attacks)</li><li>Try to find a pattern (Check for consective id requests and higher number of requests)</li></ul><p><strong>5. Local and Remote File Inclusion (RFI and LFI)</strong></p><p>Occurs when a file is included in an attack in which data obtained from user is not santized.</p><p><strong>In LFI</strong>- File that is intended to be included is on the same web server that the web application is hosted on.</p><p><strong>In RFI</strong>- The included file is hosted on another server.</p><pre>&lt;?php<br>  $language= $_GET[&quot;language&quot;];<br>  include(&quot;website/$language/home.php&quot;);<br>?&gt;</pre><p>In the above query, If a normal input is given for language like “IN” , then we will see the file below:</p><p><strong>“website/IN/home.php”</strong></p><p>But if a payload is entered in that field, then the web app will display the <strong>“/etc/passwd”</strong> file to the user.</p><p>Payload:<strong> /../../../../../../../../../etc/passwd%00</strong></p><p>“website/<strong>/../../../../../../../../../etc/passwd%00</strong>/home.php”</p><p>The end of the string will be “%0” is to hide the rest of “/home.php” from being read by the web app.</p><p><strong>Detecting LFI and RFI attacks from user’s perspective:</strong></p><ul><li>Look for any special characters(“/”,”.”,”\”)</li><li>Look for acronyms such as HTTP and HTTPS</li></ul><p>These were some of the known web attacks that can be very harmful if you are not careful.</p><p>Obviously one can dive deep into them, I have only discussed some of the main points.</p><p>Hope you liked it! Thank you :)</p><p><strong>Content and images reference- letsdefend.io</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5504795a0105" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Phishing Email Analysis]]></title>
            <link>https://medium.com/@jasmehrkaur/phishing-email-analysis-18f0b65305cc?source=rss-98137d69ded4------2</link>
            <guid isPermaLink="false">https://medium.com/p/18f0b65305cc</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[phishing-attacks]]></category>
            <category><![CDATA[email-analysis]]></category>
            <category><![CDATA[phishing-email]]></category>
            <category><![CDATA[web-security]]></category>
            <dc:creator><![CDATA[Jasmehr Kaur]]></dc:creator>
            <pubDate>Sun, 08 Jun 2025 05:58:59 GMT</pubDate>
            <atom:updated>2025-06-08T06:46:53.772Z</atom:updated>
            <content:encoded><![CDATA[<p>Don’t fall into the trap of fake emails!</p><p><strong>What is phishing?</strong></p><p>A type of attack that tries to steal your information by trying to make you click on links/download documents to your host- basically making you run malicious files on your computer.</p><p>The email can tempt you by saying “You have won Rs.XX, kindly confirm your details on the link below”</p><p>or it can also pressurize you by saying “Your KYC has expired, kindly complete your details to renew the banking services”</p><pre>Phishing falls into the &#39;Delivery&#39; Phase of the Cyber Kill Chain model<br>(Where the attacker tried to get the malicious content to the <br>target system)</pre><h3><strong>Analysing the Email</strong></h3><p>Since email don’t authenticate your identity, anyone can create an email by the name of someone else. This is called <strong>spoofing.</strong></p><p>They make you believe that the email is coming from a trusted source- could be an impersonation of a bank, company or even friends and family!</p><p>Some protocols like Sender Policy Framework (SPF) or DomainKeys Identified Mail (DKIM) are used to identify spoofed emails, but how to simplify this and take measures from our end?</p><p><strong>Checking an Email manually:</strong></p><ul><li>The <strong>SMTP</strong> address of the mail should firstly be identified. This can be done by a tool like <strong>Mxtoolbox: </strong><a href="https://mxtoolbox.com/EmailHeaders.aspx">https://mxtoolbox.com/EmailHeaders.aspx</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IeWXXvJIWo8_ZMo_0hRpPg.png" /><figcaption>Credit: letsdefend.io</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C9HwTIKS61qMo2zo3i9_6w.png" /></figure><ul><li>Almost all companies use their own mail servers which have their own IP addresses, you can try looking if that IP belongs to the correct institution by checking the <strong>whois </strong>records of SMTP IP address</li></ul><p><strong>Parameters to check in an email:</strong></p><ul><li>Sender address (naukri.com (for example))</li><li>IP is correctly mapped to that address(<a href="https://mxtoolbox.com/SuperTool.aspx?action=mx%3anaukri.com&amp;run=toolpage#">52.101.144.0</a> in this case)</li><li>domain base (.io/.com/.co.in/.gov)</li><li>Subject (sender address and SMTP address may constantly be changing)</li></ul><h3>Reading the Email Header</h3><p>Everyone is familiar with fields like To, From, Date and Subject in an email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xU34Ye2sRW4wvCk8m9fjgg.png" /></figure><p><strong>Let’s refer to the screenshot above and learn about other important fields:</strong></p><p><strong>Return-Path: </strong>This email header field is also known as Reply-To. When you reply to an email, the reply is sent to the address specified in the Return-Path field</p><p>Note that the ‘Reply-to’ and ‘Return-Path’ fields contain different values. We expect to reply to the same email we have received the mail from, right?</p><p>In this case, if the email or name matches the person who actually works at the impersonated organization, the email inserts the real address in reply-to section so that the fake email will not stand out when the email is replied to</p><p><strong>Message-ID: </strong>A unique combination of letters and numbers that identifies each email. No two emails will have the same Message ID</p><p><strong>Received: </strong>The Received section lists each mail server that an email has passed through before arriving in the recipient’s inbox. The mail server at the top is the last server the email message passed through, and the mail server at the bottom is where the email originated</p><p><strong>X-Spam status: </strong>Shows the spam score of the email. It highlights if the message is classified as spam and also shows the spam score. If the score is too high, it will automatically go into the SPAM folder</p><p>How to check these detailed headers?</p><ol><li>GMAIL- Open the Email -&gt; click on the three dots on top righ t-&gt; ”Download message”</li><li>OUTLOOK- Open the mail-&gt;File-&gt;Info-&gt;Properties-&gt;Internet headers</li></ol><h3>Static Analysis</h3><p>Attackers often hide the malicious links under colorful images/buttons/text</p><p>Check out the example below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AORrc-qhSvAAhr5XOqFHUA.png" /><figcaption>Screenshot credit: letsdefend.io</figcaption></figure><p>The actual address and the name of the URL are completely different. The actual address is seen when you hover your cursor over the link</p><blockquote>Some antivirus softwares give the old results, if a specific has already been scanned in the past. Go to the URL detector and make sure it was scanned today and not months ago!</blockquote><p><a href="https://talosintelligence.com/">Cisco Talos Intelligence</a> can provide you insights about the reputation of IP addresses, you can check if it is marked under the blacklist category:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ht7xj2ROCF4aaqsurd20Pg.png" /></figure><h3>Dynamic Analysis</h3><p>Broswers like Broswerling help you quickly check the addresses in the mail without running it on your host first. But at the same time, it doesn’t let you open any malicious file which could interrupt your analysis.</p><p>Sandbox/Virtual Machines help you to examine suspicious file without infecting your host machine!</p><p>Some popular ones are:</p><ul><li>VMRay</li><li>AnyRun</li><li>JoeSandbox</li></ul><blockquote>The malicious content could also be hidden in text or PDFs or images in an email. It is not just URLs!</blockquote><p><em>Lab credits and Screenshot credits: Letsdefend.io</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18f0b65305cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Behind the Color-Coded Teams of CyberSecurity]]></title>
            <link>https://medium.com/@jasmehrkaur/behind-the-color-coded-teams-of-cybersecurity-210942a92bcb?source=rss-98137d69ded4------2</link>
            <guid isPermaLink="false">https://medium.com/p/210942a92bcb</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cybersecurity-careers]]></category>
            <category><![CDATA[cybersecurity-awareness]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[cybersecurity-analyst]]></category>
            <dc:creator><![CDATA[Jasmehr Kaur]]></dc:creator>
            <pubDate>Tue, 27 May 2025 10:21:59 GMT</pubDate>
            <atom:updated>2025-05-27T10:21:59.110Z</atom:updated>
            <content:encoded><![CDATA[<p>Just Red and Blue teams? Or more?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*EVW6Wvs4wZDRb4wGQoA2yw.jpeg" /><figcaption><strong>Offensive vs Defensive </strong>and everything in between!</figcaption></figure><p>While the above two form the foundation of cybersecurity, there’s more to it than most people realize.</p><p>In this article, we’ll explore the full spectrum of color-coded teams and their roles in security.</p><p>Before we discuss further, here’s a graphic of the complete color spectrum:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/853/0*TzeiMTRRjll5OYGd.png" /></figure><p>While some still believe in only Red and Blue Teams, I feel knowing all the aspects is crucial for a full understanding of cybersecurity.</p><p>Let’s begin with the <strong>primary teams</strong>-</p><ul><li><strong>Blue team</strong> — the <strong>defenders</strong></li><li><strong>Red team</strong> — the <strong>attackers</strong></li><li><strong>Purple team</strong> — the <strong>collaborators</strong></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/796/0*QJ3rygX7eg6YDFym.png" /></figure><h4>THE DEFENDERS</h4><p>The <strong>Blue Team</strong> plays a critical role in defending an organization’s infrastructure against cyber threats. They’re responsible for monitoring systems, detecting suspicious activities, and responding to incidents in real time. Their main goal is to <strong>prevent</strong>, <strong>detect</strong>, and <strong>stop</strong> attacks before they can cause significant damage.</p><p>Some of the key activities of the Blue Team include:</p><ul><li>Monitoring network traffic and system logs</li><li>Managing security tools — firewalls, intrusion detection systems, etc.</li><li>Responding to and investigating security incidents</li><li>Performing risk/vulnerability assessments and system hardening by identifying potential threats</li></ul><p>A few examples of job roles that fall in Blue Team category are-</p><ul><li>Security Operations Centre(SOC) Analyst</li><li>Incident Responder</li><li>Forensic Analyst</li><li>Threat Hunter</li><li>Security Engineer</li></ul><h4><strong>THE ATTACKERS</strong></h4><p>The <strong>Red Team</strong> acts like ethical hackers hired to test an organization’s security by simulating real cyberattacks. Their goal is to find vulnerabilities — whether in software, networks, or even people — that could be exploited by the “bad guys”.</p><p>By thinking like attackers and attempting to break the secure systems, the Red Team helps organizations identify weak points before real criminals can. They use a variety of techniques, including technical hacking, social engineering, and sometimes testing physical security measures.</p><p><strong>Key Activities of the Red Team:</strong></p><ul><li>Performing penetration tests to discover security gaps</li><li>Running social engineering campaigns to test employee awareness</li><li>Simulating realistic attack scenarios to evaluate defenses</li><li>Testing physical security by attempting unauthorized access</li></ul><p>Examples of job roles include:</p><ul><li>Penetration Tester (Ethical Hacker)</li><li>Social Engineer</li><li>Exploit Developer</li></ul><h4>THE COLLABORATORS</h4><p>The Purple Team acts as a bridge between the Red and Blue, combining <strong>offensive</strong> and <strong>defensive</strong> skills to improve overall security. Their main role is to ensure that the insights gained from the Red Team’s attacks are effectively shared with the Blue Team defenders.</p><p>By promoting collaboration, this team helps organizations learn from simulated attacks and strengthen their defenses faster. They work to close gaps that attackers might exploit and make sure both teams communicate clearly and efficiently.</p><p><strong>Key Activities of the Purple Team:</strong></p><ul><li>Coordinating Red and Blue Team exercises and sharing findings.</li><li>Analyzing attack results to improve detection and response strategies.</li><li>Helping Blue Teams understand attacker methods and tactics.</li><li>Identifying security gaps and suggesting improvements on both sides.</li><li>Facilitating continuous feedback loops between the attack and defense teams.</li></ul><p>Common Purple Team Roles:</p><ul><li>Malware Analyst</li><li>Security Engineer</li><li>Threat Intelligence Specialist</li></ul><p><strong>Now that we have discussed about the foundation, let’s talk about the less known secondary teams that complete the wheel-</strong></p><ul><li><strong>Yello team</strong> — the <strong>Builders</strong></li><li><strong>Green team</strong> — the <strong>Automation Engineers</strong></li><li><strong>Orange team </strong>— the <strong>Educators</strong></li><li><strong>White team</strong> — Comprises of all the teams combined</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/606/0*7QDd3GwVkJ0KAl1y.png" /></figure><h4>THE BUILDERS</h4><p>Their main focus is on <strong>requirements</strong>, <strong>functionality</strong>, <strong>user experience</strong>, and <strong>back-end performance</strong>. Due to this, the <strong>Yellow</strong> team often has to work closely with both the <strong>Red</strong> and <strong>Blue</strong> teams, giving us the <strong>Orange</strong> and <strong>Green</strong> teams. Without this collaboration, a system designed by a <strong>Yellow</strong> team alone may be a prime target for a threat actor due to its potentially insecure design.</p><p><strong>Key Activities of the Yellow Team:</strong></p><ul><li>Writing secure code and following best practices for software development.</li><li>Performing code reviews to identify and fix security flaws early.</li><li>Integrating security features like encryption and authentication into software.</li><li>Designing system architectures with security in mind.</li><li>Educating developers on secure coding techniques and practices.</li></ul><p><strong>Common Yellow Team Roles:</strong></p><ul><li>Software Developer / Engineer</li><li>Application Security Engineer</li><li>DevSecOps Engineer</li><li>Security Architect</li></ul><h4>THE AUTOMATION ENGINEERS</h4><p>The <strong>Green Team</strong> operates at the intersection of development and security operations, ensuring that the systems and applications built by the Yellow Team are secure and that the Blue Team has the necessary visibility and tools to monitor and protect these systems effectively.</p><p>Their primary focus is to enhance security into the development process (DevSecOps) and automating security measures to enhance detection, incident response, and digital forensics capabilities.</p><p><strong>Key Responsibilities:</strong></p><ul><li><strong>Facilitating Collaboration:</strong> Bringing together the Blue and Yellow Teams for secure development.</li><li><strong>Automating Security:</strong> Integrating security checks into development pipelines (CI/CD).</li><li><strong>Enhancing Detection:</strong> Helping the Blue Teams monitor and secure the Yellow Team’s systems.</li><li><strong>Securing Code:</strong> Working with developers to adopt secure coding practices.</li></ul><p>Common Roles in the Green Team:</p><ul><li>DevSecOps Engineer</li><li>Security Automation Engineer</li><li>Security Architect</li><li>Security Analyst</li></ul><h4>THE EDUCATORS</h4><p>The Orange Team focuses on <strong>training, awareness, and building a security-first culture</strong>. Their role is to ensure that all employees understand security risks, know how to recognize threats like phishing, and follow best practices.</p><p>They design and deliver training programs, run simulated attacks (like phishing tests), and promote a mindset where everyone in the organization is aware of their role in maintaining security.</p><p><strong>Key Responsibilities:</strong></p><ul><li>Designing and delivering security awareness training.</li><li>Running phishing simulations to test and educate staff.</li><li>Promoting security best practices and policies.</li><li>Building a strong, proactive security culture.</li></ul><p>Common Roles in the Orange Team:</p><ul><li>Security Awareness Trainer</li><li>Phishing Simulation Specialist</li><li>Security Culture Advocate</li><li>Communications and Training Specialist</li></ul><h4>THE ORGANIZERS</h4><p>The White Team plays a <strong>neutral and supervisory role</strong>. They are responsible for overseeing security exercises (like Red and Blue Team tests), ensuring they follow rules, and ensuring fair play. They also document the activities, measure effectiveness, and generate reports for continuous improvement.</p><p>This team includes elements of management, compliance, analysis, and logistics. Their main goals are to provide neutrality, organize teams, set strategy, perform risk assessments, and monitor incident remediation.</p><p><strong>Key Responsibilities:</strong></p><ul><li>Setting up rules and objectives for security exercises.</li><li>Documenting results and lessons learned.</li><li>Reporting on exercise outcomes and making recommendations.</li></ul><p>Common Roles in the White Team:</p><ul><li>Security Compliance Specialist</li><li>Rules and Engagement Manager</li><li>Exercise Monitor</li></ul><p><strong>That’s all for now! I hope this gave you a clear understanding of the full cybersecurity team architecture.</strong></p><p><strong>Thanks for reading!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=210942a92bcb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cracking CISCO Ideathon]]></title>
            <link>https://medium.com/@jasmehrkaur/cracking-cisco-ideathon-40898ddcafdd?source=rss-98137d69ded4------2</link>
            <guid isPermaLink="false">https://medium.com/p/40898ddcafdd</guid>
            <category><![CDATA[ideathon]]></category>
            <category><![CDATA[cisco-ideathon]]></category>
            <category><![CDATA[cisco]]></category>
            <category><![CDATA[placement]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Jasmehr Kaur]]></dc:creator>
            <pubDate>Mon, 24 Jun 2024 13:49:49 GMT</pubDate>
            <atom:updated>2024-11-13T18:55:54.684Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Insights and reflections on How I got into Cisco</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*j8h9eZcqfmptIQkg.jpg" /></figure><p>Hey!</p><p>Just to quickly introduce myself- I’m Jasmehr Kaur, a TCE intern at Cisco and a final year B.Tech-CSE student at Manipal University Jaipur.</p><p>Networks have always fascinated me and Cisco was definitely one of my aim companies during placements. The past 6 months have undoubtedly been wonderful and the first company in corporate is always special :)</p><p>In this blog, I’ll discuss the Ideathon process as well as my personal experiences while preparing for various stages. So if you’re someone who’s interested in this field and looking to get into a company that specialises in networks, I hope you find this helpful.</p><p><strong>About Cisco Ideathon and eligibility</strong></p><p>A competitive event, the Cisco Ideathon is hosted with the objective of showcasing students’ creative thinking and problem-solving abilities. The aim is to present your approach in addressing global challenges like education, healthcare, and water conservation using technology. If selected, Cisco offers a six-month internship with a potential full-time offer to the final year students.</p><p>As for the eligibility, you need to be a final year B.Tech student with a CGPA above 6.0/10.0 and must have completed a couple of Cisco NetAcad courses according to the role you apply for.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ceRJ0LxU4IMyu5lX.jpg" /></figure><p><strong>Round 1: Online Assessment (Elimination Round)</strong></p><p>Everyone who meets the eligibility criteria, will get a chance to attempt the OA. On the starting page, there is an option to select the role you wish to appear for. In my case, I chose Technical Consulting Engineer which is basically a pure networking role. Other options include Consulting Engineer, Software Engineer, Data Engineer, etc. This blog will mainly focus on Technical Consulting Engineer role.</p><p><strong>Tip</strong>: There are more openings and better chances to get hired for Consulting and Technical Consulting roles. Software is also an excellent option but has comparatively lower intake through Ideathon. If you’re a Software person, keep an eye out for Cisco Codeathon or apply directy through the careers portal.</p><p>The format of the OA is as follows-</p><ul><li>Reasoning section (Analytical and mental ability)</li><li>Foundational Networking section</li><li>Coding section</li><li>Advance Networking section</li></ul><p><strong>Insight: </strong>There are multiple diagram based questions, so just memorizing theory won’t help- know how to apply networking concepts in a topology. In the coding section, once you have chosen a programming language, it can’t be changed. Don’t panic and waste all of the time if test cases of the code are not passing, focus more on the sections you know better- I did well in advanced networking and passed the OA without attempting the coding question perfectly. Once you click on next, you can’t go back to the previous question, so take your time.</p><p>Try to go through the NetAcad courses properly as most of the questions in the OA as well as the technical interview will be CCNA based.</p><p><strong>Ideation and PPT phase</strong></p><p>If you receive an email saying -</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cz5NX5jOb3yJ3pOdkUCaBA.png" /></figure><p>Then congratulations! You have made it to the interview and ideation round. Moving forward, you will receive a few problem statements attached with this email and a time period of 5–6 days to ideate and create a PPT on any one of them.</p><p>You will get these 5 days to ideate as well as prepare for the interviews, so try to manage time wisely!</p><p><strong>What is expected in the PPT and how much to include?</strong></p><ul><li>Do a thorough research and look for ideas that have NOT yet been implemented on any one of the challenges given</li><li>Consider all the factors- environmental, governance, monetary and tech</li><li>Interviewers look for solving problems with the company’s own technologies- so research on the current solutions provided by Cisco, their technologies and try to present your approach using them</li><li>Don’t create a mess by putting all the technologies, pick a direction and create an in-depth approach to address the problem</li><li>Think of all the corner cases and drawbacks of your approach</li><li>If solution is missing a component or implementation, include that in future scope</li><li>Before jumping directly to the solution, explain your understanding of the problem statement first</li></ul><p><strong>Resources and material for the interviews</strong></p><p>During these 5 days, you will get an email to create an inclusive resume- it means all you need to include is your technical qualifications, skills and projects.</p><p><strong>Tip: </strong>Don’t include any skill or project you are not completely sure about, anything technical or non-technical can be asked on the basis of your resume.</p><p>I have attached some of the resources to study Networking and OS during this week -</p><ul><li><a href="https://www.interviewbit.com/ccna-interview-questions/">https://www.interviewbit.com/ccna-interview-questions/</a></li><li><a href="https://www.interviewbit.com/computer-network-mcq/">https://www.interviewbit.com/computer-network-mcq/</a></li><li><a href="https://www.geeksforgeeks.org/networking-interview-questions/">https://www.geeksforgeeks.org/networking-interview-questions/</a></li></ul><p>Make full use of interviewbit, geeksforgeeks, javatpoint, etc and thoroughly read the most asked interview questions in Networking, OS and Network security.</p><p><strong>Round 2: Interviews (Technical, Managerial and HR)</strong></p><p>On the given date, all three interviews will happen on the same day. Each interview is an elimination round and can last for approximately 60–70 mins.</p><p><strong>Technical Interview-</strong></p><p>For the first 15–20 mins, I presented my idea and the problem statement. The interviewer asked a couple questions on the tech stack and future scope of my solution.</p><p>For the next one hour I was asked questions on Networking, SQL and Security (since I had mentioned databases and network security on my resume)</p><p><strong>Some of the sample questions-</strong></p><ul><li>What is router on a stick?</li><li>Explain OSI and TCP/IP layers</li><li>Difference in worm and virus</li><li>Explain the flow of a packet</li></ul><p><strong>Tip: </strong>If you’re unable to recall an answer, instead of saying “I don’t know”, try saying “Can we come back to this question later? I am trying to recall the concept”</p><p><strong>Managerial Interview-</strong></p><p>This round tests your interpersonal and communication skills. The panelist will give you situations and observe your approach to the problem and reactions to various situations. It will also include discussions and questions based on the projects mentioned in your resume, know the tech stack of your projects well.</p><p>In situational based scenarios, mould your answer and solutions according to the response or expressions of your panelist.</p><p><strong>Tip:</strong> I would recommend to research a little about Cisco, things like- main line of business, revenue, CEO and background of the company</p><p><strong>HR round-</strong></p><p>This was a basic 20–30 mins HR connect about the role and why you want to join the company. Simple questions like- Plans for masters, other offers, joining and compensation would be discussed in this round.</p><p>(Sounds simple but answer smartly, it is still an elimination round!)</p><p>After a long day of interviews, sit back and wait for the results, it might take upto 3–4 weeks for the final list to be released, so don’t lose patience, it will be worth it:)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LyTUCo7jwHW2iKgldrUr4w.png" /></figure><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40898ddcafdd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>