<?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 Ajay Monga on Medium]]></title>
        <description><![CDATA[Stories by Ajay Monga on Medium]]></description>
        <link>https://medium.com/@ajay.monga73?source=rss-907ba3e21fa6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*C-QJfBeophOaGMW9L5twOA.jpeg</url>
            <title>Stories by Ajay Monga on Medium</title>
            <link>https://medium.com/@ajay.monga73?source=rss-907ba3e21fa6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:13:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ajay.monga73/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[Find SQL Injection in Code and Fix: A Simple, Practical Guide]]></title>
            <link>https://medium.com/@ajay.monga73/find-sql-injection-in-code-and-fix-a-simple-practical-guide-64d2d65208a5?source=rss-907ba3e21fa6------2</link>
            <guid isPermaLink="false">https://medium.com/p/64d2d65208a5</guid>
            <category><![CDATA[code-review]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[sql-injection]]></category>
            <dc:creator><![CDATA[Ajay Monga]]></dc:creator>
            <pubDate>Wed, 26 Nov 2025 12:27:07 GMT</pubDate>
            <atom:updated>2025-11-26T12:27:07.833Z</atom:updated>
            <content:encoded><![CDATA[<h4>Manual Secure Code Review to Find SQL Injection in Code</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/579/1*cnOLznHqwVgYzyMzOQjZPw.png" /></figure><p>If you use raw user input directly into an SQL string, the database will treat that input like code not a separate value and an attacker can change what the query intended to execute. This guide shows a simple Python example with a SQL injection vulnerability, explains how an attacker can exploit it, and demonstrates the correct fix using parameterized queries and a few secure-coding practices.</p><p>Here’s a small Python script that creates a users table (with demo rows) and looks up a user by username.</p><pre>import sqlite3<br>conn = sqlite3.connect(&#39;test1.db&#39;)<br>c = conn.cursor()<br>demo_users = {<br>    (1, &#39;jose&#39;, &#39;jose@xyz.com&#39;, &#39;1234567890&#39;),<br>    (2, &#39;rolf&#39;, &#39;rolf@xyz.com&#39;, &#39;1234567890&#39;),<br>    (3, &#39;admin&#39;, &#39;admin@xyz.com&#39;, &#39;1234567890&#39;)<br>}<br>insert_query = &quot;INSERT INTO users VALUES (?, ?, ?, ?)&quot;<br>c.executemany(insert_query, demo_users)<br>def get_user_by_username(username):<br>    c = conn.cursor()<br>    select_query= &quot;SELECT * FROM users WHERE username = &#39;&quot; + username + &quot;&#39;&quot;<br>    c.execute(select_query)<br>    return c.fetchall()<br>user_input = input(&quot;Enter username: &quot;)<br>print(get_user_by_username(user_input))</pre><p>This code is intentionally minimal so we can focus on the vulnerability.</p><h4>What’s wrong?</h4><p>The function get_user_by_username builds the SQL query by concatenating the username directly into the SQL string:</p><pre>select_query = &quot;SELECT * FROM users WHERE username = &#39;&quot; + username + &quot;&#39;&quot;</pre><p>That means whatever a user types becomes part of the SQL statement. If the input contains SQL syntax (quotes, OR, UNION, comment markers like --), it can change the structure of the query. In short: user input is being treated as <em>code</em>, not as <em>data</em>.</p><h4>Real examples: what an attacker can do</h4><p>Assume the table contains jose, rolf, and admin.</p><ul><li>Normal input: jose<br>Query becomes: SELECT * FROM users WHERE username = &#39;jose&#39; — returns Jose’s row.</li><li>Non-existent user: AJ<br>Query becomes: SELECT * FROM users WHERE username = &#39;AJ&#39; — returns nothing.</li><li>Malicious input: &#39; OR &#39;1&#39;=&#39;1<br>Constructed query:<br>SELECT * FROM users WHERE username = &#39;&#39; OR &#39;1&#39;=&#39;1&#39;<br>Since &#39;1&#39;=&#39;1&#39; is always true, the WHERE clause matches all rows — the attacker gets every user record.</li><li>Injection with comment: anything&#39; --<br>The -- starts a comment in many SQL dialects, causing the rest of the original query to be ignored. Attackers can neutralize parts of the query or append their own payloads.</li><li>More advanced: UNION-based queries, or DELETE/UPDATE statements (if DB permissions allow), can be used to exfiltrate or destroy data.</li></ul><p>Even a single unmatched quote in input can cause errors that leak information about the database schema. That’s why concatenating raw input into SQL strings is dangerous.</p><h4>How to find these issues during a manual review</h4><p>When you review code, ask:</p><ol><li>Is any SQL string built by concatenating user input or other untrusted data?</li><li>Are inputs validated or escaped properly?</li><li>Are there places where input can change SQL structure (quotes, logical operators, comment markers)?</li><li>Is the DB user following least privilege (no unnecessary admin rights)?</li></ol><p>If the answer to (1) or (3) is yes, mark it as a confirmed SQL injection risk and plan remediation.</p><h4>The right fix: parameterized queries</h4><p>Never build SQL by concatenating strings with user input. Use parameter binding so the database treats user values as data. In Python use ? placeholders:</p><pre>def get_user_by_username_safe(username):<br>    c = conn.cursor()<br>    select_query = &quot;SELECT * FROM users WHERE username = ?&quot;<br>    c.execute(select_query, (username,))<br>    return c.fetchall()</pre><p>Why this works: the SQL statement and the data are sent separately. The database engine parses the SQL once and treats the bound values only as data, so special characters in input won’t change SQL structure.</p><h4>Full, remediated code</h4><p>A clean example that avoids reinserting demo data every run and uses the safe query:</p><pre>import sqlite3<br><br>conn = sqlite3.connect(&quot;test1.db&quot;)<br>c = conn.cursor()<br>c.execute(&quot;CREATE TABLE users(id INTEGER, username TEXT, email TEXT, phone TEXT)&quot;)<br>demo_users = [        (1, &#39;jose&#39;, &#39;jose@xyz.com&#39;, &#39;1234567890&#39;),        (2, &#39;rolf&#39;, &#39;rolf@xyz.com&#39;, &#39;1234567890&#39;),        (3, &#39;admin&#39;, &#39;admin@xyz.com&#39;, &#39;1234567890&#39;)    ]<br>c.executemany(&quot;INSERT INTO users VALUES (?, ?, ?, ?)&quot;, demo_users)<br>conn.commit()<br>conn.close()<br>def get_user_by_username_safe(username):<br>    conn = sqlite3.connect(DB_PATH)<br>    c = conn.cursor()<br>    select_query = &quot;SELECT * FROM users WHERE username = ?&quot;<br>    c.execute(select_query, (username,))<br>    rows = c.fetchall()<br><br><br>user_input = input(&quot;Enter username: &quot;)<br>print(get_user_by_username_safe(user_input))</pre><h4>Manual secure code review checklist for SQL injection</h4><p>Use this checklist when reviewing code:</p><ul><li>Any SQL constructed by concatenating strings with user input? If yes → risky.</li><li>Are parameterized queries / prepared statements available and used? If not → refactor.</li><li>Are ORMs used correctly (are their query methods parameterized)?</li><li>Are inputs validated for expected format/length? (Defense-in-depth; not a substitute for parameters.)</li><li>Is the DB account using least privilege? (No unnecessary DROP/DELETE/INSERT rights.)</li><li>Is sensitive data avoided in logs?</li><li>Is any dynamic SQL absolutely necessary? If yes, whitelist and validate the parts that affect SQL syntax.</li><li>Are automated SAST/DAST scans configured in CI/CD and triaged?</li></ul><h4>Tools that help (automated + manual)</h4><ul><li><strong>SAST (Static Application Security Testing):</strong> Scans source code for patterns where user input flows into SQL strings. Examples include commercial tools and a few open-source scanners.</li><li><strong>DAST (Dynamic Application Security Testing):</strong> Runs against running apps and tries payloads to find live vulnerabilities.</li><li><strong>Manual review:</strong> Essential for complex dynamic SQL and business logic issues that scanners may miss.</li></ul><p>Combine automated tools with human review for best coverage.</p><h4>Quick mitigation checklist:</h4><ol><li>Replace string-concatenation SQL with parameterized queries everywhere.</li><li>Validate and sanitize input for expected type/length (whitelists where possible).</li><li>Use least-privilege database accounts.</li><li>Add SAST and DAST into CI/CD pipelines and triage findings promptly.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64d2d65208a5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Security as a Culture: Why It’s Everyone’s Job]]></title>
            <link>https://medium.com/@ajay.monga73/security-as-a-culture-why-its-everyone-s-job-6a737f143df0?source=rss-907ba3e21fa6------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a737f143df0</guid>
            <category><![CDATA[cyber]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[ethical-hacking]]></category>
            <dc:creator><![CDATA[Ajay Monga]]></dc:creator>
            <pubDate>Sat, 20 Sep 2025 15:04:57 GMT</pubDate>
            <atom:updated>2025-09-20T15:04:57.246Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Shared Responsibility: The Only Way to Stay Secure</strong></h4><p>When most people think of security, they imagine firewalls, penetration tests, or a small team working in the background. But the reality is different — security is not just about tools or experts. It’s about culture.</p><p>A culture where every person in an organization, from a developer to a business executive, feels ownership of keeping systems, data, and people safe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*pSjKKpGGz5EfZpOOlg4qlg.png" /></figure><p>Think of it this way:</p><ul><li>In a family, safety at home is not just one person’s job. Everyone contributes — locking the door, turning off the gas, checking the windows.</li><li>Similarly, in an organization, <strong>security is a shared responsibility</strong>. If even one person ignores it, the whole system is at risk.</li></ul><h3>Why Security Can’t Be a “Team Thing” Anymore</h3><p>Organizations often fall into the trap of putting the security team in a silo. The mindset becomes:</p><ul><li>Developers build.</li><li>Ops deploy.</li><li>Security tests.</li><li>End users… click whatever link they want.</li></ul><p>This model might have worked a decade ago. Today? It’s broken.</p><p>We’re living in a world where a single phishing email can compromise an entire enterprise. Where a developer copy-pasting one insecure code snippet can create a data breach costing millions. Where a manager ignoring a security policy for “speed” can open the door to attackers.</p><p>When risks are everywhere, responsibility must also be everywhere.</p><h4>Security-as-a-Culture: What It Means</h4><p>Think of security not as a tool, but as a behavior. It’s the <em>habits</em> and <em>mindset</em> baked into how people work.</p><ul><li><strong>For Developers</strong>: Writing code with security checks in mind, reviewing for potential vulnerabilities as naturally as checking for logic bugs.</li><li><strong>For Ops Teams</strong>: Ensuring deployments don’t just work, but also follow least privilege, proper patching, and monitoring.</li><li><strong>For Business Leaders</strong>: Making decisions that balance speed with safety, because a shortcut that saves a week could cost the company its reputation.</li><li><strong>For End Users</strong>: Being aware that a suspicious link, weak password, or overshared file isn’t just “their problem,” it’s everyone’s.</li></ul><p>Security-as-a-culture means that <em>every single person sees themselves as a guardian of the organization’s trust</em>.</p><h4>Why Culture Wins Over Tools</h4><p>You can buy the best SAST, DAST, firewalls, and endpoint security. You can automate every scan. But if the people using and building systems don’t care, or don’t know, those tools become band-aids.</p><p>Culture is stronger than any tool. Because culture is about <em>ownership</em>. When developers say, “This is my code, I want it to be secure,” or when employees say, “I’ll double-check this email before clicking,” that’s when real protection happens.</p><h4>How to Build Security-as-a-Culture</h4><p>Changing culture doesn’t happen overnight, but it can be done step by step:</p><ol><li><strong>Awareness First</strong><br>People can’t care about what they don’t understand. Training, storytelling, and real-life case studies make threats relatable. Not boring 1-hour PPTs once a year, but short, scenario-based training. (“What would you do if…?”)</li><li><strong>Shift-Left Everywhere</strong><br>Security should enter conversations as early as possible in SDLC( requirements, design, code, and deployments). Don’t wait for “the security check at the end.”</li><li><strong>Reward Good Practices<br></strong>Appreciate teams and individuals who follow secure practices. People follow what’s appreciated.</li><li><strong>Gamification<br></strong>Run capture-the-flag challenges, red vs. blue exercises, or reward teams who prevent incidents.</li><li><strong>Make It Personal</strong><br>Help people see how security protects <em>their</em> data, <em>their</em> families, <em>their</em> privacy. Once it feels personal, it becomes second nature.</li></ol><h4>Why This Matters</h4><p>The cost of one breach can wipe out years of effort. But more importantly, a weak security culture erodes trust, with users, with partners, and even internally.</p><p>On the other hand, when security becomes part of your culture:</p><ul><li>Releases become faster (because you don’t fix issues at the last minute).</li><li>Developers gain confidence (because they know they’re building right from the start).</li><li>Customers trust you more (because you actually respect their data).</li></ul><h4>Shared Responsibility is Always Better</h4><p>Security teams will always play a critical role, but they should act as <em>enablers</em>, not the sole guardians. They build frameworks, provide expertise, and guide others, but the execution belongs to everyone.</p><p>The companies that thrive in the digital era will be the ones where security isn’t a box to check. It’s a way of working. A part of identity. A culture.</p><p><em>Follow me on LinkedIn: </em><a href="https://www.linkedin.com/in/ajay-monga2/"><em>https://www.linkedin.com/in/ajay-monga2/</em></a></p><h4>If you like my work &gt;&gt;&gt; Buy Me A Coffee</h4><p><a href="https://buymeacoffee.com/ajaymonga">Ajay Monga</a></p><p>Because in today’s world, security isn’t a checkbox or a department. It’s a culture, and culture is built by everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a737f143df0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Supply Chain Attacks: The Hidden Cost Nobody Talks About]]></title>
            <link>https://medium.com/@ajay.monga73/supply-chain-attacks-the-hidden-cost-nobody-talks-about-d5ea31a0297f?source=rss-907ba3e21fa6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5ea31a0297f</guid>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[supply-chain]]></category>
            <dc:creator><![CDATA[Ajay Monga]]></dc:creator>
            <pubDate>Tue, 09 Sep 2025 10:51:49 GMT</pubDate>
            <atom:updated>2025-09-09T10:51:49.359Z</atom:updated>
            <content:encoded><![CDATA[<h4>When we hear about a supply chain attack, most headlines focus on <em>how much money was stolen</em>.</h4><p>But here’s the truth: the <strong>real cost is not the money stolen</strong>. The real cost comes from the <strong>thousands of hours engineers spend checking, fixing, and cleaning up after the attack</strong>.</p><h4>The Real Cost</h4><p>Take the recent npm compromise as an example. Attackers tried to steal crypto by swapping wallet addresses. In the end, they only managed to get about <strong>$500 so far</strong>.</p><p>Sounds small, right?<br>But the impact was huge:</p><ul><li>Millions of apps that used packages like <strong>chalk, debug, and ansi-styles</strong> had to be checked.</li><li>Companies had to stop everything and <strong>audit dependencies, patch code, and redeploy apps</strong>.</li><li>Security teams had to <strong>watch logs, review lock files, and warn developers</strong>.</li></ul><p>This takes days or even weeks of work. Multiply that by thousands of companies worldwide, and the “$500 hack” actually cost the community <strong>millions of dollars in lost time and productivity</strong>.</p><h4>Supply chain attacks spread fast because:</h4><ul><li>One small library is used in <strong>millions of apps</strong>.</li><li>Developers often don’t even know they’re using it (it’s hidden as a sub-dependency).</li><li>Many packages are maintained by just <strong>one person</strong>, making them easy targets.</li></ul><p>So even if the direct theft is small, the <strong>cleanup is massive</strong>.</p><h4>What Dev/ Can Do</h4><p>Here are a few simple steps to reduce the damage next time:</p><ol><li><strong>Use lock files</strong> → don’t let packages auto-update blindly.</li><li><strong>Monitor dependencies</strong> with tools like Snyk or Dependabot.</li><li><strong>Prioritize critical apps</strong> (like payments or crypto).</li><li><strong>Practice response drills</strong> for when something like this happens.</li><li><strong>Support open source maintainers</strong> so they can make packages safer.</li></ol><p>Supply chain attacks are not just about stolen money.<br>They are about <strong>lost trust, lost time, and lost focus</strong>.</p><p>Attackers may walk away with a few hundred dollars…<br>But the world loses <strong>millions of dollars worth of engineering hours</strong> cleaning up the mess.</p><p>That’s the real cost we need to pay attention to.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5ea31a0297f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Largest npm Compromise in History: Supply Chain Attack]]></title>
            <link>https://medium.com/@ajay.monga73/the-biggest-npm-compromise-yet-popular-packages-like-chalk-and-debug-hijacked-dfeb7fb8e142?source=rss-907ba3e21fa6------2</link>
            <guid isPermaLink="false">https://medium.com/p/dfeb7fb8e142</guid>
            <category><![CDATA[zero-day-vulnerability]]></category>
            <category><![CDATA[cyberattack]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Ajay Monga]]></dc:creator>
            <pubDate>Mon, 08 Sep 2025 19:33:32 GMT</pubDate>
            <atom:updated>2025-09-09T04:08:23.234Z</atom:updated>
            <content:encoded><![CDATA[<h4>npm debug and chalk packages compromised</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*BmL0EUXYRPkczuS5c7vcBA.png" /></figure><p>Hey Everyone,</p><p>On September 8th, 13:16 UTC, the open-source system got hit with one of the <strong>largest npm compromises ever</strong>. Packages with <strong>over 2 billion weekly downloads</strong> were found to be compromised — all belonging to a single developer account that was taken over by a phishing attack.</p><p>Here’s what we know so far 👇</p><h4>🔴 Affected Packages (Some of the Biggest Names)</h4><ul><li>backslash (0.26m downloads per week)</li><li>chalk-template (3.9m downloads per week)</li><li>supports-hyperlinks (19.2m downloads per week)</li><li>has-ansi (12.1m downloads per week)</li><li>simple-swizzle (26.26m downloads per week)</li><li>color-string (27.48m downloads per week)</li><li>error-ex (47.17m downloads per week)</li><li>color-name (191.71m downloads per week)</li><li>is-arrayish (73.8m downloads per week)</li><li>slice-ansi (59.8m downloads per week)</li><li>color-convert (193.5m downloads per week)</li><li>wrap-ansi (197.99m downloads per week)</li><li>ansi-regex (243.64m downloads per week)</li><li>supports-color (287.1m downloads per week)</li><li>strip-ansi (261.17m downloads per week)</li><li>chalk (299.99m downloads per week)</li><li>debug (357.6m downloads per week)</li><li>ansi-styles (371.41m downloads per week)</li></ul><p>Together, these packages have garnered more than 2 billion downloads per week.</p><h4>⚠️ What Happened?</h4><p>The attack started when the developer’s npm account was compromised via a <strong>phishing campaign</strong>.</p><ul><li>The phishing email looked like it came from support@npmjs.help — tricking the maintainer into clicking a malicious link.</li><li>Once the attacker had control of the account, they published <strong>infected versions of multiple packages</strong>.</li></ul><h4>How the Malware Works (Simplified)</h4><p><em>The malicious code was designed primarily for </em><strong><em>crypto wallet theft</em></strong><em>:</em></p><p><strong>Injects into browsers</strong> → Hooks into functions like fetch, XMLHttpRequest, and wallet APIs (window.ethereum, Solana, etc.).</p><ol><li><strong>Monitors sensitive data</strong> → Looks for wallet addresses and transactions across Bitcoin, Ethereum, Solana, Tron, Litecoin, and more.</li><li><strong>Swaps addresses</strong> → Replaces the real recipient with the attacker’s wallet address (using lookalike strings so it’s less obvious).</li><li><strong>Hijacks transactions before signing</strong> → Even if the UI looks correct, the signed transaction routes funds to the attacker.</li><li><strong>Stays stealthy</strong> → Avoids detection, runs silently in the background, and hides changes from the user.</li></ol><p>Luckily, it seems targeted <strong>only at crypto wallets</strong>, not at inserting backdoors into systems — but the scale of this is massive.</p><h4><strong>Immediate Steps for Developers &amp; Security Teams:</strong></h4><p>If you’re using any of these packages:</p><p>&gt; Security teams can use these to detect possible exposure:</p><p><strong>Malicious Versions (known so far):</strong></p><ul><li>chalk@5.6.1</li><li>debug@4.4.2</li><li>ansi-styles@6.2.2</li><li>strip-ansi@7.2.2</li><li>supports-color@9.4.2</li><li>wrap-ansi@9.2.2</li><li>slice-ansi@7.1.2</li><li>color-convert@3.2.2</li><li>color-name@3.2.2</li><li>color-string@2.1.2</li><li>supports-hyperlinks@3.1.2</li><li>chalk-template@1.1.2</li><li>error-ex@2.1.2</li><li>is-arrayish@0.4.2</li><li>simple-swizzle@0.3.2</li><li>has-ansi@5.1.2</li><li>backslash@0.2.2</li></ul><p><em>(Stick to earlier safe versions if you depend on these packages.)</em></p><p><strong>&gt; How to Check if You’re Affected</strong></p><p>Run this in your project folder to see if compromised versions are installed:</p><pre>npm ls chalk debug ansi-styles strip-ansi supports-color wrap-ansi slice-ansi color-convert color-name color-string supports-hyperlinks chalk-template error-ex is-arrayish simple-swizzle has-ansi backslash</pre><p>If any results show the malicious versions listed above → roll back immediately and pin to a safe version. See if you’ve pulled in the compromised versions.</p><p><strong>&gt; Avoid auto updates</strong></p><ul><li>Don’t rush to update to the “latest” without verifying integrity.</li></ul><p><strong>&gt; Monitor npm security advisories</strong></p><ul><li>Keep an eye on npm advisories or GitHub’s security feed.</li></ul><p><strong>&gt; Harden your supply chain</strong></p><ul><li>Use version pinning.</li><li>Regularly audit dependencies (npm audit).</li><li>Consider tools like Snyk, Socket, or Aikido to catch malicious dependencies faster.</li></ul><h4>Why This Matters Beyond Crypto</h4><p>While this specific malware is after crypto, the <strong>real danger is trust erosion</strong> in open-source supply chains. With millions of apps indirectly depending on these packages, a backdoor could have been catastrophic.</p><p>This event is a reminder:</p><ul><li>Open source is powerful but fragile.</li><li>One phishing email can ripple across the entire ecosystem.</li></ul><p>🔗 The story is still unfolding. Maintainers are actively working on fixes, and some compromised versions are already yanked. You can follow a live update here: <a href="https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised">Aikido Blog Post</a>.</p><p>Stay safe out there. Lock your dependencies. And double-check that email before you click.</p><p>References:</p><p><a href="https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised">npm debug and chalk packages compromised</a></p><p><a href="https://www.reddit.com/r/programming/comments/1nbqt4d/largest_npm_compromise_in_history_supply_chain/">https://www.reddit.com/r/programming/comments/1nbqt4d/largest_npm_compromise_in_history_supply_chain/</a></p><p><em>Follow me on LinkedIn: </em><a href="https://www.linkedin.com/in/ajay-monga2/"><em>https://www.linkedin.com/in/ajay-monga2/</em></a></p><h3>If you like my work &gt;&gt;&gt; Buy Me A Coffee</h3><p><a href="https://buymeacoffee.com/ajaymonga">Ajay Monga</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dfeb7fb8e142" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[File Created with Incorrect Permissions Vulnerability : Java & Python Security Guide]]></title>
            <link>https://medium.com/@ajay.monga73/file-created-with-incorrect-permissions-vulnerability-java-python-security-guide-b1f7d88c8187?source=rss-907ba3e21fa6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1f7d88c8187</guid>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[pentesting]]></category>
            <category><![CDATA[secure-coding]]></category>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <dc:creator><![CDATA[Ajay Monga]]></dc:creator>
            <pubDate>Sat, 09 Aug 2025 13:35:08 GMT</pubDate>
            <atom:updated>2025-08-09T13:35:08.153Z</atom:updated>
            <content:encoded><![CDATA[<h3>File Created with Incorrect Permissions Vulnerability : Java &amp; Python Security Guide</h3><h4><em>A developer’s guide to understanding, detecting, and preventing insecure file creation.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LbU5us3gRNIlhw-h" /></figure><h4>Introduction to File Created with Incorrect Permissions</h4><p>In a software or application, Whenever an application creates a file, the OS assigns <strong>default permissions</strong> unless explicitly overridden.<strong> It</strong> unintentionally set unauthorized users access (read, write, execute) without knowing what is necessary. This is a common security issue that can lead to <strong>data leaks</strong>, <strong>data manipulation, code modification, </strong>or even whole <strong>system compromise.</strong></p><p>Usually it happens when:</p><ul><li>Developers <strong>do not explicitly set file permissions </strong>at the application level.(Developers think: “It’s just a log/temp/config file”)</li><li>The system applies <strong>default permissions</strong> that are too permissive.</li><li>Some libraries create temporary or cache files without secure defaults.</li><li>Permissions are <strong>hardcoded incorrectly</strong> in the code.</li><li>Incorrect <strong>container volume mount permissions</strong> or <strong>deployment scripts</strong>.</li></ul><h4>Impact?</h4><p>A file created with incorrect permissions can make:</p><ul><li><strong>Unauthorized write access<br></strong>allowing an attacker to inject malicious code, tamper with configurations, or alter logs.</li><li><strong>Information Disclosure</strong><br>Sensitive logs, configs, or temp files can be read by other users or processes.</li><li><strong>Privilege Escalation</strong><br>Writable files in privileged directories can be modified to execute malicious code.</li><li><strong>Regulatory Violations</strong><br>Exposing personal data via insecure files can breach GDPR, HIPAA, etc.</li></ul><p>For example:</p><ul><li><strong>Log files</strong> with rw-rw-rw- (world-writable) permissions can be overwritten with fake logs to hide traces of an attack.</li><li><strong>Configuration files</strong> containing database credentials with read access to all users can be stolen by any unprivileged account.</li></ul><p><strong>Vulnerable code example: </strong>Creates file without setting permissions, set world-readable/writable by default</p><pre>public class Main {<br>    public static void main(String[] args) throws IOException {<br>        FileWriter fw = new FileWriter(&quot;data.txt&quot;);<br>        fw.write(&quot;Secret API Key: 12345&quot;);<br>        fw.close();<br>    }<br>}</pre><h4>How to detect?</h4><p><strong>1. Manual Check</strong></p><p>On Linux:</p><pre>find /app -type f -perm /o=w</pre><p>Finds files writable by others.</p><p><strong>2. Static Code Analysis</strong></p><p>Tools like <strong>Checkmarx</strong>, <strong>SonarQube</strong>, <strong>Semgrep</strong> can flag insecure file creation functions.<br>Example Semgrep rule snippet:</p><pre>rules:<br>- id: insecure-file-permissions<br>  patterns:<br>    - pattern: open($FILENAME, &quot;w&quot;)<br>  message: &quot;Consider setting restrictive file permissions.&quot;<br>  severity: WARNING</pre><h4>Remediation and Best Practices:</h4><p><strong>Principle of Least Privilege</strong></p><ul><li>By default set <strong>only</strong> the minimum permissions required.</li><li>Avoid world-readable/writable unless absolutely necessary.</li></ul><p><strong>Explicitly Set Permissions in Code</strong></p><pre>        File file = new File(&quot;data.txt&quot;);<br>        file.setReadable(false, false); // remove read for everyone<br>        file.setWritable(false, false); // remove write for everyone<br>        file.setReadable(true, true);   // owner read<br>        file.setWritable(true, true);   // owner write</pre><pre># Create file with owner read/write only (0o600)<br>fd = os.open(&quot;data.txt&quot;, os.O_WRONLY | os.O_CREAT, 0o600)</pre><pre>touch secure.txt<br>chmod 600 secure.txt</pre><p><strong>Secure Temporary Files</strong></p><ul><li>Use language-safe temp functions:</li><li>Python: tempfile.NamedTemporaryFile(delete=True)</li><li>Java: Files.createTempFile with secure attributes.</li><li>Avoid predictable names in /tmp.</li></ul><p><strong>Secure Deployment</strong></p><ul><li>In Docker/K8s, ensure, Non-root containers, Proper volume mount permissions.</li><li>Secure CI/CD file handling.</li></ul><p><strong>Vulnerable Code Example In Java</strong></p><pre>public class Main {<br>    public static void main(String[] args) throws IOException {<br>        FileWriter fw = new FileWriter(&quot;data.txt&quot;);<br>        fw.write(&quot;Secret API Key: 12345&quot;);<br>        fw.close();<br>    }<br>}</pre><p><strong>Remediated Code</strong></p><pre>public class Main {<br>    public static void main(String[] args) throws IOException {<br>        File file = new File(&quot;data.txt&quot;);<br>        file.setReadable(false, false); // remove read for everyone<br>        file.setWritable(false, false); // remove write for everyone<br>        file.setReadable(true, true);   // owner read<br>        file.setWritable(true, true);   // owner write<br>        FileWriter fw = new FileWriter(file);<br>        fw.write(&quot;Secret API Key: 12345&quot;);<br>        fw.close();<br>    }<br>}</pre><p><strong>Vulnerable Code Example in Python</strong></p><pre># Creates file with default permissions <br>with open(&quot;data.txt&quot;, &quot;w&quot;) as f:<br>    f.write(&quot;Secret API Key: 12345&quot;)</pre><p><strong>Remediated Code</strong></p><pre># Create file with owner read/write only (0o600)<br>fd = os.open(&quot;data.txt&quot;, os.O_WRONLY | os.O_CREAT, 0o600)<br>with os.fdopen(fd, &quot;w&quot;) as f:<br>    f.write(&quot;Secret API Key: 12345&quot;)</pre><p>A single incorrect permission bit can be the difference between a secure system and a breach. Don’t rely on defaults. <strong>Explicitly set permissions, validate them, and automate checks</strong> in your pipeline.</p><h4>Let me know if you’d like additional details or specific code examples for any section!</h4><p><em>Follow me on LinkedIn: </em><a href="https://www.linkedin.com/in/ajay-monga2/"><em>https://www.linkedin.com/in/ajay-monga2/</em></a></p><h4>If you like my work &gt;&gt;&gt; Buy Me A Coffee</h4><p><a href="https://buymeacoffee.com/ajaymonga">https://buymeacoffee.com/ajaymonga</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1f7d88c8187" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You’re Already Training Yourself — Whether You Know It or Not]]></title>
            <link>https://medium.com/@ajay.monga73/youre-already-training-yourself-whether-you-know-it-or-not-eb01aaa71900?source=rss-907ba3e21fa6------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb01aaa71900</guid>
            <category><![CDATA[habits-for-success]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[new-book]]></category>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Ajay Monga]]></dc:creator>
            <pubDate>Mon, 14 Jul 2025 14:12:33 GMT</pubDate>
            <atom:updated>2025-07-14T14:12:33.642Z</atom:updated>
            <content:encoded><![CDATA[<h3>You’re Already Training Yourself — Whether You Know It or Not</h3><h4>Your identity isn’t fixed. It’s trained — one unconscious loop at a time.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*eNuYt-qUCSUAPliQuoexZQ.png" /></figure><p>Every day, you’re shaping the person you are becoming.</p><p>Not by setting goals.<br>Not by reading self-help books.<br>But by something far more subtle:</p><blockquote><strong><em>Your attention.<br>Your repetition.<br>Your reactions.<br>Your loops.</em></strong></blockquote><p>Most people think personality is something they’re born with.<br>But I want to show you something else:</p><blockquote><strong><em>You are already training yourself — whether you know it or not.</em></strong><em><br>And that’s exactly what </em>Reverse Intelligence<em> is about.</em></blockquote><h4>🧠 The Loop That Shapes Your Identity</h4><p>In my book <em>Reverse Intelligence</em>, I introduce a powerful idea:</p><p>Your personality is not a result.<br>It’s an outcome — of a loop that started long ago.</p><p>This is the loop:</p><blockquote><strong><em>Senses → Attention → Thought → Repetition → Interest → Action → Habit → Personality</em></strong></blockquote><p>Let’s walk through it quickly.</p><h4>1. Senses</h4><p>Everything begins with what you expose yourself to.<br>What you scroll through, hear, read, watch, taste.<br>That’s your raw input.</p><h4>2. Attention</h4><p>But not everything you sense becomes important.<br>Only what you pay attention to gets stored.<br>This is where the loop starts to narrow.</p><h4>3. Thought</h4><p>What you focus on becomes a thought.<br>One thought might not matter. But…</p><h4>4. Repetition</h4><p>…what you repeat becomes belief.<br>The loop deepens every time you dwell on something familiar.</p><h4>5. Interest</h4><p>Repetition leads to attachment.<br>You start caring about certain thoughts more than others.</p><h4>6. Action</h4><p>Interest guides your decisions.<br>You act based on what your loop prioritizes.</p><h4>7. Habit</h4><p>Repeated actions become automatic.<br>The loop tightens. You stop thinking — you just do.</p><h4>8. Personality</h4><p>And after all those steps…<br>That’s who you become.</p><h4>🔁 You’ve Been Looping All Along</h4><p>Think about it.</p><p>That habit you can’t break?<br>It didn’t just happen.</p><p>You trained it — through thousands of micro-repetitions.</p><p>That reaction you have when someone criticizes you?<br>That’s not “just how you are.”<br>It’s how you trained your emotional loop to respond.</p><blockquote><em>Your current self is a </em><strong><em>feedback-trained identity</em></strong><em>.</em></blockquote><p>But unlike AI systems, most people are trained <strong>by default,</strong> not by design.</p><h4>⚠️ Default Training Looks Like This:</h4><p>– Sense: boredom →<br> — Attention: phone notification →<br> — Thought: “Let me check something real quick” →<br> — Repetition: scrolling →<br> — Interest: short-term content →<br> — Action: mindless consumption →<br> — Habit: distraction →<br> — Personality: reactive, scattered</p><h4>✅ Designed Training Looks Like This:</h4><p>– Sense: discomfort →<br> — Attention: breath, body →<br> — Thought: “Let’s pause here” →<br> — Repetition: journaling or reflection →<br> — Interest: inner clarity →<br> — Action: intentional response →<br> — Habit: reflection →<br> — Personality: calm, grounded</p><h4>🛠️ Reverse Intelligence = Awareness of the Loop</h4><p>In <em>Reverse Intelligence</em>, I help you recognize:</p><ul><li>Where your loops are running without permission</li><li>Where your identity has become automated</li><li>And how to consciously redirect the flow, <strong>starting from “Attention”</strong></li></ul><p>It’s not about changing everything at once.<br>It’s about becoming aware of what’s shaping you… and interrupting it.</p><p>Because once you see the loop, you can reverse it.</p><h4>📘 Why I Wrote This</h4><p>This entire framework started with a single question:</p><blockquote>“We all see the same world…<br>So why do we think, act, and become such different people?”</blockquote><p>That question turned into pages.<br>Those pages became loops.<br>Those loops became a system.</p><p>That system is <em>Reverse Intelligence</em>.</p><h4>🚘 You Are the Trainer Now</h4><p>You don’t need to fix yourself.<br>You’re not broken.</p><p>But you <strong>do</strong> need to realize:</p><blockquote><em>You’ve already been training your mind.<br>You’re already running loops.<br>You’re already in a system.</em></blockquote><p>Now it’s time to train consciously.</p><h4>📘 Read the Book</h4><p>If this article felt like a mirror, not just a post, then <em>Reverse Intelligence</em> was written for you.</p><p>📘 <em>Reverse Intelligence — Train Your Mind Like AI and Shape the Person You Want to Be</em><br> 🛒 Available now on Amazon Kindle<br> 👉 <a href="https://www.amazon.com/dp/B0FGVLC66V">https://www.amazon.com/dp/B0FGVLC66V</a></p><p>You’re already training yourself.<br>It’s time to take the loop back into your hands.</p><p>— <em>Ajay Monga</em></p><p><a href="https://medium.com/@ajay.monga73/you-are-not-just-a-passenger-in-life-you-are-the-driver-0ee01b9c4aae">You Are Not Just a Passenger in Life. You Are the Driver.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb01aaa71900" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Don’t Suffer Naturally Anymore — We Suffer by Design]]></title>
            <link>https://medium.com/@ajay.monga73/we-dont-suffer-naturally-anymore-we-suffer-by-design-0df915a9e707?source=rss-907ba3e21fa6------2</link>
            <guid isPermaLink="false">https://medium.com/p/0df915a9e707</guid>
            <category><![CDATA[consumer-psychology]]></category>
            <category><![CDATA[personal-growth]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[fomo]]></category>
            <category><![CDATA[human-behavior]]></category>
            <dc:creator><![CDATA[Ajay Monga]]></dc:creator>
            <pubDate>Sun, 13 Jul 2025 04:45:43 GMT</pubDate>
            <atom:updated>2025-07-13T05:21:47.363Z</atom:updated>
            <content:encoded><![CDATA[<h3>We Don’t Suffer Naturally Anymore — We Suffer by Design</h3><h4>This Is Why You Feel Incomplete (Even When You Have Everything)</h4><h4>By Ajay Monga</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DkCp2M_0EmaHQQJZ" /></figure><p>Have you ever paused for a moment and thought — <br>“I have everything I need, so why do I still feel behind?”</p><p>You’re not alone.<br>Most of us aren’t suffering because of food, floods, or wild animals anymore.<br>We’re suffering because of flash sales, notifications, unrealistic standards, and the fear of missing out.</p><p>We’re not running from lions.<br>We’re running from <em>feeling left out</em>.</p><h4>What Happened to Our Needs?</h4><p>Back in the day, human problems were simple:</p><ul><li>Find food</li><li>Stay safe</li><li>Build shelter</li><li>Connect with others</li></ul><p>Today?<br>It’s more like:</p><ul><li>Buy the latest phone</li><li>Look fit in selfies</li><li>Be part of every trend</li><li>Don’t miss that “limited drop”</li></ul><p>We’ve moved from <em>needs</em> to <em>wants</em>, and from <em>wants</em> to <em>pressured desires</em> — most of them planted in our minds by someone else.</p><blockquote><strong><em>“If you don’t program your mind, someone else will.”</em></strong><em> — A quote read somewhere</em></blockquote><h4>FOMO: The Engine That Drives It All</h4><p>FOMO (Fear of Missing Out) is no longer just a feeling — <br>it’s a tool, a strategy, and a billion-dollar weapon used by brands to keep you buying, scrolling, upgrading.</p><p><strong>Let’s look at a few real-life examples:</strong></p><ul><li>Your skin was fine until an influencer told you it needs 10 products.</li><li>Your phone worked great — until an ad showed you a “pro version” with features you never needed.</li><li>You felt happy with your vacation — until social media made you think you should’ve gone somewhere more “aesthetic.”</li></ul><p>We don’t just buy things anymore.<br>We buy <em>relevance</em>.<br>We buy <em>belonging</em>.<br>We buy <em>peace of mind</em> from a fear that was <em>first planted by the same system that sells us the cure.</em></p><h4>This Happened to Me Too</h4><p>I once spent hours comparing headphones just because a YouTube reviewer said mine were “outdated.”<br>I didn’t even need new ones.<br>They still worked perfectly — but somehow, I felt like I was missing out.</p><p>That feeling? It wasn’t my own.<br>It was marketed to me.</p><h4>The Real Cost: Mental Load, Debt, and Identity Loss</h4><p>The biggest price we’re paying isn’t just money — it’s mental peace.</p><p>We feel anxious when we don’t buy.<br>We feel guilty when we do.<br>We’re always in a loop of comparing, catching up, upgrading.</p><p>This constant pressure has led to:</p><ul><li>Rising credit card debt</li><li>Burnout culture</li><li>Declining self-worth</li><li>Decision fatigue</li><li>A blurred sense of identity</li></ul><p>People are chasing lifestyles that don’t even align with their values , just because “everyone else seems to be doing it.”</p><p>“Too many people spend money they haven’t earned to buy things they don’t want to impress people they don’t like.” — Will Rogers</p><h4>The Brain Doesn’t Know the Difference</h4><p>Here’s the scary part:<br>Your brain doesn’t fully distinguish between real threats and perceived ones.</p><p>That “Only 3 left!” banner?<br>It activates the same stress response your ancestors felt when food was scarce.</p><blockquote><em>Scarcity, urgency, social proof — these aren’t just tactics. They’re </em>triggers<em> wired into our psychology.<br>And marketing teams know it.</em></blockquote><h4>Marketing Doesn’t Sell Products. It Sells Insecurity.</h4><p>Here’s a hard truth:<br>Most ads don’t just say “buy this.”<br>They say, <em>“You’re incomplete without this.”</em></p><p>That’s the formula:</p><ul><li>Create a gap in your self-image</li><li>Fill it with their product</li><li>Repeat</li></ul><p>This isn’t by accident. It’s intentional.<br>Why sell a soap that cleans, when you can sell a soap that makes someone feel confident, sexy, or successful?</p><p>The more you feel like you’re lacking, the more you buy.</p><h3>So, Who’s Winning?</h3><p>Not us.<br>Not our minds.<br>Not our wallets.</p><p>The winners are:</p><ul><li>Social platforms that profit from your endless scrolling</li><li>Brands that benefit when you feel insecure</li><li>Influencers and algorithms that survive on your attention</li></ul><p>They win when you feel like you’re not enough.<br>They profit when you’re overwhelmed, distracted, and hooked.</p><h4>Stop and Ask Yourself</h4><p><em>Take a moment right now.<br>Open your phone. Look at the last 5 things you bought or saved.</em></p><p><em>Were they really </em>your<em> decisions?<br>Or were they nudged into your mind by what you saw online?</em></p><p>This is not about guilt — it’s about <strong>getting back your power</strong>.</p><h3>The Way Out: From FOMO to JOMO</h3><p>There <em>is</em> a way out — and it starts with awareness.</p><p>Instead of FOMO<strong> (Fear of Missing Out),</strong> we can learn JOMO (<strong>Joy of Missing Out)</strong>.<br>We can ask:</p><ul><li>Do I really want this, or was I made to want it?</li><li>Would I still care about this if no one could see it on Instagram?</li><li>Is this choice adding peace or pressure?</li></ul><p>Here are a few small changes that make a big impact:</p><ul><li><strong>Unfollow accounts</strong> that make you feel behind.</li><li><strong>Delay buying</strong> by 24 hours. Most wants fade.</li><li><strong>Practice gratitude</strong> for what you already have.</li><li><strong>Reconnect</strong> with real needs — rest, purpose, relationships.</li></ul><p>The goal isn’t to avoid everything modern — it’s to <em>choose consciously</em>.</p><h3>Final Thoughts</h3><p>We’re not being hunted by wild animals anymore.<br>But something else is hunting us — our attention, our insecurity, our sense of “enough.”</p><p>We have to wake up.<br>Not everything trending is worth chasing.<br>Not everything expensive is valuable.<br>And not every problem you feel is <em>your</em> problem.</p><p>Some were sold to you.<br>Now it’s time to unsubscribe.</p><blockquote><em>Imagine a world where we buy slowly, live simply, and share joyfully — not because an ad told us to, but because it truly feels enough.</em></blockquote><p><strong>Want to go deeper?</strong><br> I wrote a book that unpacks how we can reprogram our minds in the age of digital noise.</p><p>📘 <strong><em>Reverse Intelligence: </em></strong>Train Your Mind Like AI and Shape the Person You</p><p>Available on Amazon</p><p>→ <a href="https://www.amazon.com/dp/B0FGVLC66V">https://www.amazon.com/dp/B0FGVLC66V</a></p><p>If you’re someone who enjoys reflecting on modern life, habits, and self-awareness, let’s connect:<br> 📷 Instagram → <a href="https://www.instagram.com/hellofromajay/">https://www.instagram.com/hellofromajay/</a></p><p>I regularly share short thoughts, lessons, and behind-the-scenes ideas.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0df915a9e707" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Are Not Just a Passenger in Life. You Are the Driver.]]></title>
            <link>https://medium.com/@ajay.monga73/you-are-not-just-a-passenger-in-life-you-are-the-driver-0ee01b9c4aae?source=rss-907ba3e21fa6------2</link>
            <guid isPermaLink="false">https://medium.com/p/0ee01b9c4aae</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[self-awareness]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[book-recommendations]]></category>
            <category><![CDATA[new-book]]></category>
            <dc:creator><![CDATA[Ajay Monga]]></dc:creator>
            <pubDate>Fri, 11 Jul 2025 17:26:17 GMT</pubDate>
            <atom:updated>2025-07-11T17:26:17.455Z</atom:updated>
            <content:encoded><![CDATA[<h4>By Ajay Monga</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tCWSeQM0jN_NJReL33j4GA.png" /></figure><p>Most of us go through life feeling like we’re being carried along.</p><p>We follow routines.<br>We respond to situations.<br>We react to emotions.</p><p>It’s like life is this giant vehicle we’re sitting in — and we’re not the one steering.</p><p>That’s exactly why I wrote this line in <em>Reverse Intelligence</em>:</p><blockquote><strong><em>“You are not just a passenger in life. You are the driver.”</em></strong></blockquote><p>It’s a simple sentence. But it carries a truth that changed how I live — and how I see personal growth.</p><h4>🧠 From Autopilot to Awareness</h4><p>There was a time when I thought personality was something we were born with. Fixed. Unchanging. A label.</p><p>But over the years, I started observing a pattern — in myself, in others, and even in AI systems I studied in my work.</p><p>We repeat the same thoughts.<br>We follow the same habits.<br>We react in the same ways.</p><p>That’s not personality.<br>That’s a loop.</p><h4>🔁 The Loop That Shapes You</h4><p>In <em>Reverse Intelligence</em>, I explain this loop:</p><p><strong>Senses → Thoughts → Habits → Identity</strong></p><p>We see the same world around us.<br>But each of us processes it differently.<br>Some ignore pain. Some learn from it. Some get stuck in it.<br>And slowly, that loop becomes a “personality.”</p><p>But what if you could step back and say:</p><blockquote><em>“Wait. I can choose how I respond.<br> I can choose what I repeat.<br> I can choose the direction of this loop.”</em></blockquote><p>That’s what drivers do.<br>Passengers go where the road takes them.<br>Drivers take the wheel — and design their path.</p><h4>🧭 Designing Your Mindset</h4><p><em>Reverse Intelligence</em> isn’t about motivation or quick hacks.<br>It’s a mindset shift.<br>It teaches you how to see your habits as code — and your thoughts as input.</p><p>It helps you:</p><ul><li>Understand your loops</li><li>Break the ones that no longer serve you</li><li>Build a better version of yourself — one conscious choice at a time</li></ul><p>You don’t need a breakthrough.<br>You need awareness.<br>And that begins by deciding to stop riding shotgun in your own life.</p><h4>📘 Ready to Take the Wheel?</h4><p>If this message speaks to you, I invite you to explore more in my book:<br><strong>Reverse Intelligence — Train Your Mind Like AI and Shape the Person You Want to Be</strong></p><p>It’s now available on Amazon Kindle- <a href="https://www.amazon.com/dp/B0FGVLC66V">https://www.amazon.com/dp/B0FGVLC66V</a></p><p>Let’s stop living by default.<br>Let’s start driving by design.</p><p>Thanks for reading.<br> — <em>Ajay</em></p><p><a href="https://ajaymonga.medium.com/why-i-wrote-reverse-intelligence-b9a467381142">Why I Wrote Reverse Intelligence</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0ee01b9c4aae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why CSPM(Cloud Security Posture Management) Is the Future of Scalable Cloud Security]]></title>
            <link>https://medium.com/@ajay.monga73/why-cspm-cloud-security-posture-management-is-the-future-of-scalable-cloud-security-2dfcaf638c4b?source=rss-907ba3e21fa6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2dfcaf638c4b</guid>
            <category><![CDATA[cloud-services]]></category>
            <category><![CDATA[cloud-security]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[application-security]]></category>
            <dc:creator><![CDATA[Ajay Monga]]></dc:creator>
            <pubDate>Wed, 21 May 2025 17:10:50 GMT</pubDate>
            <atom:updated>2025-05-21T17:10:50.801Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>Scaling Cloud Security? Here’s Why CSPM Is the Key to Doing It Right</strong></h4><p>In today’s cloud-first world, organizations are rapidly adopting multi-cloud environments to scale faster, deploy quicker, and innovate continuously. But this also introduces new security challenges. Unlike traditional environments, cloud infrastructure is dynamic, ephemeral, and managed across distributed teams.</p><p>Security teams often rely on tools like cloud configuration scanners, compliance checkers, IAM analyzers, and more — but these tools generate thousands of findings in silos, with no unified visibility.<br> And as environments change hourly, keeping up with misconfigurations, over-permissions, and exposed data becomes overwhelming.</p><p>That’s where <strong>CSPM</strong>, or <strong>Cloud Security Posture Management</strong>, becomes essential.<br> It acts as a centralized system to monitor, assess, and improve your cloud security posture at scale.</p><p>Let’s break down what CSPM is, why it matters, and how it helps secure cloud environments efficiently.</p><h4>What Is CSPM?</h4><p><strong>Cloud Security Posture Management (CSPM)</strong> is a solution that continuously monitors cloud environments for security risks, misconfigurations, and compliance violations.</p><p>Think of it as a central command center that:</p><ul><li>Scans your cloud accounts (AWS, Azure, GCP, etc.)</li><li>Detects misconfigurations (like open S3 buckets or unrestricted ports)</li><li>Flags compliance violations (CIS, GDPR, SOC2, etc.)</li><li>Helps prioritize and fix issues based on context and risk</li></ul><p>It doesn’t just show you that something is wrong — it shows you what it means, why it matters, and how to fix it.</p><h4>The Problem CSPM Solves</h4><p>Cloud environments grow quickly. New services are spun up, policies change, teams experiment, and workloads shift.<br> Without proper guardrails, this leads to:</p><ul><li>Publicly accessible storage buckets</li><li>Over-permissive IAM roles</li><li>Disabled encryption or logging</li><li>Forgotten test environments exposing data</li><li>Inconsistent security policies across regions</li></ul><p>These misconfigurations are among the <strong>leading causes of cloud data breaches</strong>.</p><p>Security teams need real-time visibility across multiple accounts, business units, and cloud providers — something traditional tools can’t offer.<br> CSPM fills this gap.</p><h4>How CSPM Works</h4><p>A modern CSPM platform typically follows this workflow:</p><p><strong>1. Asset Discovery</strong></p><p>First, CSPM tools keep track of inventory of your cloud environment:</p><ul><li>Cloud resources (VMs, containers, databases, etc.)</li><li>Network configurations</li><li>IAM users, roles, policies</li><li>Storage buckets, APIs, serverless functions</li></ul><p>It automatically builds a <strong>live map of your cloud assets</strong>.</p><p><strong>2. Continuous Misconfiguration/Issue Detection</strong></p><p>CSPM runs continuous scans for:</p><ul><li>Security group rules (e.g., open ports)</li><li>Unencrypted storage or databases</li><li>Disabled logging or versioning</li><li>Overly broad IAM roles</li><li>Public access to cloud services</li></ul><p>It checks against best practices and compliance frameworks (CIS Benchmarks, PCI, HIPAA, etc.).</p><p><strong>3. Risk Prioritization</strong></p><p>Instead of treating all issues equally, CSPM uses context:</p><ul><li>Is the asset exposed to the internet?</li><li>Does it contain sensitive data?</li><li>What’s the privilege level of the IAM user?</li><li>Is the resource in production?</li></ul><p>This helps teams prioritize what really matters.</p><p><strong>4. Alerting and Automation</strong></p><p>CSPM can:</p><ul><li>Alert teams on Slack, email, or ticketing tools (Jira, ServiceNow)</li><li>Auto-remediate low-risk issues (e.g., disabling public access)</li><li>Trigger workflows via Lambda or automation runbooks</li></ul><p>It ensures that findings don’t just sit in dashboards.</p><p><strong>5. Compliance Monitoring</strong></p><p>It maps your cloud posture to standards like:</p><ul><li>CIS AWS Foundations Benchmark</li><li>NIST, ISO 27001</li><li>GDPR, SOC 2, HIPAA, PCI-DSS</li></ul><p>You can track <strong>compliance scores</strong> and generate audit-ready reports.</p><h4>Useful Metrics CSPM Provides</h4><p>CSPM makes it easy to measure security effectiveness. Key metrics include:</p><ul><li><strong>Total misconfigurations per account/project</strong></li><li><strong>Exposure rate</strong>: % of resources publicly accessible</li><li><strong>IAM risk score</strong>: based on privilege levels and access patterns</li><li><strong>Fix rate and MTTR</strong>: how fast issues are resolved</li><li><strong>Compliance score</strong>: per framework, per region/account</li><li><strong>Top risky accounts</strong>: ranked by misconfigurations or data exposure</li><li><strong>Change detection</strong>: how posture changed after deployments</li></ul><p>These metrics help communicate risk to leadership and track progress over time.</p><h4>Benefits of CSPM</h4><ul><li><strong>Unified Visibility</strong>: View entire cloud environment from a single dashboard</li><li><strong>Faster Remediation</strong>: Actionable, prioritized alerts</li><li><strong>Better Compliance</strong>: Continuously track and report on compliance posture</li><li><strong>Context-Aware Triage</strong>: Focus on what matters, not just what exists</li><li><strong>Developer Collaboration</strong>: Sends misconfig findings to the right team with fix guidance</li><li><strong>Security at Scale</strong>: Covers all accounts, services, and changes in real-time</li></ul><h4>Getting Started with CSPM</h4><p>You can adopt CSPM through commercial tools like Wiz, Prisma Cloud, Orca, or build your own using open-source + cloud APIs.</p><p>Key Steps:</p><ol><li><strong>Inventory Cloud Accounts</strong>: Document all AWS, Azure, and GCP environments</li><li><strong>Connect CSPM Platform</strong>: Use secure read-only permissions</li><li><strong>Define Security Policies</strong>: Use built-in benchmarks or create custom rules</li><li><strong>Prioritize Risks</strong>: Set risk tolerance thresholds and filters</li><li><strong>Automate Workflows</strong>: Integrate with ticketing, CI/CD, and alerting tools</li><li><strong>Track KPIs</strong>: Set goals for risk reduction, SLA compliance, and fix rates</li></ol><h4>High Level CSPM Architecture</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XQHecc5dGpDvuRqB" /></figure><h4>Final Thoughts: Why CSPM Is the Future</h4><p>If your cloud technology usage is growing, <strong>CSPM isn’t optional</strong> — it’s necessary.</p><p>It’s not just about scanning for issues. It’s about gaining <strong>continuous, real-time, contextual visibility</strong> into your cloud environment and being able to take action at scale.</p><p>CSPM helps organizations:</p><ul><li>Prevent misconfiguration based breaches</li><li>Meet compliance faster</li><li>Collaborate better with DevOps and cloud teams</li><li>Strengthen cloud governance and risk posture</li></ul><p>If you’re building a secure cloud-native environment, <strong>CSPM is your starting point.</strong></p><p>Let me know if you’d like a checklist or phased implementation roadmap. I’m also happyto provide sample dashboards, open-source tools, or metrics templates!</p><p><em>Follow me on LinkedIn: </em><a href="https://www.linkedin.com/in/ajay-monga2/"><em>https://www.linkedin.com/in/ajay-monga2/</em></a></p><p><strong>If you like my work &gt;&gt;&gt; Buy Me A Coffee</strong></p><p><a href="https://buymeacoffee.com/ajaymonga">Ajay Monga</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2dfcaf638c4b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why ASPM(Application Security Posture Management) Is the Future of Scalable Application Security]]></title>
            <link>https://medium.com/@ajay.monga73/why-aspm-is-the-future-of-scalable-application-security-43aa795407ec?source=rss-907ba3e21fa6------2</link>
            <guid isPermaLink="false">https://medium.com/p/43aa795407ec</guid>
            <category><![CDATA[application-security]]></category>
            <category><![CDATA[penetration-testing]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[appsec]]></category>
            <category><![CDATA[aspm]]></category>
            <dc:creator><![CDATA[Ajay Monga]]></dc:creator>
            <pubDate>Tue, 20 May 2025 15:20:18 GMT</pubDate>
            <atom:updated>2025-05-21T16:06:13.272Z</atom:updated>
            <content:encoded><![CDATA[<h4>Scaling AppSec? Here’s Why ASPM Is the Key to Doing It Right</h4><p>In today’s world, modern software development is fast, continuous, and complex. Applications are pushed to production weekly, sometimes daily, through automated pipelines. In this dynamic environment, ensuring consistent and effective security is a challenge. Security teams rely on a variety of tools — SAST, DAST, SCA, container scanners, secret detectors, and more — but these tools generate massive amounts of findings in isolation.</p><p>They need to keep up with vulnerabilities, tools, teams, and deadlines — all at once.</p><p>This is where <strong>ASPM</strong>, or <strong>Application Security Posture Management</strong>, comes in: a centralized platform that brings visibility, context, and control over application security at scale.</p><p>Let’s understand ASPM, why it’s useful, and how it helps make applications more secure and easier to manage.</p><h3>What Is ASPM?</h3><p><strong>Application Security Posture Management (ASPM)</strong> is a modern approach to managing and improving the security of applications throughout their lifecycle. It helps organizations gain complete visibility into their application security risks and take action to fix them effectively.</p><p>It acts as a centralized platform that aggregates data from multiple security tools, contextualizes it, and provides a unified view of application risk.</p><p>It collects results from different security tools, put them in one place, and helps teams:</p><ul><li>See which applications have issues</li><li>Understand how risky those issues are</li><li>Assign fixes to the right people</li><li>Track whether things are getting better or worse over time</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*z-oWLkXupx3Wlen6" /></figure><h4>The Problem ASPM Solves</h4><p>Many organizations use multiple security tools: SAST, DAST, SCA, container scanning, secret scanning, and more. But these tools often work in silos. The results end up scattered, duplicated, or even ignored.</p><p>Without a unified layer, it becomes nearly impossible to answer fundamental questions like:</p><ul><li><em>Which applications are the riskiest?</em></li><li><em>Which vulnerabilities are exploitable in production?</em></li><li><em>Which teams are behind on remediation SLAs?</em></li></ul><p>ASPM addresses these gaps.</p><h4>How ASPM Works</h4><p>A typical ASPM implementation includes the following components:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RyjPAAKVM-kZ5swO" /></figure><p><strong>Step 1: Data Integration</strong></p><p>ASPM integrates with a wide range of tools:</p><ul><li><strong>SAST</strong> (CodeQL, Checkmarx)</li><li><strong>SCA</strong> (Snyk, Black Duck)</li><li><strong>DAST</strong> (OWASP ZAP, Burp)</li><li><strong>Container/IaC Scanners</strong> (Trivy, Checkov)</li><li><strong>Secret Scanners and CNAPP Tools</strong></li><li><strong>CI/CD pipelines and Version Control Systems</strong></li></ul><p><strong>Step 2: Normalization and Correlation</strong></p><p>ASPM solutions normalize findings and correlated them to specific:</p><ul><li>Specific applications and microservices</li><li>Repositories and pipelines</li><li>Responsible teams or owners</li><li>Environments (dev, staging, prod)</li></ul><p>Now, a single UI shows which apps have open issues, what severity they are, whether they’re reachable, and who owns fixing them.</p><p><strong>Step 3: Risk Contextualization</strong></p><p>This is where ASPM excels. Instead of blindly prioritizing based on CVSS, we can look at:</p><ul><li>Is the app internet-facing?</li><li>Is the vulnerable function reachable?</li><li>Are there known exploits in the wild?</li><li>What’s the business criticality of the app?</li></ul><p>This allows for <strong>risk-based prioritization</strong>, not just severity-based triage.</p><p><strong>Step 4: Automation and Developer Enablement</strong></p><p>ASPM can:</p><ul><li>Auto-generate tickets in tools like Jira or Azure DevOps</li><li>Notify the correct teams with remediation guidance</li><li>Track SLAs, measure MTTR, and escalate overdue issues</li></ul><p><strong>Step 5: Automates Remediation</strong></p><p>ASPM can automatically create tickets in tools like Jira, send alerts to teams, and track deadlines (SLAs).</p><p><strong>Step 6: Tracks Progress</strong></p><p>You can use ASPM to generate reports showing how quickly teams fix issues, which apps are improving, and where help is needed.</p><h4>Useful Metrics ASPM Provides</h4><p>ASPM makes it easier to measure and report security progress. Common metrics include:</p><ul><li><strong>Total vulnerabilities</strong> per application or team</li><li><strong>Fix rate</strong> (how many issues are fixed vs. found)</li><li><strong>Tool coverage: </strong>Which scanners are running on which apps</li><li><strong>App Risk Score: </strong>Weighted score based on severity, exposure, etc.</li><li><strong>Mean Time to Remediate (MTTR): </strong>how fast issues are being fixed</li><li><strong>SLA compliance: </strong>whether fixes are done within deadlines</li><li><strong>Top risky applications</strong> in the organization</li><li><strong>Reopened issues: </strong>Issues marked fixed but reopened in new scans</li></ul><h4>Benefits of ASPM</h4><ul><li><strong>Unified Risk View:</strong> Complete visibility into security posture across applications.</li><li><strong>Improved Prioritization:</strong> Focus remediation efforts on issues that pose real risk.</li><li><strong>Developer Enablement:</strong> Reduce noise and provide contextual, actionable findings.</li><li><strong>Scalable AppSec Operations:</strong> Automate triage, ticketing, and reporting.</li><li><strong>Stronger Governance:</strong> Track trends, measure outcomes, and report to stakeholders.</li></ul><h4>Getting Started with ASPM</h4><p>Organizations can adopt ASPM through commercial platforms or build custom solutions using open-source tools and internal pipelines.</p><p><strong>Key steps:</strong></p><ol><li><strong>Inventory Applications</strong>: Establish a registry of all apps, teams, and environments.</li><li><strong>Integrate Security Scanners</strong>: Feed findings into a central platform.</li><li><strong>Map Context</strong>: Tie vulnerabilities to apps, owners, and business functions.</li><li><strong>Define Risk Scoring Logic</strong>: Include factors like exposure, data sensitivity, and runtime reachability.</li><li><strong>Automate Workflows</strong>: Create policies for ticketing, SLA management, and alerts.</li><li><strong>Track KPIs</strong>: Set goals for MTTR, fix rate, and risk reduction.</li></ol><h4>High-level ASPM Architecture:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0BPhOYSMyjTixTzn" /></figure><h4>Final Thoughts: Why ASPM Is the Future</h4><p>If you’re working in AppSec at scale — across dozens or hundreds of applications — <strong>you need ASPM</strong>. It doesn’t replace your scanners; it <strong>orchestrates and elevates them</strong>.</p><p>In my experience, ASPM:</p><ul><li>Brings security and developers on the same page</li><li>Focuses remediation where it matters most</li><li>Drives measurable improvements in posture</li></ul><p>It’s the backbone of modern, scalable, intelligent AppSec.</p><p><em>If you’re a security engineer wondering whether ASPM is worth the effort, my answer is: absolutely. It’s not just a tool — it’s a mindset shift.</em></p><p>Let me know if you’d like a practical implementation checklist or a walkthrough of how we rolled this out in phases.</p><p><strong>Let me know if you’d like more examples or want to delve deeper!</strong></p><p><em>Follow me on LinkedIn: </em><a href="https://www.linkedin.com/in/ajay-monga2/"><em>https://www.linkedin.com/in/ajay-monga2/</em></a></p><p><strong>If you like my work &gt;&gt;&gt; Buy Me A Coffee</strong></p><p><a href="https://buymeacoffee.com/ajaymonga">Ajay Monga</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43aa795407ec" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>