<?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 Yash Kitey on Medium]]></title>
        <description><![CDATA[Stories by Yash Kitey on Medium]]></description>
        <link>https://medium.com/@kiteyyash3?source=rss-1c31f195dc4c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*H_7b7Fo8bw3DpYBx</url>
            <title>Stories by Yash Kitey on Medium</title>
            <link>https://medium.com/@kiteyyash3?source=rss-1c31f195dc4c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 15:34:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kiteyyash3/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[Episode 13: Identity & Access Management (IAM)]]></title>
            <link>https://medium.com/@kiteyyash3/episode-13-identity-access-management-iam-5ebfdd863d18?source=rss-1c31f195dc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ebfdd863d18</guid>
            <category><![CDATA[cybersecurity-awareness]]></category>
            <category><![CDATA[access-control]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Yash Kitey]]></dc:creator>
            <pubDate>Mon, 14 Sep 2026 19:55:04 GMT</pubDate>
            <atom:updated>2026-09-14T20:34:46.593Z</atom:updated>
            <content:encoded><![CDATA[<h3>From Access Models to Modern Federation</h3><p>Welcome back to <em>Cybersecurity Unlocked</em>!:<em> A Journey in Cybersec with Yash</em>.</p><p>In our last episode, we broke down how to build a layered defense using Technical, Managerial, and Physical security controls. We looked at the walls, locks, and guardposts that keep intruders out.</p><p>Now, imagine walking into an ultra-secure office building. You passed the front security desk with your photo ID, but once you are inside the elevator, which floor buttons actually light up when you scan your badge? Can you open the server room door on the 4th floor, or does your badge only get you into the breakroom? What are all the things you can access.</p><p>That is <strong>Identity and Access Management (IAM)</strong>.</p><p>If AAA is the receptionist verifying your identity, <strong>IAM is the entire master key and permissions engine</strong> running behind the walls. Let’stry to understand how modern systems decide who gets in, how permissions are managed, and how identity travels securely across the web.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fGNzMhLjeBI24wyy5BBbCA.png" /></figure><h3>1. How Access Decisions Get Made: The Access Models</h3><p>When you are using an application and it asks, <em>&quot;Should this user be allowed to read this file?&quot;</em>, it relies on an access control model. Here are the four primary models you need to know:</p><ul><li><strong>Role-Based Access Control (RBAC): The Department Badge</strong></li></ul><p><strong>How it works:</strong> Permissions are tied directly to job roles, not individual people. If you join the company as a &quot;DevOps Engineer,&quot; you automatically inherit permissions to deploy containers and view build logs. So you will be able to perform all the things that particular role should be able to do. (Consider Role as a group for better understanding and you are providing permission to that group. So if you are added to that group you will automatically get all those permissions those are given to that role)</p><p><strong>The Catch:</strong> As companies grow, roles get messy. You end up with roles like &quot;DevOps-Engineer-Who-Also-Needs-Access-To-Billing-On-Tuesdays.&quot; This is called <strong>role explosion</strong> or <strong>role bloat</strong>.</p><ul><li><strong>Attribute-Based Access Control (ABAC): The Smart Scanner</strong></li></ul><p><strong>How it works:</strong> Instead of looking just at your title, the system evaluates dynamic <strong>attributes</strong> in real time:<br>- <em>Subject attributes:</em> Who are you? (Engineer, Intern, Contractor)<br>- <em>Resource attributes:</em> How sensitive is the data? (Public, Internal, Top Secret)<br>- <em>Environment attributes:</em> Where and when are you logging in? (From corporate Wi-Fi at 2 PM vs. an unrecognized IP in another country at 3 AM)</p><p>ABAC is the brain behind <strong>Zero Trust</strong> architectures because it constantly asks: <em>&quot;Given the current context, does this request make sense right now?&quot;</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lXT6OnJ8Phu5N9lYspIYtA.png" /></figure><ul><li><strong>Discretionary Access Control (DAC): The House Party</strong></li></ul><p><strong>How it works:</strong> The creator or owner of the resource decides who gets in. Think of standard file permissions on your personal computer or sharing a Google Doc: you own the file, so you decide whether your colleague gets &quot;Viewer&quot; or &quot;Editor&quot; rights.</p><ul><li><strong>Mandatory Access Control (MAC): The Military Clearance</strong></li></ul><p><strong>How it works:</strong> The user does not get to choose permissions. A centralized authority assigns strict security labels (e.g., <em>Confidential, Secret, Top Secret</em>) to both users and resources. Even if you created a file, you cannot share it with someone unless their official clearance matches or exceeds the classification level of that file.</p><h3>2. Identity Across the Web: Federation &amp; Modern Auth Protocols</h3><p>Back in the day, every application maintained its own separate database of usernames and passwords. Today, you do not want your employees managing 40 different passwords across 40 different SaaS tools.</p><p>Instead, we use <strong>Federated Identity</strong> and <strong>Single Sign-On (SSO)</strong>, allowing a central <strong>Identity Provider (IdP)</strong> (like Okta, Azure AD, or Google Workspace) to vouch for you when you log into a <strong>Service Provider (SP)</strong> (like Slack, GitHub, or AWS). So basically in simple language, you just login once and then if you want to access any software you can use the same login — you don’t have to provide username and password again.</p><p>Here is how the three major protocols handle this:</p><ul><li><strong>SAML 2.0 (Security Assertion Markup Language): The Enterprise Passport</strong></li></ul><p><strong>Format:</strong> XML-based.<br><strong>Use Case:</strong> Traditional enterprise Single Sign-On (SSO).<br><strong>How it works:</strong> When you log into your company portal, the IdP generates a digitally signed XML document (a SAML assertion) that tells the service provider, <em>&quot;Yes, this is Yash, and his email is verified.&quot;</em></p><ul><li><strong>OAuth 2.0: The Valet Key (Authorization)</strong></li></ul><p><strong>Format:</strong> JSON-based.<br><strong>Use Case:</strong> Delegated access.<br><strong>How it works:</strong> Think of OAuth like a hotel valet key. It lets the valet drive your car, but it won&#39;t open the glove box or trunk. When an app asks, <em>&quot;Allow this app to access your Google Drive photos?&quot;</em>, OAuth issues a scoped token that lets the app access <em>only</em> your photos without you ever handing over your Google password.</p><ul><li><strong>OpenID Connect (OIDC): The ID Card on Top of OAuth (Authentication)</strong></li></ul><p><strong>Format:</strong> JSON Web Tokens (JWT).<br><strong>Use Case:</strong> Consumer and modern web/mobile app logins (&quot;Log in with Google/Apple&quot;).<br><strong>How it works:</strong> OAuth 2.0 was designed for <em>authorization</em> (what you can access), not <em>authentication</em> (who you are). OIDC was built directly on top of OAuth 2.0 to deliver an id_token verifying your identity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MTxlcLbtSpCtO7lWWa0Ggw.png" /></figure><h3>3. Securing the Keys to the Kingdom: PAM &amp; Passwordless</h3><p>Managing regular users is only half the battle. What about administrator accounts, database root access, and automated service credentials?</p><ul><li><strong>Privileged Access Management (PAM):</strong> Admin accounts shouldn&#39;t sit around with 24/7 root access. PAM introduces <strong>Just-In-Time (JIT) elevation</strong>, where elevated privileges are granted temporarily for a specific task and automatically revoked once the maintenance window closes.</li><li><strong>FIDO2 / WebAuthn (Going Truly Passwordless):</strong> Traditional SMS and email OTP codes are vulnerable to SIM swapping and reverse-proxy phishing. Modern architectures are moving to FIDO2 hardware keys (like YubiKeys) and platform passkeys, which rely on asymmetric cryptography bound directly to the website&#39;s domain making them cryptographically immune to credential-harvesting phishing sites.</li></ul><h3>Quick Cheat Sheet</h3><ul><li><strong>RBAC:</strong> Access based on your job title.</li><li><strong>ABAC:</strong> Access based on dynamic attributes (who, what, where, when).</li><li><strong>SAML:</strong> Enterprise XML-based SSO.</li><li><strong>OAuth 2.0:</strong> Grants permission without sharing passwords (authorization).</li><li><strong>OIDC:</strong> Adds identity verification on top of OAuth (authentication).</li></ul><h3>What’s Next?</h3><p>Now that we know how identities are verified and permissions are enforced across distributed environments, what happens when data actually moves across the wire?</p><p>I hope you guys have a basic understanding of what IAM us and what are the different catrgories of IAM. The best way to understand IAM and to practice creating IAM rules. This was just a brief introduction but we will dive deeper in future.</p><p>Note: All images were created by GenAI and was used for correction adn grammatical errors.</p><p>Stay tuned, and keep securing!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ebfdd863d18" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Episode 12: Security Controls Explained: Technical, Managerial & Physical]]></title>
            <link>https://medium.com/@kiteyyash3/episode-12-security-controls-explained-technical-managerial-physical-e6c4980bab3d?source=rss-1c31f195dc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6c4980bab3d</guid>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <dc:creator><![CDATA[Yash Kitey]]></dc:creator>
            <pubDate>Thu, 02 Apr 2026 17:22:24 GMT</pubDate>
            <atom:updated>2026-04-02T17:22:24.446Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cybersecurity Unlocked: A Journey into Cybersec with Yash</h3><p>Over the last few episodes, we’ve spent a lot of time looking at the dark side of the network. We’ve covered how attackers trick humans with Social Engineering (Episode 10) and how they exploit bad code with vulnerabilities like SQLi and Zero-Days (Episode 11).</p><p>But how do we actually fight back?<br>Personally I love Blue Team in Cybersecurity where we try to configure and defend our systems. So let’s try to understand this deeper.</p><p>You can’t just buy a shiny “cybersecurity box,” and plug it into the wall, and call it a day. Real defense requires a layered approach. In the industry, we call the tools, rules, and fences we use to protect our data <strong>Security Controls</strong>.</p><p>If you are studying for Security+, Domain 1.1 requires you to understand the “Security Control Matrix.” It sounds intimidating, but it just comes down to two questions: <strong>What</strong> is the control made of, and <strong>When</strong> does it do its job?</p><p>Let’s break it down.</p><h3>Dimension 1: The “What” (Control Types)</h3><p>This is the nature of the control itself. What is it physically (or digitally) made of?</p><p><strong>1. Technical (Logical) Controls</strong> These are the controls executed by computer systems. Back in my system engineering days, this was where I lived. These are the <strong>configurations, the code, and the software that protect the network.</strong></p><ul><li><em>Examples:</em> Firewalls, Encryption algorithms, Antivirus software, Multi-Factor Authentication (MFA), and Intrusion Prevention Systems (IPS).</li><li><em>The Reality:</em> Technical controls are great because they don’t sleep, but they only do exactly what you tell them to do. If you misconfigure a firewall rule, it will happily let the attacker right in. It does not have a brain of its own.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r8JrVAMmUmmYeu_u9td8CA.png" /></figure><p><strong>2. Managerial (Administrative) Controls</strong> You can have the best technology in the world, but it means nothing without the rules to govern it. Managerial controls are the <strong>paperwork, policies, and human processes that dictate how security is handled.</strong></p><ul><li><em>Examples:</em> The company Acceptable Use Policy (AUP), employee onboarding/offboarding procedures, risk assessments, and annual security awareness training.</li><li><em>The Reality:</em> A firewall (Technical) blocks traffic, but a Managerial policy is what tells the firewall administrator <em>which</em> traffic is allowed in the first place.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dwzkVjMxrCNnWH6GTGXCiw.png" /></figure><p><strong>3. Physical Controls</strong> If an attacker can physically touch your server, it’s not your server anymore. Physical controls protect the real-world perimeter.</p><ul><li><em>Examples:</em> Fences, security guards, locked doors, badge readers, and server room climate controls (HVAC).</li><li><em>The Reality:</em> Remember our talk on “Tailgating” in Episode 10? A badge reader is a physical control designed to stop an unauthorized person from walking into the building.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*acBXh5TiIYJb6LoXlVh32g.png" /></figure><h3>Dimension 2: The “When” (Control Categories)</h3><p>Now that we know <em>what</em> the controls are, we need to categorize them by the phase of the attack they are designed to handle.</p><p><strong>1. Preventive Controls (The Bouncers)</strong> The absolute best-case scenario is stopping the attack before it ever happens. Preventive controls are like the bouncers at the door.</p><ul><li><em>Examples:</em> A locked door (Physical/Preventive), a firewall blocking malicious IP addresses (Technical/Preventive), or an employee background check (Managerial/Preventive).</li></ul><p><strong>2. Detective Controls (The Alarms)</strong> Preventive controls fail. It is a harsh reality of cybersecurity. When an attacker slips past the bouncer, you need to know they are inside. Detective controls don’t stop the attack, they just sound the alarm.</p><ul><li><em>Examples:</em> Security cameras (Physical/Detective), Intrusion Detection Systems (Technical/Detective), or log monitoring.</li><li><em>The Golden Rule of Logs:</em> A log file is a detective control, but it is completely useless if nobody is looking at it. An alarm ringing in an empty building doesn’t save the data.</li></ul><p><strong>3. Corrective Controls (The Medics)</strong> The attacker got in, the alarm sounded, and damage was done. Now what? Corrective controls are designed to fix the mess and restore the system back to normal.</p><ul><li><em>Examples:</em> Restoring data from a Backup (Technical/Corrective), patching the vulnerability the attacker used, or putting out a fire with a sprinkler system (Physical/Corrective).</li></ul><h3>The Synthesis: Defense in Depth</h3><p>The secret to a secure architecture is realizing that no single control is perfect. You have to layer them one on top of another. This concept is known as <strong>Defense in Depth</strong>.</p><p>Imagine a scenario: Your company creates a <strong>Policy (Managerial)</strong> stating all employees must use MFA(Multi Factor Authentication). The IT team configures the <strong>MFA system (Technical)</strong> to act as a <strong>Preventive</strong> measure against stolen passwords. If an attacker somehow bypasses the MFA, your <strong>SIEM monitoring tool (Detective)</strong> flags the weird login location, alerting the security team that something suspicious is happening and someone has entered the system. Security team then isolates the infected machine and restores it from a <strong>Backup (Corrective)</strong>.</p><p>That is how the shield is built. This is what defense in depth looks like in real life. It isn’t just a textbook term you memorize. It is a fundamental acknowledgment that failure is inevitable. Firewalls get misconfigured. Policies get ignored. People make mistakes. But when you intentionally overlap your Technical, Managerial, and Physical controls, the failure of one system doesn’t mean the collapse of the whole network. An attacker might be able to pick one lock, but a properly layered defense ensures they will never make it through the maze.</p><p><strong>Question for the comments:</strong> Which category of control do you think is the most under-funded in most modern companies: Preventive, Detective, or Corrective? Let me know your thoughts!</p><p>#Cybersecurity #InfoSec #SecurityPlus #DefenseInDepth #BlueTeam #TechBlog #SecurityControls #SystemEngineering</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6c4980bab3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Weakest Link: How Bad Code Destroys Good Security — Cybersecurity Unlocked Ep. 11]]></title>
            <link>https://medium.com/@kiteyyash3/the-weakest-link-how-bad-code-destroys-good-security-cybersecurity-unlocked-ep-11-8424e969e428?source=rss-1c31f195dc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8424e969e428</guid>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cybersecurity-awareness]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[data-security]]></category>
            <dc:creator><![CDATA[Yash Kitey]]></dc:creator>
            <pubDate>Thu, 05 Mar 2026 18:55:04 GMT</pubDate>
            <atom:updated>2026-03-05T18:55:04.557Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cybersecurity Unlocked: A Journey into Cybersec with Yash</h3><p>In Episode 10, we talked about “Hacking Humans” and how Social Engineering bypasses expensive security tools by tricking employees.</p><p>Let us assume that your employees are perfectly trained. What if nobody clicks the phishing link, and nobody lets the attacker through the front door?</p><blockquote>Do you think attackers just give up. They pivot. Instead of attacking the people, they attack the <strong>code</strong>.</blockquote><p>It does not matter if you have strongest firewall. It won’t protect an application that was built with gaping security holes. <em>Today, we are diving into </em><strong><em>Application Security (AppSec) </em></strong><em>and looking at the</em><strong><em> four most dangerous vulnerabilities </em></strong><em>attackers exploit to break into systems.</em></p><h3>1. The Zero-Day Vulnerability (The Unknown )</h3><blockquote><strong>The Flaw:</strong> Software is written by humans, which means it has mistakes. (Now a days, we are moving to AI written software but that is a whole different topic we will cover in future). <br>A “Zero-Day” is a software flaw that the software creator (like Microsoft or Apple) doesn’t know about yet, but an attacker has discovered.</blockquote><p><strong>The Attack:</strong> Because the creator doesn’t know about it, there is no patch available. The attacker has “zero days” of warning to exploit it before the good guys realize what is happening and start fixing it. As a defender you have no idea that this could be a vulnerability and you won’t be able to patch it or work on it unless there is a exploit.</p><p><strong>The Fix:</strong> You can’t patch what you don’t know is broken. Now there our all the defense here relies on <strong>Threat Intelligence</strong> and anomaly detection. This means spotting weird behavior on your network even if you don’t recognize the specific malware.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VF_Sc0t3Yec1oEwjDSG50g.png" /><figcaption>Zero day vulnerability</figcaption></figure><h3>2. SQL Injection (SQLi) (The Jedi Mind Trick — That’s what I call it) ️</h3><blockquote><strong>The Flaw:</strong> SQL (Structured Query Language) is how websites talk to their backend databases. Database is the place where all your passwords, credit cards, and user data live. In simplest terms, SQL Injection happens when a website takes user input (like a username) and blindly trusts it without checking if it’s safe or if its supposed to be there or the format is correct or not. Basically SQL injection happens when you don’t verify the input, that is called Input validation or Input Sanitization.</blockquote><p><strong>The Attack:</strong> Instead of typing a username like “Yash,” an attacker types a database command, like<strong> &#39; OR 1=1 — —</strong> . So if the website doesn&#39;t validate the input, it passes that command directly to the database. The database gets confused, and executes the attacker&#39;s command, and often spits out the entire table of user passwords.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-39RxMZZOkuDT6167r9zvw.png" /><figcaption>SQL Injection</figcaption></figure><p><strong>The Fix:</strong> <strong>Input Validation</strong> and <strong>Prepared Statements</strong>. Never trust user input. Always verify the input. If the input has something extra which is not to be there for example if with username if the input has something extra , we tell the code Not To Trust it and should return a message like username not in proper format. <strong>The code must strictly define that a name field can <em>only</em> contain letters, not database commands.</strong></p><h3>3. Cross-Site Scripting (XSS) (The Poisoned Well) ️</h3><blockquote><strong>The Flaw:</strong> Similar to SQLi, XSS happens when a website accepts user input without filtering it. But instead of attacking the <em>database</em>, XSS attacks the <em>other users</em> who visit the website. Also it could compromise the you and some unwanted activity or code/script will run which you have not authorized.</blockquote><p><strong>The Attack:</strong> An attacker goes to a forum or comment section and types a malicious JavaScript code snippet instead of a normal comment. The website saves this poisoned comment. When a normal user visits that page later, their browser reads the attacker’s script and executes it. Now this code snippet could be anything like getting details of certificates of normal user or anything that attacker wants. Usually they often steal the user’s session cookies and allowing the attacker to hijack their account.</p><p><strong>The Fix:</strong> <strong>Output Encoding</strong>. The website needs to convert special characters (like “&lt;”and “&gt;”) into a safe text format so the browser knows it’s just a comment to display, not code to run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pz_WSm4ROj9rUnWP5G3P-Q.png" /><figcaption>XSS Attack</figcaption></figure><h3>4. Buffer Overflows (The Spill-Cup)</h3><blockquote><strong>The Flaw:</strong> Coming from a background in system engineering and DevOps, I can tell you that poorly configured memory limits are a ticking time bomb. Every application allocates a specific amount of memory (a buffer) to store data. Once that is exceeds, you are on our way to have your application crashed.</blockquote><p><strong>The Attack:</strong> Imagine a 10-ounce glass. If you pour 12 ounces of water into it, it overflows onto the table. A Buffer Overflow works in the same way. Attacker deliberately sends too much data or requests to an application’s memory block. The excess data spills over into adjacent memory spaces, which can crash the system (causing a Denial of Service) or, worse, allow the attacker to overwrite legitimate code with their own malicious instructions.</p><p><strong>The Fix:</strong> Use modern programming languages that automatically manage memory, and implement security controls like <strong>ASLR</strong> (Address Space Layout Randomization). In web server like Nginx web server you can try to add rate limiting and buffer overflow size to put a limit on all the data/requests that is being sent to web server. Once that amount is crossed the service will start accepting and blocking or will drop any data sent to avoid DoS and Buffer Overflow limit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_dDZExDrqur_FR7BB6VP4g.png" /><figcaption>Buffer Overflow</figcaption></figure><h3>The Takeaway</h3><p>Security is not something you “bolt on” at the end of building an application. it has to be baked in from the very first line of code. I always say this and will keep saying this. <strong>Security start with the mindset</strong>. You need to develop a security mindset to protect your assets. This will help you embed security at each part or phase of application naturally.</p><p>Whether it’s sanitizing user inputs to stop an SQL Injection or managing memory to prevent an overflow, <strong>Secure Coding Practices</strong> are the ultimate defense against application attacks.</p><p><strong>Question for the comments:</strong> Which of these vulnerabilities do you think is the hardest for a development team to defend against? Let me know below!</p><p>#AppSec #Cybersecurity #InfoSec #SQLInjection #ZeroDay #VulnerabilityManagement #TechBlog #StudentJourney #DevSecOps</p><p>Disclaimer: All the images are AI generated for better understanding.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8424e969e428" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hacking Humans ( The Art of Social Engineering ) — Cybersecurity Unlocked: Episode 10]]></title>
            <link>https://medium.com/@kiteyyash3/hacking-humans-the-art-of-social-engineering-cybersecurity-unlocked-episode-10-de8747af0413?source=rss-1c31f195dc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/de8747af0413</guid>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cybersecurity-awareness]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyber-security-awareness]]></category>
            <dc:creator><![CDATA[Yash Kitey]]></dc:creator>
            <pubDate>Fri, 13 Feb 2026 20:47:21 GMT</pubDate>
            <atom:updated>2026-02-13T20:47:21.693Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cybersecurity Unlocked: A Journey into Cybersec with Yash</h3><blockquote>When people imagine a “hacker,” they picture a guy in a dark hoodie, furiously typing green code onto a black screen, trying to break a complex encryption algorithm by brute force.</blockquote><blockquote>That’s Hollywood.</blockquote><blockquote>In reality, if an attacker wants your password, they usually won’t spend weeks trying to crack your company’s firewall. Why would they try to smash through a bank vault door with a hammer when they can just ask the security guard for the key?</blockquote><p>This is the grim reality of cybersecurity: <strong>You can buy the most expensive firewalls, deploy the most advanced AI threat detection, and encrypt every byte of data. But all of that technology can be defeated by a single employee clicking a link that promises a free Starbucks gift card.</strong></p><blockquote><strong>Welcome to the world of Social Engineering — the art of hacking humans.</strong></blockquote><p>In Episodes 8 and 9, we covered threat actors and their malware weapons. Today, we cover their most effective delivery mechanism: <strong>You</strong>.</p><h3>What is Social Engineering?</h3><p>Social Engineering isn’t a technical exploit. it’s a con game. It’s the act of manipulating people into performing actions or divulging sensitive information.</p><p>It relies on a simple, uncomfortable truth: Humans are helpful, trusting, and easily frightened. Attackers exploit these traits to bypass technical controls entirely. Why hack a server when you can just hack the person with access to the server?</p><p>Here is a detailed breakdown of the psychological arsenal attackers use against us.</p><h3>The Digital Toolkit: Phishing and Its Cousins</h3><p>The most common form of social engineering happens digitally.</p><h4>1. Phishing (The Dragnet)</h4><p>This is the “spray and pray” approach. Attackers send emails to millions of people hoping a small percentage will take the bait.</p><ul><li><strong>The Scenario:</strong> You get an email that looks like it’s from Microsoft/Google/Netflix saying, “Your account has been suspended! Click here to verify.”</li><li><strong>The Goal:</strong> To get you to click a malicious link that downloads malware (like the Ransomware we discussed in Ep 9) or directs you to a fake login page to steal your credentials.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PKg7-Bm5WTlwAH0EFfqBSA.png" /><figcaption>Phisihng Email to reset password</figcaption></figure><h4>2. Spear Phishing &amp; Whaling (The Sniper)</h4><p>This is where it gets scary. Regular phishing is generic. <strong>Spear Phishing</strong> is highly targeted.</p><ul><li>The attacker researches <strong>you</strong> specifically using LinkedIn and social media. They know your job title, your boss’s name, and the projects you are working on.</li><li><strong>The Scenario:</strong> Instead of a generic “Dear User,” the email says, <em>“Hi Yash, Dr. Phil needs those vulnerability reports by noon. Can you review this attachment first?”</em> Because it includes specific, correct details, you are much more likely to trust it.</li><li><strong>Whaling:</strong> This is spear phishing targeting a “big fish” like a CEO or CFO, usually to authorize a massive fraudulent wire transfer.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SRKu5UaY-5iLhiAMkE-aGQ.png" /><figcaption>Spear Phishing</figcaption></figure><h4>3. Vishing (Voice Phishing)</h4><p>Attacks that happen over the phone.</p><ul><li><strong>The Scenario:</strong> You get a call with a spoofed Caller ID that says “IT Department.” The panicked voice on the other end says they detect a virus on your machine and need your password <em>immediately</em> to stop it.</li><li><strong>The Reality:</strong> It’s an attacker using urgency to fluster you into handing over credentials.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a8pw-hJ1S-mMlx7KWQEUMg.png" /><figcaption>Vishing</figcaption></figure><h4>4. Smishing (SMS Phishing)</h4><p>Attacks that happen via text message.</p><ul><li><strong>The Scenario:</strong> “USPS: We cannot deliver your package due to an incomplete address. Click here to update delivery instructions.”</li><li><strong>The Reality:</strong> We are trained to trust text messages more than email. One tap on that link on your phone can compromise the device.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7cLdE6fYQJCP7-yf7RtEGA.png" /></figure><h3>The Real-World Toolkit: Pretexting and Physical Attacks</h3><p>Not all social engineering happens behind a screen. Some of the most effective attacks happen face-to-face or through elaborate setups.</p><h4>5. Pretexting (The Setup)</h4><p>Pretexting is the creation of a fabricated scenario (the pretext) to build trust <em>before</em> launching the attack. It’s the backstory of the con.</p><ul><li><strong>Example:</strong> An attacker calls a company receptionist pretending to be from an external audit firm. They spend 10 minutes casually chatting to build rapport. Only <em>after</em> establishing trust do they ask for the internal phone directory “just to verify some names for the audit.” The receptionist, now trusting them, hands over the entire company contact list.</li></ul><h4>6. Tailgating &amp; Piggybacking (The Physical Breach)</h4><p>Why hack an RFID badge reader when you can just smile?</p><ul><li><strong>Tailgating:</strong> An attacker waits outside a secure door. When an authorized employee unlocks it, the attacker catches the door before it closes and slips in behind them.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KlUsn_0bbcMNKiBDVlsGSw.png" /><figcaption>Tailgating</figcaption></figure><ul><li><strong>Piggybacking:</strong> The attacker approaches the door carrying two heavy boxes of donuts. An authorized employee, wanting to be polite, holds the secure door open for them. The attacker is now inside the secure facility thanks to human kindness.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nt_9ABuqty1jnQnLdMHf1A.png" /><figcaption>Piggybacking</figcaption></figure><h3>The Psychology: Why We Fall For It</h3><p>You might be reading this thinking, <em>“I would never fall for that.”</em></p><p>But attackers don’t catch you on your best day. They catch you when you are tired, stressed, or distracted. They will wait for their chance. They use specific psychological triggers to short-circuit your critical thinking:</p><ol><li><strong>Urgency:</strong> “Act NOW or your account will be deleted.” (Stops you from thinking).</li><li><strong>Fear:</strong> “ The IRS has a warrant for your arrest.” (Induces panic).</li><li><strong>Authority:</strong> “This is the CEO calling.” (We are trained to obey).</li><li><strong>Greed/Curiosity:</strong> “You’ve won a free iPhone!” or “Salary_Report_2025.pdf”</li></ol><h3>The Defense: Patching the Human</h3><p>You cannot install antivirus software on a human brain. The only defense against social engineering is <strong>skepticism and behavior change</strong>. You have to to careful, aware of surroundings and, always be skeptical</p><ul><li><strong>Stop and Think:</strong> If an email or call creates a sudden sense of urgency or fear, that is a massive red flag. Pause. Do not open it or click any links on it until you have verified that it is from the authenticated source.</li><li><strong>Verify Out-of-Band:</strong> If you get a strange email from your boss asking for a wire transfer, do <em>not</em> reply to the email. Pick up the phone and call them on a known, trusted number to verify.</li><li><strong>Hover Before You Click:</strong> On a computer, hover your mouse over a link to see the <em>actual</em> destination URL before clicking. Does microsoft-support-verify.com actually look legitimate? (Hint: No).</li></ul><h3>The Takeaway</h3><p>We spend billions on technology to secure our networks. But your security is only as strong as your most gullible employee on their most tired Friday afternoon.</p><p><strong>The strongest firewall you have is a paranoid human.</strong></p><p><strong>Question:</strong> What’s the most convincing phishing email or scam call you’ve ever received? Did you almost fall for it?</p><p>Disclaimer: All images are created using AI and AI is used for grammatical and stylistic changes.</p><p>#Cybersecurity #SocialEngineering #Phishing #HumanFirewall #InfoSec #CybersecurityUnlocked #StudentJourney #CompTIASecurityPlus</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de8747af0413" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Defend Against 5 Types of Threat Actors — Cybersecurity Unlocked Ep. 9]]></title>
            <link>https://medium.com/@kiteyyash3/how-to-defend-against-5-types-of-threat-actors-cybersecurity-unlocked-ep-9-12141aa79468?source=rss-1c31f195dc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/12141aa79468</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity-awareness]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Yash Kitey]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 17:08:56 GMT</pubDate>
            <atom:updated>2026-01-19T17:08:56.755Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to Defend Against 5 Types of Threat Actors — Cybersecurity Unlocked Ep. 9</h3><h3>Cybersecurity Unlocked: A Journey into Cybersec with Yash</h3><blockquote>In Episode 8, we met the “Cast of Characters” — from the annoying Script Kiddies to the terrifying Nation-States.</blockquote><blockquote>But knowing your enemy is only Step 1. Step 2 is the most important part of the job: <strong>How do we actually stop them?</strong></blockquote><blockquote>In cybersecurity, you don’t use a bazooka to kill a mosquito, and you definitely don’t bring a flyswatter to a tank battle. Different threat actors require different defensive strategies. If you try to stop a <strong>Nation-State spy</strong> with the same tools you use for a <strong>Script Kiddie</strong>, you will fail.</blockquote><blockquote>Here is the defensive playbook for stopping the 5 major types of adversaries.</blockquote><h3>1. Stopping the “Script Kiddie” (The Amateur)</h3><p><strong>The Threat:</strong> They use pre-made tools to scan thousands of computers for easy openings. They aren’t trying to pick the lock; they are just walking down the street checking if any front doors were left open.</p><p><strong>The Defense:</strong> <strong>Basic Hygiene &amp; Patching.</strong></p><ul><li><strong>Patch Management:</strong> Keep your software updated. Script kiddies rely on old vulnerabilities (like the ones from 2017). If you patch, their tools stop working.</li><li><strong>Change Default Passwords:</strong> Never leave a router or server with admin/admin.</li><li><strong>The Logic:</strong> If you aren’t an “easy target,” they will get bored and move on to someone else.</li></ul><h3>2. Stopping the “Hacktivist” (The Protester)</h3><p><strong>The Threat:</strong> They want to embarrass you or take your website offline (DDoS) to send a political message. They target your reputation and availability.</p><p><strong>The Defense:</strong> <strong>Resilience &amp; WAFs.</strong></p><ul><li><strong>DDoS Protection:</strong> Use services like Cloudflare or AWS Shield. These act like a giant sponge that absorbs the flood of traffic so your actual server doesn’t crash.</li><li><strong>Web Application Firewalls (WAF):</strong> This stops them from defacing your website with graffiti or political messages.</li><li><strong>The Logic:</strong> Make your public-facing systems strong enough to withstand the noise.</li></ul><h3>3. Stopping “Organized Crime” (The Mafia)</h3><p><strong>The Threat:</strong> They want one thing: Money. They will use <strong>Phishing</strong> to steal credentials or <strong>Ransomware</strong> to lock your data and demand payment.</p><p><strong>The Defense:</strong> <strong>Training &amp; Backups.</strong></p><ul><li><strong>Security Awareness Training:</strong> Technology fails when humans make mistakes. Train employees to spot suspicious emails so the hackers never get in.</li><li><strong>Offline Backups:</strong> This is your “Get Out of Jail Free” card. If they encrypt your data with Ransomware, you don’t have to pay the ransom. You just wipe the system and restore from your backup.</li><li><strong>The Logic:</strong> Remove their leverage. If they can’t lock your data permanently, they can’t extort you.</li></ul><h3>4. Stopping the “Insider Threat” (The Betrayal)</h3><p><strong>The Threat:</strong> An employee with legitimate access who goes rogue (or makes a careless mistake). Firewalls don’t work here because the threat is already <em>inside</em> the building. <strong>The Defense:</strong> <strong>Least Privilege &amp; DLP.</strong></p><ul><li><strong>Principle of Least Privilege:</strong> Don’t give an intern “Admin” access. Give users only the exact level of access they need to do their job, and nothing more.</li><li><strong>DLP (Data Loss Prevention):</strong> These are tools that monitor for sensitive data leaving the company. If an employee tries to email the entire customer database to a personal Gmail account, DLP blocks it.</li><li><strong>The Logic:</strong> Limit the damage a single person can do.</li></ul><h3>5. Stopping the “APT / Nation-State” (The Spy)</h3><p><strong>The Threat:</strong> Highly funded, patient, and sophisticated. They will find a way in, often staying hidden for months to steal intelligence.</p><p><strong>The Defense:</strong> <strong>Defense in Depth &amp; Threat Hunting.</strong></p><ul><li><strong>Zero Trust Architecture:</strong> Assume the breach has already happened. “Trust no one, verify everything.”</li><li><strong>Network Segmentation:</strong> Divide your network into small, secure zones. If they hack the lobby (your web server), make sure they can’t open the door to the vault (your database).</li><li><strong>Threat Hunting:</strong> Don’t wait for an alert. Proactively search your network for clues that a spy is hiding in the shadows.</li></ul><h3>The Takeaway</h3><p>There is no “Silver Bullet” in cybersecurity. You can’t buy one tool to stop everyone.</p><ul><li>For the kid in the basement? <strong>Patch.</strong></li><li>For the criminal ring? <strong>Backup.</strong></li><li>For the spy? <strong>Hunt.</strong></li></ul><p>This layered approach is what we call <strong>Defense in Depth</strong>.</p><p><strong>Question:</strong> If you had the budget for only ONE security control (Backups, Firewalls, or User Training), which one would you pick? (I’d pick User Training because humans are usually the weakest link!)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12141aa79468" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cybersecurity Unlocked: Episode 8— The Cast of Characters (Threat Actors)]]></title>
            <link>https://medium.com/@kiteyyash3/cybersecurity-unlocked-episode-8-the-cast-of-characters-threat-actors-46ff5f017307?source=rss-1c31f195dc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/46ff5f017307</guid>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Yash Kitey]]></dc:creator>
            <pubDate>Tue, 30 Dec 2025 17:37:46 GMT</pubDate>
            <atom:updated>2025-12-30T17:37:46.580Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Cybersecurity Unlocked: A Journey into Cybersec with Yash</strong></p><blockquote>When we watch movies, every hacker looks the same: a lone genius in a basement, with a black screen with green lines of code running on the screen, typing furiously to break a firewall.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jZJUTDuuCCxt4EZ_Syt_Ew.png" /></figure><p>But in the real world (and in cybersecurity frameworks), that is just one tiny slice of the pie. We aren’t fighting a monolith or any single person behind a computer. We are fighting a diverse cast of characters, ranging from bored teenagers to military units.</p><p>To defend a network, We first have to profile the enemy. We analyze them based on three key metrics: <strong>Sophistication</strong> (skill level) , <strong>Resources</strong> (funding) , and <strong>Motivation</strong> (why they do it).</p><p>Here is the full breakdown of the enemies we face:</p><h3>1. The Mercenaries (Organized Crime)</h3><ul><li><strong>Who they are:</strong> These aren’t random individuals. These are sophisticated criminal enterprises that operate like Fortune 500 companies. They often have payroll, HR, and even “customer support” to help you pay them.</li><li><strong>The Motivation:</strong> Pure <strong>Financial Gain</strong>. They don’t care about your politics or your secrets or anything else. All they care about your is your wallet.</li><li><strong>The Tactic:</strong> They are the kings of <strong>Ransomware</strong> and <strong>Blackmail</strong>. They lock your data and sell the key back to you. with the help of ransomware they will encrypt all your data and blackmail you to pay them a sum of amount to get your own data back.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yXzyauMaMLp8Y41TgjgMGA.png" /></figure><h3>2. The Spies (Nation-State Actors) ️</h3><ul><li><strong>Who they are:</strong> Government-sponsored hacking teams. They have massive <strong>resources and funding</strong> and an extreme level of <strong>sophistication</strong>. These are generally teams working with the government to spy on terrorist / other nations.</li><li><strong>The Motivation:</strong> <strong>Espionage,</strong> <strong>War or proactive way to counter the the incoming threat. </strong>They want strategic secrets intellectual property, defense plans, or voter data etc.</li><li><strong>The Danger:</strong> They play the long game (often called Advanced Persistent Threats). If they are in your network, they don’t want to break things; they want to stay invisible for years and secretly collect your data and watch for patterns and use that data for their own intelligence.</li></ul><h3>3. The Ideologists (Hacktivists)</h3><ul><li><strong>Who they are:</strong> Attackers driven by a cause rather than cash.</li><li><strong>The Motivation:</strong> <strong>Philosophical or Political beliefs</strong>. They want to expose corruption, protest a policy, or embarrass a target.</li><li><strong>The Tactic:</strong> They often rely on <strong>Data Exfiltration</strong> (leaking emails) or <strong>Service Disruption</strong> (taking down a website) to make a statement.</li></ul><h3>4. The Betrayal (Insider Threats)</h3><ul><li><strong>Who they are:</strong> The most dangerous call comes from inside the house. This is an <strong>Internal</strong> threat, someone with legitimate access (an employee or contractor).</li><li><strong>The Motivation:</strong> It varies. It could be <strong>Revenge</strong> (a fired employee) , <strong>Financial Gain</strong> (bribed by a competitor), or simple negligence.</li><li><strong>The Danger:</strong> Traditional firewalls point <em>outward</em>. They are useless against someone who already has a badge and a login.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ADwzeSi7MAg4vJ1xbPmXWw.png" /></figure><h3>5. The Graffiti Artists (Unskilled Attackers)</h3><ul><li><strong>Who they are:</strong> Often called “<em>Script Kiddies</em>.” These are attackers with <strong>low sophistication</strong> who use off-the-shelf tools they don’t fully understand.</li><li><strong>The Motivation:</strong> Bragging rights, curiosity, or simply creating <strong>chaos</strong>.</li><li><strong>The Reality:</strong> While they aren’t “pros,” there are millions of them. They are like vandals checking every door handle to see if one is unlocked.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HL-myB_3g8B1kpNTttBbDw.png" /></figure><h3>6. The Silent Risk (Shadow IT)</h3><ul><li><strong>Who they are:</strong> This is a unique category. It refers to employees installing unauthorized software or hardware on the company network without IT knowing.</li><li><strong>The Motivation:</strong> Usually efficiency they just want to get their job done faster but they neglect compliance and increase the risks.</li><li><strong>The Danger:</strong> It creates an unmonitored <strong>Attack Surface</strong> that security teams can’t patch or protect.</li></ul><blockquote><strong>The Takeaway:</strong> You cannot use the same shield for every sword. Defending against a <strong>Nation-State</strong> requires totally different tools than stopping a <strong>Script Kiddie</strong>. Understanding the <strong>Actor</strong> is the first step in building the <strong>Defense</strong>.</blockquote><p><strong>Question for the class:</strong> Which of these scares you the most? (Personally, the <strong>Insider Threat</strong> keeps me up at night how do you stop someone who has the keys?)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46ff5f017307" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cybersecurity Unlocked: Episode 7 — The “Cloud” is Just Someone Else’s Computer]]></title>
            <link>https://medium.com/@kiteyyash3/cloud-computing-security-basics-f74f0d55bddf?source=rss-1c31f195dc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f74f0d55bddf</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[google]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Yash Kitey]]></dc:creator>
            <pubDate>Mon, 01 Dec 2025 17:02:36 GMT</pubDate>
            <atom:updated>2025-12-01T17:02:36.739Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cybersecurity Unlocked: Episode 7 — The “Cloud” is Just Someone Else’s Computer</h3><p><strong>Cybersecurity Unlocked: A Journey into Cybersec with Yash</strong></p><blockquote>Where are all your photos right now?</blockquote><blockquote>Are they physically inside your phone? Probably not all of them. They are in iCloud, or Google Photos, or OneDrive. They are “in the Cloud.”</blockquote><blockquote>But here is the funny thing about the “Cloud.” It’s not actually a fluffy white thing in the sky.</blockquote><p>There is a famous joke in the tech world: <strong>“There is no cloud, it’s just someone else’s computer.”</strong></p><p>(And yes, that is basically true.)</p><p>When you use Amazon Web Services (AWS) or Microsoft Azure, you are actually renting a super-powerful computer sitting in a massive, freezing cold warehouse in Virginia (or Ohio, or Mumbai). You don’t own the hardware but you just rent the power.</p><p>So, today we are talking about <strong>Cloud Computing</strong>. But because we are security people, we have to ask the big questions: If my data is on <em>someone else’s</em> computer… how do I keep it safe?(That’s what we call having a Security Mindset) And how does “Least Privilege” work when I don’t even own the building?</p><blockquote><strong>What is Cloud Computing? (The Basics)</strong></blockquote><p>In the old days, if you wanted to build an app, you had to buy a physical server, put it in a room, install air conditioning, and hire a guy to watch it.</p><p><strong>Cloud Computing</strong> is the same but on-demand delivery of IT resources over the internet. Instead actually buying all the infrastructure you are just renting the infrastructure (who already has it) for your purpose. You won’t actually own the infrastructure for your application but you will be hosting your application on someone else’s infrastructure so that you don’t have to manage all that stuff.</p><p>Instead of buying the car, you are calling an Uber.</p><ul><li>You pay only for what you use.</li><li>You can scale up (get a bigger car) instantly.</li><li>You can turn it off when you’re done.</li></ul><p>But this convenience brings up a huge security challenge.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C8iavtM4hzMTcxf8fu9s1Q.png" /><figcaption>Cloud</figcaption></figure><blockquote><strong>Question 1: How Does “Least Privilege” Work in the Cloud?</strong></blockquote><p>We talked about <strong>Least Privilege</strong> in our last episode (Episode 6: Zero Trust). Remember? It means giving someone <em>only</em> the keys they need, and nothing else.</p><p>But in a Cloud environment, this gets tricky.</p><p>In a physical office, you can just lock the door to the server room. But in the Cloud, the “server room” is a website dashboard.</p><p>So, how do we enforce Least Privilege here? We use something called <strong>IAM (Identity and Access Management).</strong></p><p>Think of the Cloud environment (like AWS) as a giant hotel. When you log in, you don’t get a “Master Key” that opens every room. That would be a disaster! (If a hacker stole that key, they would own your entire company).</p><p>Instead, we create <strong>Roles and Policies</strong>.</p><ul><li><strong>The Developer Role:</strong> We give them a digital key card that <em>only</em> opens the “Test Server” room. If they try to open the “Billing” room? <em>Access Denied.</em></li><li><strong>The Finance Role:</strong> We give them a key that <em>only</em> opens the “Billing” room. If they try to delete a server? <em>Access Denied.</em></li></ul><p>This is Least Privilege in action in the Cloud. We don’t rely on physical locks; we rely on <strong>Policy-Based Access Control</strong>. You will only be able to access the resources that you are allowed to. These rules are called policies. We write a rule (a policy) that says: <em>“Yash can view the database, but he cannot delete the database.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L4rw2H-RLL59C-dcq0mxAA.png" /></figure><blockquote><strong>Question 2: The “Company Laptop” Mystery</strong></blockquote><p>This brings us to a question I get asked a lot.</p><p><em>Scenario: You have a company-provided laptop. You are sitting at a Starbucks. You are NOT on the office network. But somehow, you can still open the company’s internal HR app, while the guy sitting next to you (on his personal laptop) can’t.</em></p><p>How does that work? What kind of security restriction is this?</p><p>This is where Cloud Security meets <strong>Endpoint Security</strong>.</p><p>Even though you are at Starbucks, your laptop isn’t really “at Starbucks.”</p><ol><li><strong>The Secure Tunnel (VPN or ZTNA):</strong> Usually, your company laptop has a special piece of software running in the background (like a VPN client or a Zero Trust agent). This software creates a secret, encrypted tunnel through the internet. So, even though you are on the “dirty” public Wi-Fi, your data is traveling through a bulletproof tube directly to the company’s Cloud (Company’s actual infrastructure like servers etc.). To the Cloud, it looks like you are sitting inside the office!</li><li><strong>Device Authentication (The “Company Laptop” Check):</strong> Remember <strong>AAA</strong> (Authentication, Authorization, Accounting) from Episode 4? The Cloud doesn’t just check <em>who</em> you are (your password). It checks <em>what</em> you are using. The company application asks: <em>“Is this request coming from a Managed Device?”</em></li><li>Your company laptop has a digital certificate (like a hidden ID card) installed deep in its system.</li></ol><ul><li><strong>Company Laptop:</strong> “Here is my certificate. I am a trusted device. I have my antivirus running.” -&gt; <strong>Access Granted.</strong></li><li><strong>Personal Laptop:</strong> “I don’t have the certificate.” -&gt; <strong>Access Denied.</strong></li></ul><p>This is called <strong>Conditional Access</strong>. The “restriction” isn’t just a password; it’s a check on the <em>health and identity of the device itself</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z9LSN2LlNOJ4C8qFpFOPsA.png" /></figure><blockquote><strong>The Big Picture</strong></blockquote><p>Cloud Computing changes the game. We aren’t building physical walls anymore.</p><p>We are building logical walls using <strong>IAM policies</strong> (for Least Privilege) and <strong>Encrypted Tunnels</strong> (for secure access).</p><p>The computer might belong to Amazon or Microsoft, but the <strong>Security</strong>? That is still 100% our responsibility.</p><h3>A Journey, Not a Destination</h3><p>We are moving fast now! We’ve gone from basic definitions to understanding how <strong><em>giant cloud networks secure our data</em></strong>.</p><p>Next time, we might look at what happens when these defenses fail… and how we hunt for the bad guys.</p><p>Let me know if this clears up the confusion about Cloud and company access!</p><p>Disclaimer : All the images are AI-Generated !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f74f0d55bddf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cybersecurity Unlocked: Episode 6 — The “Trust No One” Rule]]></title>
            <link>https://medium.com/@kiteyyash3/cybersecurity-unlocked-episode-6-the-trust-no-one-rule-757cebf0647c?source=rss-1c31f195dc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/757cebf0647c</guid>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[zero-trust]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Yash Kitey]]></dc:creator>
            <pubDate>Fri, 07 Nov 2025 05:31:59 GMT</pubDate>
            <atom:updated>2025-11-07T05:31:59.575Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cybersecurity Unlocked: Episode 6 — The “Trust No One” Rule</h3><h3>Cybersecurity Unlocked: A Journey into Cybersec with Yash</h3><blockquote>What is the first thing you do when a guest comes at your house?</blockquote><blockquote>You unlock the front door and let them in. Once they are inside, you trust them, right? You trust them to use the guest bathroom, to sit on your couch, to walk into the kitchen. They are “inside,” so they are “trusted.”</blockquote><p>For decades, this is exactly how we built our computer networks.</p><p>We spent millions on a strong “front door” which is nothing but a big firewall that kept attackers out. We called it the “castle and moat” model. (As we looked in previous episode) We figured anyone <em>inside</em> the network was a “good guy” and could be trusted.</p><p>But what happens if a bad guy steals an employee’s keys (their password/credentials)? What about an employee who is already inside and wants to snoop around? Or what about when your “house” isn’t a house at all, but your data is in the cloud, and your employees are at a coffee shop?</p><p>The “front door” model is broken. The Big wall has fallen. So to counter this we introduced another security model. This model is based on counterpart of Castle and Moat that is “Trust No One”. (Yes, Not even the CEO of the company)</p><p>That new rule is <strong>Zero Trust</strong>.</p><blockquote><strong><em>So, What is Zero Trust?</em></strong></blockquote><p>The idea is simple, and it’s right in the name. It’s a security model built on this one core philosophy:</p><p><strong>“Never trust, always verify.”</strong></p><p>That’s it.</p><p>Zero Trust means we don’t trust <em>anyone</em> by default. Not you, not your boss, not your co-worker. It doesn’t matter if you are “inside” the network or “outside.”</p><p>Every single time you try to open a file, access an app, or look at any data, the system stops and asks, “Who <em>are</em> you, and are you <em>really</em> allowed to do this?” <em>(Who are you — authentication, Are you allowed to do this -authorization, we saw this in CIA triad episode)</em></p><p><em>Think of it this way: instead of just one big lock on the front door, </em><strong><em>Zero Trust puts a lock on every single door inside the house.</em></strong></p><p>If you want to enter the kitchen? You need a key. If you want to open the fridge? You need a key. If you want to use the bathroom? You need a key. And every time, we verify it’s <em>you</em> and that you’re <em>allowed</em> in that specific room, for that specific reason, at that specific time.</p><p>It’s a huge shift in thinking.</p><blockquote><strong><em>How Does It Actually Work?</em></strong></blockquote><p>Zero Trust isn’t one single product you can buy. It’s a <em>strategy</em>, or you can say its a entire framework, a new way of building our “house.” This strategy stands on a few main pillars:</p><h4>1. Identity is Everything (Who are you?)</h4><p>This is the most important pillar. Before we can let you in <em>any</em> room, we have to be <em>100% sure</em> you are who you say you are. A simple password isn’t good enough (someone could steal it!).</p><p>This is where <strong>Multi-Factor Authentication (MFA)</strong> comes in. It’s the same as your bank:</p><ul><li><strong>Something you know</strong> (your password)</li><li><strong>Something you have</strong> (a one-time code on your phone)</li></ul><p>Only with <em>both</em> can you prove your identity. Zero Trust <em>demands</em> this for everything.</p><h4>2. Least Privilege (What are you allowed to do?)</h4><p>Okay, so we’ve verified it’s <em>you</em>. Great.</p><p>Does that mean you should be able to walk into the finance department’s “room” and see everyone’s salary? No!</p><p>The Principle of Least Privilege means you are <em>only</em> given the absolute minimum access you need to do your job. Just like your Netflix subscription lets you <em>watch</em> movies but doesn’t let you <em>delete</em> movies from Netflix’s servers.</p><p>You’re a sales intern? You get access to the sales folder, and <em>only</em> the sales folder. You can’t even <em>see</em> that the finance folder exists.</p><h4>3. Micro-segmentation (The “Locked Rooms”)</h4><p>This is the fancy term for “putting locks on every door.”</p><p>Instead of having one big, open-plan office where everyone can wander around, we “micro-segment” our network. We build small, digital, walled-off zones around every single important app or data.</p><p>The finance app is in one “room.” The email server is in another “room.”</p><p>So, even if a hacker <em>does</em> break into one room (say, the printer network), they’re trapped. The doors to all the <em>other</em> rooms are locked. This prevents a small breach from becoming a total disaster.</p><h4>4. Control Policies and Procedures (The “Rulebook”)</h4><p>This is the brain of the whole operation. A Zero Trust system runs on a powerful “policy engine.” Think of it as a security guard with a very specific, dynamic rulebook.</p><p>For every single access request, the policy engine asks:</p><ul><li><strong>Who</strong> is asking? (Is the user verified?)</li><li><strong>What</strong> are they trying to access? (Is it sensitive data?)</li><li><strong>Where</strong> are they asking from? (Is it a trusted company laptop on the office network, or a personal phone in a coffee shop?)</li><li><strong>When</strong> are they asking? (Is it during normal work hours?)</li><li><strong>How</strong> are they asking? (Is the device’s software updated and secure?)</li></ul><p>This isn’t a one-time check. It’s a continuous evaluation. This constant checking is what makes the system so powerful.</p><blockquote><strong><em>The Big Picture: How This Changes Everything</em></strong></blockquote><p>When we combine all these pillars, we get some amazing benefits over traditional security models that we that completely change the security game.</p><p><strong>Adaptive Identity:</strong> The system is smart. If you log in from your normal work laptop at 10 AM, it might just require your password and a phone notification (MFA). But if the <em>same account</em> tries to log in from a new country at 3 AM, the policy engine sees this as high-risk. It can then <em>adapt</em>, requiring more proof of identity like a biometric scan or answering security questions before granting access. It adapts the security to the risk.</p><p><strong>Threat Scope Reduction:</strong> Because of micro-segmentation and the principle of least privilege, if the system is hacked then the hackers are trapped. Even if they compromise one user’s account, they can’t move laterally across the network. This means then cannot jump from one section to another within same platform. The “blast radius” of an attack is tiny. They might get into the kitchen, but they’ll never get to the master bedroom where the valuables are kept.</p><p><strong>Policy-Driven Access Control:</strong> This is the core of it all. Access is no longer all-or-nothing. It’s dynamic and granular, driven by the “rulebook” (the policies we set). We can create rules like, “Allow the marketing team to access the social media app, but only from company-managed devices during business hours.” This gives us an incredible level of control that was impossible in the old “castle and moat” world.</p><blockquote><strong><em>A Journey, Not a Destination</em></strong></blockquote><p>No company can just flip a switch and “be Zero Trust” overnight. It’s a big, slow, and important shift.</p><p>It’s about moving away from that old, friendly “trust-once-you’re-in” model to a new, smarter, “always-be-suspicious” model. In our journey in cybersecurity, this is one of the biggest and most important ideas for building the future of security.</p><p>That’s it for this one! I hope this post on Zero Trust was clear and helpful. Are you loving the series so far? Please let me know your views about these blogs, your feedback is what keeps this journey going. See you in Episode 7!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=757cebf0647c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Episode 5: Fundamentals Of Cybersecurity — Security Model]]></title>
            <link>https://medium.com/@kiteyyash3/episode-4-fundamentals-of-cybersecurity-security-model-a9ceb5f73bac?source=rss-1c31f195dc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/a9ceb5f73bac</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[information-technology]]></category>
            <category><![CDATA[networking]]></category>
            <dc:creator><![CDATA[Yash Kitey]]></dc:creator>
            <pubDate>Fri, 10 Oct 2025 16:29:57 GMT</pubDate>
            <atom:updated>2025-10-10T19:32:17.063Z</atom:updated>
            <content:encoded><![CDATA[<h3>Episode 5: Fundamentals Of Cybersecurity — Security Model</h3><h3>Cybersecurity Unlocked: A Journey into Cybersec with Yash</h3><blockquote>Imagine you just bought a beautiful piece of land in prime residential area and now you’re ready to build your dream house that you have been dreaming about from a long time. Now that you have land would you just start dividing the piece of land into sections and start throwing your stuff there ? build aa wall and a door directly and call it a HOME?</blockquote><blockquote>Will that even work? Crazy, right?</blockquote><p>Of course not! You would follow a step-by-step process. You will start with what we call a<em> </em><strong><em>blueprint</em></strong> — a detailed plan showing where everything should go, how will you structure your house and all the necessary steps needed make a a home. First step will be llaying a foundation that is digging up the hole in ground, then you will put up some structural frames which will act as outline of the house you are trying to build. Once that is done, you will start with walls and internal design, right? You will follow a step by step guide for this which will act as a instruction manual and a map for to build your house. Now this is nothing but a <strong><em>model </em></strong>we are following to ensure we have a strong, functional, and safe house, not just a pile of materials.</p><blockquote><strong>Security Model</strong></blockquote><p>Believe it or not, when we are building the security for an entire organization, we follow that exact same logic. That essential<strong><em> blueprint</em></strong>, the <strong>master plan</strong> for our <strong>digital defense</strong>, is what we call a <strong>Security Model</strong>.</p><p>So, in our journey so far, we’ve covered some big ideas. We’ve figured out what we need to protect with the <em>CIA Triad </em>and the<em> invisible force</em> that keeps our digital world safe, <em>the AAA</em>. But the main question is, how do these work together? What binds them together so we can use it practically?</p><p>The answer is simple, our <strong>Blueprint </strong>which is know as<strong> Security model. T</strong>he master plan that binds them all together.</p><p><strong><em>Technical Definition </em></strong><em>: Security Model is a framework, a set of rules that outlives how a system or organization will protect and manage the data.</em></p><blockquote><strong>We have our security tools, so why do we need this extra layer of rules to follow ?</strong></blockquote><p>The most important reason is that , a security model helps us change from a <strong>random</strong> use of our security tools to a <strong>structured</strong> one. Let’s think about this for a second. Without a plan, an organization might just buy a bunch of security products, that is a firewall, an antivirus, some monitoring software and many more and hope they all work. It’s like having a pile of bricks, wood, and windows but no blueprint. But we don’t want that. we want them to work together to secure the organizations.</p><p>With the help of a security model, we create a <strong>structured system</strong>. This helps us bridge the gap between our high-level security policies (the big rules we want to follow) and the actual tools we use every day.</p><p>Suddenly, all our tools start to work together <strong>coherently</strong>, like a well-oiled machine instead of a bunch of separate parts. This structured approach makes sure there are no weak links or forgotten corners in our digital house. It’s the plan that makes sure everything works together to keep you safe.</p><blockquote><strong>Different security models</strong></blockquote><p>So, if a security model is our blueprint, can one blueprint be used by all organizations?</p><p>Let’s go back to our example of house. Would you use the same blueprint you designed for your personal cozy dream house to build a massive shopping mall or let’s say a high-tech office complex? Of course not. A mall needs huge open spaces, tons of parking, and dozens of separate stores. An office complex needs server rooms, conference areas, and a completely different layout. so your blueprint of house will be useless in this area.</p><p>Like different structures need different blueprints, In cybersecurity also different goals need different security models.</p><p>Different organizations have different primary goals, and they need specific security models designed to achieve their goals. One organization, like the military, might focus almost entirely on <strong>Confidentiality</strong>. Their number one priority is keeping secrets safe. Another organization, like a bank, might be more focused on <strong>Integrity, </strong>so<strong> </strong>making sure the financial data can never be changed incorrectly.</p><p>To achieve these different goals, different security models were proposed and used over the years. We won’t look deep into all the security models today, but let’s take a quick peek at a few of the most famous ones to see what they were trying to solve.</p><figure><img alt="Different Types and categories of security model." src="https://cdn-images-1.medium.com/max/1024/1*YVEwRwEUYYII-5w6Sw7FYg.png" /><figcaption>Different types and categories of security models.</figcaption></figure><blockquote><strong>1. Models for Different Goals (The CIA Triad in Action)</strong></blockquote><p>This is where our old friends Confidentiality and Integrity come back to play a major role.</p><h4>A. Confidentiality-Focused (Keeping Secrets)</h4><p>Imagine you are a spy in a top-secret agency. Here information is organized by clearance levels: Public knowledge, Confidential, Secret, Top Secret. The number one rule is that information can only flow down, never up.</p><p>This is the idea behind the <strong>Bell-LaPadula Model</strong>. It’s built entirely to protect <strong>Confidentiality</strong>. It has two simple rules:</p><ul><li><strong>No Read Up:</strong> A junior agent with “Secret” clearance can’t read a “Top Secret” file.</li><li><strong>No Write Down:</strong> The director with “Top Secret” clearance can’t accidentally copy a secret into a “Confidential” report, because that could cause a leak.</li></ul><p>This model is perfect for hierarchical organizations like the <strong>military,</strong> where keeping secrets is the most important mission.</p><h4>B. Integrity-Focused (Keeping Data Accurate)</h4><p>Now, what if our main goal isn’t keeping secrets, but making sure our data is 100% accurate and trustworthy ? We don’t want our integrity to be breached. Think about a hospital’s patient records or a bank’s financial database.</p><p>This is where the <strong>Biba Model</strong> comes in. It’s the complete opposite of Bell-LaPadula and is all about <strong>Integrity</strong>. Its rules are designed to stop bad or untrusted data from messing up good data.</p><ul><li><strong>No Read Down:</strong> A critical, high-trust system (like a patient’s life support monitor) shouldn’t take input from a less-trusted source (like a random health app), because that data could be corrupt or false.</li><li><strong>No Write Up:</strong> A user with low trust levels (like a new intern) cannot make changes to highly-trusted data (like the official financial document).</li></ul><p>Perfect, let’s move on to the next section.</p><p>Here is a draft for <strong>“Models for Different Contexts,”</strong> which covers the specific business problems that led to new types of security models. It’s written in the same conversational, analogy-driven style we’ve been using.</p><p>Please feel free to change, add, or rewrite it completely so it’s a perfect match for your voice.</p><blockquote><strong>2. Models for Different Contexts</strong></blockquote><p>Sometimes, the goal isn’t as simple as just “keeping secrets” or “keeping data accurate.” But what happens when the goal isn’t just about keeping secrets or keeping data accurate? Sometimes, the <em>situation</em> a business is in creates a whole new set of problems that need a special kind of blueprint.</p><h4>A. Military vs. Commercial Context</h4><p>The strict, top-down rules of the military models don’t always fit a commercial business. Think about a bank. For a bank, the challenge isn’t just about a low-level employee changing data. Their biggest worry is about complex fraud and ensuring that financial transactions are done <em>perfectly and correctly, every single time</em>.</p><p>This is the context for the <strong>Clark-Wilson Model</strong>. It’s built for business integrity and introduces a key idea: <strong>separation of duties</strong>.</p><ul><li><strong>Example:</strong> A bank teller can’t just open the database and change a customer’s account balance directly. To do their job, they have to use a specific, pre-approved program, think of a ‘Deposit’ button or a ‘Withdrawal’ function on their screen. They can’t access the raw database themselves. All the security rules are built directly into that program. This is a genius move because it separates the person from the raw data, which is a powerful way to prevent both fraud and simple human error.</li></ul><h4>B. The “Conflict of Interest” Context</h4><p>Now for a really cool one that solves a very specific, high-stakes business problem.</p><p>Imagine you’re a top analyst at a major investment bank. Your firm advises many different, competing tech giants, and in the company’s system, you have potential access to project folders for both <strong>Google</strong> and <strong>Meta</strong>. Now suppose, this week, you are assigned to a new project to advise Google on acquiring a cutting-edge AI startup.</p><p>The moment you access the folder containing the “Google Project” files, the <strong>Brewer and Nash (Chinese Wall) Model</strong> springs into action.</p><ul><li><strong>How it Works:</strong> It instantly blocks your access to the <strong>Meta</strong> folders that you <em>could have</em> opened. A virtual “wall” is built. This ensures that your advice to Google is untainted by confidential information from their rival. This way, the system automatically protects every client by making sure you, the employee, can never be put in the middle of a conflict.</li></ul><blockquote>3. Models for Different Technologies</blockquote><p>Finally, the technology we use has a huge impact on the kind of blueprint we need. A plan that worked in an era of office buildings with desktop computers just won’t work in today’s world of cloud services and work form home.</p><h4>A. The Traditional Blueprint: The Perimeter Model</h4><p>For decades, almost every organization on the planet used the <strong>Perimeter Model</strong>. This is the <strong>Castle-and-Moat</strong> approach .</p><p>The strategy was simple: build incredibly strong walls (firewalls) around your entire company network. The main rule was that everything <em>inside</em> the castle was considered a trusted friend, and everything <em>outside</em> was a potential enemy. If you were an employee, once you got past the main bridge and main gate (by logging into the office network or a VPN), you could access most things freely.</p><p>But this brings up a scary question, right? What happens when a spy manages to sneak past the guards? Once a bad guy gets inside the walls, it’s often game over. They can roam the so called “trusted” network, looking for treasure.</p><h4>B. The Modern Blueprint: The Zero Trust Model</h4><p>As you can probably guess, the castle model is completely broken in today’s world. We have remote workers, data stored in the cloud, and people accessing things from their personal phones. There is no “inside” or “outside” anymore the network is everywhere!</p><p>This new reality demanded a completely new blueprint: the <strong>Zero Trust Model</strong>.</p><p>Imagine a top-secret government building where there is no “trusted” lobby area. To get through <em>any door</em> inside the building, whether it’s to your own office, the server room, or even the cafeteria, you have to scan your ID card and you need authorization to access it. Every, Single, Time. The system constantly checks who you are, what you’re trying to open, and if you <em>should</em> be allowed to at that exact moment. It doesn’t matter that you’re already “inside” or if you are the CEO of the company, every single action is challenged and verified.</p><p>That, in a nutshell, is Zero Trust. The motto is very simple: <strong>Never Trust, Always Verify.</strong></p><blockquote><strong>What’s Next !!</strong></blockquote><p>And that’s our tour of the different Security Models for today!</p><p>I really hope this overview of the different ‘blueprints’ was helpful and made sense. Did you enjoy this post and the analogies? Let me know your thoughts in the comments!</p><p>Understanding these traditional models is the perfect foundation for our next topic, where we will do a deep dive into the most important modern blueprint: the <strong>Zero Trust Model</strong>.</p><p>For everyone studying for the <strong>CompTIA</strong> <strong>Security+ exam</strong>, think of this post as a great reference for the concepts in Objective 1.2. You can use this series as a reference point for your Security+ exam.</p><p>I hope this was helpful, and I’ll see you in the next post!</p><blockquote>Disclaimer</blockquote><p><em>Just a quick note on the content you see here! All the text, analogies, and explanations in this post are original content crafted specifically for the “Cybersecurity Unlocked” series by me. Basic examples are textbook examples widely used. To help visualize these concepts, all images and diagrams used in this article were generated with the help of Google’s Gemini.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a9ceb5f73bac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Episode 4: Fundamentals Of Cybersecurity — AAA Security]]></title>
            <link>https://medium.com/@kiteyyash3/episode-4-fundamentals-of-cybersecurity-aaa-security-f006a169402a?source=rss-1c31f195dc4c------2</link>
            <guid isPermaLink="false">https://medium.com/p/f006a169402a</guid>
            <category><![CDATA[authentication]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[accounting]]></category>
            <category><![CDATA[authorization]]></category>
            <dc:creator><![CDATA[Yash Kitey]]></dc:creator>
            <pubDate>Sun, 21 Sep 2025 21:30:01 GMT</pubDate>
            <atom:updated>2025-09-21T21:45:18.414Z</atom:updated>
            <content:encoded><![CDATA[<h3>Episode 4: Fundamentals Of Cybersecurity — AAA Security</h3><h3>Cybersecurity Unlocked: A Journey into Cybersec with Yash</h3><p>Ever wonder what <em>really</em> keeps our digital world safe? It’s not just fancy firewalls, it’s the invisible force known as <strong>AAA Security! </strong>Well in today’s digital landscape AAA security plays a vital role. AAA stands for Authentication. Authorization, Accounting. To keep system secure, an organization should have a strong AAA. That means it should have strong authentication policy, strong authorization policy and strong accounting.</p><blockquote><strong>Authentication</strong></blockquote><p>In simplest terms, <em>it is the security measure that checks if you are who you say you are</em>. When you are entering a office building, you have to show your identity card to security personal to show and verify your identity. Or consider the case when you are at airport and you have to show your passport for identity proof, correct ? That’s nothing but Authentication in a nutshell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CmhMMSnOR9OBXUXe-uPR3g.png" /></figure><p>In technical terms, it is a security measure that ensures individuals or entities are who they say they claim to be during a communication or transaction. The<strong> verification of identity</strong> of individuals participating in digital transaction is called<strong> Authentication</strong>.</p><blockquote><strong>Different verification methods for Authentication</strong></blockquote><p>Now, when we talk about digital, there are different ways and factors through which authentication is provided.</p><ol><li><em>Something you know (Knowledge factor)</em>: This method relies on something we know. relies on information that a user can recall. This way of authentication is most widely used everywhere. Best example is username and password.</li><li><em>Something you are:</em> This method relies on, user providing a unique physical or behavioral characteristics of a person. Something that can’t be changed so drastically. Best example for this is biometric, your face unlock feature or finger sensor.</li><li><em>Something you do:</em> This is, as the name suggests, something you do uniquely to provide your identity. For example a secret handshake between 2 people (here in computers).</li><li><em>Something you have (Possession factor)</em>: This relies on user presenting a physical item that he already have to prove who they say they are. Example a security card or a flash drive that only few possess. In recent days while ordering or doing some bank transactions we enter One Time Passwords (OTP), this is nothing but a physical thing that we have and can be considered possession factor as in theory it is understood that only you have your phone.</li><li><em>Somewhere you are (location factor):</em> This relies on geographical location of the user. Basically where they are present. Example, when I was coming to US, I had received a credit card, but that card could not work when I was back in India but as soon as I landed in the US, the card was activated. This was because the card was supposed to work only in the US.</li></ol><blockquote><strong>2-Factor and Multi Factor Authentication</strong></blockquote><p>Now, these are different methods by which we can verify someone, but if there is an attack and one of these is broken by an attacker, we are at risk of loosing the data. So, when applying Authentication policies in an organization 2 or more policies are combined to reduce the risk. <em>If 2 of these are used at a time, it is called 2-factor authentication. If more than 2 methods are used, then it is called as multi-factor authentication. </em>I recommend using more than one authentication method, combined to improve authentication and security.</p><blockquote><strong>Authorization</strong></blockquote><p>You went to your office, you logged into your system using username and password, that’s authentication but once logged in, what are you allowed to do ? Are you allowed to gain root access ? Definitely not unless you are a system admin. As an employee you are only allowed to access few things.</p><p>Let’s take another example. You visit a online shopping website, what you will see is the client view, where you can add items to cart and make payment and order stuff. But you are not allowed to see the backend systems like inventory, or who else bought the same thing or backend systems, that’s only allowed to system admin who handle the stuff. This is nothing but authorization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oZjyhRjXLqzGTkwttzCGuw.png" /></figure><p><em>The security measure which states what an authorized user can do is authorization. Permissions and privileges granted to users or entities after they have been authenticated.</em></p><p><strong>Authentication verifies identity, authorization states what they can do.</strong> These permissions and privileges are granted to users who manages the system that is system admin.</p><p><strong>Authorization</strong> is briefly categorized into 3 types.</p><ol><li>Rule Based</li><li>Role Based</li><li>Attribute Based</li></ol><p>We will better understand these 3 types when we will learn about IAM policies. Authorization is used</p><ol><li>To protect the sensitive data — like we should only be able to see what is necessary to us reducing our options. For example a junior employee should not have access to publish or push the code to production. So technically he not be able to see the option to push the code or access the production files at first place.</li><li>To maintain system integrity</li><li>To create more streamlined user experience that is reducing the options and only show the allowed access and permissions.</li></ol><blockquote><strong>Accounting</strong></blockquote><p>So far, we know Authentication checks <em>who you are</em>, and Authorization decides <em>what you can do</em>. But here’s the catch once you’re inside the system and start doing things, someone needs to <strong>track your actions</strong>. That’s where <strong>Accounting</strong> comes in.</p><p>Think of it this way when you visit a hotel, you check in at the reception (authentication), and you’re given access to only your room (authorization). But later, when you order food, use the gym, or take something from the minibar, all of that is <strong>recorded in your bill</strong>. That’s nothing but <strong>Accounting</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oEejlL6nvEEczo1RfdIvrw.png" /></figure><p>In technical terms, <strong>Accounting</strong> is the process of logging and keeping track of a user’s activities in the system. It helps an organization <strong>record, monitor, and audit</strong> what users do once they are authenticated and authorized.</p><blockquote><strong>Importance of Accounting</strong></blockquote><ol><li><strong>Traceability</strong>: Imagine a file got deleted from a system. With accounting logs, we can track <em>who deleted it, when, and from where</em>.</li><li><strong>Auditing</strong>: Security auditors can check logs to ensure policies are being followed.</li><li><strong>Billing/Usage Tracking</strong>: In cloud computing or ISPs, accounting helps track resource usage (like CPU, storage, data usage) for billing.</li><li><strong>Forensics</strong>: If a security breach happens, accounting logs are often the <em>first place investigators look</em>.</li></ol><blockquote><strong>Examples of Accounting in Action</strong></blockquote><ol><li><strong>System Logs</strong>: Every time you log in, fail a login attempt, or change a file, the system logs it.</li><li><strong>Network Logs</strong>: Routers, firewalls, and VPNs record who connected, when, and what resources they accessed.</li><li><strong>Cloud Services</strong>: AWS, Azure, and GCP maintain accounting through detailed logs, billing dashboards, and monitoring tools.</li><li><strong>Banking</strong>: Every transaction is tracked with timestamps, transaction IDs, and user IDs.</li></ol><blockquote><strong>Summary</strong></blockquote><ol><li><strong>Authentication</strong> = Who you are.</li><li><strong>Authorization</strong> = What you can do.</li><li><strong>Accounting</strong> = What you did (and when, and how).</li></ol><p>That is it for today. I hope now you all understand the AAA as this is building block of zero trust model which we will cover soon. Comment down your examples of AAA.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f006a169402a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>