<?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 `Mr-IoT` on Medium]]></title>
        <description><![CDATA[Stories by `Mr-IoT` on Medium]]></description>
        <link>https://medium.com/@veerababupenugonda?source=rss-fcb52ffdadd4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nLkb92f5hzEQYoW4MzG7hw.jpeg</url>
            <title>Stories by `Mr-IoT` on Medium</title>
            <link>https://medium.com/@veerababupenugonda?source=rss-fcb52ffdadd4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:25:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@veerababupenugonda/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[Conferences and community collaborations - why is it failing?]]></title>
            <link>https://medium.com/@veerababupenugonda/conferences-and-community-collaborations-why-is-it-failing-9266d0082cd2?source=rss-fcb52ffdadd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/9266d0082cd2</guid>
            <dc:creator><![CDATA[`Mr-IoT`]]></dc:creator>
            <pubDate>Sun, 28 Sep 2025 21:09:57 GMT</pubDate>
            <atom:updated>2025-09-29T04:38:07.706Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-ZO8lSgoyS-Dl0vX5Lkbzw.png" /></figure><p>This post is based on my discussions with conference organizers and individual community organizers.</p><h4>1 Different community types</h4><p><strong>Non-technical communities</strong> : Awareness-driven, beginners, hobbyists. Focus on spreading general knowledge.</p><p><strong>Technical communities</strong> : Practitioners, engineers, testers. Focus on tools, skill development, and sharing know-how.</p><p><strong>Research communities</strong> : Exploit developers, reverse engineers, deep-divers. Focus on publishing research, papers, and advanced findings.</p><p><strong>Company-driven communities</strong> : A legally registered company (like Pvt Ltd or LLP) that also maintains a “community.”</p><ul><li>On paper, they look like a community.</li><li>In practice, they often operate as a hybrid model: partly brand-building/lead generation for the company, partly genuine community activity.</li><li>Sometimes, the community side is real (knowledge sharing, meetups). Other times, it’s mostly marketing under a community tag.</li></ul><p>👉 Conferences expect the same results from all, which doesn’t work.</p><h4>2 Broadcasting power of communities</h4><ul><li>Yes, they can push on Telegram, Discord, LinkedIn, etc.</li><li>But reach ≠ conversions.</li><li>10k views doesn’t mean 100 tickets.</li></ul><h4>3 Why coupon codes are not used</h4><ul><li>People don’t know codes exist.</li><li>They don’t trust it will work.</li><li>Discounts feel too small.</li><li>Many register last minute → skip codes.</li><li>Corporate-sponsored folks don’t care.</li></ul><h4>4 Are people too rich to care?</h4><ul><li>Not really.</li><li>Corporate budgets = no need for coupons.</li><li>But students &amp; self-funded professionals still care.</li></ul><p>👉 The issue is poor design of collaboration, not just money.</p><h4>5 The rise of “founder” culture</h4><ul><li>Many folks start communities without knowing even ABC of security.</li><li>Tag themselves as “Founder of XYZ community.”</li><li>Main goal? Free passes &amp; recognition.</li></ul><p>👉 This dilutes the value of true collaboration.</p><h4>6 Why collaboration is failing</h4><ul><li>Conferences treat communities as marketing channels, not partners.</li><li>Communities feel used for logos and ignored otherwise.</li><li>Coupons don’t track true impact.</li><li>It ends up looking like an identity game, not real collaboration.</li></ul><h4><strong>7 End of the day</strong></h4><ul><li>Real collaboration = amplifying voices, helping students, supporting research culture, logos, and coupon codes that actually help those who need them.</li><li>Fake collaboration = free passes for “founders” and trusted circles(without doing proper broadcast) , vanity titles.</li></ul><p>👉 The difference comes down to intent + execution.</p><h3>Let me give my suggestion make it better collaboration that can bring success</h3><ul><li>Add coupon codes directly in posters and flyers to improve visibility.</li><li>Provide special offers for example, if a certain number of tickets are sold using a community’s coupon, that community could receive a few free passes in return.</li><li>If communities run meetups (online or in person), they should utilize those platforms to broadcast conferences more effectively.</li><li>To the conferences: it may be better to stop messy collaborations that don’t add real value. Move forward without unnecessary community partnerships and focus on cleaner, more meaningful engagement.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9266d0082cd2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Conferences… Conferences… Conferences…]]></title>
            <link>https://medium.com/@veerababupenugonda/conferences-conferences-conferences-e36679508938?source=rss-fcb52ffdadd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e36679508938</guid>
            <category><![CDATA[discipline]]></category>
            <category><![CDATA[security-conference]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[conference]]></category>
            <dc:creator><![CDATA[`Mr-IoT`]]></dc:creator>
            <pubDate>Thu, 06 Mar 2025 14:43:03 GMT</pubDate>
            <atom:updated>2025-03-06T14:43:20.640Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4oorHPaaR6c52Yh-" /></figure><p>Yay! I got goodies from different stalls.</p><p>What’s the main motive of conferences from the OG generation to present generation?</p><p>Here are some stories I’ve heard (not mentioning any conference names):</p><h4><strong>Accidentally overheard stories:</strong></h4><p>There are groups of girls and boys who definitely don’t seem like professionals. They say that people come to these conferences to hunt for girls, not bugs. That’s a strong statement, but it might be true.</p><p>I’ve seen with my own eyes people offering drinks and vapes to girls to look cool and start conversations. It could be vice versa too, but is this really the purpose of attending conferences?</p><p>Not at all. At the end of the conference, I met a person (maybe from Delhi, I don’t remember his name and don’t want to disclose it). He came to the conference by himself, spent thousands of rupees on stay and the conference, but he didn’t waste his time. He participated in a live bug bounty program and earned a good bounty that covered his expenses. On the second day, he focused on networking.</p><h4>Conclusion:</h4><p>If you don’t know much what to do in conference, instead of roaming around, look at the schedule multiple times. You might find something familiar and attend that <strong>workshop/village/talk</strong>. Focus on listening and learning.</p><p>Not everyone will teach you these things; we have to learn on our own.</p><h4>So, my thoughts: Nobody is interested in impressing anyone unless they don’t have a proper aim in life.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e36679508938" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[No More ask the question . “How to step into IoT Security?”]]></title>
            <link>https://medium.com/@veerababupenugonda/no-more-ask-the-question-how-to-step-into-iot-security-3b7b08348eeb?source=rss-fcb52ffdadd4------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b7b08348eeb</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[bluetooth]]></category>
            <category><![CDATA[iot]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[zigbee]]></category>
            <dc:creator><![CDATA[`Mr-IoT`]]></dc:creator>
            <pubDate>Sun, 19 Jul 2020 12:58:53 GMT</pubDate>
            <atom:updated>2025-02-17T06:05:49.459Z</atom:updated>
            <content:encoded><![CDATA[<h3>No More ask the question . “How to step into IoT Security?”</h3><p>Hi myself Mr-IoT.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AJKHEc28AFa7txyryf-4sg.jpeg" /><figcaption>card</figcaption></figure><p>As I have overwhelmingly received the same question more than I ever anticipated, I have decided to write a blog on the same.</p><p><strong>Frequently Asked Question:</strong><br>“Hi, can someone help me get started with pentesting IoT devices and their communications? I’m searching for a reliable book or course. Thank you.”</p><p><strong>Answer:</strong><br>Just Start Dive into the World of IoT Security</p><p>Welcome to the threshold of IoT security, a dynamic and ever-evolving field that beckons with both challenge and opportunity. The path to mastering pentesting in IoT is less about finding a single starting point and more about immersing yourself in a community and resources dedicated to this niche.</p><p><strong>IoTSRG: Open Security Community:</strong></p><p><strong>Website: </strong><a href="https://www.iotsrg.org/">https://www.iotsrg.org/</a><br>We’ve established <strong>IoT Security Research Group</strong> as a vibrant open security community, specifically tailored for those intrigued by IoT development and security testing. Our ethos revolves around sharing knowledge and solutions, not just answers. Here, you’ll find a collective of experts and enthusiasts committed to exploring the depths of IoT security, ensuring you’re always equipped with cutting-edge insights and strategies.</p><p><strong>One-Stop Repository for IoT Security Resources:</strong><br>Curated by myself, this repository stands as one of the world’s most recognized treasure troves for IoT security resources. It’s your gateway to an exhaustive array of materials, from beginner guides to advanced techniques.<br><a href="https://v33ru.github.io/IoTSecurity101/">Explore IoTSRG on GitHub</a></p><p><strong>Overcoming Common Challenges:</strong><br>We acknowledge the hurdles that newcomers face, such as installing tools for Bluetooth pentesting. Solutions for these initial challenges have been personally identified and addressed, ensuring you have a smoother start.<br><a href="https://github.com/IoTSecurity101/BLE-UAE">Bluetooth Pentesting Tool Installation Guide</a></p><p><strong>Stepping into IoT Security:</strong><br>For those who are taking their first steps, I’ve shared insights and experiences in one of my talks at null Bangalore. These slides offer a foundational understanding of what it means to venture into IoT security.<br><a href="https://speakerdeck.com/v33ru/stepping-into-iot-security">View the Slides: Stepping into IoT Security</a></p><p><strong>A Key Reminder:</strong><br>To effectively pentest and secure IoT devices, hands-on experience is invaluable. Owning a device to test, break, and ultimately understand its vulnerabilities and workings is crucial. It’s through this practical engagement that you’ll develop a nuanced understanding of IoT security.</p><p><strong>In Conclusion:</strong><br>Embarking on your IoT pentesting journey is about making that first step with curiosity and enthusiasm. Leverage the community, resources, and tools available to you. Remember, the journey is as rewarding as the destination. Welcome to IoTSecurity101, where your journey into IoT security begins.</p><p><strong>Remember this: To hack/break a device, need a device</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*1Fs55x8EOP2Sk3oD" /></figure><p>In the Security industry, there are always two types of people including enthusiasm</p><p><strong>Type 1</strong>: those who are starting a career in the security field (completely freshers)</p><p><strong>Type 2:</strong> those who are from the infosec field and want to learn IoT Pentesting</p><p><strong>Type 1: NOOBS guide (freshers):</strong></p><p>Those who don’t have any knowledge of the information security field and wanted to start IoT security as a career option is somewhat risks as per my understanding, cause there are very nominal jobs for freshers in IoT security jobs or product security jobs.</p><p>The main reason is IoT security is not only related to hardware and firmware it includes all new and old technologies inside.</p><p>Let us consider one device that works with Bluetooth and is operated by an android app in this case we need to have knowledge of both Bluetooth and android pentesting. Starting a career in IoT Security without having minimum essential knowledge of information security is bit hard, until a company supports you well.</p><p>Need to learn for basics pentesting following areas</p><h4><strong>1. Network Pentesting in the IoT Context:</strong></h4><ol><li>TCP and UDP Protocols: Start by focusing on TCP and UDP, as most IoT communications leverage these protocols. Utilize packet filters like “dns” to analyze data behavior outside your network, providing insights into potential vulnerabilities.</li><li>Port and Service Scanning: Conduct scans to identify open ports and determine the versions of services running on the IoT device. This step is crucial for understanding the device’s network footprint.</li><li>Vulnerability Identification: Look for known vulnerabilities associated with the versions of the running services on the device. This approach can quickly highlight potential weaknesses without extensive testing.</li><li>Debug Access and Remote Connections: Check if the device offers debug access and use commands like “netstat” to review any established remote connections and listening ports. This information can reveal unauthorized access points or insecure configurations.</li><li>Traffic Analysis with Port Mirroring: Employ a smart managed switch capable of port mirroring to capture and analyze traffic directly from the IoT device. This method allows for a deeper understanding of the device’s network behavior and interactions.</li><li>Utilizing Metasploit and Vulners.com: Metasploit offers an array of network-based attack scripts and tools for enumeration tailored to specific protocols, services, or device models. Complement this with vulnerability searches on vulners.com to find exploits and security flaws related to your IoT device.</li></ol><h4><strong>2. Embedded application:</strong></h4><p>Nothing But web UI of the device.</p><p>Focusing on the Web UI of IoT devices is a critical aspect of understanding and mitigating device-side attacks. Here’s how you can approach this:</p><ol><li>Choose Your Targets: Begin with home network routers or affordable IoT devices that feature web configuration interfaces. These devices are accessible and represent common targets for attackers, making them ideal for educational purposes.</li><li>Understand Device-Side Attacks: Concentrate on how attacks can be launched from the WebUI. This involves exploring vulnerabilities that can be exploited through the web interface, such as cross-site scripting (XSS), SQL injection, command injection, and improper authentication and authorization checks.</li><li>Utilize Established Resources:</li></ol><ul><li>The OWASP Web Security Testing Guide (WSTG): This guide provides a comprehensive framework for testing the security of web applications and services. It covers everything from information gathering to post-exploitation, tailored to web interfaces, which can be directly applied to IoT device web UIs. <a href="https://owasp.org/www-project-web-security-testing-guide/stable/">OWASP WSTG</a></li><li>Embedded Application Security Best Practices: This resource focuses on security best practices for embedded applications, including web interfaces on IoT devices. It offers insights into common vulnerabilities and how to address them. <a href="https://scriptingxss.gitbook.io/embedded-appsec-best-practices/">Embedded AppSec Best Practices</a></li></ul><p>4. Practical Exploration: Experiment with identified vulnerabilities on your test devices. Understand how different types of attacks can be executed through the web UI and observe the device’s response. This hands-on approach is invaluable for learning about real-world exploits and defenses.</p><p>5. Security Testing: Apply methodologies from the OWASP WSTG to conduct systematic security testing of the web UI. This includes testing for authentication flaws, session management issues, input validation vulnerabilities, and more.</p><p>6. Remediation and Reporting: Learn how to remediate identified vulnerabilities and understand the importance of reporting and documentation in the context of security testing.</p><h4><strong>3. Mobile IoT Apps (android/iOS):</strong></h4><p>In the realm of IoT security, the significance of mobile applications, particularly those on Android and iOS platforms, cannot be overstated. These applications often serve as the primary interface for controlling and interacting with IoT devices, making them a critical component of the overall security posture of IoT ecosystems. Here’s how knowledge in Android and iOS pentesting becomes a valuable asset:</p><p><strong>Android Pentesting:</strong></p><ul><li>Understanding Android Security Architecture: Familiarity with the underlying security mechanisms of Android, including permission models, sandboxing, and secure communication channels, is essential.</li><li>Android Pentesting Tools and Techniques: Learning to use tools like apktool, dex2jar, and Frida, as well as understanding how to perform static and dynamic analysis of Android applications, are key skills.</li><li>Resource: The “Android Hacker’s Handbook” offers a comprehensive exploration into the vulnerabilities, exploitation techniques, and defense mechanisms within Android devices.</li><li><a href="https://www.amazon.in/Android-Hackers-Handbook-MISL-WILEY-Joshua/dp/812654922X">Android Hacker’s Handbook on Amazon</a></li></ul><p><strong>iOS Pentesting:</strong></p><ul><li>iOS Security Features: Gaining insights into iOS’s security features, including its permission system, data protection APIs, and secure enclave, is crucial for effective pentesting.</li><li>Exploitation and Reverse Engineering: Mastery over tools and methodologies for jailbreaking, reverse engineering, and exploiting iOS applications is necessary for uncovering vulnerabilities.</li><li>Resource: The GitHub repository “osx-and-ios-security-awesome” curated by Ashish B provides an extensive list of resources, tools, and reading materials dedicated to macOS and iOS security.</li><li><a href="https://github.com/ashishb/osx-and-ios-security-awesome">osx-and-ios-security-awesome on GitHub</a></li></ul><h4><strong>4. Wireless communication (WiFi / Bluetooth / Zigbee / Zwave /LoraWAN) :</strong></h4><p>Let’s see the attacks on wireless technology</p><p>Wireless technologies are a cornerstone of IoT devices, facilitating seamless communication and connectivity. However, this convenience also introduces vulnerabilities that can be exploited by attackers. Understanding the landscape of wireless attacks, especially within Wi-Fi networks, is essential for IoT security professionals. Let’s delve into the types of Wi-Fi attacks and resources for learning.</p><p><strong>Types of Wi-Fi Attacks:</strong></p><p><strong>1. AP (Access Point) Side Attacks:</strong></p><ul><li>Rogue AP: An attacker sets up a malicious AP with a strong signal to lure victims into connecting, enabling the attacker to intercept sensitive data.</li><li>Evil Twin: Similar to the Rogue AP attack, but specifically mimics a legitimate AP to trick users into connecting.</li><li>AP Deauthentication: The attacker sends deauthentication packets to clients, disconnecting them from their legitimate AP, often as a precursor to other attacks like Evil Twin.</li></ul><p><strong>2. Client-Side Attacks:</strong></p><ul><li>Man-in-the-Middle (MitM): After a client connects to a malicious or compromised AP, the attacker intercepts and potentially alters the communication between the client and the internet.</li><li>Client Misassociation: Clients can be tricked into connecting to attacker-controlled APs if they are configured to automatically connect to known networks.</li></ul><p><strong>Learning Resources:</strong></p><p>To effectively defend against these attacks, it’s important to have a solid understanding of how they work and how to conduct penetration testing to identify vulnerabilities. One highly recommended resource is:</p><ul><li>“Linux Wireless Penetration Testing for Beginners” by Vivek Ramachandran: This book provides a comprehensive guide to penetration testing Wi-Fi networks, covering both theory and practical, hands-on techniques. It is tailored for beginners and progresses to more advanced topics, making it an excellent starting point for those new to wireless penetration testing.</li><li><a href="https://www.amazon.in/Linux-Wireless-Penetration-Testing-Beginners/dp/1788831926/ref=sr_1_1?dchild=1&amp;qid=1595158943&amp;refinements=p_27%3AVivek+Ramachandran&amp;s=books&amp;sr=1-1">Linux Wireless Penetration Testing for Beginners on Amazon</a></li></ul><p><strong>Bluetooth technology:</strong></p><p>Here as well two types of Bluetooth is there</p><p>In the realm of IoT, communication technologies are foundational to device operation and functionality. Securing these technologies is paramount due to their ubiquitous use in environments ranging from smart homes to industrial systems. Below, we explore key wireless communication standards used in IoT, focusing on their security aspects and where to find resources for deeper learning.</p><ol><li><strong>Low-Energy Devices (BLE — Bluetooth Low Energy):</strong></li></ol><ul><li>Overview: BLE is designed for low-power devices that require periodic or sporadic communication with minimal data exchange.</li><li>Security Concerns: Vulnerabilities often stem from improper implementation, such as weak pairing mechanisms and encryption protocols.</li><li>Learning Resource: On the IoTSRG GitHub repository, search for Bluetooth data to find information on BLE Intro and both software and hardware tools for penetration testing. This resource is invaluable for understanding BLE security and how to test for vulnerabilities.</li><li><a href="https://github.com/V33RU/IoTSecurity101#BLE-Intro-and-SW-HW-Tools-to-pentest">BLE Intro and Tools</a></li></ul><p><strong>2. Classic Bluetooth:</strong></p><ul><li>Overview: Classic Bluetooth provides higher data rates and is typically used in devices requiring continuous connectivity.</li><li>Security Concerns: Issues can include eavesdropping, man-in-the-middle attacks, and bluejacking, especially if devices are using outdated versions of Bluetooth.</li><li>Learning Resource: The same IoTSRG GitHub link above offers insights into Classic Bluetooth’s vulnerabilities and how to secure devices against potential threats.</li></ul><p><strong>Zigbee and Z-Wave:</strong></p><ul><li>Overview: Both are popular in smart home devices for their low-power operation and mesh networking capabilities, enabling devices to communicate through other devices to extend range.</li><li>Security Concerns: Vulnerabilities may arise from inadequate encryption, device spoofing, or replay attacks.</li><li>Learning Resource: IoTSecurity101 provides a starting point for understanding these technologies’ security landscape. While not as widely used as Bluetooth, knowledge in Zigbee and Z-Wave security is crucial for a comprehensive IoT security skill set.</li><li><a href="https://github.com/V33RU/IoTSecurity101">IoTSecurity101 Resources</a></li></ul><p><strong>LoRaWAN:</strong></p><ul><li>Overview: LoRaWAN is used for wide-area network applications, offering long-range, low-power communication for IoT devices.</li><li>Security Concerns: Key areas include packet interception, encryption weaknesses, and network layer attacks.</li><li>Learning Resource: Though specifics on LoRaWAN might not be extensively covered in the provided GitHub repository, it serves as a jumping-off point for exploring other dedicated resources and communities focused on LoRaWAN security.</li></ul><h4><strong>5. Firmware reversing:</strong></h4><p>Firmware is the foundational software embedded within an IoT device, controlling its behavior and functionality. Having a deep understanding of firmware architectures and their operational principles is crucial for anyone involved in IoT security. Here’s a structured approach to building, analyzing, and securing firmware:</p><p><strong>Building and Understanding Firmware:</strong></p><ol><li>Use Buildroot: A tool that simplifies the process of building a complete Linux system for an embedded system, allowing you to understand and customize the firmware development process.</li><li>Firmware Filesystems and Security: Learn about different filesystems used in firmware, and the importance of encryption or signing mechanisms. Grasp the concept of the root of trust, which ensures the integrity and authenticity of the firmware from the ground up.</li></ol><p><strong>Static Analysis of Firmware:</strong></p><ol><li>Extracting Firmware: The first step involves obtaining the firmware image from the device or manufacturer’s website.</li><li>Automated Analysis: Use automated scripts or tools such as Binwalk or Firmware Analysis Toolkit (FAT) to dissect the firmware image, identifying its structure and components.</li><li>Identifying Sensitive Information: Search for embedded sensitive information like passwords, certificates, cryptographic keys, OTA update mechanisms, and server communication URLs, which could be leveraged by an attacker.</li></ol><p><strong>Dynamic Analysis of Firmware:</strong></p><ol><li>Emulation: Tools like QEMU and the Qiling Framework allow for the emulation of firmware, providing a sandbox environment to run and interact with the firmware without needing physical hardware.</li><li>Executing and Reversing Binaries: With the firmware running in an emulator, execute its binaries and apply reverse engineering techniques to understand its functionality and uncover vulnerabilities.</li><li>Breaking Encryption and Signatures: Analyze and, if possible, break encryption mechanisms or digital signatures to understand the security measures in place and how they might be bypassed.</li><li>Overflow Bugs: Specifically focus on identifying buffer overflow vulnerabilities, which are common in embedded systems and can lead to arbitrary code execution.</li></ol><h4><strong>6. Hardware hacking:</strong></h4><p>One way the answer is to read this book: <a href="https://nostarch.com/xboxfree">https://nostarch.com/xboxfree</a></p><p>(Or)</p><p>IoT-Security101-Kit — Roughly costing 8000+ INR : <a href="https://github.com/IoT-PTv/IoT-Security101-Kit-Roughly-costing-110USD">https://github.com/IoT-PTv/IoT-Security101-Kit-Roughly-costing-110USD</a></p><p>Resources: <a href="https://github.com/V33RU/IoTSecurity101#IoT-hardware-Overview-and-Hacking">https://github.com/V33RU/IoTSecurity101#IoT-hardware-Overview-and-Hacking</a></p><p>IoT-Security/Development-Lab-Setup : <a href="https://github.com/IoT-PTv/IoT-Lab-Setup">https://github.com/IoT-PTv/IoT-Lab-Setup</a></p><p>OS: A new pentesting virtual environment for IoT Devices — IoT-PT OSv1 : <a href="https://github.com/IoT-PTv/IoT-PT">https://github.com/IoT-PTv/IoT-PT</a></p><h3><strong>Type 2 : Security Experts</strong></h3><p>Professionals in the cybersecurity domain, with expertise in areas like web, network, hardware, mobile, forensics, and malware analysis, can smoothly transition their skills to IoT penetration testing. The foundational security principles remain consistent; the key is to adapt these principles to the unique characteristics of IoT devices. Here are some targeted hints and guidance for professionals looking to pivot or expand their expertise into the IoT security space.</p><p><strong>1. SoC/Malware Analysts:</strong></p><ul><li>Focus Area: Explore IoT botnets, exemplified by the Mirai botnet. Analyzing its source code can offer insights into the attack surfaces specific to IoT devices and the operational tactics of IoT-targeted malware.</li><li>Mirai Source Code: <a href="https://github.com/jgamblin/Mirai-Source-Code">GitHub — Mirai Source Code</a></li><li>Ransomware Evolution: Study the development of ransomware in IoT contexts, such as R4IoT, to understand how these threats adapt and evolve.</li><li>Resource: <a href="https://industrialcyber.co/zero-trust/as-ransomware-evolves-r4iot-approach-could-further-weaken-cybersecurity-posture-across-it-iot-ot-environments/">R4IoT Analysis</a></li></ul><p><strong>2. Pentesters (Web/Network/Mobile/Others):</strong></p><ul><li>Adaptation: Shift focus from traditional application testing frameworks (e.g., OWASP Top 10) to device-centric testing. IoT devices, often running on Linux-based systems, require understanding the device’s functionality and features from a security perspective.</li><li>Testing Focus: Prioritize finding command injection vulnerabilities, which are more prevalent in IoT devices, over common web vulnerabilities like SQL injection.</li></ul><p><strong>3. Reverse Engineers and Exploit Developers:</strong></p><ul><li>Skill Development: No specific guidance but a continuous learning curve in:</li><li>Architecture Reversing: Focus on ARM/MIPS architectures through resources like Azeria Labs for a better understanding of IoT device hardware.</li><li>Service Binary Analysis: Analyze and emulate device service binaries for dynamic testing.</li><li>Bug Hunting: Look for crash-inducing bugs, buffer overflows, and exploit unsafe functions within device firmware.</li><li>Tools: Utilize reverse engineering and fuzzing tools like radare2, Ghidra, ret2dec, AFL-fuzz, and Boofuzz.</li></ul><p><strong>4. Embedded Systems Professionals:</strong></p><ul><li>Approach: Understand Linux security hardening techniques. The knowledge of embedded systems, combined with an understanding of security practices, can be directly applied to IoT devices, allowing for a seamless transition into IoT security.</li></ul><p><strong>5. Hardware Security:</strong></p><p>Hardware security is a critical aspect of IoT security that addresses vulnerabilities at the physical device level. This domain involves understanding and exploiting weaknesses in the hardware components and interfaces of IoT devices. Here, we outline core attacks in hardware security that IoT penetration testers should be proficient in to ensure a comprehensive security assessment.</p><p><strong>Side-Channel Attacks:</strong></p><ul><li>Description: Exploits that extract sensitive information from physical implementations of a system, rather than weaknesses in the implemented algorithms themselves.</li><li>Common Types:</li><li>Power Analysis Attacks: Derive cryptographic keys by analyzing power consumption patterns.</li><li>Electromagnetic Attacks: Utilize electromagnetic emissions to extract data or infer cryptographic keys.</li><li>Timing Attacks: Analyze the time taken to execute cryptographic algorithms to find vulnerabilities.</li></ul><p><strong>Fault Injection Attacks:</strong></p><ul><li>Description: Intentionally causing devices to malfunction to bypass security controls or extract sensitive information.</li><li>Techniques:</li><li>Voltage Glitching: Briefly altering the device’s power supply to induce errors in processor execution.</li><li>Clock Glitching: Manipulating the clock signal to disrupt the timing of instructions and cause errors.</li><li>Laser Fault Injection: Using focused laser beams to induce transient faults in specific parts of the silicon.</li></ul><p><strong>Physical Tampering and Reverse Engineering:</strong></p><ul><li>Description: Directly manipulating the device hardware to bypass security measures or to understand the device’s operation for further exploitation.</li><li>Approaches:</li><li>Microprobing: Accessing the chip’s surface directly with microscopic needles to read or manipulate data.</li><li>Decapsulation: Chemically removing the chip’s packaging to access the die for probing or fault injection.</li><li>Firmware Extraction: Physically accessing memory chips to dump firmware data for reverse engineering.</li></ul><p><strong>Hardware Trojans:</strong></p><p>Description: Malicious modifications to the hardware components that can create backdoors or compromise the device’s integrity.</p><ul><li>Identification: Requires thorough inspection and testing of the hardware for any unauthorized modifications or suspicious components.</li></ul><p><strong>JTAG and Debug Port Exploitation:</strong></p><ul><li>Description: Utilizing debug interfaces like JTAG or UART ports, often left accessible on devices, to gain unauthorized access to the firmware or hardware configuration.</li><li>Mitigation: Secure or disable debug ports in production devices and use access controls.</li></ul><p><strong>Note: there are many things that haven’t mention because it all depends on self-learning. When there is any doubt about the IoT Stuff where you have not found after google, you can reach out to the our most active groups : </strong><a href="https://github.com/V33RU/IoTSecurity101#Chat-groups-for-IoT-Security"><strong>https://github.com/V33RU/IoTSecurity101#Chat-groups-for-IoT-Security</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b7b08348eeb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>