<?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 Anubhav on Medium]]></title>
        <description><![CDATA[Stories by Anubhav on Medium]]></description>
        <link>https://medium.com/@lifehacker1981_78415?source=rss-e27218c32ce0------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RWqjfHvYYXy2LP_SZK2sDw.png</url>
            <title>Stories by Anubhav on Medium</title>
            <link>https://medium.com/@lifehacker1981_78415?source=rss-e27218c32ce0------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:49:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lifehacker1981_78415/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[Detecting Web Attacks]]></title>
            <link>https://medium.com/@lifehacker1981_78415/detecting-web-attacks-5761a70c8fcd?source=rss-e27218c32ce0------2</link>
            <guid isPermaLink="false">https://medium.com/p/5761a70c8fcd</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[detecting-web-attacks]]></category>
            <category><![CDATA[offensive-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[defensive-security]]></category>
            <dc:creator><![CDATA[Anubhav]]></dc:creator>
            <pubDate>Mon, 09 Nov 2026 17:42:41 GMT</pubDate>
            <atom:updated>2026-11-09T17:42:41.595Z</atom:updated>
            <content:encoded><![CDATA[<p>Web attacks are among the most common ways attackers gain entry into target systems. Public-facing websites and web applications often sit in front of databases and other infrastructure, which are appealing targets for attackers. In this room, you’ll learn how to identify these threats using practical detection methods and industry-standard tools.</p><h3><strong>Client-side</strong> Attacks</h3><p><strong>Client-side</strong> attacks rely on abusing weaknesses in user behavior or on the user’s device. These attacks often exploit vulnerabilities in browsers or trick the user into performing unsafe actions to gain access to accounts and steal sensitive information. Valuable data can be stored on a user’s device, so a successful client-side attack can result in data loss. With the demand for dynamic and versatile web applications rising, companies are integrating more third-party plugins, broadening the attack surface in browsers, and opening more opportunities for client-side attacks.</p><p>Imagine browsing your favorite e-commerce site and clicking on an image of a product you are interested in. Unknown to you, an attacker has hidden a malicious invisible window inside the page that loads another site in the background. This hidden site runs malicious code that steals your login session cookies. Nothing seems out of the ordinary, but now the attacker is able to impersonate you and access your account!</p><h3>SOC Limitations</h3><p>The tools available to an analyst, such as server-side logs and network traffic captures, offer little to no visibility into what occurs inside a user’s browser. As discussed above, client-side attacks occur on the user’s system, meaning they can execute malicious code, steal information, or manipulate the environment without generating suspicious HTTP requests or network traffic that the SOC can see. As a result, detecting these attacks from a SOC perspective is often difficult or even impossible without additional browser-side security controls or endpoint monitoring.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VdTxJp_yHd6354eV4rH85g.png" /></figure><h3>Common Client-Side Attacks</h3><ul><li><a href="https://tryhackme.com/room/axss"><strong>Cross-Site Scripting</strong></a><strong> </strong>(<strong>XSS) </strong>is the <a href="https://www.hackerone.com/blog/how-cross-site-scripting-vulnerability-led-account-takeover">most common</a> client-side attack, in which malicious scripts are run in a trusted website and executed in the user’s browser. If your website has a comment box that doesn’t filter input, an attacker could post a comment like: Hello &lt;script&gt;alert(&#39;You have been hacked&#39;);&lt;/script&gt;. When visitors load the page, the script runs inside their browser, and the pop-up appears. In a real attack, instead of a harmless pop-up, the attacker could steal cookies or session data.</li><li><a href="https://tryhackme.com/room/csrfV2"><strong>Cross-Site Request Forgery</strong></a><strong> </strong>(CSRF): The browser is tricked into sending unauthorized requests on behalf of the trusted user.</li><li><strong>Click-jacking</strong>: Attackers overlay invisible elements on top of legitimate content, making users believe they are interacting with something safe.</li></ul><h3>Server-Side Attacks</h3><p><strong>Server-side</strong> attacks rely on exploiting vulnerabilities within a web server, the application’s code, or the backend that supports a website or a web application. While client-side attacks manipulate users’ interaction with a site, server-side attacks focus on taking advantage of the systems themselves. By exploiting flaws and vulnerabilities, server logic, misconfigurations, or input handling, attackers can gain access, steal information, and cause damage to running services.</p><h3>Catching Server-Side Attacks</h3><p>One advantage for defenders when dealing with server-side attacks is that they leave a trail of evidence, if you know where to look. Every web request sent to an application is processed by the server and is recorded in logs or other monitoring systems. These requests also travel across the network, meaning network traffic can reveal suspicious behavior.</p><h3>Catching Server-Side Attacks</h3><p>One advantage for defenders when dealing with server-side attacks is that they leave a trail of evidence, if you know where to look. Every web request sent to an application is processed by the server and is recorded in logs or other monitoring systems. These requests also travel across the network, meaning network traffic can reveal suspicious behavior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Y2GRageQ2T1i0OAW6VB4A.png" /></figure><h3>Common Server-Side Attacks</h3><ul><li><strong>Brute-Force</strong> attacks occur when an attacker repeatedly attempts different usernames or passwords in an attempt to gain unauthorized access to an account. Automated tools are often used to send these requests quickly, allowing attackers to go through large lists of credentials and common passwords. <a href="https://www.fierce-network.com/operators/t-mobile-ceo-says-hacker-used-brute-force-attacks-to-breach-it-servers">T-Mobile</a> faced a breach in 2021 that stemmed from a brute-force attack, allowing attackers access to the personally identifiable information (PII) of over 50 million T-Mobile customers.</li><li><strong>SQL Injection(SQLi)</strong> relies on attacking the database that sits behind a website and occurs when applications build queries through string concatenation instead of using parameterized queries, allowing attackers to alter the intended SQL command and access or manipulate data. In 2023, an SQLi vulnerability in <a href="https://www.akamai.com/blog/security-research/moveit-sqli-zero-day-exploit-clop-ransomware">MOVEit</a>, a file-transfer software, was exploited, affecting over 2,700 organizations, including U.S. government agencies, the BBC, and British Airways.</li><li><strong>Command Injection</strong> is a <a href="https://krishnag.ceo/blog/the-2024-cwe-top-25-understanding-and-mitigating-cwe-78-os-command-injection/">common attack</a> that occurs when a website takes user input and passes it to the system without checking it. Attackers can sneak in commands, making the server run them with the same permissions as the application.</li></ul><h3>Logs-Based Detection</h3><p>Logs can be a valuable tool for detecting web attacks. Every request sent to a web server can leave evidence in its access and error logs. Defenders can spot patterns that reveal scanning, exploitation attempts, or other attacks by reviewing log entries.</p><p><strong>Access Log Format</strong></p><p>Below is a sample access log entry. Depending on the context, each field can indicate either benign or malicious traffic. While not all access logs follow this exact format, they generally include the following information:</p><p><strong>Log Field — — — — — — — Example Indicator</strong></p><ol><li><strong>Client IP Address </strong>— A known malicious or outside of the expected geo range.</li><li><strong>Timestamp and Requested Page —</strong> Requests made at unusual hours or repeated in a short period of time.</li><li><strong>Status Code —</strong> Repeated 404 responses indicating a page could not be found.</li><li><strong>Response Size</strong> — Significantly smaller or larger than normal response sizes.</li><li><strong>Referrer — </strong>Referring pages that don’t fit normal site navigation .</li><li><strong>User-Agent — </strong>Outdated browser versions or common attack tools (e.g. sqlmap, wpscan)</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MbsDDtm9P4GS6V03YfJzvw.png" /></figure><h3><strong>Network-Based Detection</strong></h3><p><strong>Network traffic analysis</strong> allows analysts to examine the raw data exchanged between a client and a server. By capturing and inspecting packets, analysts can observe attack behavior on a more detailed level, including the underlying transport protocols and the application data itself. Network captures are more verbose than server logs, revealing the data behind every request and response. This can include full HTTP headers, POST bodies, cookies, and uploaded and downloaded files, for example.</p><p>Protocols that rely on encryption, like HTTPS and SSH, limit what can be seen in packet payloads without access to the decryption keys.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JkAQLvTRmP-QLwKI1F0A0A.png" /></figure><h3>Web-Based Detection</h3><p><strong>Web Application Firewalls (WAFs)</strong> are often the first line of defense for websites and web applications. So far in this room, we have focused on detecting and analyzing malicious activity. Now, we will shift our focus to one of the most effective mitigation tools available. WAFs act as gatekeepers for your web applications, inspecting full request packets, similar to Wireshark but with the ability to decrypt traffic and filter it before it reaches the server.</p><h3>Rules</h3><p>WAFs inspect and decide whether to allow a web request or block it entirely based on predefined rules. Let’s examine a few categories of firewall rules.</p><p><strong>Rule Type — — — — — — — — — — — — — Description</strong></p><ol><li><strong>Block common attack patterns</strong>— Blocks known malicious payloads and indicators.</li><li><strong>Deny known malicious sources — </strong>Uses IP reputation, threat intel, or geo-blocking to stop risky traffic.</li><li><strong>Rate-limiting &amp; abuse prevention —</strong> Limits request frequency to prevent abuse.</li></ol><p>Imagine you notice repeated GET requests to /changeusername with the User-Agent string sqlmap/1.9.</p><p>SQLMap is an automated tool for detecting and exploiting SQL injection vulnerabilities. After reviewing the network traffic, you see that the requests include SQLi payloads.</p><p>You might create a rule to block any User-Agent string matching sqlmap:</p><p>If User-Agent contains &quot;sqlmap&quot;<br>then BLOCK</p><p>This is a rudimentary example and modern WAFs will detect and block known suspicious User-Agents automatically. However, rules like this can be custom-made to suit your specific application or threat scenario, allowing you to block malicious activity without impacting normal site traffic.</p><h3>Integrating Known Indicators and Threat Intelligence</h3><p>Many modern WAF solutions include built-in rule sets designed to mitigate the <a href="https://owasp.org/www-project-top-ten/"><strong>OWASP Top 10</strong></a><strong> </strong>security risks, some of which we have covered previously. WAFs also leverage threat intelligence feeds to automatically block requests from known malicious IP addresses and suspicious User-Agents. They receive regular updates to combat new and emerging threats, including those from known APT groups and recently discovered CVEs. <a href="https://blog.cloudflare.com/new-waf-intelligence-feeds"><strong>Check out</strong></a><strong> </strong>how Cloudflare maintains curated IP lists, from sources like botnets, VPNs, anonymizers, and malware, based on global threat intelligence.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5761a70c8fcd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[FlareVM :Arsenal Of Tools]]></title>
            <link>https://medium.com/@lifehacker1981_78415/flarevm-arsenal-of-tools-c95f808c369c?source=rss-e27218c32ce0------2</link>
            <guid isPermaLink="false">https://medium.com/p/c95f808c369c</guid>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[flarevm]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[defensive-security]]></category>
            <dc:creator><![CDATA[Anubhav]]></dc:creator>
            <pubDate>Thu, 22 Oct 2026 18:12:13 GMT</pubDate>
            <atom:updated>2026-10-22T18:12:13.898Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*OU4f6C6beuCKIvVoreFvZg.png" /></figure><p><strong>FlareVM</strong>, or “<strong>Forensics, Logic Analysis, and Reverse Engineering</strong>,” stands out as a comprehensive and carefully curated collection of specialized tools uniquely designed to meet the specific needs of reverse engineers, malware analysts, incident responders, forensic investigators, and penetration testers. This toolkit, expertly crafted by the FLARE Team at FireEye, is a powerful aid in unravelling digital mysteries, gaining insight into malware behaviour, and delving into the complex details within executables.</p><h3>Arsenal Of Tools</h3><h3>Reverse Engineering &amp; Debugging</h3><p>Reverse engineering is like solving a puzzle backward: you take a finished product apart to understand how it works. Debugging is identifying errors, understanding why they happen, and correcting the code to prevent them.</p><ul><li><strong>Ghidra</strong> - NSA-developed open-source reverse engineering suite.</li><li><strong>x64dbg</strong> — Open-source debugger for binaries in x64 and x32 formats.</li><li><strong>OllyDbg</strong> — Debugger for reverse engineering at the assembly level.</li><li><strong>Radare2</strong> — A sophisticated open-source platform for reverse engineering.</li><li><strong>Binary Ninja</strong> — A tool for disassembling and decompiling binaries.</li><li><strong>PEiD</strong> — Packer, cryptor, and compiler detection tool.</li></ul><h3>Disassemblers &amp; Decompilers</h3><p>Disassemblers and Decompilers are crucial tools in malware analysis. They help analysts understand malicious software’s behaviour, logic, and control flow by breaking it into a more understandable format. The tools mentioned below are commonly used in this category.</p><ul><li><strong>CFF Explorer</strong> — A PE(Portable Executable) editor designed to analyze and edit Portable Executable (PE) files.</li><li><strong>Hopper Disassembler</strong> — A Debugger, disassembler, and decompiler.</li><li><strong>RetDec</strong> — Open-source decompiler for machine code.</li></ul><h3>Static &amp; Dynamic Analysis</h3><p>Static and dynamic analysis are two crucial methods in cyber security for examining malware. Static Analysis involves inspecting the code without executing it, while dynamic analysis involves observing its behaviour as it runs. The tools mentioned below are commonly used in this category.</p><ul><li><strong>Process Hacker</strong> — Sophisticated memory editor and process watcher.</li><li><strong>PEview</strong> — A portable executable (PE) file viewer for analysis.</li><li><strong>Dependency Walker</strong> — A tool for displaying an executable’s DLL dependencies.</li><li><strong>DIE (Detect It Easy)</strong> — A packer, compiler, and cryptor detection tool.</li></ul><h3>Forensics &amp; Incident Response</h3><p>Digital Forensics involves the collection, analysis, and preservation of digital evidence from various sources like computers, networks, and storage devices. At the same time, Incident Response focuses on the detection, containment, eradication, and recovery from cyberattacks. The tools mentioned below are commonly used in this category.</p><ul><li><strong>Volatility</strong> — RAM dump analysis framework for memory forensics.</li><li><strong>Rekall</strong> — Framework for memory forensics in incident response.</li><li><strong>FTK Imager</strong> — Disc image acquisition and analysis tools for forensic use.</li></ul><h3>Network Analysis</h3><p>Network Analysis includes different methods and techniques for studying and analysing networks to uncover patterns, optimize performance, and understand the underlying structure and behaviour of the network.</p><ul><li><strong>Wireshark</strong> — Network protocol analyzer for traffic recording and examination.</li><li><strong>Nmap</strong> - A vulnerability detection and network mapping tool.</li><li><strong>Netcat</strong> — Read and write data across network connections with this helpful tool.</li></ul><h3>File Analysis</h3><p>File Analysis is a technique used to examine files for potential security threats and ensure proper file permissions.</p><ul><li><strong>FileInsight</strong> — A program for looking through and editing binary files.</li><li><strong>Hex Fiend</strong> — Hex editor that is light and quick.</li><li><strong>HxD</strong> — Binary file viewing and editing with a hex editor.</li></ul><h3>Scripting &amp; Automation</h3><p>Scripting and Automation involve using scripts such as Powershell and Python to automate repetitive tasks and processes, making them more efficient and less prone to human error.</p><ul><li><strong>Python</strong> — Mainly automation-focused on Python modules and tools.</li><li><strong>PowerShell Empire</strong> — Framework for PowerShell post-exploitation.</li></ul><h3>Sysinternals Suite</h3><p>The Sysinternals Suite is a collection of advanced system utilities designed to help IT professionals and developers manage, troubleshoot, and diagnose Windows systems.</p><ul><li><strong>Autoruns</strong> — Shows what executables are configured to run during system boot-up.</li><li><strong>Process Explorer</strong> — Provides information about running processes.</li><li><strong>Process Monitor</strong> -Monitors and logs real-time process/thread activity.</li></ul><h3>Commonly Tool use for Investigation:Overview</h3><p>These tools are the basic ones used for initial investigations. See the list below.</p><p><strong>Tool — — — — — Investigative Value</strong></p><ul><li><strong>Procmon</strong> — A helpful tool for tracking system activity, especially regarding malware research, troubleshooting, and forensic investigations.</li><li><strong>Process Explorer </strong>— Allows you to see the Process of the Parent-child relationship, DLLs loaded, and its path.</li><li><strong>HxD </strong>— Malicious files can be examined or altered via hex editing.</li><li><strong>Wireshark</strong> — Observing and investigating network traffic to look for unusual activity.</li><li><strong>CFF Explorer</strong> — Can generate file hashes for verification, authenticate the source of system files, and validate their validity.</li><li><strong>PEStudio </strong>— Static Analysis or studying executable file properties without running the files.</li><li><strong>FLOSS —</strong> Extracts and de-obfuscates all strings from malware programs using advanced static analysis techniques.</li></ul><h3>Questions &amp; Answers</h3><p>Which tool was formerly known as FireEye Labs Obfuscated String Solver?</p><ul><li><strong>Floss</strong></li></ul><p>Which tool offers in-depth insights into the active processes running on your computer?</p><ul><li><strong>Process Explorer</strong></li></ul><p>Which powerful Windows tool is designed to help you record issues with your system’s apps?</p><ul><li><strong>Procmon</strong></li></ul><p>Which tool can be used for Static analysis or studying executable file properties without running the files?</p><ul><li><strong>PEStudio</strong></li></ul><p>What tool can generate file hashes for integrity verification, authenticate the source of system files, and validate their validity?</p><ul><li><strong>CFF Explorer</strong></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c95f808c369c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Logs Fundamental:]]></title>
            <link>https://medium.com/@lifehacker1981_78415/logs-fundamental-cfb3394478ef?source=rss-e27218c32ce0------2</link>
            <guid isPermaLink="false">https://medium.com/p/cfb3394478ef</guid>
            <category><![CDATA[siem]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[log-analysis]]></category>
            <category><![CDATA[soc]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <dc:creator><![CDATA[Anubhav]]></dc:creator>
            <pubDate>Sat, 10 Oct 2026 14:40:49 GMT</pubDate>
            <atom:updated>2026-10-10T14:40:49.614Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Beginner’s Learning From TryHackMe</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TOLWWUWMG4sGC4Auuq7_eA.png" /></figure><h3>Introduction to Logs</h3><p>Attackers are clever. They avoid leaving maximum traces on the victim’s side to avoid detection. Yet, the security team successfully determines how the attack was executed and is even sometimes successful in finding who was behind the attack.</p><p>Suppose a few policemen are investigating the disappearance of a precious locket in a snowy jungle cabin. They observed that the wooden door of the cabin was brutally damaged, and the ceiling collapsed. There were some footprints on the snowy path to that cabin. Lastly, they discovered some CCTV footage from a neighbouring residence. By placing together all these traces, the police successfully determined who was behind the attack. Various traces are found in several such cases; putting all these together takes you closer to the criminal.</p><p>What if something happened within a digital device? Where do we find all these traces to investigate further?</p><p>There are various places inside a system where the traces of an attack could be fetched. The logs contain most of these traces. <strong><em>Logs are the digital footprints left behind by any activity. </em></strong>The activity could be a normal one or the one with malicious intent. Tracing down the activity and the individual behind the execution of that activity becomes easier through logs.</p><h3>Use Cases of Logs</h3><p>The following are some key areas in which the logs play an integral role.</p><p><strong>Use Case — — — — — — — — — Description</strong></p><p><strong>Security Events Monitoring</strong> <strong>—</strong> Logs help us detect anomalous behavior when real-time monitoring is used.</p><p><strong>Incident Investigation and Forensics — </strong>Logs are the traces of every kind of activity. It offers detailed information on what happened during the incident. The security team utilizes the logs to perform root cause analysis of incidents.</p><p><strong>Troubleshooting — </strong>As the logs also record the errors in systems or applications, they can be used to diagnose issues and helpful in fixing them.</p><p><strong>Performance Monitoring — </strong>Logs can also provide valuable insights into the performance of applications.</p><p><strong>Auditing and Compliance —</strong> Logs play a major role in Auditing and Compliance, making it easier with its capability to establish a trail of different kinds of activities.</p><h3>Types Of Logs</h3><p>Above, We saw various use cases of logs. But there is a challenge. Imagine you have to investigate an issue in a system through the logs; you open the log file of that system, and now you are lost after seeing numerous events of different categories.</p><p>Here is the solution: Logs are segregated into multiple categories according to the type of information they provide. So now you just need to look into the specific log file for which the issue relates.</p><p>For example, you need to investigate the successful logins from yesterday at a specific time frame in Windows OS.Instead of looking into all the logs, you only need to see the system’s <strong>Security Logs</strong> to find the login information. We also have other types of logs that are useful in investigating different incidents. Let’s have a look at them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/1*S_CbNLnRI4yDDnt4GAfj_w.png" /></figure><p>These logs are extremely useful during troubleshooting and cybersecurity investigations because they help us understand <strong>what happened, when it happened, and sometimes who performed the action</strong>.</p><p>Different systems generate different types of logs. Here are some of the most common ones: —</p><h3>🖥️ 1. System Logs</h3><p><strong>System logs</strong> record activities related to the operating system. They help us understand the overall health and behavior of a system.</p><p><strong>Common examples include:</strong></p><ul><li>System startup and shutdown</li><li>Driver loading</li><li>System errors</li><li>Hardware-related events</li></ul><p><strong>Why are they useful?</strong><br>They can help investigators troubleshoot system problems and understand what was happening on a device.</p><h3>🔐 2. Security Logs</h3><p><strong>Security logs</strong> record activities related to authentication, authorization, and other security-related actions. These are especially important for SOC analysts and incident responders.</p><p><strong>Common examples include:</strong></p><ul><li>Successful and failed logins</li><li>Authorization attempts</li><li>Security policy changes</li><li>User account changes</li><li>Suspicious or abnormal activities</li></ul><p><strong>Why are they useful?</strong><br>They can help identify activities such as <strong>unauthorized access, account compromise, and suspicious login attempts</strong>.</p><h3>📱 3. Application Logs</h3><p><strong>Application logs</strong> record activities and errors generated by applications running on a system.</p><p><strong>Common examples include:</strong></p><ul><li>User interactions</li><li>Application changes</li><li>Application updates</li><li>Application errors</li></ul><p><strong>Why are they useful?</strong><br>They help analysts understand what happened inside an application and can also help troubleshoot application-related problems.</p><h3>📋 4. Audit Logs</h3><p><strong>Audit logs</strong> provide a detailed record of user activities and changes made to systems or resources.</p><p><strong>Common examples include:</strong></p><ul><li>Data access</li><li>System configuration changes</li><li>User activities</li><li>Policy changes or enforcement</li></ul><p><strong>Why are they useful?</strong><br>They are useful for <strong>security investigations, monitoring, accountability, and compliance</strong>.</p><h3>🌐 5. Network Logs</h3><p><strong>Network logs</strong> contain information about network communication, including connections and traffic moving between systems.</p><p><strong>Common examples include:</strong></p><ul><li>Incoming traffic</li><li>Outgoing traffic</li><li>Network connections</li><li>Firewall activity</li></ul><p><strong>Why are they useful?</strong><br>They can help identify unusual network communication, troubleshoot connectivity problems, and investigate possible <strong>network-based attacks or data exfiltration</strong>.</p><h3>🔑 6. Access Logs</h3><p><strong>Access logs</strong> record requests made to specific resources or services.</p><p><strong>Common examples include:</strong></p><ul><li>Web server requests</li><li>Database access</li><li>Application access</li><li>API requests</li></ul><p><strong>Why are they useful?</strong><br>They help investigators determine <strong>who accessed a resource, what was accessed, and when the access occurred</strong>.</p><h3>Windows Event Logs Analysis</h3><p>Like other operating systems, Windows OS also logs many of the activities that take place. These are stored in segregated log files, each with a specific log category. Some of the crucial types of logs stored in a Windows Operating System are:</p><ul><li><strong>Application:</strong> There are many applications running on the operating system. Any information related to those applications is logged into this file. This information includes errors, warnings, compatibility issues, etc.</li><li><strong>System:</strong> The operating system itself has different running operations. Any information related to these operations is logged in the System log file. This information includes driver issues, hardware issues, system startup and shutdown information, services information, etc.</li><li><strong>Security:</strong> This is the most important log file in Windows OS in terms of security. It logs all security-related activities, including user authentication, changes in user accounts, security policy changes, etc.</li></ul><p>Besides these, several other log files in the Windows operating system are designed for logging activities related to specific actions and applications.</p><p>Unlike other log files studied in the previous logs types, which had no built-in application to view them, Windows OS has a utility known as Event Viewer, which gives a nice graphical user interface to view and search for anything in these logs.</p><p>To open Event Viewer, click on the Start button of Windows and type ‘Event Viewer’. It will open the Event Viewer for you, as shown below. The highlighted area in the screenshot below shows the different available logs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*T3nXITTidJ3sfpx8" /></figure><p>You can click ‘Windows Logs’ from the highlighted section to see the different types of logs we discussed at the beginning of this task. <br>The first highlighted portion shows the different log files. When we click one of these log files, we will see the different logs, as can be seen in the second highlighted portion. Lastly, in the third highlighted portion, we have different options for analyzing the logs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ofv3nt3DJvLR6zyi" /></figure><p>Let’s double-click on one of these logs to see its contents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eA4qmowatYBFWavD" /></figure><p>This is how a Windows event log looks. It has different fields. The major fields are discussed below:</p><ul><li><strong>Description:</strong> This field has a detailed information of the activity.</li><li><strong>Log Name:</strong> The Log Name indicates the log file name.</li><li><strong>Logged:</strong> This field indicates the time of the activity.</li><li><strong>Event ID: </strong>Event IDs are unique identifiers for a specific activity.</li></ul><p>Numerous event IDs are available in Windows event logs. We can use these event IDs to search for any specific activity. For example, event ID 4624 uniquely identifies the activity of a successful login, so you only need to search for this event ID 4624 when investigating successful logins.</p><p>Here is a table of some important Event IDs in Windows Operating System.</p><p>Event ID — -Description</p><p>4624 — A user account successfully logged in</p><p>4625 — A user account failed to login</p><p>4634 — A user account successfully logged off</p><p>4724 — An attempt was made to reset an account’s password</p><p>4722 — A user account was enabled</p><p>4725 — A user account was disabled</p><p>4726 — A user account was deleted</p><p>There are many more event IDs. It is not necessary to remember all of them, but it is good to remember the crucial event IDs.</p><p>Event Viewer allows us to search for the logs related to a specific event ID with its ‘Filter Current Log’ feature. We can click on this feature to apply any filter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QfRWnnA0Xfnoyhra" /></figure><p>When we click on the ‘Filter Current Log’ option, we will be prompted to enter the event IDs we want to filter. In the screenshot below, I filtered the event ID 4624.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*E2mrVlWqdFzP-aUr" /></figure><p>Once I hit the ‘OK’ button, I can see all the logs with the event ID: 4624. I can now view any of these logs by double-clicking them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Tl6kTnWpDaFU3UCv" /></figure><h3>Web Server Access log Analysis</h3><p>We interact with many websites daily. Sometimes, we just want to view the website, and sometimes, we want to log in or upload a file into any available input field. These are just different kinds of requests we make to a website. All these requests are logged by the website and stored in a log file on the web server running that website.</p><p>This log file contains all the requests made to the website along with the information on the timeframe, the IP requested, the request type, and the URL. Following are the fields taken from a sample log from an Apache web server access log file which can be found in the directory: /var/log/apache2/access.log</p><ul><li><strong>IP Address:</strong> “172.16.0.1” — The IP address of the user who made the request.</li><li><strong>Timestamp:</strong> “[06/Jun/2024:13:58:44]” — The time when the request was made to the website.</li><li><strong>Request:</strong> The request details.</li></ul><p><strong>— Method:</strong> “GET” — Tells the website what action to be performed on the request.</p><p><strong>— URL:</strong> “/” — The requested resource.</p><ul><li><strong>Status Code:</strong> “200” — The response from the server. Different numbers indicate different response results.</li><li><strong>User-Agent:</strong> “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36” — Information about the user’s Operating System, browser, etc. when making the request.</li></ul><p>We can perform manual log analysis by using some command line utilities in the</p><p>operating system. The following are some commands that can be useful during manual log analysis.</p><p>cat is a popular utility for displaying the contents of a text file. We can use the cat command to display the contents of a log file, as they are typically in the text format.</p><p>grep is a very useful command line utility that allows you to search for strings and patterns inside a log file. For example, you may need to search if a specific IP address is present in your log file</p><p>$ grep &quot;192.168.1.1&quot; access.log</p><p>less command is helpful for handling multiple log files. You may need to analyze specific chunks one by one.</p><ul><li>Use spacebar to move to the next page and b to the previous page.</li><li>After running this command, the logs would be displayed in pages, one after one, making it easy for manual analysis. If you wish to search for something in the logs, you can type / followed by the pattern you are searching for and hit enter.</li><li>Use n to navigate to the next occurrence of your search and N to navigate to the previous occurrence of your search.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cfb3394478ef" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Nessus Basic Understanding :]]></title>
            <link>https://medium.com/@lifehacker1981_78415/nessus-basic-understanding-ddaece9fbaed?source=rss-e27218c32ce0------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddaece9fbaed</guid>
            <category><![CDATA[vulnerability-management]]></category>
            <category><![CDATA[nessus]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Anubhav]]></dc:creator>
            <pubDate>Fri, 09 Oct 2026 16:46:54 GMT</pubDate>
            <atom:updated>2026-10-09T16:47:37.149Z</atom:updated>
            <content:encoded><![CDATA[<p>Installation and setting up Nessus</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aGpj2_dNBorilj-E4FK_PQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*xPR0bfuAtQtbFMf_BdfR2Q.png" /></figure><p>In this section, we are going to learn how to use Nessus Essentials, a free version of the enterprise-grade vulnerability scanning platform, Nessus. Please remember you may only use this version for personal projects at home, and using it in a business environment is a breach of Tenable’s licensing. This tool is great to use during certification exams (if it’s permitted! Check before using it), and performing vulnerability discovery on platforms such as HackTheBox.</p><h3><strong>Nessus Installation</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*1sJpFavpYALJVZ4RqmSKGg.png" /></figure><p>We recommend you complete the next steps whilst in a Kali Linux VM. Visit <a href="https://www.tenable.com/products/nessus/nessus-essentials">https://www.tenable.com/products/nessus/nessus-essentials</a> and register for an activation code. Once you’re taken to the next page, on the right-hand side you’ll see this box, where you can download Nessus:</p><p>If you can’t find that box, then visit <a href="https://www.tenable.com/downloads/nessus">https://www.tenable.com/downloads/nessus</a> and download the right version for your host system — it should be <strong>Nessus-X.X.X-debian6_amd64.deb</strong> (just CTRL+F and search for “Kali”).</p><p>In a terminal, navigate to the directory you downloaded the file to (Most likely /root/Downloads or /(UsernameHere)/Downloads) and use the following command to install Nessus from the .deb file:</p><p><strong><em>sudo dpkg -i &lt;Nessus .deb file name&gt; (run as super user) (Debian package tool) (install) (Nessus package)</em></strong></p><p>Next you’ll need to run the Nessus service (also referred to as the Nessus Daemon), which starts everything up. Use the command <strong><em>service nessusd start</em></strong>, and after a few seconds, go to your browser, and visit <a href="https://kali:8834/">https://kali:8834/</a> — this is the local web GUI for Nessus. Can’t find the webpage? the “kali” section of the URL is your hostname (the part that appears in the terminal after “root@”).</p><p>If you’ve previously used Nessus, you may get an error stating you have a corrupt database. To fix this, you need to kill the service using <strong><em>service nessud stop</em></strong>, remove all Nessus files, download the latest version, and install it again. To delete all files for a clean re-install, use the following command in the terminal: <strong><em>rm -rf /opt/nessus</em></strong> (recursively remove everything in the Nessus directory, opt/nessus)</p><p>Once you get to the site, you should now be asked what product you want to use, select Nessus Essentials. You can either register here, or if you did it earlier, skip this step to submit your activation code which should’ve been emailed to you. Finally, you’ll be asked to create a username and password to access Nessus locally within your VM. This form should inherit you Kali account details (in my case, ‘root’ and ‘toor’) however you are able to change them to anything you wish.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*OZN-jP9_GNPyKFnkQbTPAw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*vOhnj1Gq3XGU6hicotHMzg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*ojkySFM80sXWvsGuSYstSQ.png" /></figure><p>Now Nessus will download plugins and other crucial files that it needs to function properly, so let it complete (this may take a LONG time, so get up, move around, and come back to it). Once that’s done, you’ll be presented with the Nessus dashboard. <strong><em>From here we can launch scans, create policies, review plugins, and more.</em></strong> For the scope of this module, we will only be looking briefly at plugins, and focusing on using a premade scan template. <strong>We strongly encourage you to explore Nessus, as it is widely used in industry and hands-on experience is a great thing to have.</strong></p><h3>Nessus GUI Walkthrough</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yGhKiVOlQlYihExbJ7ooxw.png" /></figure><p>On the left-hand side we have a navigation menu, the following sections are interesting to us:</p><p><strong>My Scans —</strong> Any scans that have been conducted by the currently signed-in user. This includes completed, scheduled, pending, and failed scans.<br><strong>All Scans —</strong> Any scans that have been conducted by any users within an organisation. This includes completed, scheduled, pending, and failed scans.<br><strong>Trash — </strong>Once you’ve got a scan template, you can send it to the Trash, so that it is no longer in the “My Scans” or “All Scans” tabs.<br><strong>Policies — </strong>Scans are conducted using a target and a policy, which is a list of settings and plugins that you use. Different plugins will identify and test different things.<br><strong>Plugin Rules —</strong> Plugins are the part of Nessus that actually conduct the scanning and enumeration. Using different ones will provide different results, so this is where you can fine tune the scan to look for specific security issues.<br><strong>Scanners —</strong> Scanners are different hosts that are able to perform enumeration. This is useful if there are multiple V-LANs or physical networks that need to be scanned, and the hosts can’t communicate directly. In our case, we only have one, the local scanner running in our VM.</p><h3>Scanning With Nessus</h3><p>Next we’re going to perform a simple scan of own our machine to demonstrate how scans work, and what the results look like. You can use the following steps to scan any other hosts on your network (provided you have permission to do so).</p><ol><li>Head over to the Policies tab on the left, and click “Scan Templates” in the description text.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jKzbmhyPoZ9YYiRA3fDy1w.png" /></figure><p>We will now be able to choose from a list of pre-defined templates that can be used for specific actions, such as vulnerability scanning, and host discovery. We will be using the Basic Network Scan for this example.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R2PbrtMAiBzCZEo0qxHaHQ.png" /></figure><p>After clicking on our scan template, we’ll be able to customize the settings for this specific scan. Take a look at all of the settings you can change, as well as the Credentials tab, and Plugins tab. What are the credentials used for? They allow the scanner to log into the system, and collect much more valuable information, as opposed to being locked out and only being able to collect surface information.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vXJ89Bq5qMZKlqQmvJykUQ.png" /></figure><p>For this example, you can name the scan anything you like, and we want to enter the localhost (127.0.0.1) as the target.Click Save in the bottom left-hand corner, and you’ll be taken to the “My Scans” page. From here, we can launch our scan by pressing on the play icon to the right. Once clicked, the scan will get to work. Once it’s finished, a tick will appear, and we’ll be able to take a look at the results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gKvZyM617etFMYohFXRROA.png" /></figure><p>This is the results pane and provides us with all of the information the scan collected. On the left we have a list of hosts scanned, along with a summary of any vulnerabilities discovered. This would be full of different hosts if we were scanning an entire network and is arranged by criticality of vulnerability by default. On the right we have the Scan Details, and below it we have a donut chart for the security issues identified. Click on the Vulnerabilities tab to see exactly what the scanner identified.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Az3fw3EVZA-31ZvwZ5PkvA.png" /></figure><p>In this example, we don’t expect to see any major vulnerabilities. <strong>Here can see there some issues with SSL</strong> (this is because of the security exception we had to allow earlier when trying to open Nessus), and some informational issues. You can click on any of these rows in order to get more information and see how to fix them. Click on the SSL issues, then click on the medium-rated SSL issue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VaELITEQ5TkDhfBEtVkgAw.png" /></figure><p>This page shows us a description of the issue, the plugin that was used to detect it, and risk information. Below the description is a solution for how to address the issue. When contacting system owners after a scan, it is good practice to attach an export of the scan as a PDF, but also provide a concise summary in an email with a quick overview of the hosts, any issues, and how to fix them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*199PMpQQLOGZCBVR6RJwRg.png" /></figure><p><strong>This has been a quick learning on how to get Nessus running, and how to launch a scan!</strong></p><ol><li>Which company created Nessus?</li></ol><p>Ans: Tenable</p><p>2. Under Scan Templates in Nessus, there is a scan for what type of Ransomware?</p><p>Ans: WannaCry</p><p>3. When creating a new Plugin Rule, what 4 fields do you need to enter?</p><p>Ans: Host, Severity, Plugin ID, Expiration Date</p><p>4. Is there a scan template specifically designed for mobile devices?</p><p>Ans: True</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddaece9fbaed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Incident Response Fundamentals:]]></title>
            <link>https://medium.com/@lifehacker1981_78415/incident-response-fundamentals-bfe3ec3f7a42?source=rss-e27218c32ce0------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfe3ec3f7a42</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[blue-team]]></category>
            <category><![CDATA[incident-response]]></category>
            <category><![CDATA[infosec]]></category>
            <dc:creator><![CDATA[Anubhav]]></dc:creator>
            <pubDate>Wed, 07 Oct 2026 18:39:52 GMT</pubDate>
            <atom:updated>2026-10-07T18:39:52.041Z</atom:updated>
            <content:encoded><![CDATA[<h4>My TryHackMe Journey</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9IwuhY3LuTfbPgsaLLyA3w.jpeg" /></figure><h3>Introduction to Incident Response</h3><p>Imagine living in a heavily insecure street with many expensive things in your home. You must be thinking of having a security guard and a few CCTV cameras in your home. Hiding the expensive material inside a hidden underground room is a good idea if any intruder successfully enters the house. These are the things that you plan for the safety of your home, even before any attack occurs.</p><p>Besides these proactive measures, did you ever consider how things would work if someone successfully bypassed your external security mechanisms and gained access to your home? You must also take several other measures after your home is attacked.</p><p>Let’s take the above into the Digital Realm. You may have heard about a cyber attack on any organization that caused them to lose thousands of dollars. Several such cases are reported daily on the internet. These are referred to as <strong>Cyber Security Incidents</strong>.</p><h3>What is an Incident?</h3><p>In cybersecurity, an <strong>incident is a security event that indicates a possible or confirmed threat to a system, network, or organization</strong>. Examples include a phishing attack, malware infection, unauthorized access, or data theft.</p><p>Devices constantly generate <strong>events</strong> whenever something happens, such as a user logging in or a file being accessed. Security tools analyze these events and generate <strong>alerts</strong> when they detect suspicious activity.</p><p>The security team then investigates these alerts to determine whether they are:</p><ul><li><strong>False Positive:</strong> The activity looks suspicious but is actually legitimate.</li><li>Example — A security solution raised an alert on a high amount of data being transferred from one system to an external IP address. Upon analyzing this alert, the security team found that the subject system was undergoing a backup process to a cloud storage service, which caused this.</li><li><strong>True Positive:</strong> The activity is genuinely malicious and represents a security threat.</li><li>Example — A security solution raised an alert on a attempt on one of the organization’s users. Upon analyzing this alert, the security team found that the email was a phishing email sent to this user to compromise the system.</li></ul><p>These true positive alerts are sometimes referred to as <strong>Incidents</strong>. Assuming the alert is now categorized as an incident, the next phase is to give a severity level to the incident. Imagine you are part of the security team and get multiple incidents simultaneously. Which incident would you choose first to respond to? This is where the idea of incident severity helps. Incidents can be categorized as low, medium, high, or critical based on the impact they can create.</p><h3>Types Of Incident</h3><p>People usually label every harmful activity associated with the digital world as a hacking attempt. This may be correct, but it is very generic in terms of cyber security. Security Incidents can be of different types. In the above tasks, we saw an example of a true positive alert, which became an incident after the analysis of the security team. This incident was related to the phishing email, which probably came with a malicious attachment. If downloaded into the system, this attachment may have harmful consequences.</p><p>There are several other types of incidents :—</p><ul><li><strong>Malware Infections</strong>: Malware is a malicious program that can damage a system, network, or application. The majority of incidents are associated with malware infections. There are different types of malware, each with a unique potential to cause damage. Malware infections are mostly caused by files that can be text, documents, executables, etc.</li><li><strong>Security Breaches:</strong> Security Breaches arise when an unauthorized person gets access to confidential data (something we don’t want them to see or have). Security Breaches are of the utmost importance as many businesses rely on their confidential data.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hCcLaf6Lxw48tWIpnwFqdg.png" /></figure><ul><li><strong>Data Leaks:</strong> Data leaks are incidents in which confidential information of an individual or an organization is exposed to unauthorized entities. Many attackers use data leaks for reputational damage to their victims or use this technique to threaten their victims and get what they need from them.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/944/1*UXvPxlh60pbi8UVhBfiuGg.png" /></figure><ul><li><strong>Insider Attacks:</strong> Incidents from within an organization are known as insider attacks. Think about a disgruntled employee infecting the whole network through a USB on his last day. These attacks can be hazardous, as an insider always has greater access to resources than an outsider.</li><li><strong>Denial Of Service Attacks:</strong> Availability is one of the three pillars of cyber security. Defensive security solutions and people constantly find ways to protect information; they ensure that the data is available to the people simultaneously. This is because there is no point in protecting something that is unavailable to us. Denial of Service attacks, or attacks, are incidents where the attacker floods a system/network/application with false requests, eventually making it unavailable to legitimate users. This happens due to the exhaustion of resources available to entertain the requests.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XLM_KNHp4o5u89Qn" /></figure><h3>Incident Response Process</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/832/0*ycGSIznwJo_4jN1z" /></figure><p>Sometimes, handling a variety of incidents in an environment can be difficult. Due to the distinct nature of incidents in organizations, there should be a structured process for incident response. Incident Response Frameworks help us in this regard. These are the generic approaches to follow in any incident for effective response. We will discuss the two widely used incident response frameworks: SANS and NIST.</p><p>SANS and NIST are popular organizations contributing to cyber security. SANS has offered various courses and certifications in cyber security, and NIST played its role in developing standards and guidelines for cyber security. Both SANS and NIST have quite similar incident response frameworks.</p><p>The SANS incident Response framework has 6 phases, which can be called ‘PICERL’ to remember them easily.</p><p><strong>Preparation : </strong>This is the first phase. The preparation phase includes building the necessary resources to handle an incident. These resources include developing incident response teams, having a proper incident response plan in place, and deploying necessary security solutions to combat the incidents.</p><p><strong>Identification : </strong>The identification phase refers to looking for any abnormal behavior that may indicate an incident. This involves using various security solutions and techniques to monitor abnormal events.</p><p><strong>Containment :</strong> Once an incident has been identified, the next step should be to contain it. This means minimizing the impact of the attack. This is usually done by isolating the victim machine, disabling the compromised user accounts, etc.</p><p><strong>Eradication : </strong>This phase, as its name suggests, involves removing the threat from the attacked environment. The threat may be of any kind. The eradication phase will ensure the subject environment is clean, and now we can move to the recovery phase.</p><p><strong>Recovery : </strong>The recovery phase is very important in this chain. It involves recovering the affected systems from backup or rebuilding them. The recovered systems are then tested and are ready to use.</p><p><strong>Lessons Learned : </strong>This is also an important part of the incident response lifecycle. Gaps in the detection and analysis of the incident are identified and documented, helping to improve the overall process in future incidents.</p><p>The <strong>Incident Response Framework of NIST</strong> is similar to the SANS framework we studied above. The number of phases in this framework is reduced to 4.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dQE_2-yFEwClFwAE" /></figure><h3>Incident Response Techniques</h3><p>Remember we studied the second phase of the incident response lifecycle, ‘Identification’ in SANS, and ‘Detection and Analysis’ in NIST. It is very hard to look for abnormal behavior and identify incidents manually. There are multiple security solutions that serve their own unique roles in detecting any incidents. Some of them even have the capability to respond to the incidents and execute the other phases of the lifecycle, such as containment, eradication, etc.</p><p>A brief explanation of some of these solutions is given below:</p><ul><li><strong>SIEM :</strong> The Security Information and Event Management Solution (SIEM) collects all important logs in one centralized location and correlates them to identify incidents.</li><li><strong>AV :</strong> Antivirus (AV) detects known malicious programs in a system and regularly scans your system for these.</li><li><strong>EDR :</strong> Endpoint Detection and Response (EDR) is deployed on every system, protecting it against some advanced-level threats. This solution can also contain and eradicate the threat.</li></ul><p>After incidents are identified, certain procedures must be followed, including investigating the extent of the attack, taking necessary actions to prevent further damage and eliminate it from the root. These steps may be different for different kinds of incidents. In this scenario, having step-by-step instructions to deal with each kind of incident helps you save a lot of time. These types of instructions are known as <strong>Playbooks</strong>.</p><p>Playbooks are the guidelines for a comprehensive incident response.</p><p>Following is an example of a <strong>Playbook</strong> for an incident: Phishing Email</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/0*tdkk48pNruVezaSr" /></figure><ol><li>Notify all the stakeholders of the phishing email incident</li><li>Determine if the email was malicious by conducting header and body analysis of the email</li><li>Look for any attachments with the email and analyze them</li><li>Determine if anybody opened the attachments</li><li>Isolate the infected systems from the network</li><li>Block the email sender.</li></ol><p>In this blog, we learned about the different concepts of incident response. We studied how and when an event is categorized as an incident and the priorities given to different incidents. We also looked into types of incidents and the frameworks of incident response: SANS and NIST, which guide us through handling an incident. Lastly, we saw some tools for incident response.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfe3ec3f7a42" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Digital Forensics Fundamentals: A Beginner’s Guide]]></title>
            <link>https://medium.com/@lifehacker1981_78415/digital-forensics-fundamentals-a-beginners-guide-6072e0c2cc00?source=rss-e27218c32ce0------2</link>
            <guid isPermaLink="false">https://medium.com/p/6072e0c2cc00</guid>
            <category><![CDATA[tryhackme]]></category>
            <category><![CDATA[infosec]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[digital-forensics]]></category>
            <dc:creator><![CDATA[Anubhav]]></dc:creator>
            <pubDate>Mon, 05 Oct 2026 17:23:40 GMT</pubDate>
            <atom:updated>2026-10-05T17:23:40.790Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Inspired by my learning journey on TryHackMe</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/676/1*OXRtqBrvx7RuVERklLqFJA.png" /></figure><p>Imagine a team of law enforcement officers raiding a notorious bank robber’s safehouse. While they might look for physical cash or weapons, they also secure a laptop, a smartphone, an external hard drive, and a USB drive left on the desk.</p><p>In the modern world, the most critical clues aren’t left behind as physical fingerprints — they are hidden inside these electronic devices as digital evidence.</p><h3><strong>Introduction to Digital Forensics</strong></h3><p>Forensics is the application of methods and procedures to investigate and solve crimes. The branch of forensics that investigates cyber crimes is known as <strong>digital forensics</strong>.</p><p><strong>Cyber crime</strong> is any criminal activity conducted on or using a digital device.</p><p><strong>Example —</strong></p><p>Consider an example where law enforcement agencies raid a bank robber’s place with proper search warrants. Some digital devices, including a laptop, mobile phone, hard drive, and a USB, were found in the robber’s home. The law enforcement agency handed over the case to the digital forensics team. The team collected evidence securely and conducted a thorough investigation inside their digital forensics lab equipped with forensics tools. The following evidence was found on the digital devices:</p><ul><li>A digital map of the bank was found on the suspect’s laptop, which they kept for planning the robbery.</li><li>A document with the bank’s entrance and escape routes was found on the suspect’s hard drive.</li><li>A document on the hard drive that listed all the bank’s physical security controls. The suspect devised plans to bypass the security measures.</li><li>Some media files, including photos and videos of the suspect’s previous robberies, were inside the suspect’s laptop.</li><li>After conducting a thorough investigation of the suspect’s mobile phone, some illegal chat groups and call records related to the bank robbery were also found.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*u1KTMbd4hm1SMApr.png" /></figure><h3><strong>Digital Forensics Methodology</strong></h3><p>The digital forensics team has various cases requiring different tools and techniques. However, the National Institute of Standards and Technology (NIST) defines a general process for every case. The NIST works on defining frameworks for different areas of technology, including cyber security, where they introduce the <strong>process of digital forensics in four phases.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dpVVi-393CSxgSKh.png" /></figure><ol><li><strong>Collection:</strong> The first phase of digital forensics is data collection. Identifying all the devices from which the data can be collected is essential. Usually, an investigator can find personal computers, laptops, digital cameras, USBs, etc., on the crime scene.</li><li><strong>Examination:</strong> The collected data may overwhelm investigators due to its size. This data usually needs to be filtered, and the data of interest needs to be extracted.The examination phase helps you filter this particular data for analysis.</li><li><strong>Analysis:</strong> This is a critical phase. The investigators now have to analyze the data by correlating it with multiple pieces of evidence to draw conclusions. The analysis depends upon the case scenario and available data. The analysis aims to extract the activities relevant to the case chronologically.</li><li><strong>Reporting:</strong> In the last phase of digital forensics, a detailed report is prepared. This report contains the investigation’s methodology and detailed findings from the collected evidence. It may also contain recommendations. This report is presented to law enforcement and executive management.</li></ol><p>As part of the collection phase, we saw that various pieces of evidence can be found at the crime scene. Analyzing these multiple categories of evidence requires various tools and techniques.</p><p><strong><em>There are different types of digital forensics, </em></strong>all with their own collection and analysis methodologies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pRgpTO3mOPg2gfCn.png" /></figure><ul><li><strong>Computer forensics:</strong> The most common type of digital forensics is computer forensics, which concerns investigating computers, the devices most commonly used in crimes.</li><li><strong>Mobile forensics:</strong> Mobile forensics involves investigating mobile devices and extracting evidence such as call records, text messages, GPS locations, and more.</li><li><strong>Network forensics:</strong> This area of forensics covers investigation beyond individual devices. It includes the whole network. The majority of the evidence found in networks is the network traffic logs.</li><li><strong>Database forensics:</strong> Many critical data is stored in dedicated databases. Database forensics investigates any intrusion into these databases that results in data modification or exfiltration.</li><li><strong>Cloud forensics:</strong> Cloud forensics is the type of forensics that involves investigating data stored on cloud infrastructure. This type of forensics sometimes gets tricky for the investigators as there is little evidence on cloud infrastructures.</li><li><strong>Email forensics:</strong> Email, the most common communication method between professionals, has become an important part of digital forensics. Emails are investigated to determine whether they are part of phishing or fraudulent campaigns.</li></ul><h3>Evidence Acquisition</h3><p>Acquiring evidence is a critical job. The forensics team must collect all the evidence securely without tampering with the original data. Evidence acquisition methods for digital devices depend on the type of digital device.</p><p><strong><em>Let’s discuss some of the important ones.</em></strong></p><h4>Proper Authorization —</h4><p>The forensics team should obtain authorization from the relevant authorities before collecting any data. Evidence collected without prior approval may be deemed inadmissible in court.</p><h4>Chain Of Custody —</h4><p>Process of documenting the complete journey of evidence during a legal case lifetime, from the collection to final presentation in court.</p><p>Some of the key details are listed below:</p><ul><li>Description of the evidence (name, type).</li><li>Name of individuals who collected the evidence.</li><li>Date and time of evidence collection.</li><li>Storage location of each piece of evidence.</li><li>Access times and the individual record who accessed the evidence.</li></ul><p><strong>A sample chain of custody can be downloaded from — </strong><a href="https://www.nist.gov/document/sample-chain-custody-formdocx"><strong><em>Here</em></strong></a></p><blockquote><strong><em>Write Blockers </em></strong><em>is a tool is used to ensure data integrity during the collection.</em></blockquote><h3>Windows Forensics</h3><p>The most common types of evidence collected from crime scenes are desktop computers and laptops, as most criminal activity involves a personal system.</p><p>In this task, we will discuss the evidence acquisition and analysis of the Windows operating system, which is a very common operating system that has been investigated in several cases.</p><p>As part of the data collection phase, forensic images of the Windows operating system are taken. These forensic images are bit-by-bit copies of the whole operating system.</p><p>Two different categories of forensic images are taken from a Windows operating system.</p><ul><li><strong>Disk image:</strong> The disk image contains all the data present on the storage device of the system (HDD, SSD, etc.). This data is non-volatile, meaning that the disk data would survive even after a restart of the operating system. For example, all the files like media, documents, internet browsing history, and more.</li><li><strong>Memory image:</strong> The memory image contains the data inside the operating system’s . This memory is volatile, meaning the data will get lost after the system is powered off or restarted. For example, to capture open files, running processes, current network connections, etc.,</li></ul><p>Let’s discuss some popular tools used for disk and memory image acquisition and analysis of the Windows operating system.</p><p><strong>FTK Imager:</strong> FTK Imager is a widely used tool for taking disk images of Windows operating systems. It offers a user-friendly graphical interface for creating the image in various formats. This tool can also analyze the contents of a disk image. It can be used for both acquisition and analysis purposes.</p><p><strong>Autopsy:</strong> <a href="https://www.autopsy.com/">Autopsy (opens in new tab)</a> is a popular open-source digital forensics platform. An investigator can import an acquired disk image into this tool, and the tool will conduct an extensive analysis of the image. It offers various features during image analysis, including keyword search, deleted file recovery, file metadata, extension mismatch detection, and many more.</p><p><strong>DumpIt:</strong> <a href="https://www.toolwar.com/2014/01/dumpit-memory-dump-tools.html">DumpIt (opens in new tab)</a>offers the utility of taking a memory image from a Windows operating system. This tool creates memory images using a command-line interface and a few commands. The memory image can also be taken in different formats.</p><p><strong>Volatility:</strong> <a href="https://volatilityfoundation.org/">Volatility (opens in new tab)</a> is a powerful open-source tool for analyzing memory images. It offers some extremely useful plugins. Each artifact can be analyzed using a specific plugin. This tool supports various operating systems, including Windows, Linux, macOS, and Android.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6072e0c2cc00" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>