<?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 Aadil Faheem on Medium]]></title>
        <description><![CDATA[Stories by Aadil Faheem on Medium]]></description>
        <link>https://medium.com/@lzysoul?source=rss-c4118c0837e8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6ePlNFNT0zTjPyDyAGhN_w.jpeg</url>
            <title>Stories by Aadil Faheem on Medium</title>
            <link>https://medium.com/@lzysoul?source=rss-c4118c0837e8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 22:52:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@lzysoul/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[Building Practical Cyber security for a Growing Business]]></title>
            <link>https://medium.com/@lzysoul/building-practical-cyber-security-for-a-growing-business-eb03e1e56078?source=rss-c4118c0837e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/eb03e1e56078</guid>
            <category><![CDATA[cyber-security-awareness]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[information-security]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <dc:creator><![CDATA[Aadil Faheem]]></dc:creator>
            <pubDate>Sun, 19 Jul 2026 11:20:48 GMT</pubDate>
            <atom:updated>2026-07-19T11:22:16.521Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t9q9APgNDZSL7S-7KkGq4g.jpeg" /></figure><p>When people think about cyber security, they often picture enterprise products costing thousands of dollars every month - CrowdStrike, Microsoft Sentinel, Palo Alto firewalls, dedicated SOC teams, and security engineers working around the clock.</p><p><strong>Most small businesses don’t have any of that.</strong></p><p>What they do have is customer data, employee laptops, internet-connected servers, and the same attackers targeting much larger organisations.</p><p>When I began improving security for our company, buying expensive security products wasn’t an option. Instead, the goal was simple: reduce risk using reliable, well-configured tools that were either already available or completely free.</p><p><strong>Before I begin, I want to emphasise that this approach is not perfect. In cyber security, no solution provides absolute security. </strong>That said, this approach is cost-effective, practical, and particularly suitable for small businesses and organisations.</p><h3><strong>Every Security Decision Started With One Question; Does this reduce risk enough to justify the effort?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*lptqEo2sCUeF24HmN-gAIA.png" /></figure><p>Small businesses don’t need every security product on the market. They need controls that address their biggest risks:</p><ul><li>Malware</li><li>Stolen credentials</li><li>Accidental deletion</li><li>Insider mistakes</li><li>Internet-facing attacks</li><li>Data loss</li></ul><h3>1. Windows Defender is Better Than People Think.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/580/1*2s7_Yjx0fb7e-waM3oDiOg.png" /></figure><p>Windows Defender comes built into all modern Windows operating systems, making it one of the easiest security solutions to deploy and configure. It provides regular security updates, real-time protection, access controls, Controlled Folder Access, and Microsoft SmartScreen — all with zero licensing costs.</p><p>While SmartScreen can occasionally be overly cautious and require workarounds for legitimate applications, its protection against malicious downloads and phishing attempts for regular employees makes it a valuable security feature.</p><p>A well-configured Defender installation is significantly better than an expensive antivirus solution that nobody manages.</p><h3>2. Firewalls Aren’t Just for Routers.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/385/1*JPoCM4TZelTAqwjT2_PH0A.png" /></figure><p>A common misconception is that having a company firewall at the network perimeter is enough to keep systems secure. While a router or perimeter firewall provides an important first line of defence, it should not be the only layer protecting an organisation&#39;s devices. Every endpoint should also have its own firewall configured to restrict unnecessary network traffic.</p><p>On Windows systems, <strong>Windows Defender Firewall</strong> provides robust host-based protection. Properly configured inbound and outbound rules can block unnecessary services, prevent unauthorised applications from communicating over the network, and restrict access to sensitive services such as Remote Desktop Protocol (RDP) to only trusted devices or networks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZLVPBYk1KzQ8unHHDf6L9Q.png" /></figure><p>For Linux systems, tools such as <strong>UFW (Uncomplicated Firewall)</strong> and <strong>iptables</strong> allow administrators to define strict firewall policies. A good practice is to allow only the ports and services that are required while using a <strong>default deny</strong> policy for all other incoming connections. This significantly reduces the attack surface and limits opportunities for unauthorised access.</p><p>A firewall at the network edge is important, but it should never be the only line of defence. By combining perimeter firewalls with properly configured host-based firewalls on every endpoint, organisations implement defence in depth, ensuring that if one layer fails, additional security controls remain in place.</p><h3>3. Backups Are Security Too.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*id__kr80C-c01l4EmHPcxQ.png" /></figure><p>Many organisations only realise the importance of backups after experiencing a ransomware attack or other major data loss event. However, backups are a fundamental part of any cyber security strategy, helping organisations recover from malware, hardware failures, accidental deletion, and natural disasters.</p><p>One of the most widely accepted backup strategies is the <strong>3–2–1 rule</strong>:</p><ul><li><strong>3 copies</strong> of your data — the original data and two backup copies.</li><li><strong>2 different types of storage media — </strong>such as an internal drive and external storage or cloud storage.</li><li><strong>1 offline or offsite copy</strong> — kept disconnected from the primary network.</li></ul><p>The offline copy is particularly important because ransomware often attempts to encrypt any connected drives or network shares it can access. If backups remain connected to the system, they may be encrypted along with the original data, leaving no clean copy available for recovery.</p><p>Equally important is regularly <strong>testing backup restores</strong>. Organisations should periodically verify that backups are complete, uncorrupted, and can be restored within an acceptable time frame. A backup that has never been tested may fail when it is needed most.</p><p>A backup you can’t restore isn’t a backup.</p><h3>4. Least Privilege Solves More Problems Than Antivirus.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/629/1*SxLDqmGpemr7ZaLOPMyLww.png" /></figure><p>One of the most overlooked principles in cyber security is the <strong>Principle of Least Privilege</strong>. Simply put, users should only have the permissions they need to perform their jobs — nothing more.</p><p>For example, most employees should not be able to:</p><ul><li>Install or uninstall software.</li><li>Disable antivirus or other security features.</li><li>Access payroll or HR records.</li><li>Modify server configurations.</li><li>Access sensitive systems unrelated to their role.</li></ul><p>This concept is commonly implemented using <strong>Role-Based Access Control (RBAC)</strong>, where permissions are assigned based on an employee’s role within the organisation. An accountant does not need access to server settings, just as an IT administrator does not need access to payroll records. Restricting permissions reduces the potential impact of both accidental mistakes and malicious activity.</p><p>Some organisations view restricting software installation as inconvenient because it requires IT involvement.</p><p><strong>Personally, I would rather walk to every employee’s computer and install the required software myself, even if I had to explain the process a thousand times rather than deal with the consequences of a single successful malware infection caused by an unauthorised download. </strong>Spending a few extra minutes helping users is far less costly than recovering from a security breach.</p><h3>5. Password Managers Beat Password Policies</h3><p>For many years, organisations focused on enforcing complex password policies. Employees were required to create passwords with uppercase letters, lowercase letters, numbers, special characters, and to change them every few months. In practice, this often resulted in predictable passwords such as <strong>Password123!</strong>, <strong>Password124!</strong>, and <strong>Password125!</strong>, which provide little real security.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/1*UYtHcVGCGLFH5beTNEOmsg.png" /></figure><p>Modern security guidance takes a different approach. Rather than forcing users to memorise increasingly complex passwords, organisations should encourage:</p><ul><li>Unique passwords for every account.</li><li>Long passwords or passphrases.</li><li>Multi-Factor Authentication (MFA) wherever possible.</li><li>The use of a reputable password manager to securely generate and store credentials.</li></ul><p><strong>During my own security audits and testing, approximately 99% of employees failed to create passwords that met even basic security expectations without guidance.</strong> This reinforces an important lesson: relying solely on password policies is rarely enough. Giving users the right tools such as password managers and reinforcing them with MFA produces far better security than expecting people to remember dozens of complex, unique passwords.</p><p>Strong security should work with human behaviour, not against it.</p><h3>6. Documentation Is a Security Control.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/1*8sqaPQ3X3vk9Dn16UnJAJw.png" /></figure><p>Documentation is one of the most overlooked aspects of cyber security, yet it is one of the most valuable security controls an organisation can have. Keeping accurate records of asset inventories, firewall rule changes, server configurations, patch history, and incident response procedures ensures systems can be managed consistently and recovered quickly when problems occur.</p><p>I know documentation isn’t something most people enjoy writing or maintaining, but it is absolutely necessary. Personally, I enjoy documenting systems because it makes troubleshooting, maintenance, and security far more manageable. Good documentation saves time, reduces mistakes, and makes it easier for anyone to understand the environment.</p><p>When something breaks, or worse, a security incident occurs — documentation is often what saves you.</p><h3>7. What I Didn’t Buy</h3><p>One of the biggest misconceptions in cyber security is that effective security requires expensive enterprise solutions. <strong>For this project, I didn’t purchase an enterprise EDR platform, hire a 24/7 Security Operations Center (SOC), or deploy AI-powered threat detection.</strong></p><p>Instead, I focused on getting the fundamentals right. Properly configuring Windows Defender, enforcing firewall rules, applying the principle of least privilege, maintaining reliable backups, using password managers, and documenting everything provided far more value than buying expensive tools without the resources to manage them.</p><p>For small businesses, strong fundamentals will almost always provide a better return on investment than advanced security products that go unused or are poorly configured.</p><h3>The Biggest Lesson</h3><p>I learned from this project is that security isn’t determined by price. A poorly configured enterprise security platform provides far less protection than free tools that are properly configured, regularly maintained, and used consistently. Small businesses don’t need perfect security — they need practical, well-managed security that fits their environment and resources.</p><p>Attackers rarely compromise small businesses because they defeated cutting-edge security products. More often, they succeed because of weak passwords, exposed services, missing backups, excessive permissions, or systems that haven’t been updated in months. Those problems don’t require million-dollar budgets to fix — they require discipline, planning, and a commitment to implementing the fundamentals consistently.</p><p><strong>Good cybersecurity isn’t built by buying the most expensive tools. It’s built by doing the simple things well, every single day.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb03e1e56078" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Aadhaar and PAN Card Leaks: What I Discovered and Reported]]></title>
            <link>https://medium.com/@lzysoul/aadhaar-and-pan-card-leaks-what-i-discovered-and-reported-5c30bb848186?source=rss-c4118c0837e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c30bb848186</guid>
            <category><![CDATA[awareness]]></category>
            <category><![CDATA[aadhaar-card]]></category>
            <category><![CDATA[india]]></category>
            <category><![CDATA[data-breach-report]]></category>
            <category><![CDATA[data-breaches-news]]></category>
            <dc:creator><![CDATA[Aadil Faheem]]></dc:creator>
            <pubDate>Sun, 27 Apr 2025 18:32:03 GMT</pubDate>
            <atom:updated>2025-10-27T21:31:35.747Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>My name is <a href="http://www.linkedin.com/in/aadilfaheem"><strong>Aadil Faheem</strong></a>, a cybersecurity enthusiast and analyst. When I discovered these vulnerabilities in Indian government websites, I was just <strong>18 years old</strong>, fueled by curiosity and boredom. At the time, I was skeptical about revealing my findings publicly, unsure of how they would be received. Today, with more confidence and experience, I’m finally sharing the full story behind how I contributed to protecting sensitive citizen data.</p><h3>Setting the Stage: Why This Matters</h3><p>In today’s interconnected world, safeguarding sensitive personal data is more critical than ever. Governments, institutions, and companies hold vast amounts of user data, making them prime targets for breaches or victims of simple misconfigurations. <strong>Aadhaar Card and PAN Cards were and still are the 2 most Important Identifiers in India</strong> with details like Name, D.O.B, Address, Phone Numbers, Signature etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*li9ZSX5J4Mqow8x8g8UMLQ.png" /></figure><h3>Inspiration</h3><p>My journey into cybersecurity started with curiosity, but it turned into action when I came across the work of <strong>Robert Baptiste</strong>, popularly known as <a href="https://x.com/fs0c131y"><strong>@fs0c131y</strong></a> on Twitter/X.<br> Baptiste became widely known for discovering vulnerabilities in major Indian apps and government platforms, always disclosing them ethically and respectfully.</p><p>His approach? finding real problems, helping fix them, and respecting privacy — motivated me to see if I could apply the same mindset and give back to the community.</p><h3>Enough Intros. Lets talk details!</h3><p>Following responsible research practices, I began manually exploring publicly accessible government portals and associated websites without breaching any terms of service or bypassing any authentication systems.</p><p><strong>I focused on three main aspects:</strong></p><ul><li>Misconfigured databases</li><li>API endpoints exposing sensitive data</li><li>Incorrect permissions on downloadable files</li></ul><p><strong>Key methods included:</strong></p><ul><li>Passive browsing</li><li>URL parameter tampering</li><li>Checking for exposed .json, .csv, and .xls files</li><li>Looking into publicly available APIs without authentication</li></ul><p>At no point did I attempt to exploit, manipulate, or access unauthorized systems.</p><p>Within a few days, I started noticing patterns — particularly in smaller government-affiliated websites — where improperly configured servers and APIs were unintentionally leaking <strong>Aadhaar numbers</strong>, <strong>PAN card details</strong>, <strong>phone numbers</strong>, and <strong>addresses</strong> in plaintext formats, It was extremely concerning when I found out that by changing the characters in the links random Aadhaar would just load ready to be downloaded without any password protections!</p><p><strong>Sites like:</strong></p><p><a href="http://ipindiaonline.gov.in/">ipindiaonline.gov.in</a></p><p><a href="http://haryanarera.gov.in/">haryanarera.gov.in</a></p><p><a href="http://uidai.gov.in/">uidai.gov.in</a></p><p><a href="http://gujrera.gujarat.gov.in/">gujrera.gujarat.gov.in</a></p><p>were just randomly leaking Aadhaar cards</p><p><strong>Examples of issues found:</strong></p><ul><li>Public API returning full citizen registration data without access controls</li><li>Downloadable Excel sheets containing Aadhaar and PAN numbers</li><li>Downloadable PDF Files showing Aadhaar and PAN cards</li><li>Incorrectly configured cloud storage buckets</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zZIwBmBcex88cuKANHeVBg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RCULWxkF_LQ3-JMkTSOr_w.jpeg" /><figcaption><strong>Examples of Exposed Aadhaar Cards</strong> (Important Info Redacted)</figcaption></figure><h3>Responsible Disclosure</h3><p>Upon confirming the issues, my next step was <strong>responsible disclosure</strong>.</p><p><strong>I gathered the necessary evidence:</strong></p><ul><li>Screenshots of exposed data (without downloading excessive data)</li><li>Network requests showing unsecured endpoints</li><li>URLs and detailed explanations</li></ul><p><strong>I reported these vulnerabilities to:</strong></p><ul><li>The respective site administrators (when emails were listed)</li><li>Indian government cybersecurity emails</li></ul><p><strong>In my communications, I made it clear:</strong></p><ul><li>No exploitation or misuse occurred</li><li>I was willing to provide full details for patching</li><li>I would not publicly disclose anything until the issue was fixed</li></ul><p>It took some time — some teams responded faster than others — but eventually, the vulnerabilities were acknowledged, and patches were deployed.</p><p><strong>In some cases, the affected websites:</strong></p><ul><li>Disabled vulnerable endpoints</li><li>Added authentication checks</li><li>Moved data behind secure access controls</li></ul><h3>Lessons Learned</h3><p>This experience taught me valuable lessons:</p><ul><li><strong>Small websites matter</strong>: While large government portals often have better security teams, smaller affiliated websites often slip through the cracks.</li><li><strong>Ethical hacking is important</strong>: It’s possible to help improve security without being destructive.</li><li><strong>Patience is key</strong>: Responsible disclosure often requires multiple follow-ups and a lot of waiting.</li><li><strong>You don’t need to break the law to find problems</strong>: Everything I found was accessible through public means and<strong> required no hacking tools or unauthorized access.</strong></li></ul><p>Moreover, this strengthened my belief that <strong>individuals can make a real difference</strong>, even when working alone, with limited resources, purely driven by the idea of protecting data and helping people.</p><h3>Conclusion</h3><p>Security is a collective responsibility — and whether it’s big tech companies or national governments, even the best systems can have vulnerabilities.</p><p>By sharing this story, I hope to inspire others to <strong>look, learn, and act responsibly</strong>.<br> Cybersecurity is not just about pointing out flaws; it’s about <strong>making the internet a safer place for everyone</strong>.</p><h4>Written by: Aadil Faheem</h4><p><a href="https://aadilfaheem.framer.website/"><strong>Portfolio</strong></a><strong> | </strong><a href="https://www.linkedin.com/in/aadilfaheem/"><strong>LinkedIn</strong></a><strong> | </strong><a href="https://github.com/Aadil-Faheem"><strong>Github</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c30bb848186" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Securing Game Code in 2025: Modern Anti-Cheat Techniques and Best Practices]]></title>
            <link>https://medium.com/@lzysoul/securing-game-code-in-2025-modern-anti-cheat-techniques-and-best-practices-e2e0f6f14173?source=rss-c4118c0837e8------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2e0f6f14173</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[unity-game-development]]></category>
            <category><![CDATA[unity3d]]></category>
            <category><![CDATA[anti-cheat-system]]></category>
            <dc:creator><![CDATA[Aadil Faheem]]></dc:creator>
            <pubDate>Fri, 18 Apr 2025 18:23:34 GMT</pubDate>
            <atom:updated>2025-04-18T18:23:34.207Z</atom:updated>
            <content:encoded><![CDATA[<p>As the global gaming industry surpasses $200B, the sophistication of cheats and exploits has grown alongside it. For developers and security analysts, ensuring code security and fair play is now a critical component of game development — not just a post-launch patch fix.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dJmLmiTmXzWEH-Bw1hTlOg.png" /><figcaption>Various Tools Used for Cheating/Hacking in Video Games</figcaption></figure><p>Having worked extensively in <strong>code security and anti-cheat for Unity</strong>, this blog breaks down the current threat landscape and what modern studios can do to stay ahead.</p><h3><strong>Understanding Modern Game Cheating</strong></h3><p>Cheating has evolved far beyond<strong> “</strong><a href="https://en.wikipedia.org/wiki/Glossary_of_video_game_terms#God_mode"><strong>god mode</strong></a><strong>”</strong> hacks and save file tampering. Today’s exploit landscape includes:</p><ul><li><strong>Runtime memory manipulation</strong> via tools like Cheat Engine and ArtMoney</li><li><strong>DLL injection</strong> to override or hook into core game functions</li><li><strong>Packet spoofing or replay attacks</strong> in online multiplayer</li><li><strong>Aimbots and ESPs</strong> built using OCR, screen reading, or direct memory access</li><li><strong>Code decompilation</strong> via tools like dnSpy and ILSpy targeting Unity’s managed assemblies</li></ul><p>The attackers aren’t hobbyists anymore — many are running sophisticated monetized cheat services with update support and user dashboards.</p><h3><strong>Core Code Security Practices (Unity Focus)</strong></h3><p>If you’re shipping a Unity game, you’re likely using C# with Mono or IL2CPP. Here’s how to harden your build:</p><h4><strong>1) IL2CPP Build Target</strong></h4><p>Translating C# assemblies into native C++ code makes reverse engineering significantly harder than standard Mono builds. Combine this with:</p><ul><li><strong>Stripping managed symbols</strong></li><li><strong>Disabling script debugging</strong></li><li><strong>Disabling unsafe serialization</strong></li></ul><h4><strong>2) Obfuscation</strong></h4><p>Use tools like <a href="https://www.red-gate.com/products/smartassembly/"><strong>SmartAssembly</strong></a> or <a href="https://assetstore.unity.com/packages/tools/utilities/obfuscator-free-89420"><strong>Unity Obfuscator</strong></a> to rename methods, obscure control flow, and hide sensitive logic. This deters casual reverse engineers and slows down cheat devs.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*-6H9whhOge-e9CcB14k6hg.png" /><figcaption>Obfuscation Techniques</figcaption></figure><h4><strong>3) Data Encryption</strong></h4><p>Secure any sensitive local data such as:</p><ul><li>Save files (use AES or RSA with device-bound keys)</li><li>PlayerPrefs (never store plaintext stats)</li><li>Local tokens or user auth info</li></ul><p>Unity has no built-in encryption, so custom encryption logic or libraries like <a href="https://www.bouncycastle.org/"><strong>BouncyCastle</strong></a> are essential.</p><h3><strong>Anti-Cheat Techniques: Local &amp; Server-Side</strong></h3><p>Depending on your game architecture, you’ll likely need a hybrid model. Here’s a breakdown:</p><h4><strong>Client-Side Detection</strong></h4><ul><li>Detect memory tampering (e.g., hash-based verification of runtime memory)</li><li>Detect speed hacks via delta-time inconsistencies</li><li>Use heuristics to detect automation (inhuman reaction times, perfect aim trajectories)</li><li>Anti-debugging logic to crash or isolate suspicious environments</li></ul><h4><strong>Server-Side Enforcement</strong></h4><ul><li>Validate every major game action (movement, damage, XP gain)</li><li>Rate-limit or sequence-check user actions (prevent packet flooding)</li><li>Use authoritative simulations for competitive elements (hit detection, physics)</li><li>Timestamp verification and nonce tracking to prevent packet replay</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*9tLgKi9Vsh0gMdXQiMPgPQ.png" /><figcaption>Techniques Used in Server-Side Enforcement</figcaption></figure><h4><strong>Network Security</strong></h4><ul><li>Encrypted communication with backend (TLS/SSL mandatory)</li><li>Use HMACs or signed tokens for session validation</li><li>Obfuscate protocol structure if using UDP or custom protocols</li></ul><h4><strong>Logging &amp; Post-Match Review</strong></h4><p>Real-time detection is ideal, but post-match analytics are just as important:</p><ul><li>Build a <strong>replay system</strong> to verify suspect matches</li><li>Store <strong>user event logs</strong> for server-side review (damage dealt, movement patterns, actions per minute)</li><li>Use anomaly detection to auto-flag outliers for moderation</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/999/1*Raqhbs_E0jZi8VgQdODEBA.jpeg" /></figure><h3><strong>Final Thoughts</strong></h3><p>You can’t fully stop cheaters — but you can slow them down, detect them early, and design systems that make cheating unrewarding or visible. Think of security as layered defense — obfuscation, runtime checks, secure networking, and analytics working in tandem.</p><p>At the indie studio level, prioritizing IL2CPP, encrypted save files, and basic server validation already puts you ahead of most Unity games on the market, So best of luck with your journey!</p><p>Written By: <a href="http://www.linkedin.com/in/aadilfaheem">Aadil Faheem</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2e0f6f14173" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>