Technology

Related News

French Police Raid X Paris Office, Summon Musk Over Grok Deepfakes

  • Jeffrey Burt
  • Published date: 2026-02-03 00:00:00

None

<p>The accelerating month-long fury over xAI’s Grok chatbot feature that lets X users alter any images posted to the social network – a feature that has led to millions of nonconsensual and sexualized images of women and children – escalated this week when French authorities searched X’s offices in Paris and summoned Elon Musk to appear for questioning.</p><p>At the same time, the UK’s Information Commissioner’s Office (ICO) <a href="https://ico.org.uk/about-the-ico/media-centre/news-and-blogs/2026/02/ico-announces-investigation-into-grok/" target="_blank" rel="noopener">announced</a> that it’s opened formal investigations into X and xAI due to the new Grok tool and the sexualized images and videos that it is generating.</p><p>In a statement, William Malcolm, the ICO’s executive director of regulatory risk and innovation, said “the reports about Grok raise deeply troubling questions about how people’s personal data has been used to generate intimate or sexualised images without their knowledge or consent, and whether the necessary safeguards were put in place to prevent this. Losing control of personal data in this way can cause immediate and significant harm. This is particularly the case where children are involved.”</p><p>The feature introduced to Grok in late December 2025 allows X users to edit posted images immediately and without the consent of the people who initially post them. Soon after, such sexualized and intimate deepfake images of people – particularly women and minors – began appearing on X, touching off a far-reaching firestorm of criticism that included government officials and regulatory agencies, advocacy groups, and individuals.</p><p>In mid-January, Musk announced the controversial feature would be available only to paying subscribers on X and that guardrails, such as changing Grok responses to some prompts, were implemented, with Musk saying it would stem the posting of the controversial images. However, the guardrails are <a href="https://www.theverge.com/news/861894/grok-still-undressing-in-uk" target="_blank" rel="noopener">easily bypassed</a>, according to numerous reports, and while it may have slowed the number of such images, it didn’t eliminate them.</p><h3>France Takes Action</h3><p>Now European governments are taking next steps. <a href="https://www.nbcnews.com/world/europe/france-paris-prosecutors-x-office-elon-musk-sexual-deepfakes-holocaust-rcna257202" target="_blank" rel="noopener">According to NBC News</a>, the search of X’s Paris office was conducted by a prosecutor’s cybercrime unit, with both the distribution of the sexualized deepfakes and the Holocaust denial content on X as its targets. The prosecutor’s office said it was investigating a range of criminal offenses related to child pornography, violations of personal rights, and the denial of “crimes against humanity.”</p><p>The voluntary summons to come to France the week of April 20 to be questioned were sent out to Musk and former X CEO Linda Yaccarino. According to NBC News, neither has commented on the office raid or summons, though X executives last year said investigations by French authorities in regard to algorithm manipulation on the social media platform were <a href="https://x.com/GlobalAffairs/status/1947213316331282504" target="_blank" rel="noopener">part of a “political agenda”</a> to “restrict free speech.”</p><h3>Fierce Global Response</h3><p>The mounting global response to Grok, X, and Musk over the deepfake controversy suggests otherwise.  The European Union – which already has had an unrelated investigation into X since 2023 – in January <a href="https://ec.europa.eu/commission/presscorner/detail/en/ip_26_203" target="_blank" rel="noopener">launched its own investigation</a> against the social media platform over the deepfake feature, with the probe coming under the EU’s Digital Services Act (DSA).</p><p>“Sexual deepfakes of women and children are a violent, unacceptable form of degradation,” Henna Virkkunen, executive vice president for tech sovereignty, security, and democracy, said in a statement. “With this investigation, we will determine whether X has met its legal obligations under the DSA, or whether it treated rights of European citizens – including those of women and children – as collateral damage of its service.”</p><p>Last month, the U.S. Senate <a href="https://19thnews.org/2026/01/senate-defiance-act-nonconsensual-images-deepfakes/" target="_blank" rel="noopener">passed the DEFIANCE Act</a> that would allow victims to sue the creators of nonconsensual sexually explicit deepfakes.</p><h3>Taking to the Courts</h3><p>There have been lawsuits filed, including one by the <a href="https://www.cnn.com/2026/01/15/business/elon-musk-son-mom-sues-grok-images" target="_blank" rel="noopener">mother of one of his children</a>, who said the chatbot generated sexually suggestive images of her without her consent. A <a href="https://storage.courtlistener.com/recap/gov.uscourts.cand.463184/gov.uscourts.cand.463184.1.0.pdf" target="_blank" rel="noopener">class action lawsuit</a> was in federal court in California last month.</p><p>“AI companies like xAI are familiar with these dangers to women and girls that their technology enables,” the lawsuit reads. “Most companies have taken action to implement guardrails to prevent their technology from being used to create sexual and revealing deepfakes of nonconsenting women. xAI, however, has chosen instead to capitalize on the internet’s seemingly insatiable appetite for humiliating non-consensual sexual images.”</p><p>The lawsuit adds that Grok not only doesn’t conform with industry standards, it is touting the capability, including with its “spicy” model used to produce the nonconsensual deepfakes.</p><h3>Organizations are Adding Pressure</h3><p>Advocacy groups have been outspoken about the deepfakes, with the Center for Countering Digital Hate writing on January 22 that an analysis of a sample of images indicates that the Grok tool has been used to <a href="https://counterhate.com/research/grok-floods-x-with-sexualized-images/" target="_blank" rel="noopener">generate about 3 million sexualized images</a>, including 23,000 “that appear to depict children.”</p><p>Some also are pushing tech companies that support the Grok chatbot and X – including those whose infrastructure they run on – to act. In letters to <a href="https://weareultraviolet.org/wp-content/uploads/2026/01/FINAL-Organizational-Sign-On-Letter_-Demand-Apple-Google-Remove-Grok-from-App-Stores-3.pdf" target="_blank" rel="noopener">Google’s Sundar Pichai</a> and <a href="https://weareultraviolet.org/wp-content/uploads/2026/01/FINAL-Organizational-Sign-On-Letter_-Demand-Apple-Google-Remove-Grok-from-App-Stores-1.pdf" target="_blank" rel="noopener">Apple’s Tim Cook</a> on January 14, 28 organizations urged the CEOs to ban Grok from their online stores, saying the “content that is both a criminal offense and in direct violation of” the app stores’ guidelines.</p><p>Google and Apple not only are enabling such offenses, but profiting from it, they wrote.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/02/french-police-raid-x-paris-office-summons-musk-over-grok-deepfakes/" data-a2a-title="French Police Raid X Paris Office, Summon Musk Over Grok Deepfakes"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Ffrench-police-raid-x-paris-office-summons-musk-over-grok-deepfakes%2F&amp;linkname=French%20Police%20Raid%20X%20Paris%20Office%2C%20Summon%20Musk%20Over%20Grok%20Deepfakes" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Ffrench-police-raid-x-paris-office-summons-musk-over-grok-deepfakes%2F&amp;linkname=French%20Police%20Raid%20X%20Paris%20Office%2C%20Summon%20Musk%20Over%20Grok%20Deepfakes" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Ffrench-police-raid-x-paris-office-summons-musk-over-grok-deepfakes%2F&amp;linkname=French%20Police%20Raid%20X%20Paris%20Office%2C%20Summon%20Musk%20Over%20Grok%20Deepfakes" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Ffrench-police-raid-x-paris-office-summons-musk-over-grok-deepfakes%2F&amp;linkname=French%20Police%20Raid%20X%20Paris%20Office%2C%20Summon%20Musk%20Over%20Grok%20Deepfakes" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Ffrench-police-raid-x-paris-office-summons-musk-over-grok-deepfakes%2F&amp;linkname=French%20Police%20Raid%20X%20Paris%20Office%2C%20Summon%20Musk%20Over%20Grok%20Deepfakes" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div>

Using AI Agents to Separate Real Risk From Vulnerability Noise

  • Alan Shimel
  • Published date: 2026-02-03 00:00:00

None

<div style="padding: 56.25% 0 0 0; position: relative;"><iframe style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;" title="AI Agents That Eliminate 90% of Security Vulnerabilities?" src="https://player.vimeo.com/video/1157594771?badge=0&amp;autopause=0&amp;player_id=0&amp;app_id=58479" frameborder="0"></iframe></div><p><script src="https://player.vimeo.com/api/player.js"></script></p><p data-start="195" data-end="664">Snir Ben Shimol, CEO and co-founder of Zest Security, talks about why vulnerability and exposure management has become one of the most stubborn problems in security operations. Ben Shimol argues that the numbers are getting worse, not better. Exploitation has become the top initial access path, new CVEs keep piling up and teams are still drowning in triage and remediation work that remains largely manual.</p><p data-start="666" data-end="1388">Zest’s answer is what it calls AI Sweeper Agents. The concept is straightforward: instead of handing security teams an even larger list of findings, use AI agents to determine which vulnerabilities in a specific environment are actually reachable and exploitable. Ben Shimol describes the agents as mimicking the work of a senior security engineer at scale. They ingest vulnerability details, identify the real requirements for exploitation and compare those requirements to evidence in the customer’s environment, such as network placement, permissions and configuration. If key conditions are missing, the vulnerability is swept out of the backlog. If the conditions are met, it stays for prioritization and remediation.</p><p data-start="1390" data-end="1747">Ben Shimol says this approach can eliminate the bulk of findings that teams feel compelled to chase, claiming Zest has swept more than 11 million vulnerabilities across customers. The result, he says, is waking up to a backlog that is dramatically smaller, leaving teams able to focus on the issues that actually matter rather than spending cycles on noise.</p><p data-start="1749" data-end="2089">The conversation also touches on a familiar friction point: audits and compliance. Ben Shimol notes that highly regulated customers initially faced pushback when large portions of a backlog disappeared, but argues that the agents provide evidence-based reasoning that auditors can review, turning subjective arguments into documented facts.</p><p data-start="2091" data-end="2288" data-is-last-node="" data-is-only-node="">For security leaders buried under vulnerability volume, this is a look at how agentic AI is being positioned to reduce manual triage and help teams focus remediation where it reduces risk.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/02/using-ai-agents-to-separate-real-risk-from-vulnerability-noise/" data-a2a-title="Using AI Agents to Separate Real Risk From Vulnerability Noise"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fusing-ai-agents-to-separate-real-risk-from-vulnerability-noise%2F&amp;linkname=Using%20AI%20Agents%20to%20Separate%20Real%20Risk%20From%20Vulnerability%20Noise" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fusing-ai-agents-to-separate-real-risk-from-vulnerability-noise%2F&amp;linkname=Using%20AI%20Agents%20to%20Separate%20Real%20Risk%20From%20Vulnerability%20Noise" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fusing-ai-agents-to-separate-real-risk-from-vulnerability-noise%2F&amp;linkname=Using%20AI%20Agents%20to%20Separate%20Real%20Risk%20From%20Vulnerability%20Noise" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fusing-ai-agents-to-separate-real-risk-from-vulnerability-noise%2F&amp;linkname=Using%20AI%20Agents%20to%20Separate%20Real%20Risk%20From%20Vulnerability%20Noise" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fusing-ai-agents-to-separate-real-risk-from-vulnerability-noise%2F&amp;linkname=Using%20AI%20Agents%20to%20Separate%20Real%20Risk%20From%20Vulnerability%20Noise" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div>

95% of AI Projects Are Unproductive and Not Breach Ready

  • None
  • Published date: 2026-02-03 00:00:00

None

<p>Like me, this news probably shocked almost all AI enthusiasts. The GenAI gold rush has apparently turned into a reckoning. And the fallout may be the next cyberattack.</p><p>A <a href="https://mlq.ai/media/quarterly_decks/v0.1_State_of_AI_in_Business_2025_Report.pdf" rel="noreferrer noopener nofollow">recent MIT report</a> reveals an unexpected twist in the AI market, making waves across boardrooms and leadership circles. The report, based on analysis of over 300 AI deployments, interviews with 52 organizations, and surveys from 153 senior leaders, reveals an uncomfortable truth.</p><p><strong>Despite $30–40 billion in enterprise investment in GenAI, up to 95% of organizations are getting zero return. No, that is not a typo. Ninety-five percent.</strong></p><p>The findings are sobering and, frankly, confirm what many of us in cybersecurity and digital transformation have been saying for years. Rushing the capability doesn’t guarantee you’ll capture the value. While large enterprises are running the most AI pilots, investing the most resources, and assembling the biggest teams, they’re reporting the lowest pilot-to-scale conversion rates. By contrast, mid-market companies moved more decisively, with top performers reporting average timelines of just 90 days from pilot to full implementation.</p><p>The malaise seems similar to the cybersecurity industry.</p><p>While the cybersecurity market approaches half a trillion dollars in 2025, attacks continue to rise rather than decline. While AI budgets explode, business impact remains elusive. And I’m convinced the real issue is the same in both domains.</p><p class="p-5 has-background" style="background-color:#e0f8f4"><strong>Are You Breach Ready?</strong> Uncover hidden lateral attack risks in just 5 days. <a href="https://colortokens.com/breach-readiness-assessment/">Get a free Breach Readiness and Impact Assessment</a> with a visual roadmap of what to fix first.</p><p><strong>An overreliance on technology to solve problems without investing in the foundational capabilities required to manage and adapt to it.</strong></p><p>While the world debates how to improve value and make AI projects more successful, I’ve been thinking about the breach exposure risks posed by abandoned AI projects.</p><p>It is no secret that increased digitalization and <em>adoption</em> of artificial intelligence have exponentially expanded the attack surface that threat actors can exploit. And fewer than 1% of organizations have adopted <a href="https://colortokens.com/microsegmentation/">microsegmentation</a> capabilities that can anticipate, withstand, and evolve from cyberattacks.</p><p>This means most organizations remain grossly unprepared and far from <a href="https://colortokens.com/breach-ready/">breach ready</a>.</p><p>The MIT report mentions that <em>“most organizations fall on the wrong side of the GenAI Divide: adoption is high, but disruption is low. Seven of nine sectors show little structural change. Enterprises are piloting GenAI tools, but very few reach deployment. Generic tools like ChatGPT are widely used, but custom solutions stall due to integration complexity and a lack of fit with existing workflows.”</em></p><p class="p-5 has-background" style="background-color:#e0f8f4"><a href="https://colortokens.com/blogs/ai-in-cybersecurity-microsegmentation/"><strong>Also Read:</strong></a> “Would You Like to Play a Game?” The AI-Accelerated Cyber Battlefield is Here Now</p><p>AI systems are not the same as traditional IT systems. They are data-hungry, often requiring access to multiple sensitive datasets; highly interconnected, spanning clouds, SaaS platforms, APIs, and internal systems; and continuously evolving, with changing models, features, and dependencies.</p><p>This poses even larger problems in Digital Industrial Systems (OT/ICS/CPS/IIoT/IoMD). These environments often rely on older, disparate machinery, making it difficult to aggregate data and leading to poor training sets. Because AI systems often do not understand the “common sense” or real-world physical constraints of a factory floor, they can be inaccurate, generate excessive false alerts, and quickly lose operator trust. More importantly, Digital Industrial Systems prioritize safety and reliability, and “up to 95%” accuracy from an AI system is simply unacceptable.</p><p>Despite this, most AI projects were architected using legacy security assumptions: trusted internal networks, broad east-west access, and perimeter-centric defenses. When business confidence waned, projects were paused or abandoned. However, pilots whose anomalies were initially tolerated in the name of speed quietly became persistent deployments, and temporary exceptions hardened into architecture.</p><p class="p-5 has-background" style="background-color:#e0f8f4"><a href="https://colortokens.com/report/forrester-wave-microsegmentation/"><strong>Access Forrester Wave<img decoding="async" src="https://s.w.org/images/core/emoji/17.0.2/72x72/2122.png" alt="™" class="wp-smiley" style="height: 1em; max-height: 1em;"> Report</strong></a> | Discover why ColorTokens was rated ‘Superior’ in OT, IoT, and Healthcare Security.</p><p>Abandoned AI projects and pilots also create unforeseen and often undetectable vulnerabilities. These can be exploited through AI-driven attacks that evade traditional cybersecurity tools, including prompt injection (via website content or emails), training data poisoning, subtle adversarial inputs (such as imperceptible noise added to data), model inversion and extraction, or even LLM jailbreaking to bypass safety controls.</p><p>From a breach-readiness standpoint, abandoned AI systems are more dangerous than actively managed ones — not only because they leave behind an “uncontained” blast radius due to AI workloads being placed in flat network segments with unrestricted lateral connectivity. Without microsegmentation, a compromised AI workload is not a single isolated incident. It becomes an entry point into the enterprise.</p><p><strong>Nonproductive or abandoned AI pilots do not reduce this blast radius; they freeze it in place.</strong></p><p>AI pipelines rely on service accounts, tokens, and API keys to function autonomously. When projects stop, these identities persist. Over time, they become invisible, unrotated, and highly attractive to attackers seeking low-noise access. Training datasets, feature stores, embeddings, and intermediate artifacts often contain regulated, proprietary, or mission-critical data. These artifacts are rarely classified, encrypted, or lifecycle-managed. Abandoned systems leave this data exposed and undetected.</p><p>However, the biggest risks they create are Shadow AI and supply chain attack exposure. Many AI initiatives integrate external model providers or data sources through weakly governed interfaces. Once projects stall, vendor oversight erodes, creating latent supply chain risk that is difficult to detect and even harder to explain after a breach.</p><p class="p-5 has-background" style="background-color:#e0f8f4"><a href="https://colortokens.com/blogs/microsegmentation-breach-readiness-2026/"><strong>Also Read:</strong></a> Containing the Inevitable: What Cyber Leaders Must Prepare for in 2026</p><p><strong>We need to act now.</strong></p><p>If my point of view sounds alarming, consider recent <a href="https://red.anthropic.com/2026/cyber-toolkits-update/" rel="noreferrer noopener nofollow">Anthropic red-teaming research</a>. In a recent evaluation of AI models’ cyber capabilities, current Claude models succeeded at multistage attacks on networks with dozens of hosts using only standard open-source tools, rather than the custom tooling required by previous generations. This demonstrates how quickly barriers to AI-driven cyber operations are falling and reinforces the importance of fundamentals like prompt patching of known vulnerabilities.</p><p>The bottom line: everyone needs to step up. Improve governance. Ensure all abandoned or unproductive AI projects are formally shut down and decommissioned. Most AI initiatives were designed to prevent breaches, not to survive them. The implicit assumption was that if controls were added later, risk would be manageable. In reality, AI systems amplify risk because they sit at the intersection of data, automation, and trust.</p><p>Breach readiness demands a different mindset: assume compromise, design for containment, and minimize blast radius by default. If you haven’t already, invest in foundational microsegmentation and run AI projects in isolated microsegments that are disconnected from production systems until least-privileged access is explicitly granted.</p><p><em>If AI expansion is increasing your exposure, <a href="https://colortokens.com/contact-us/">let’s talk</a> about containing risk and building true breach readiness.</em></p><p>The post <a href="https://colortokens.com/blogs/breach-readiness-ai-attack-surface-microsegmentation/">95% of AI Projects Are Unproductive and Not Breach Ready</a> appeared first on <a href="https://colortokens.com/">ColorTokens</a>.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/02/95-of-ai-projects-are-unproductive-and-not-breach-ready/" data-a2a-title="95% of AI Projects Are Unproductive and Not Breach Ready"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2F95-of-ai-projects-are-unproductive-and-not-breach-ready%2F&amp;linkname=95%25%20of%20AI%20Projects%20Are%20Unproductive%20and%20Not%20Breach%20Ready" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2F95-of-ai-projects-are-unproductive-and-not-breach-ready%2F&amp;linkname=95%25%20of%20AI%20Projects%20Are%20Unproductive%20and%20Not%20Breach%20Ready" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2F95-of-ai-projects-are-unproductive-and-not-breach-ready%2F&amp;linkname=95%25%20of%20AI%20Projects%20Are%20Unproductive%20and%20Not%20Breach%20Ready" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2F95-of-ai-projects-are-unproductive-and-not-breach-ready%2F&amp;linkname=95%25%20of%20AI%20Projects%20Are%20Unproductive%20and%20Not%20Breach%20Ready" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2F95-of-ai-projects-are-unproductive-and-not-breach-ready%2F&amp;linkname=95%25%20of%20AI%20Projects%20Are%20Unproductive%20and%20Not%20Breach%20Ready" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://colortokens.com/">ColorTokens</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Agnidipta Sarkar">Agnidipta Sarkar</a>. Read the original post at: <a href="https://colortokens.com/blogs/breach-readiness-ai-attack-surface-microsegmentation/">https://colortokens.com/blogs/breach-readiness-ai-attack-surface-microsegmentation/</a> </p>

Jan Recap: New AWS Privileged Permissions and Services

  • None
  • Published date: 2026-02-03 00:00:00

None

<p>As January 2026 comes to a close, Sonrai’s latest review of newly released AWS permissions highlights a sharp expansion of privilege concentrated in networking, traffic control, and collaboration services. This month’s updates focus heavily on AWS Network Firewall, Route 53 Global Resolver, EC2 networking controls, and cross-account data collaboration, introducing new ways to reroute traffic, weaken filtering, expand network reach, and expose shared data.</p><p>Taken together, these permissions reinforce a critical cloud security reality: privilege increasingly lives in routing decisions and configuration layers, not just identity policies. From bypassing DNS and proxy-based protections to expanding access across VPCs and external accounts, each change subtly reshapes trust boundaries and increases the blast radius of misuse. Security teams must stay vigilant, as these non-obvious privileges continue to redefine the cloud attack surface through the very controls meant to secure it.</p><h2 class="wp-block-heading">Existing Services with New Privileged Permissions</h2><h3 class="wp-block-heading">AWS Clean Rooms</h3><p><strong>Service Type: Data and Analytics</strong></p><h4 class="wp-block-heading">Permission: cleanrooms:UpdateCollaborationChangeRequest</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to update a change request in a collaboration</li> <li><strong>Mitre Tactic:</strong> Exfiltration</li> <li><strong>Why it’s privileged: </strong>Allows approving or modifying change requests that expand what external AWS accounts can do within a collaboration, potentially granting access to additional data through analysis templates.</li> </ul><h3 class="wp-block-heading">AWS Network Firewall</h3><p><strong>Service Type: Security Services</strong></p><h4 class="wp-block-heading">Permission: network-firewall:UpdateProxyRule</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to update an existing proxy rule on a proxy rule group</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows modification of proxy rules designed to block malicious or unauthorized traffic, potentially permitting traffic that would otherwise be filtered.</li> </ul><h4 class="wp-block-heading">Permission: network-firewall:AttachRuleGroupsToProxyConfiguration</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to attach proxy rule groups to a proxy configuration</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows attaching rule groups with broad allow rules early in a proxy configuration, potentially permitting malicious traffic to bypass filtering.</li> </ul><h4 class="wp-block-heading">Permission: network-firewall:UpdateProxyConfiguration</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to modify a proxy configuration</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows changing proxy behavior from default-deny to default-allow, significantly weakening network traffic filtering.</li> </ul><h4 class="wp-block-heading">Permission: network-firewall:UpdateProxyRuleGroupPriorities</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to modify rule group priorities on a proxy configuration</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows reordering rule groups so broad allow rules are evaluated first, enabling traffic to bypass filtering and permitting otherwise blocked connections.</li> </ul><h4 class="wp-block-heading">Permission: network-firewall:CreateProxyRules</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to add proxy rules to a proxy rule group</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows inserting explicit allow or deny rules ahead of existing filters, potentially preempting protections and permitting unauthorized traffic.</li> </ul><h4 class="wp-block-heading">Permission: network-firewall:DetachRuleGroupsFromProxyConfiguration</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to detach proxy rule group from a proxy configuration</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows removal of rule groups designed to filter malicious or unauthorized traffic, weakening proxy-based network protections.</li> </ul><h4 class="wp-block-heading">Permission: network-firewall:DeleteProxy</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to delete a proxy</li> <li><strong>Mitre Tactic:</strong> Impact</li> <li><strong>Why it’s privileged: </strong>Allows deletion of a network proxy, disrupting connectivity for resources that rely on it and causing traffic to fail.</li> </ul><h4 class="wp-block-heading">Permission: network-firewall:UpdateProxyRulePriorities</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to update proxy rule priorities within a proxy rule group</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows reordering proxy rules so broad allow rules are evaluated first, enabling traffic to bypass existing filtering controls.</li> </ul><h4 class="wp-block-heading">Permission: network-firewall:DeleteProxyRules</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to remove proxy rules from a proxy rule group</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows removal of proxy rules designed to filter malicious or unauthorized traffic, weakening network security controls.</li> </ul><h4 class="wp-block-heading">Permission: network-firewall:UpdateProxy</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to modify a proxy</li> <li><strong>Mitre Tactic:</strong> Impact</li> <li><strong>Why it’s privileged: </strong>Allows removing or altering proxy listeners, causing network traffic to fail and preventing clients from establishing connections.</li> </ul><h3 class="wp-block-heading">Amazon EC2</h3><p><strong>Service Type: Compute Services</strong></p><h4 class="wp-block-heading">Permission: ec2:ModifyVpcEncryptionControl</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to modify an existing VPC Encryption Control</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows weakening or disabling enforcement of VPC traffic encryption by switching controls to monitor mode, reducing protection of network traffic and potentially disrupting encryption guarantees.</li> </ul><h4 class="wp-block-heading">Permission: ec2:ModifyIpamPrefixListResolver</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to modify an IPAM prefix list resolver</li> <li><strong>Mitre Tactic:</strong> Lateral Movement</li> <li><strong>Why it’s privileged: </strong>Allows expanding the CIDR ranges resolved by a prefix list, potentially broadening network access to sensitive resources protected by security group rules.</li> </ul><h4 class="wp-block-heading">Permission: ec2:DeleteVpcEncryptionControl</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to delete a VPC Encryption Control</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Removes controls that enforce VPC traffic encryption, eliminating safeguards that protect network traffic confidentiality.</li> </ul><h4 class="wp-block-heading">Permission: ec2:CreateIpamPrefixListResolverTarget</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to create an IPAM prefix list resolver target that links a resolver to a managed prefix list</li> <li><strong>Mitre Tactic:</strong> Lateral Movement</li> <li><strong>Why it’s privileged: </strong>Allows forcing a prefix list to sync with an empty or permissive resolver, effectively wiping enforced network restrictions and expanding communication between resources or VPCs.</li> </ul><h3 class="wp-block-heading">AWS CloudWatch Logs</h3><p><strong>Service Type: Observability and Monitoring</strong></p><h4 class="wp-block-heading">Permission: logs:CreateImportTask</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to start an asynchronous process to import data from a CloudTrail Lake event data store into a managed log group in CloudWatch </li> <li><strong>Mitre Tactic:</strong> Collection</li> <li><strong>Why it’s privileged: </strong>Allows importing CloudTrail data into CloudWatch using a passed role, enabling collection of log data that the caller may not otherwise have direct access to.</li> </ul><h3 class="wp-block-heading">Amazon API Gateway</h3><p><strong>Service Type: Compute Services</strong></p><h4 class="wp-block-heading">Permission: apigateway:UpdatePortal</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to update a portal</li> <li><strong>Mitre Tactic:</strong> Persistence</li> <li><strong>Why it’s privileged: </strong>Allows disabling authorization controls on the portal, exposing internal API documentation to the public and enabling persistent unauthorized access.</li> </ul><h4 class="wp-block-heading">Permission: apigateway:PutPortalProductSharingPolicy</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to put a portal product sharing policy</li> <li><strong>Mitre Tactic:</strong> Persistence</li> <li><strong>Why it’s privileged: </strong>Allows making an API Gateway portal accessible from another AWS account, enabling persistent external access to potentially internal API documentation.</li> </ul><h3 class="wp-block-heading">Amazon Connect</h3><p><strong>Service Type: Customer Engagement</strong></p><h4 class="wp-block-heading">Permission: connect:DisassociateEmailAddressAlias</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to disassociate an alias from an email address resource in an Amazon Connect instance</li> <li><strong>Mitre Tactic:</strong> Impact</li> <li><strong>Why it’s privileged: </strong>Allows removal of email address aliases used for routing or identification, disrupting email-based contact handling and potentially impacting business communications or workflows.</li> </ul><h4 class="wp-block-heading">Permission: connect:AssociateEmailAddressAlias</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to associate an alias with an email address resource in an Amazon Connect instance</li> <li><strong>Mitre Tactic:</strong> Exfiltration</li> <li><strong>Why it’s privileged: </strong>Allows routing or duplicating email communications through additional aliases, potentially enabling interception or unauthorized exposure of sensitive customer messages.</li> </ul><h3 class="wp-block-heading">Amazon CloudFront</h3><p><strong>Service Type: Networking and Content Delivery</strong></p><h4 class="wp-block-heading">Permission: cloudfront:DeleteResourcePolicy</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to delete a resource’s policy document</li> <li><strong>Mitre Tactic:</strong> Impact</li> <li><strong>Why it’s privileged: </strong>Allows removal of resource-based access controls for CloudFront resources, causing severe disruption to content delivery and access enforcement.</li> </ul><h4 class="wp-block-heading">Permission: cloudfront:PutResourcePolicy</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to update or create a resource’s policy document</li> <li><strong>Mitre Tactic:</strong> Persistence</li> <li><strong>Why it’s privileged: </strong>Allows adding or modifying resource-based policies to grant or maintain access to CloudFront resources, enabling persistent control over content delivery access.</li> </ul><h3 class="wp-block-heading">Amazon Bedrock</h3><p><strong>Service Type: Artificial Intelligence &amp; Machine Learning</strong></p><h4 class="wp-block-heading">Permission: bedrock:PutEnforcedGuardrailConfiguration</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to set account-level enforced guardrail configuration</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows replacing or weakening enforced account-level guardrails, enabling models or agents to bypass safety and policy controls.</li> </ul><h4 class="wp-block-heading">Permission: bedrock:DeleteEnforcedGuardrailConfiguration</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to delete account-level enforced guardrail configuration</li> <li><strong>Mitre Tactic:</strong> Impact</li> <li><strong>Why it’s privileged: </strong>Allows removal of enforced guardrails across the account, eliminating safety and policy controls and potentially disrupting or exposing downstream AI workloads.</li> </ul><h3 class="wp-block-heading">AWS Network Manager</h3><p><strong>Service Type: Networking and Content Delivery</strong></p><h4 class="wp-block-heading">Permission: networkmanager:PutAttachmentRoutingPolicyLabel</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to put an attachment routing policy label</li> <li><strong>Mitre Tactic:</strong> Lateral Movement</li> <li><strong>Why it’s privileged: </strong>Allows associating routing policies that enable broader prefix propagation, granting compromised attachments access to network segments or prefixes that were previously unreachable.</li> </ul><h4 class="wp-block-heading">Permission: networkmanager:RemoveAttachmentRoutingPolicyLabel</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to remove an attachment </li> <li><strong>Mitre Tactic:</strong> Lateral Movement</li> <li><strong>Why it’s privileged: </strong>Allows removal of labels that enforce strict routing policies, potentially eliminating network segmentation controls and enabling movement between previously isolated environments.</li> </ul><h3 class="wp-block-heading">AWS Launch Wizard</h3><p><strong>Service Type: Infrastructure Management</strong></p><h4 class="wp-block-heading">Permission: launchwizard:UpdateDeployment</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to update a deployment</li> <li><strong>Mitre Tactic:</strong> Credential Access</li> <li><strong>Why it’s privileged: </strong>Allows modifying deployment parameters to change credentials for underlying application databases, enabling unauthorized credential access or takeover.</li> </ul><h2 class="wp-block-heading">New Services with Privileged Permissions</h2><h3 class="wp-block-heading">AWS Route 53 Global Resolver</h3><p><strong>Service Type: Networking and Content Delivery</strong></p><h4 class="wp-block-heading">Permission: route53globalresolver:BatchCreateFirewallRule</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to create multiple firewall rules</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows creation of high-priority allow rules that can bypass existing DNS filtering and evade network-based controls.</li> </ul><h4 class="wp-block-heading">Permission: route53globalresolver:BatchDeleteFirewallRule</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to delete multiple firewall rules</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows removal of DNS firewall rules, disabling DNS-based filtering and reducing network-level visibility and protection.</li> </ul><h4 class="wp-block-heading">Permission: route53globalresolver:BatchUpdateFirewallRule</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to update multiple firewall rules</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows modifying deny rules into allow rules, permitting DNS traffic that would otherwise be filtered or blocked.</li> </ul><h4 class="wp-block-heading">Permission: route53globalresolver:CreateAccessSource</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to create an access source</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows remapping CIDR ranges between DNS views with different firewall policies, enabling DNS queries from the CIDR range to bypass stricter filtering rules.</li> </ul><h4 class="wp-block-heading">Permission: route53globalresolver:CreateFirewallRule</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to create a firewall rule</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows creation of high-priority allow rules that can bypass existing DNS filtering and evade network-based controls.</li> </ul><h4 class="wp-block-heading">Permission: route53globalresolver:DeleteFirewallRule</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to delete a firewall rule</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows removal of DNS firewall rules, disabling DNS-based filtering and reducing network-level protection.</li> </ul><h4 class="wp-block-heading">Permission: route53globalresolver:ImportFirewallDomains</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to import firewall domains from an S3 bucket</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows tampering with domain lists used by firewall rules, potentially permitting DNS traffic that would otherwise be filtered or blocked.</li> </ul><h4 class="wp-block-heading">Permission: route53globalresolver:UpdateAccessSource</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to update an access source</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows remapping CIDR ranges between DNS views with different firewall policies, enabling DNS queries to bypass stricter filtering rules.</li> </ul><h4 class="wp-block-heading">Permission: route53globalresolver:UpdateDNSView</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to update a dns view</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows disabling or weakening security settings such as DNSSEC validation, enabling tampering with DNS responses and bypassing DNS integrity protections.</li> </ul><h4 class="wp-block-heading">Permission: route53globalresolver:UpdateFirewallDomains</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to update firewall domains</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows modification of domain lists used by DNS firewall rules, potentially permitting DNS traffic that would otherwise be blocked or filtered.</li> </ul><h4 class="wp-block-heading">Permission: route53globalresolver:UpdateFirewallRule</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to update a firewall rule</li> <li><strong>Mitre Tactic:</strong> Defense Evasion</li> <li><strong>Why it’s privileged: </strong>Allows changing deny rules into allow rules, permitting DNS traffic that would otherwise be filtered or blocked.</li> </ul><h3 class="wp-block-heading">AWS MCP Server</h3><p><strong>Service Type: Artificial Intelligence and Machine Learning</strong></p><h4 class="wp-block-heading">Permission: aws-mcp:CallReadWriteTool</h4><ul class="wp-block-list"> <li><strong>Action:</strong> Grants permission to call AWS read and write APIs in MCP service</li> <li><strong>Mitre Tactic:</strong> Impact</li> <li><strong>Why it’s privileged: </strong>Allows invoking AWS APIs via the MCP server, enabling unintended or malicious execution of AWS actions if the tool is triggered without explicit user intent.</li> </ul><h3 class="wp-block-heading">AWS PricingPlanManager Service</h3><p><strong>Service Type: Subscription Management</strong></p><p><em>No privileged permissions</em></p><h3 class="wp-block-heading">AWS Compute Optimizer</h3><p><strong>Service Type: Compute Services</strong></p><p><em>No privileged permissions</em></p><h3 class="wp-block-heading">Amazon Nova Act</h3><p><strong>Service Type: Artificial Intelligence &amp; Machine Learning</strong></p><p><em>No privileged permissions</em></p><h3 class="wp-block-heading">AWS ECS MCP Server</h3><p><strong>Service Type: Artificial Intelligence &amp; Machine Learning</strong></p><p><em>No privileged permissions</em></p><h2 class="wp-block-heading">Conclusion</h2><p>As AWS continues to evolve its networking, traffic management, and collaboration services, new privileged permissions are increasingly defining how data flows, access is enforced, and environments are segmented in the cloud. This month’s additions demonstrate how changes to routing policies, firewall rules, encryption controls, and shared resources can quietly expand privilege, weaken isolation, or expose sensitive systems without modifying traditional administrator roles. Even small configuration changes can have an outsized impact on network trust boundaries and lateral movement risk.</p><p>Sonrai Security’s Cloud Permissions Firewall helps organizations stay ahead of these shifts by continuously identifying emerging privileged permissions, mapping them to MITRE ATT&amp;CK tactics, and enforcing least privilege across cloud control planes. In a cloud environment where network and configuration-level privileges continue to expand each month, maintaining continuous visibility and proactive control is critical to preventing overlooked permissions from becoming attack paths.</p><figure class="wp-block-image size-full"><a href="https://sonraisecurity.com/cloud-security-platform/cloud-permissions-firewall/"><img fetchpriority="high" decoding="async" width="1584" height="365" src="https://sonraisecurity.com/wp-content/uploads/image-6.png" alt="" class="wp-image-39421"></a></figure><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/02/jan-recap-new-aws-privileged-permissions-and-services/" data-a2a-title="Jan Recap: New AWS Privileged Permissions and Services"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fjan-recap-new-aws-privileged-permissions-and-services%2F&amp;linkname=Jan%20Recap%3A%20New%20AWS%20Privileged%20Permissions%20and%20Services" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fjan-recap-new-aws-privileged-permissions-and-services%2F&amp;linkname=Jan%20Recap%3A%20New%20AWS%20Privileged%20Permissions%20and%20Services" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fjan-recap-new-aws-privileged-permissions-and-services%2F&amp;linkname=Jan%20Recap%3A%20New%20AWS%20Privileged%20Permissions%20and%20Services" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fjan-recap-new-aws-privileged-permissions-and-services%2F&amp;linkname=Jan%20Recap%3A%20New%20AWS%20Privileged%20Permissions%20and%20Services" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fjan-recap-new-aws-privileged-permissions-and-services%2F&amp;linkname=Jan%20Recap%3A%20New%20AWS%20Privileged%20Permissions%20and%20Services" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://sonraisecurity.com/">Sonrai | Enterprise Cloud Security Platform</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Adeel Nazar">Adeel Nazar</a>. Read the original post at: <a href="https://sonraisecurity.com/blog/jan-recap-new-aws-privileged-permissions-and-services/">https://sonraisecurity.com/blog/jan-recap-new-aws-privileged-permissions-and-services/</a> </p>

JFrog Researchers Surface Vulnerabilities in AI Automation Platform from n8n

  • Michael Vizard
  • Published date: 2026-02-03 00:00:00

None

<p>JFrog security researchers have discovered <a href="https://research.jfrog.com/post/achieving-remote-code-execution-on-n8n-via-sandbox-escape/">a pair of critical vulnerabilities</a> in a workflow automation platform from n8n that makes use of large language models (LLMs) to execute tasks.</p><p>A CVE-2026-1470 vulnerability, rated 9.9, enables a malicious actor to remotely execute JavaScript code by manipulating a Statement capability in the n8n platform that is used to sanitize business logic.</p><p>The CVE-2026-0863 vulnerability, rated 8.5, similarly abuses the logic sanitize tool provided by n8n to enable remote execution using Python code.</p><p>Designed to be deployed in on-premises IT environments or accessed via a cloud service provided by n8n, both issues can be resolved by upgrading to one of the later editions of the n8n platform.</p><p>Used frequently by internal IT and cybersecurity teams to automate tasks, it’s not clear how many vulnerable instances of the n8n platform have been deployed, but this issue is the latest in a series that highlight the risk associated with deploying artificial intelligence (AI) platforms, especially if they enable remote code execution.</p><p>Shachar Menashe, vice president of security research for JFrog, said that in the rush to deploy powerful emerging AI technology organizations need to have a better understanding of the potential risks. That doesn’t mean that organizations should not adopt AI, but rather they need to understand the potential cybersecurity implications, he added.</p><p>In the case of these two vulnerabilities, they have both been rated high because they are relatively trivial to exploit, noted Menashe.</p><p>In general, the discovery of new vulnerabilities is becoming much more problematic in the age of AI. It’s become much simpler for cybercriminals to discover a vulnerability and reverse engineer an exploit using AI coding tools. Cybersecurity teams now need to assume that the time between when a vulnerability is disclosed and an exploit has been created can now be measured in days, if not hours.</p><p>Historically, only a small percentage of known vulnerabilities are actually exploited, but in the age of AI, it’s probable that percentage will soon significantly increase. As a result, cybersecurity teams are likely to soon find themselves even more challenged in the coming year.</p><p>Each organization will, as a consequence, need to make sure it is running the latest and most secure version of an application. Many of them will also need to revisit the degree to which they are comfortable with automatically applying patches. Many organizations tend to prefer to test a patch before upgrading software to ensure their application doesn’t break. However, as the overall level of risk a cyberattack represents to the business continues to increase, there are more classes of patches that should be automatically applied. The risk that a potential cyberattack creates is simply larger than the cost of the potential downtime that might result from the patch being applied. Hopefully, AI tools will also soon make it easier to discover and remediate vulnerabilities before they are exploited.</p><p>In the meantime, cybersecurity teams should, as always, continue to hope for the best while being ready for the worst.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/02/jfrog-researchers-surface-vulnerabilities-in-ai-automation-platform-from-n8n/" data-a2a-title="JFrog Researchers Surface Vulnerabilities in AI Automation Platform from n8n"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fjfrog-researchers-surface-vulnerabilities-in-ai-automation-platform-from-n8n%2F&amp;linkname=JFrog%20Researchers%20Surface%20Vulnerabilities%20in%20AI%20Automation%20Platform%20from%20n8n" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fjfrog-researchers-surface-vulnerabilities-in-ai-automation-platform-from-n8n%2F&amp;linkname=JFrog%20Researchers%20Surface%20Vulnerabilities%20in%20AI%20Automation%20Platform%20from%20n8n" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fjfrog-researchers-surface-vulnerabilities-in-ai-automation-platform-from-n8n%2F&amp;linkname=JFrog%20Researchers%20Surface%20Vulnerabilities%20in%20AI%20Automation%20Platform%20from%20n8n" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fjfrog-researchers-surface-vulnerabilities-in-ai-automation-platform-from-n8n%2F&amp;linkname=JFrog%20Researchers%20Surface%20Vulnerabilities%20in%20AI%20Automation%20Platform%20from%20n8n" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fjfrog-researchers-surface-vulnerabilities-in-ai-automation-platform-from-n8n%2F&amp;linkname=JFrog%20Researchers%20Surface%20Vulnerabilities%20in%20AI%20Automation%20Platform%20from%20n8n" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div>

2026 Identity & Payments Summit Agenda: Deepfake Defense, Quantum-Resistant Transactions and The Digital Identity Revolution

  • Secure Technology Alliance
  • Published date: 2026-02-02 14:00:00

The agenda for the 2026 Identity & Payments Summit in Houston has been unveiled....

REDWOOD CITY, Calif., Feb. 02, 2026 (GLOBE NEWSWIRE) -- The Secure Technology Alliance today unveils the full agenda for the 2026 Identity &amp; Payments Summit. The Summit is the premier event of it… [+6235 chars]

What Verified Breach Data Changes About Exposure Monitoring

  • None
  • Published date: 2026-02-02 00:00:00

None

<p>Exposure monitoring has become a core function for security and risk teams but many programs still struggle to deliver clear, actionable outcomes. Alerts pile up, dashboards expand, and yet teams are often left with the same unanswered question:</p><h2 class="wp-block-heading"><strong>Which exposures actually matter right now?</strong></h2><p>The difference between noise and signal in exposure monitoring often comes down to one factor: <strong>data verification</strong>. Without verified breach data, exposure monitoring becomes an exercise in volume rather than risk prioritization.</p><p>This post breaks down what verified breach data actually changes about exposure monitoring and why it’s becoming foundational for threat intelligence teams, SOCs, and risk leaders.</p><h2 class="wp-block-heading"><strong>The Current State of Exposure Monitoring</strong></h2><p>Most exposure monitoring programs rely on a mix of sources:</p><ul class="wp-block-list"> <li>Credential dumps scraped from public or semi-public forums</li> <li>Dark web monitoring feeds</li> <li>Open-source breach repositories</li> <li>Third-party aggregators with limited validation transparency</li> </ul><p>While these sources can surface large quantities of data, <strong>quantity alone does not equal exposure intelligence</strong>.</p><p>In practice, teams often face:</p><ul class="wp-block-list"> <li>Duplicate credentials resurfacing years after an initial breach</li> <li>Fabricated or “salted” data designed to look real</li> <li>Partial records with no attribution context</li> <li>Alerts that cannot be confidently tied to a real person, customer, or employee</li> </ul><p>This creates a familiar operational problem: analysts spend significant time validating alerts before any remediation can begin.</p><h2 class="wp-block-heading"><strong>Why Unverified Breach Data Creates Risk Blind Spots</strong></h2><p>Unverified breach data doesn’t just waste time, it actively distorts exposure visibility.</p><p>When breach data is not validated:</p><ul class="wp-block-list"> <li><strong>False positives increase</strong>, overwhelming triage workflows</li> <li><strong>True exposure competes with noise</strong>, delaying response</li> <li><strong>Trust in monitoring systems erodes</strong>, leading teams to ignore alerts altogether</li> </ul><p><strong>Unverified breach data reduces confidence in exposure monitoring outcomes.</strong></p><p>This lack of confidence impacts downstream decisions—from password resets and account monitoring to executive briefings and board-level reporting.</p><h2 class="wp-block-heading"><strong>What Is Verified Breach Data?</strong></h2><p>Verified breach data is not defined by where it appears—it’s defined by <strong>how it’s validated</strong>.</p><p>At a high level, verified breach data includes:</p><ul class="wp-block-list"> <li>Confirmation that a breach event actually occurred</li> <li>Validation of the source and timeframe of the exposure</li> <li>Normalization and de-duplication across datasets</li> <li>Attribution confidence that links exposed data to real entities</li> </ul><p>In other words, verified breach data answers not just <em>what</em> was exposed, but:</p><ul class="wp-block-list"> <li><strong>When</strong> it was exposed</li> <li><strong>Where</strong> it originated</li> <li><strong>Who</strong> is actually impacted</li> </ul><p>Constella’s approach to <a href="https://constella.ai/threat-intelligence-data-signals-api/">verified breach intelligence</a> is designed to support this level of confidence and transparency across exposure workflows.</p><h2 class="wp-block-heading"><strong>How Verified Breach Data Changes Exposure Monitoring Outcomes</strong></h2><p><strong>1. Exposure Monitoring Becomes Prioritized, Not Reactive</strong></p><p>With verified breach data, alerts can be ranked by:</p><ul class="wp-block-list"> <li>Recency of exposure</li> <li>Confidence of attribution</li> <li>Sensitivity of exposed data (PII, credentials, tokens)</li> </ul><p>This allows teams to shift from reactive alert handling to <strong>risk-based prioritization</strong>, focusing first on exposures that pose real operational or fraud risk.</p><p><strong>2. Analysts Spend Less Time Validating, More Time Acting</strong></p><p>One of the most immediate operational benefits is reduced manual validation.</p><p>Instead of asking:</p><ul class="wp-block-list"> <li>“Is this breach real?”</li> <li>“Is this data recycled?”</li> <li>“Does this identity actually exist?”</li> </ul><p>Analysts can move directly into remediation workflows:</p><ul class="wp-block-list"> <li>Credential resets</li> <li>Account monitoring</li> <li>Identity risk scoring enrichment</li> </ul><p>This is especially valuable for SOCs and threat intelligence teams operating under alert fatigue.</p><p><strong>3. Exposure Intelligence Gains Identity Context</strong></p><p>Exposure monitoring without identity context only tells part of the story.</p><p>Verified breach data, when fused with identity intelligence, allows teams to understand:</p><ul class="wp-block-list"> <li>Whether exposed data maps to customers, employees, or executives</li> <li>How exposed identifiers connect across aliases, emails, and usernames</li> <li>Whether multiple exposures point to the same underlying entity</li> </ul><p>This is where exposure monitoring intersects directly with <a href="https://constella.ai/threat-intelligence-data-signals-api/"><strong>identity risk intelligence</strong></a><strong>.</strong></p><h2 class="wp-block-heading"><strong>Why Verified Breach Data Matters for Threat Intelligence Teams</strong></h2><p>Threat intelligence teams are increasingly expected to deliver <strong>actionable intelligence</strong>, not just feeds.</p><p>Verified breach data supports this shift by enabling:</p><ul class="wp-block-list"> <li>Cleaner enrichment of alerts and investigations</li> <li>Stronger attribution confidence in reporting</li> <li>Better alignment between intel findings and operational response</li> </ul><p>Instead of pushing raw breach alerts downstream, teams can provide <strong>curated, confidence-weighted exposure insights</strong> that other teams trust.</p><h2 class="wp-block-heading"><strong>Where Exposure Monitoring Breaks Without Verification</strong></h2><p>Without verified breach data, exposure monitoring programs often stall at the same point:</p><ul class="wp-block-list"> <li>Alerts are generated</li> <li>Dashboards update</li> <li>But decisive action is delayed</li> </ul><p>This is not a tooling failure—it’s a <strong>data trust problem</strong>.</p><p>Verification restores that trust by giving teams confidence that:</p><ul class="wp-block-list"> <li>Alerts are real</li> <li>Identities are accurate</li> <li>Decisions are defensible</li> </ul><h2 class="wp-block-heading"><strong>Moving from Exposure Visibility to Exposure Intelligence</strong></h2><p>Exposure monitoring is evolving. The goal is no longer visibility alone. It’s <strong>clarity</strong>.</p><p>Verified breach data enables that clarity by:</p><ul class="wp-block-list"> <li>Reducing noise</li> <li>Improving prioritization</li> <li>Anchoring exposure insights to real identities</li> </ul><p>For organizations looking to mature their threat intelligence and exposure monitoring capabilities, verification is no longer optional, it’s foundational.</p><p>Learn how Constella delivers <a href="https://constella.ai/threat-intelligence-data-signals-api/">verified breach intelligence</a> designed for operational confidence.</p><h2 class="wp-block-heading"><strong>Frequently Asked Questions About Verified Breach Data</strong></h2><p><strong>What is verified breach data?</strong></p><p>Verified breach data is breach intelligence that has been validated to confirm the breach event occurred, the data originated from a credible source, and the exposed information can be confidently attributed to real identities. Unlike scraped or recycled breach dumps, verified breach data includes contextual signals such as timing, source reliability, and attribution confidence.</p><p><strong>How is verified breach data different from dark web monitoring?</strong></p><p>Dark web monitoring focuses on where data appears. Verified breach data focuses on whether the data is real, recent, and relevant. Many dark web feeds surface unverified or recycled data, while verified breach intelligence emphasizes validation, de-duplication, and confidence scoring before alerts reach analysts.</p><p><strong>Why does exposure monitoring generate so many false positives?</strong></p><p>False positives occur when exposure monitoring relies on unverified breach feeds, partial datasets, or shallow matching logic. Without verification and identity context, alerts may reference fabricated credentials, outdated breaches, or identities that cannot be confidently resolved—forcing analysts to manually validate each alert.</p><p><strong>How does verified breach data reduce alert fatigue?</strong></p><p>By validating breach sources and confirming attribution, verified breach data reduces duplicate alerts, eliminates fabricated datasets, and prioritizes confirmed exposure. This allows security and threat intelligence teams to focus on high-confidence risks instead of triaging noise.</p><p><strong>Who benefits most from verified breach data?</strong></p><p>Verified breach data is most valuable for:</p><ul class="wp-block-list"> <li>Threat intelligence teams responsible for exposure monitoring</li> <li>SOC teams managing alert enrichment and triage</li> <li>Fraud and identity teams assessing downstream risk</li> <li>Security leaders who need defensible exposure reporting</li> </ul><p>These teams rely on confidence, not volume, to make decisions.</p><p><strong>Does verified breach data improve identity risk scoring?</strong></p><p>Yes. Identity risk scoring depends on accurate attribution. Verified breach data strengthens identity risk scores by ensuring exposed credentials or PII are linked to real entities with known confidence levels, improving both prioritization and explainability.</p><p><strong>Can verified breach data help with compliance and reporting?</strong></p><p>Verified breach data supports compliance and reporting by providing defensible evidence of exposure, clearer timelines, and validated sources. This is especially important when communicating exposure risk to executives, auditors, or regulators.</p><p><strong>Is more breach data better for exposure monitoring?</strong></p><p>No. More data without verification increases noise and slows response. Effective exposure monitoring prioritizes quality, confidence, and context over sheer volume. Verified breach data enables faster, more accurate risk decisions.</p><p><strong>How does Constella verify breach data?</strong></p><p>Constella combines source validation, continuous curation, de-duplication, and identity intelligence to deliver breach data that teams can trust. Verification is embedded into the intelligence pipeline, not added as an afterthought.</p><p><strong>What is the first step to improving exposure monitoring accuracy?</strong></p><p>The first step is evaluating the quality and verification of your breach data sources. If teams spend more time validating alerts than acting on them, verification gaps are likely limiting the effectiveness of exposure monitoring.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/02/what-verified-breach-data-changes-about-exposure-monitoring/" data-a2a-title="What Verified Breach Data Changes About Exposure Monitoring"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fwhat-verified-breach-data-changes-about-exposure-monitoring%2F&amp;linkname=What%20Verified%20Breach%20Data%20Changes%20About%20Exposure%20Monitoring" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fwhat-verified-breach-data-changes-about-exposure-monitoring%2F&amp;linkname=What%20Verified%20Breach%20Data%20Changes%20About%20Exposure%20Monitoring" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fwhat-verified-breach-data-changes-about-exposure-monitoring%2F&amp;linkname=What%20Verified%20Breach%20Data%20Changes%20About%20Exposure%20Monitoring" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fwhat-verified-breach-data-changes-about-exposure-monitoring%2F&amp;linkname=What%20Verified%20Breach%20Data%20Changes%20About%20Exposure%20Monitoring" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fwhat-verified-breach-data-changes-about-exposure-monitoring%2F&amp;linkname=What%20Verified%20Breach%20Data%20Changes%20About%20Exposure%20Monitoring" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://constella.ai">Constella Intelligence</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Jason Wagner">Jason Wagner</a>. Read the original post at: <a href="https://constella.ai/what-verified-breach-data-changes-about-exposure-monitoring/">https://constella.ai/what-verified-breach-data-changes-about-exposure-monitoring/</a> </p>

Flaw in Broadcom Wi-Fi Chipsets Illuminates Importance of Wireless Dependability and Business Continuity

  • Teri Robinson
  • Published date: 2026-02-02 00:00:00

None

<p><span data-contrast="auto">A wireless vulnerability affecting Broadcom Wi-Fi chipsets represents a timely warning for organizations that need always-on wireless access and a prime example of how easy it is for one bad actor to upset the apple cart for every user connected to a network.</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="none">“The vulnerability can be exploited by sending a single frame over the air to the router within range, regardless of the configured network security level. The immediate effect is the loss of connection for all clients on the 5 GHz network, preventing reconnection until the router is manually restarted. This includes guest networks as well,” according to </span><a href="https://www.blackduck.com/blog/cyrc-discovers-asus-tplink-wlan-vulnerabilities-cve-2025-14631.html?cmp=pr-sig&amp;utm_medium=referral" target="_blank" rel="noopener"><span data-contrast="none">Black Duck researchers</span></a><span data-contrast="none"> who discovered the vulnerability. “Ethernet connections and the 2.4 GHz network remain unaffected. After the restart, the attacker can immediately repeat the attack.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">Black Duck’s CyRC team spotted the flaw during fuzz testing when they found Defensics anomaly test cases in which the network would stop working and require a manual reset of the router. If the vulnerability is exploited, attackers can make it so that an access point doesn’t respond to clients and can end client connections underway. The potential for widespread damage from exploitation of the vulnerability is even greater because of the popularity of Broadcom Wi-Fi chipsets.</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">“Given the huge dependence on connectivity for personal devices and ever increasing numbers of IoT and smart devices, the impacts could be significant,” says James Maude, field CTO at BeyondTrust.</span></p><p><span data-contrast="auto">The flaw also “has the potential to open the door to evil twin attacks where the real access point is knocked offline and a rogue one with the same name and password replaces it,” says Maude. </span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">“While the risks of network traffic interception have decreased thanks to the widespread adoption of HTTPS encryption, there is still the risk of captive portals,” he says. “When the user tries to restore their network connection, they are presented with a captive phishing portal requesting their personal or corporate credentials, leading to identity compromise.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">Putting a more dangerous edge on the flaw is the fact that it doesn’t require authentication and encryption settings don’t thwart it. </span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">Noting that “implementation-level flaws in protocols, such as 802.11, are often more difficult to detect than cryptographic weaknesses” while “cryptographic weaknesses are easier to find because there are often only software dependencies,” Ben Ronallo, principal cybersecurity engineer at Black Duck, explains that “a researcher can build the code with breakpoints and watch the memory as the software executes.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">But in that scenario, hardware dependencies are needed for testing. “The access point and a compatible antenna are required to perform this type of testing,” says Ronallo. “Further complicating things, the access point firmware is almost always closed source, which makes introspection much more difficult.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">An attack from exploiting the flaw “is both easy to execute and highly disruptive, underscoring that even mature and widely deployed network technologies can still yield new and serious attack vectors,” says Saumitra Das, vice president of engineering at Qualys. “Because the attack can be launched by an unauthenticated client, encryption alone offers little protection.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">And while this vulnerability initially “seems scary because it lets one unverified wireless frame keep disrupting a 5 GHz network until someone has to step in,” Randolph Barr, CISO at Cequence Security, says “the main risk isn’t simply the outage itself; it’s what long-term instability allows and how deeply it affects how the organization runs.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">Past experience says “problems like this don’t usually stay limited to ‘IT issues,’” says Barr.</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">“Most offices today use wireless connections more than traditional ones. Imagine being on a Zoom escalation call with a customer and the network goes down,” he says. “Even worse, imagine a board meeting where the CEO is discussing financial results, strategy, or an acquisition update, and the connection drops in the middle of the presentation.” </span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">That’s not just annoying, “it can hurt your credibility, slow down decision-making, and make consumers, partners, and executives lose trust in you,” says Barr.</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">Fuzz testing has proven crucial in “validating protocol-stack implementations such as Wi-Fi,” over the years, uncovering “a wide range of vulnerabilities, including buffer overflows in drivers, denial-of-service conditions, remote code execution, and performance instability,” says Das. “Wi-Fi stacks are inherently complex, combining multiple state machines, cryptographic operations, and timing-dependent behaviors, which make them especially prone to subtle and dangerous implementation flaws.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">Broadcom has issued a patch for the vulnerability, but that doesn’t mean protection will come quickly. “Remediation of vulnerabilities in hardware/firmware are always slower due to the downstream effects needing to be fully tested,” says Ronallo. That testing requires time from multiple, independent parties to ensure any changes don’t introduce additional bugs into their products.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">While the industry says the deadline is 90 days, in reality, for hardware/firmware it’s closer to 180-plus days,” he explains.</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">While the flaw is serious, Barr says it “doesn’t mean that someone can immediately take over the router or spy on it.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">It does show, however, he says, “that the wireless control plane’s trust limits have broken down. This kind of issue is an area that many companies think is safe just because it is encrypted.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">To counter these threats, security teams “must start with strong visibility into their environments through accurate asset inventory and continuous scanning, combined with the ability to tag assets by business criticality,” says Das. </span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">“It is not enough to know that access points are vulnerable; teams must understand where they are deployed and how much they matter to the business,” Das explains. “An access point supporting a small innovation lab carries very different risks than one embedded in a core manufacturing or logistics operation.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">And Barr advises, “If you’re building networking in a hospital or your own home, segment your networks to prevent a direct path to your critical systems” and “audit for end of life/support systems (e.g., access points) and replace them when possible.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">If the latter isn’t possible, “lock them down, have redundant logging in place, and monitor network edges with intrusion detection/prevention,” he says. </span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><p><span data-contrast="auto">And, of course, patch systems and consider setting up honeypots “to understand what attacks you could be facing.”</span><span data-ccp-props='{"201341983":0,"335559739":0,"335559740":240}'> </span></p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/02/flaw-in-broadcom-wi-fi-chipsets-illuminates-importance-of-wireless-dependability-and-business-continuity/" data-a2a-title="Flaw in Broadcom Wi-Fi Chipsets Illuminates Importance of Wireless Dependability and Business Continuity "><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fflaw-in-broadcom-wi-fi-chipsets-illuminates-importance-of-wireless-dependability-and-business-continuity%2F&amp;linkname=Flaw%20in%20Broadcom%20Wi-Fi%20Chipsets%20Illuminates%20Importance%20of%20Wireless%20Dependability%20and%20Business%20Continuity%C2%A0" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fflaw-in-broadcom-wi-fi-chipsets-illuminates-importance-of-wireless-dependability-and-business-continuity%2F&amp;linkname=Flaw%20in%20Broadcom%20Wi-Fi%20Chipsets%20Illuminates%20Importance%20of%20Wireless%20Dependability%20and%20Business%20Continuity%C2%A0" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fflaw-in-broadcom-wi-fi-chipsets-illuminates-importance-of-wireless-dependability-and-business-continuity%2F&amp;linkname=Flaw%20in%20Broadcom%20Wi-Fi%20Chipsets%20Illuminates%20Importance%20of%20Wireless%20Dependability%20and%20Business%20Continuity%C2%A0" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fflaw-in-broadcom-wi-fi-chipsets-illuminates-importance-of-wireless-dependability-and-business-continuity%2F&amp;linkname=Flaw%20in%20Broadcom%20Wi-Fi%20Chipsets%20Illuminates%20Importance%20of%20Wireless%20Dependability%20and%20Business%20Continuity%C2%A0" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fflaw-in-broadcom-wi-fi-chipsets-illuminates-importance-of-wireless-dependability-and-business-continuity%2F&amp;linkname=Flaw%20in%20Broadcom%20Wi-Fi%20Chipsets%20Illuminates%20Importance%20of%20Wireless%20Dependability%20and%20Business%20Continuity%C2%A0" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div>

AI Agent Orchestration: How It Works and Why It Matters

  • None
  • Published date: 2026-02-02 00:00:00

None

<p>AI agent orchestration is reshaping how businesses build intelligent systems. It moves beyond single chatbots or generative interfaces, coordinating multiple specialized <a href="https://www.ishir.com/blog/141152/the-future-of-ai-why-agentic-ai-is-the-key-to-business-innovation.htm" rel="noopener">AI agents</a> to complete complex tasks with minimal human supervision. Instead of one general purpose model handling everything, orchestration connects many focused agents that collaborate, share context, and automate workflows efficiently.</p><p>This blog explains what AI agent orchestration is, how it works in enterprise environments, the major technology platforms driving adoption, key frameworks and patterns, business use cases, risks and considerations, and how companies like ISHIR support clients implementing these AI agent orchestration solutions and advanced AI systems.</p><h2>What Is AI Agent Orchestration</h2><p>AI agent orchestration is the structured management and coordination of multiple autonomous AI agents to reach shared objectives. Each agent is designed for a specific function, such as extracting data, summarizing content, handling customer requests, or triggering integrations. The orchestrator acts as the coordinator that routes tasks, manages shared state, handles communication, and sequences steps toward a goal.</p><p>This approach contrasts with single <a href="https://www.ishir.com/blog/307391/how-do-i-integrate-llms-into-my-software-product-without-blowing-up-infrastructure-costs.htm" rel="noopener">large language model (LLM) applications</a> that respond to prompts. With orchestration, intelligent agents work together, combining their specialized abilities to solve complex, multi-step problems.</p><h2>How AI Agent Orchestration Works</h2><h4><strong>AI Agent Design</strong></h4><p>AI Agents are autonomous software units with specific skills. One agent might fetch documents, another might analyze sentiment, another might check regulatory compliance, and another might summarize results for a human reviewer. All <a href="https://www.ishir.com/hire-ai-agent-developers.htm" rel="noopener">AI agents are built</a> to communicate with each other through protocols defined by the orchestrator.</p><h4><strong>Task Decomposition</strong></h4><p>The orchestrator breaks down a high-level request into steps. For example, a request to prepare a regulatory report might be broken into research, extraction, analysis, and compilation. The orchestrator assigns each step to the right agent and ensures the output feeds into the next step.</p><h4><strong>Shared Context</strong></h4><p>AI Agents maintain a shared workspace or context store so that data from one agent is available to others. The orchestrator tracks state and manages transitions, ensuring information flow does not get lost across steps.</p><h4><strong>Communication Protocols</strong></h4><p>Orchestration requires structured communication between agents. <a href="https://www.ishir.com/blog/203185/top-ai-app-builders-showdown-speed-features-pricing-which-one-wins-in-2025.htm" rel="noopener">Modern AI frameworks</a> use message buses, shared databases, or direct API calls so agents can coordinate without bottlenecks.</p><h4><strong>Workflow Patterns</strong></h4><p>Orchestrators define workflow patterns from linear sequences to parallel processing. This allows systems to run steps concurrently where possible, improving performance and throughput.</p><h2>Why AI Orchestration Matters for Business</h2><p><strong>Complexity</strong></p><p>Many real business processes involve multiple steps and decision points. Orchestration enables automation chains that align with enterprise workflows.</p><p><strong>Scalability</strong></p><p>Rather than building custom monolithic <a href="https://www.ishir.com/blog/90145/10-ai-tools-every-software-developer-should-be-using-in-2023-beyond.htm" rel="noopener">AI tools</a> for every task, orchestration allows reuse of agents across many scenarios, saving engineering effort.</p><p><strong>Transparency</strong></p><p>With proper orchestration tooling, steps are traceable. Enterprises can audit why an agent chose a particular action or path.</p><p><strong>Efficiency</strong></p><p>Orchestration systems reduce manual coordination between systems and teams, accelerating outcomes and lowering costs.</p><h2>Core Technologies Behind AI Agent Orchestration</h2><h4><strong>Large Language Models (LLMs)</strong></h4><p>LLMs provide general reasoning and language capabilities that many agents rely on to interpret inputs, plan next actions, and generate outputs.</p><h4><strong>Vector Stores and Memory Systems</strong></h4><p>Agents often need a memory layer to store knowledge, context, or reference data. Vector databases support semantic search and retrieval across agent workflows.</p><h4><strong>API Integrations</strong></h4><p>Agents use APIs to interact with systems like CRMs, data lakes, content repositories, or analytics platforms.</p><h4><strong>Workflow Engines</strong></h4><p>Workflow engines coordinate multi-step logic and state transitions across agents. These act as the backbone of orchestration systems.</p><h2>Major Technology &amp; AI Players Investing in AI Agent Orchestration</h2><h4><strong>Microsoft</strong></h4><p>Microsoft offers a suite of tools for building and orchestrating AI agents. Its Agent Framework is open source and supports multi-agent workflows, state management, tool calling, and observability. The Azure AI platform provides models, orchestration tools, and enterprise grade governance.</p><p>Microsoft also embeds agent orchestration into its productivity suite with <a href="https://www.ishir.com/microsoft-office-365-consulting-service.htm" rel="noopener">Microsoft 365</a> Copilot, allowing agents to automate tasks like data analysis, summarization, and workflow automation in everyday apps.</p><h4><strong>Google</strong></h4><p>Google’s Vertex AI Agent Builder and related tools in the Vertex AI ecosystem support rapid creation, scaling, and governance of enterprise agents. This platform integrates with Google Cloud data services and model hosting.</p><p>Google defines agentic AI as systems capable of setting goals, planning, and executing tasks with limited human oversight, which aligns directly with orchestration models.</p><h4><strong>Other Key AI Agent Platforms</strong></h4><p>There are many AI Agent frameworks and AI tools emerging in the orchestration space. Examples include n8n, LangGraph, and CrewAI, which provide orchestration features like communication layers, task routing, and workflow definition.</p><p>Some open source and experimental tools such as OpenAI’s Swarm are also advancing multi-agent orchestration research.</p><p>Enterprises like PwC have launched platforms that function as agent “switchboards” to connect agents from various providers and automate cross-functional tasks.</p><h2>Use Cases in the Real World</h2><ul> <li><strong>Customer Service Automation: </strong>Orchestrated agents can handle incoming support tickets, classify issues, retrieve relevant knowledge, and deliver answers. If escalation is needed, they route tasks to human staff.</li> <li><strong>Data Extraction and Reporting: </strong>Agents can fetch data from multiple repositories, analyze insights, and build consolidated reports for finance, compliance, or executive dashboards.</li> <li><strong>Intelligent Workflow Automation: </strong>HR, legal, procurement, and IT processes that involve many discrete steps benefit from orchestration. Agents can trigger actions, enforce policies, and integrate with backend systems.</li> <li><strong>Personalized Engagement: </strong>Marketing and sales can use orchestration to tailor outreach and content generation based on customer segments without manual intervention.</li> </ul><h2>Challenges and Risks</h2><p><strong>Governance: </strong>AI agent orchestration involves decisions across multiple systems. Without controls, it is difficult to audit why an agent acted in a certain way.</p><p><strong>Trust and Safety: </strong>Unsupervised agents could inadvertently access sensitive data or take incorrect actions. Strong safety and access controls are essential.</p><p><strong>Integration Complexity: </strong>Connecting agents to diverse systems and data sources requires engineering investment.</p><h2>How ISHIR Helps</h2><p>At ISHIR we help companies understand, plan, and <a href="https://www.ishir.com/generative-ai-solutions.htm" rel="noopener">build AI agent orchestration solutions</a> that align with business goals. Our approach begins with strategy and architecture, identifying processes most suitable for orchestration and assessing data access, integrations, and security requirements.</p><p>We build prototypes and production ready <a href="https://www.ishir.com/artificial-intelligence.htm" rel="noopener">AI solutions</a> using best practices in AI agent design, AI agent orchestration frameworks, and AI governance. ISHIR teams work closely with clients to ensure AI agent workflows are efficient, auditable, and scalable.</p><p>We serve clients in Dallas Fort Worth, Austin, Houston, and San Antonio Texas with teams in India, LATAM, and East Europe.</p><p>Our AI experience spans enterprise automation, customer AI workflows, and integration with cloud platforms from Microsoft, Google, and other leading vendors like Open AI. We focus on delivering solutions that produce measurable business value.</p><div class="ctaThreeWrapper"> <div class="ctaThreeContent"> <div class="ctaThreeConList"> <div class="content"> <h2>Your AI initiatives are isolated experiments instead of scalable, end-to-end automation.</h2> <p>Implement AI agent orchestration that connects models, data, and systems into production-ready, governed workflows.</p> <div class="linkWrapper"><a href="https://www.ishir.com/get-in-touch.htm" rel="noopener">Get Started</a></div> </div> </div> </div> </div><h2>FAQs About AI Agent Orchestration Solutions</h2><h4><strong>1. What is AI agent orchestration?</strong></h4><p><strong>A.</strong> AI agent orchestration coordinates multiple specialized AI agents to complete complex workflows efficiently.</p><h4><strong>2. How does orchestration differ from traditional AI?</strong></h4><p><strong>A.</strong> Traditional AI responds to individual prompts; orchestration links agents to work together on tasks.</p><h4><strong>3. What is an AI agent?</strong></h4><p><strong>A.</strong> An AI agent is software capable of autonomous decision-making and actions in pursuit of a goal.</p><h4><strong>4. Why use agent orchestration?</strong></h4><p><strong>A.</strong> It improves scalability, handles complexity, and enables automation of multi-step workflows.</p><h4><strong>5. What platforms support AI agent orchestration?</strong></h4><p><strong>A.</strong> Microsoft’s Agent Framework, Google’s Vertex AI Agent Builder, and open source tools like LangGraph.</p><h4><strong>6. Is AI orchestration only for large companies?</strong></h4><p><strong>A.</strong> No, small and mid-size businesses with complex processes benefit from orchestration as well.</p><h4><strong>7. What industries use AI agent orchestration?</strong></h4><p><strong>A.</strong> Finance, healthcare, retail, logistics, HR, legal, and more.</p><h4><strong>8. What risks are associated with orchestration?</strong></h4><p><strong>A.</strong> Governance, data access, and integration complexity.</p><h4><strong>9. Can agent orchestration improve customer service?</strong></h4><p><strong>A.</strong> Yes, by automating responses and workflow routing.</p><h4><strong>10. How do agents share context?</strong></h4><p><strong>A.</strong> Through shared memory stores and state tracking.</p><h4><strong>11. Do orchestrated agents learn over time?</strong></h4><p><strong>A.</strong> Some systems use feedback loops and adaptive models.</p><h4><strong>12. What languages do frameworks support?</strong></h4><p><strong>A.</strong> Frameworks often support Python, .NET, and other popular developer languages.</p><h4><strong>13. How does orchestration impact efficiency?</strong></h4><p><strong>A.</strong> It automates repetitive tasks and reduces manual coordination.</p><h4><strong>14. Is orchestration secure?</strong></h4><p><strong>A.</strong> Security depends on access controls and governance tooling.</p><h4><strong>15. Can orchestration integrate with existing systems?</strong></h4><p><strong>A.</strong> Yes, agents can call APIs and interact with enterprise apps.</p><h4><strong>16. Do orchestrators manage workflows?</strong></h4><p><strong>A.</strong> Yes, they sequence and execute multi-step tasks.</p><h4><strong>17. What is a workflow engine?</strong></h4><p><strong>A.</strong> A workflow engine coordinates steps and tracks state across agents.</p><h4><strong>18. Are there visual orchestration tools?</strong></h4><p><strong>A.</strong> Some platforms offer low-code or visual workflow design.</p><h4><strong>19. What is an example of agent orchestration?</strong></h4><p><strong>A.</strong> Coordinating data retrieval, analysis, and reporting across multiple specialized agents.</p><h4><strong>20. How does ISHIR approach orchestration projects?</strong></h4><p><strong>A.</strong> We align orchestration strategy with business goals and build scalable solutions.</p><p>The post <a href="https://www.ishir.com/blog/313910/ai-agent-orchestration-how-it-works-and-why-it-matters.htm">AI Agent Orchestration: How It Works and Why It Matters</a> appeared first on <a href="https://www.ishir.com/">ISHIR | Custom AI Software Development Dallas Fort-Worth Texas</a>.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/02/ai-agent-orchestration-how-it-works-and-why-it-matters/" data-a2a-title="AI Agent Orchestration: How It Works and Why It Matters"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fai-agent-orchestration-how-it-works-and-why-it-matters%2F&amp;linkname=AI%20Agent%20Orchestration%3A%20How%20It%20Works%20and%20Why%20It%20Matters" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fai-agent-orchestration-how-it-works-and-why-it-matters%2F&amp;linkname=AI%20Agent%20Orchestration%3A%20How%20It%20Works%20and%20Why%20It%20Matters" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fai-agent-orchestration-how-it-works-and-why-it-matters%2F&amp;linkname=AI%20Agent%20Orchestration%3A%20How%20It%20Works%20and%20Why%20It%20Matters" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fai-agent-orchestration-how-it-works-and-why-it-matters%2F&amp;linkname=AI%20Agent%20Orchestration%3A%20How%20It%20Works%20and%20Why%20It%20Matters" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fai-agent-orchestration-how-it-works-and-why-it-matters%2F&amp;linkname=AI%20Agent%20Orchestration%3A%20How%20It%20Works%20and%20Why%20It%20Matters" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://www.ishir.com/">ISHIR | Custom AI Software Development Dallas Fort-Worth Texas</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Rishi Khanna">Rishi Khanna</a>. Read the original post at: <a href="https://www.ishir.com/blog/313910/ai-agent-orchestration-how-it-works-and-why-it-matters.htm">https://www.ishir.com/blog/313910/ai-agent-orchestration-how-it-works-and-why-it-matters.htm</a> </p>

Are cloud secrets safe with automatic rotation systems

  • None
  • Published date: 2026-02-01 00:00:00

None

<h2>Are Cloud Secrets Truly Secure with Automated Rotation Systems?</h2><p>What assures you that your cloud secrets are safe? Where organizations increasingly migrate operations to the cloud, safeguarding machine identities—referred to as Non-Human Identities (NHIs)—becomes paramount. These NHIs are the machine identities within cybersecurity, defined by the pairing of a secret, such as an encrypted password or key, and the permissions accorded by destination servers.</p><h3>Understanding Non-Human Identities in Cybersecurity</h3><p>Machine identities play a crucial role in digital environments, resembling the activities of tourists with passports and visas. Here, the secret acts as a passport—a credential granting access to cloud resources—while the permissions function like a visa, subject to the hosting server’s constraints. The effective management of NHIs entails protecting both their identities and associated secrets, along with the monitoring of their interactions within systems.</p><p>By focusing on this unique approach, NHIs address prevalent security gaps, particularly those arising from the disconnection between security and R&amp;D teams. The ultimate objective is to forge a secure and cohesive cloud environment.</p><h3>The Key Benefits of NHI Management</h3><p>Achieving rigorous oversight in NHI management delivers numerous advantages for cybersecurity teams:</p><ul> <li><strong>Reduced Risk:</strong> Proactively identifying and mitigating security risks helps prevent potential breaches and data leaks.</li> <li><strong>Improved Compliance:</strong> Policies are enforced and audit trails established, assisting organizations in meeting regulatory requirements.</li> <li><strong>Increased Efficiency:</strong> Automation of NHI and secrets management enables security teams to dedicate more time to strategic initiatives.</li> <li><strong>Enhanced Visibility and Control:</strong> A centralized view offers comprehensive access management and governance.</li> <li><strong>Cost Savings:</strong> Significant operational costs are reduced through the automation of secrets rotation and the decommissioning of NHIs.</li> </ul><h3>Adopting a Holistic Approach to Security</h3><p>A robust system of NHI management provides full lifecycle protection. This strategy involves everything from discovery and classification of secrets to threat detection and remediation. Unlike point solutions—such as secret scanners that offer limited protection—comprehensive NHI management platforms deliver insights into ownership, permissions, usage patterns, and potential vulnerabilities. Context-aware security ensures a more nuanced defense against threats.</p><h3>Secrets Security in Cloud Environments</h3><p>When businesses transition to cloud-based operations, the importance of protecting cloud secrets cannot be overstated. Failure to adequately manage these secrets can lead to unauthorized access and devastating data breaches. The role of automated rotation systems in safeguarding cloud secrets becomes even more critical in preventing such security events. To explore further, see how <a href="https://entro.security/blog/secrets-security-in-hybrid-cloud-environments/">secrets security is managed in hybrid cloud environments</a>.</p><p>Automated rotation systems play a pivotal role in enhancing secrets safety by regularly updating access credentials, which minimizes the risk of exploitation. By continuously rotating secrets, these systems mitigate the risk of credential-based attacks, which are increasingly prevalent. Learn more about the complexities of secrets rotation through this <a href="https://aws.plainenglish.io/the-somewhat-complicated-process-of-rotating-secrets-91f0b6962336" rel="noopener">detailed analysis</a>.</p><h3>Integrating NHI Management for Cloud Security</h3><p>To ensure comprehensive cloud security, organizations must incorporate NHI and secrets management into their cybersecurity strategies. This integration is crucial for minimizing security risks while simultaneously achieving a balance between access control and operational efficiency. By employing an automated and systematic approach to managing NHIs and their secrets, businesses can significantly decrease the risk of unauthorized access and data leaks.</p><p>For a practical example, consider how <a href="https://entro.security/blog/how-elastic-scaled-secrets-nhi-security-elastics-playbook-from-visibility-to-automation/">Elastic successfully scaled secrets and NHI security</a>. This case study reveals how strategic planning and automation can help pivot operations towards a more secure and efficient framework. The approach demonstrates the necessity of establishing visibility and control, ensuring that organizations can navigate the challenges of cloud-centric infrastructures effectively.</p><p>NHIs empower cybersecurity teams to leverage insights and implement security measures that align with their operational goals. By keeping pace with technological advancements, organizations can enhance their cybersecurity postures and remain resilient in evolving threats, ensuring their cloud secrets stay protected in all scenarios.</p><h3>Understanding the Threat Landscape for Cloud Environments</h3><p>How prepared is your organization to fend off sophisticated cyber threats? The move to cloud environments has brought unparalleled scalability and flexibility but not without introducing a complex web of security challenges. While humans have traditionally been the focal point in identity and access management (IAM), digital demands that Non-Human Identities (NHIs) are equally prioritized in cybersecurity frameworks.</p><p>NHIs, much like human identities, are susceptible to attacks. Cybercriminals are continually devising ways to exploit machine identities, using them as gateways to infiltrate organizations’ infrastructures. These threats are further exacerbated by the rapid pace at which technology evolves, increasing the attack surface at an alarming rate. A recent report highlights that 68% of organizations have experienced attacks where machine identities were the primary target.</p><p>To mitigate such risks, organizations should adopt holistic NHI management strategies. This includes not only technological interventions but also fostering a culture of security awareness across departments.</p><h3>Fostering Collaboration Between Security and R&amp;D Teams</h3><p>Have you considered how the disparity between your security and R&amp;D teams might be a potential security vulnerability? In many organizations, these two departments often operate in silos despite their interdependent roles. The lack of collaboration can lead to oversight, especially in managing NHIs, where secrets might be embedded in deployment pipelines, unnoticed by security reviewers.</p><p>To address this, fostering an understanding between security professionals and developers is vital. Collaborative platforms and integrated tools that provide visibility into the entire NHI lifecycle are crucial in bridging these gaps. For instance, tools that allow developers to flag potential security issues early in the development cycle can significantly reduce vulnerabilities. This proactive approach encourages engineers and security experts to work together, ensuring that security is embedded into the development process right from the start, leaving no room for complacency.</p><h3>Building a Resilient Security Posture with Automated Systems</h3><p>With cyber threats becoming more sophisticated, how effective are automated systems in fortifying your security stance? Automated solutions for cloud secrets and NHIs management play a pivotal role in creating a robust security posture. These systems minimize human error, reduce the time-to-detect threats, and provide agility in responding to incidents.</p><p>The deployment of automated secrets rotation systems is one such measure. By regularly updating credentials, these systems minimize the lifespan of vulnerabilities, making it more challenging for threats to capitalize on static secrets. A pertinent example of effective automation can be explored in coordination with <a href="https://www.reddit.com/r/kubernetes/comments/nkblpg/secret_rotation_via_cronjob/" rel="noopener">secret rotation strategies via cron jobs</a>, which illustrate how a systematic approach to credential management can mitigate potential leakage risks.</p><p>However, automation doesn’t operate in a vacuum. It should be complemented by robust policies, active monitoring, and continuous education of staff to ensure that these technologies are functioning optimally and in alignment with the organization’s broader security objectives.</p><h3>Evaluating NHIs’ Lifecycle for Enhanced Security</h3><p>Is your organization equipped to manage the full lifecycle of Non-Human Identities? Comprehensive NHI management spans several critical stages—from discovery and classification to monitoring, renewal, and decommissioning. Each phase demands different strategies and tools to ensure that machine identities are protected throughout their lifecycle.</p><p>During the discovery and classification stage, identifying all active NHIs within your network is vital. Utilizing advanced analytics and AI-driven platforms can expedite this process, offering a real-time overview of active machine identities along with their associated secrets and permissions.</p><p>Once identified, monitoring these NHIs for abnormal activities or patterns is crucial. Organizations can benefit from anomaly detection models that alert security teams to potential breaches or misuse of machine credentials. This constant surveillance ensures any suspicious activity is swiftly addressed, nullifying threats before they escalate to full-blown incidents.</p><p>Finally, at the end of an NHI’s lifecycle, secure decommissioning ensures that retired identities and their secrets are purged from active directories and networks. Automated decommissioning tools can accelerate this process, closing potential security gaps that may arise from neglected machine identities.</p><h3>The Role of Policy Enforcement in Secrets Management</h3><p>Are there effective policies in place to manage secrets efficiently? Policy enforcement is an often-overlooked aspect of secrets management. Without firm policies, even well-automated systems can fail to deliver the intended outcomes. Policies should define how secrets and NHIs are created, used, rotated, and retired, offering a structured framework for all stakeholders involved.</p><p>Comprehensive audit trails, as part of policy enforcement, offer historical insights into secret use, empowering organizations to make informed decisions and forecasts. These trails are also invaluable for compliance, when they provide concrete evidence of security measures post-implementation.</p><p>To explore successful policy frameworks, consider engaging with resources like <a href="https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-add-certificate-authority" rel="noopener">IBM’s approach to secrets management in the cloud</a> or <a href="https://aps.autodesk.com/en/docs/applications/v1/developers_guide/basics/secret_rotation" rel="noopener">Autodesk’s best practices in secret rotation</a>.</p><p>Policy frameworks, combined with continuous employee training, prompt organizations to remain agile and responsive to changing threats. By establishing stringent controls and guiding their workforce on best practices, businesses can build resilient defenses to safeguard their Non-Human Identities effectively.</p><p>Organizations ready to embrace a comprehensive NHI management strategy will find themselves better positioned to navigate the challenges of the cloud-centric. By prioritizing active collaboration, leveraging automation, and enforcing robust policies, cybersecurity teams can ensure their infrastructures remain secure against the backdrop of a rapidly evolving threats.</p><p>With technologies advance, so too must our approaches to security. Keeping Non-Human Identities updated and protected will be crucial in maintaining system integrity and protecting sensitive data from unauthorized access.</p><p>The post <a href="https://entro.security/are-cloud-secrets-safe-with-automatic-rotation-systems/">Are cloud secrets safe with automatic rotation systems</a> appeared first on <a href="https://entro.security/">Entro</a>.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/02/are-cloud-secrets-safe-with-automatic-rotation-systems/" data-a2a-title="Are cloud secrets safe with automatic rotation systems"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fare-cloud-secrets-safe-with-automatic-rotation-systems%2F&amp;linkname=Are%20cloud%20secrets%20safe%20with%20automatic%20rotation%20systems" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fare-cloud-secrets-safe-with-automatic-rotation-systems%2F&amp;linkname=Are%20cloud%20secrets%20safe%20with%20automatic%20rotation%20systems" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fare-cloud-secrets-safe-with-automatic-rotation-systems%2F&amp;linkname=Are%20cloud%20secrets%20safe%20with%20automatic%20rotation%20systems" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fare-cloud-secrets-safe-with-automatic-rotation-systems%2F&amp;linkname=Are%20cloud%20secrets%20safe%20with%20automatic%20rotation%20systems" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fare-cloud-secrets-safe-with-automatic-rotation-systems%2F&amp;linkname=Are%20cloud%20secrets%20safe%20with%20automatic%20rotation%20systems" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://entro.security/">Entro</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Alison Mack">Alison Mack</a>. Read the original post at: <a href="https://entro.security/are-cloud-secrets-safe-with-automatic-rotation-systems/">https://entro.security/are-cloud-secrets-safe-with-automatic-rotation-systems/</a> </p>

What new technologies are boosting Agentic AI capabilities

  • None
  • Published date: 2026-02-01 00:00:00

None

<h2>How Are Non-Human Identities Revolutionizing Cybersecurity?</h2><p>Did you know that machine identities, also known as Non-Human Identities (NHIs), are becoming pivotal? With digital continues to expand, the need for robust security measures grows in parallel. NHIs, a crucial component, are quickly transforming the way organizations approach security, particularly in cloud-based environments.</p><h3>The Role of Non-Human Identities in Cybersecurity</h3><p>Non-Human Identities (NHIs) play an indispensable role. These machine identities are forged by coupling an encrypted password, token, or key (often referred to as the “Secret”) with the permissions granted by a destination server. Think of it like a passport and visa system, where the Secret is the passport and the permissions are the visa.</p><p>The strategic management of NHIs and their Secrets involves not only securing these identities but also monitoring their behavior. By focusing on these elements, organizations can bridge the gap between security and R&amp;D teams, ensuring a secure, uninterrupted flow of operations.</p><h3>Why NHI Management is Essential Across Industries</h3><p>Organizations across various sectors, such as financial services, healthcare, and DevOps, are increasingly adopting cloud environments. This shift necessitates robust NHI management to address potential security gaps. A comprehensive approach to managing these identities can significantly decrease the risk of breaches and data leaks, thus safeguarding sensitive data.</p><ul> <li><strong>Reduced Risk:</strong> By proactively identifying and mitigating security threats, organizations can minimize the possibility of breaches.</li> <li><strong>Improved Compliance:</strong> Meeting regulatory requirements through effective policy enforcement and thorough audit trails is now more streamlined than ever.</li> <li><strong>Increased Efficiency:</strong> With automation at its core, managing NHIs allows security teams to focus on more strategic initiatives, leveraging human intelligence where it is most needed.</li> <li><strong>Enhanced Visibility and Control:</strong> A centralized view for access management and governance offers unparalleled control over network security.</li> <li><strong>Cost Savings:</strong> Automation of secrets rotation and decommissioning of NHIs reduces operational costs significantly.</li> </ul><h3>Advancing Cybersecurity: From Discovery to Threat Detection</h3><p>An effective NHI management strategy considers all lifecycle stages, from discovery and classification to threat detection and remediation. This comprehensive approach stands in stark contrast to point solutions like secret scanners, which may offer limited protection. NHI management platforms provide insights into ownership, permissions, usage patterns, and potential vulnerabilities, which are crucial for implementing <a href="https://entro.security/blog/iast-vs-rasp-and-their-blindspots-in-non-human-identity-management/">context-aware security</a>.</p><h3>Insights into Agentic AI: Transforming Operations</h3><p>The integration of NHIs with Agentic AI brings transformative capabilities to organizations, enabling them to stay ahead of potential threats. Agentic AI leverages the intelligence of NHIs for autonomous decision-making, optimizing operations, and enhancing security frameworks. Companies across various industries are already witnessing these advancements. For example, a <a href="https://christophernoessel.medium.com/agentive-tech-and-agentic-ai-cousins-not-adversaries-2a2fa37c3134" rel="noopener">recent study</a> highlights how Agentic AI technologies are cousins, not adversaries, to traditional AI systems, working hand in hand to bolster security measures.</p><h3>Practical Applications of NHIs and Agentic AI</h3><p>In <a href="https://inform.tmforum.org/research-and-analysis/reports/new-generation-intelligent-operations-agentic-ai-driven-transformation" rel="noopener">intelligent operations</a>, NHIs are being utilized to create a secure infrastructure that accommodates the rapid scaling demands of modern businesses. This includes automating routine security checks and anomaly detection, thus relieving IT teams from manual oversight and enabling them to focus on strategic growth.</p><p>Moreover, NHIs play a crucial role in industries like <a href="https://entro.security/blog/nhi-threats-mitigations-pt1/">banking</a> and healthcare, where securing machine identities is paramount to prevent unauthorized access and ensure compliance with stringent regulations.</p><p>By leveraging Agentic AI with NHIs, companies can enhance their AI capabilities, opening new avenues for innovation and efficiency in operations. These technologies promise to deliver unmatched security levels while facilitating a seamless transition to more advanced.</p><h3>Challenges and Misconceptions in NHI Management</h3><p>What are the primary challenges when managing Non-Human Identities (NHIs) in cybersecurity? With NHIs become increasingly integral to securing digital environments, organizations face distinct obstacles that must be addressed to ensure robustness. One of the prominent challenges involves the need to maintain a delicate balance between accessibility and security. While NHIs simplify automated processes, they also create opportunities for exposure if not managed correctly.</p><p>A common misconception is that merely deploying a security solution is enough to safeguard NHIs. In reality, the dynamic nature of cyber threats requires continuous adaptation and update of security protocols. Additionally, effective NHI management demands a deep integration with existing IT infrastructure—something many organizations underestimate, leading to potential vulnerabilities.</p><h3>Industry-Specific NHI Applications and Impacts</h3><p>Each industry faces unique challenges that NHIs can help address. For instance, in finance, NHIs streamline transactions while maintaining high security through efficient monitoring of access and authentication. With <a href="https://verafin.com/2025/02/agentic-ai-ushers-in-a-new-age-of-automation-for-financial-crime-management/" rel="noopener">Agentic AI</a> transforms financial crime management, NHIs collaborate to form a defense against fraud and unauthorized transactions.</p><p>In healthcare, NHIs ensure that sensitive patient data remains secure by controlling access and permissions in line with privacy regulations. This is particularly crucial in cloud environments where healthcare providers can leverage AI-driven insights without compromising data integrity.</p><p>DevOps and SOC teams utilize NHIs for seamless integration and operation of CI/CD pipelines, automating identity-related tasks and reducing human interference. Automation not only enhances efficiency but also allows teams to detect and respond to threats proactively.</p><h3>Strategic Implementation and Best Practices</h3><p>How should organizations approach the strategic implementation of NHIs for maximum effectiveness? First, an organization must conduct an initial audit to classify and understand its entire inventory of machine identities. This audit is the foundation for developing a centralized management system that allows for real-time monitoring and adaptive decision-making.</p><p>Moreover, employing a layered security approach—incorporating firewalls, encryption, and continuous monitoring—ensures no single point of failure. Organizations should also emphasize training and awareness, empowering employees to understand the significance and usage of NHIs to avoid inadvertent security lapses.</p><p>Furthermore, aligning NHI management with broader enterprise strategies facilitates a smoother transition, ensuring it supports business objectives rather than acting as a siloed IT initiative. Businesses can facilitate this by establishing cross-departmental collaborations that foster understanding and integration between IT, security, and business units.</p><h3>The Future of NHI Management</h3><p>What’s next for NHI management, and how can companies prepare for this evolution? Embracing emerging technologies and trends, such as the integration of Agentic AI, will be pivotal. These advancements provide new opportunities for predictive security measures, allowing organizations to anticipate and mitigate threats before they materialize.</p><p>Where <a href="https://aimagazine.com/articles/aws-creates-new-group-focused-on-agentic-ai" rel="noopener">new initiatives</a> by tech giants illustrate, investing in AI-driven identity management solutions will not only enhance security but also improve decision-making processes across the board. Organizations that align with these trends will likely see benefits in efficiency, security, and competitive advantage.</p><p>In addition to technological advancements, evolving regulatory will shape how NHIs are managed. Staying ahead of these changes by actively participating in industry forums, workshops, and discussions on best practices and compliance measures can offer a significant edge.</p><p>Organizations must remain agile, continuously refining their NHI management strategies to address changing cybersecurity. A proactive approach, grounded in comprehensive data and resources, can help enterprises confidently deploy NHIs and safeguard their digital operations with utmost efficacy.</p><p>By recognizing the integral role NHIs play, businesses can transform potential vulnerabilities into fortified strengths, unlocking new possibilities for growth and innovation.</p><p>To explore more about NHI management and security enhancements, check out how <a href="https://entro.security/blog/a-new-era-of-non-human-identities-nhidr/">organizations are adapting</a> to Non-Human Identities.</p><p>The post <a href="https://entro.security/what-new-technologies-are-boosting-agentic-ai-capabilities/">What new technologies are boosting Agentic AI capabilities</a> appeared first on <a href="https://entro.security/">Entro</a>.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/02/what-new-technologies-are-boosting-agentic-ai-capabilities/" data-a2a-title="What new technologies are boosting Agentic AI capabilities"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fwhat-new-technologies-are-boosting-agentic-ai-capabilities%2F&amp;linkname=What%20new%20technologies%20are%20boosting%20Agentic%20AI%20capabilities" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fwhat-new-technologies-are-boosting-agentic-ai-capabilities%2F&amp;linkname=What%20new%20technologies%20are%20boosting%20Agentic%20AI%20capabilities" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fwhat-new-technologies-are-boosting-agentic-ai-capabilities%2F&amp;linkname=What%20new%20technologies%20are%20boosting%20Agentic%20AI%20capabilities" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fwhat-new-technologies-are-boosting-agentic-ai-capabilities%2F&amp;linkname=What%20new%20technologies%20are%20boosting%20Agentic%20AI%20capabilities" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fwhat-new-technologies-are-boosting-agentic-ai-capabilities%2F&amp;linkname=What%20new%20technologies%20are%20boosting%20Agentic%20AI%20capabilities" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://entro.security/">Entro</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Alison Mack">Alison Mack</a>. Read the original post at: <a href="https://entro.security/what-new-technologies-are-boosting-agentic-ai-capabilities/">https://entro.security/what-new-technologies-are-boosting-agentic-ai-capabilities/</a> </p>

Can Agentic AI handle complex cloud-native security tasks

  • None
  • Published date: 2026-02-01 00:00:00

None

<h2>How Do Non-Human Identities Fit into Cloud-Native Security?</h2><p>Is your current cybersecurity strategy equipped to handle the complexities posed by cloud-native environments and machine identities? Cloud computing’s rapid growth has invited a unique set of security challenges that organizations must address to protect their digital assets. A pivotal component is the management of Non-Human Identities (NHIs), a critical factor in safeguarding against data breaches and maintaining compliance.</p><h3>Understanding Non-Human Identities and Their Role in Security</h3><p>Non-Human Identities are essential concepts, particularly within cloud-native environments. Essentially, NHIs represent machine identities that incorporate encrypted passwords, tokens, or keys—collectively known as “secrets”—and the permissions granted to these secrets by a destination server. This intricate structure is akin to the way a passport and visa work together to allow international travel; the “tourist” is the machine identity, while the “passport” and “visa” represent the secrets and permissions, respectively.</p><p>Managing NHIs involves securing both the identities and their accompanying credentials. This includes monitoring behavior within systems to ensure the identities are used appropriately. Without comprehensive oversight, organizations risk leaving themselves vulnerable to cyber threats. By focusing on NHIs, businesses can bridge security gaps that often arise due to the disconnect between security teams and R&amp;D, thereby fostering a more robust cloud security posture.</p><h3>The Importance of Comprehensive NHI Management</h3><p>Why is a holistic approach to NHI management beneficial over fragmented solutions? Unlike point solutions, which may focus solely on scanning secrets, comprehensive NHI management platforms offer a robust array of insights. They provide visibility into ownership, permissions, usage patterns, and vulnerabilities, empowering organizations to implement context-aware security measures.</p><p>Effective NHI management encompasses all lifecycle stages, from discovery and classification to threat detection and remediation. By addressing each phase thoroughly, organizations can ensure they are not just reacting to security incidents but proactively safeguarding their environments.</p><ul> <li><strong>Reduce Risk:</strong> By identifying and mitigating potential security threats proactively, the risk of data breaches is significantly decreased, safeguarding sensitive information.</li> <li><strong>Improve Compliance:</strong> NHIs assist organizations in meeting rigorous regulatory requirements, offering capabilities like policy enforcement and audit trails that streamline compliance efforts.</li> <li><strong>Increase Efficiency:</strong> Automating NHI and secrets management provides security teams more time to engage in strategic initiatives, promoting operational efficiency.</li> <li><strong>Enhance Visibility and Control:</strong> A centralized view of access management and governance offers unparalleled control, simplifying identity management.</li> <li><strong>Cost Savings:</strong> By automating processes such as secrets rotation and decommissioning NHIs, organizations can significantly reduce operational costs.</li> </ul><h3>Real-World Scenario: The Healthcare Industry</h3><p>Consider the healthcare industry—a sector where data protection is not just a regulatory requirement but a fundamental component of patient trust. With the increase in telehealth and digitized patient records, the need for stringent security measures has never been higher. Incorporating NHI management into a healthcare organization’s cybersecurity strategy ensures that machine identities interacting with sensitive data are adequately protected against unauthorized access.</p><p>The security protocols established through NHIs can be likened to a healthcare provider wearing multiple layers of gloves and masks—each layer provides an additional level of security, ensuring patient data remains confidential and secure.</p><h3>Agentic AI: Revolutionizing Cloud-Native Security</h3><p>How might emerging technologies further enhance cloud-native security frameworks? Enter Agentic AI—a revolutionary concept that holds promise for managing complex security tasks within cloud-native environments. Agentic AI leverages sophisticated algorithms to autonomously monitor, detect, and respond to security threats, thereby enhancing the efficiency and reliability of cybersecurity measures. For more insights on how Agentic AI is reshaping cloud security, you can explore articles like <a href="https://outshift.cisco.com/blog/jarvis-agentic-platform-engineering-outshift" rel="noopener">this one</a> from Cisco.</p><p>Integrating technologies like Agentic AI with NHI management can equip organizations with an adaptive, resilient security apparatus capable of tackling diverse threats in real-time. The collaboration between these technologies represents a formidable advancement in cybersecurity, one that offers businesses an added layer of protection and operational excellence.</p><p>For companies operating in hybrid cloud environments, understanding how to scale secrets and NHI security can provide a competitive edge. Organizations can learn more about these strategies from resources such as <a href="https://entro.security/blog/how-elastic-scaled-secrets-nhi-security-elastics-playbook-from-visibility-to-automation">Elastic’s playbook on scaling NHI security</a>.</p><h3>Creating a Secure Future</h3><p>The importance of a robust cloud-native security posture cannot be overstated. NHIs play a vital role, providing a secure foundation upon which businesses can build their digital operations. By addressing the security challenges associated with machine identities, organizations not only protect their data but also create an environment conducive to innovation and growth.</p><p>Leveraging advances in technology, such as the integration of Agentic AI, can further enhance these efforts, making it easier for organizations to achieve their security goals. With industries continue to evolve, the strategic management of NHIs will ensure that they remain protected, compliant, and efficient. Explore more about the application of these advanced methodologies in securing hybrid cloud environments at <a href="https://entro.security/blog/secrets-security-in-hybrid-cloud-environments/">this link</a>.</p><p>For those eager to explore further, the implementation of NHI and secrets in enhancing DevOps and SOC team efficiency is discussed comprehensively in various <a href="https://rafay.co/ai-and-cloud-native-blog-author/angela" rel="noopener">articles by cloud-native security experts</a>. Businesses can harness these insights to elevate their security frameworks and achieve a more robust cybersecurity posture.</p><h3>Integration of NHIs in Financial Services</h3><p>Can a cutting-edge approach to Non-Human Identities revolutionize security in financial services? Indeed, the financial sector is a prime beneficiary of robust NHI management, given its stringent regulatory requirements and the need to protect extensive volumes of sensitive data. The management of NHIs shapes a fortified security environment ensuring that machine identities, such as those used by automated trading systems or customer service chatbots, are secure and efficiently managed.</p><p>In traditional security models, human oversight was relied upon heavily to monitor and control access. However, the digital transformation in financial services demands more sophisticated, automated security controls. The adoption of a comprehensive NHI management system aids financial institutions by providing advanced monitoring and automated alert systems that identify anomalies in real-time, thus safeguarding financial data against breaches and cyber threats.</p><h3>Impact on DevOps and Continuous Deployment</h3><p>How does the integration of NHIs enhance DevOps operations? When development teams adopt agile methodologies and continuous deployment, the increase in automated processes and workflows necessitates an elevated security posture. NHIs play a pivotal role by offering secure, automated management of machine identities that align with DevOps practices.</p><p>With scalable NHIs, DevOps teams can ensure that development, testing, and production environments maintain integrity and security. These systems can manage secrets dynamically, preventing exposure and ensuring that credentials are only accessible to their respective machine identities. By focusing on automating NHIs, DevOps teams can reduce bottlenecks, allowing faster release cycles without compromising security.</p><p>Furthermore, seamless integration between security tools and DevOps platforms offers a streamlined approach for managing identities and secrets across various stages of the deployment lifecycle. With adequate NHI management, teams can detect and remediate issues swiftly, allowing developers to focus on building features rather than fighting security fires.</p><h3>The Role of NHIs in Enhancing AI Systems</h3><p>What role do NHIs play in safeguarding AI systems? AI models and systems, increasingly integral across industries, operate with vast amounts of data and require robust security practices. The machine identities managing these AI systems must be protected from unauthorized access and manipulation.</p><p>NHI management ensures that AI systems have controlled access to data, maintaining the trust and integrity of the models used in decision-making. For instance, an autonomous financial advisory application must secure client information while providing personalized recommendations, reliant on secrets management to authenticate and authorize access to sensitive data.</p><p>Additionally, with AI systems evolve, managing the lifecycle of machine identities strains traditional security frameworks. Comprehensive NHI solutions acknowledging these complexities provide automated methods to handle secrets rotation and identity decommissioning, ensuring that AI systems remain secure and compliant.</p><h3>Adopting Best Practices for NHI Management</h3><p>How can organizations adopt best practices for NHI management to strengthen their cybersecurity? By embracing a multi-faceted strategy, companies can significantly enhance their cloud-native security posture:</p><ul> <li><strong>Data Classification:</strong> Clearly identify and classify all data assets linked to NHIs, offering insights into potential vulnerabilities.</li> <li><strong>Automated Monitoring:</strong> Implement sophisticated monitoring systems that autonomously oversee NHI usage and trigger alerts upon detecting unusual activities.</li> <li><strong>Lifecycle Management:</strong> Develop processes for securely managing the full lifecycle of NHIs from creation to decommissioning.</li> <li><strong>Cross-Departmental Coordination:</strong> Foster communication and collaboration between security, R&amp;D, and IT departments to ensure comprehensive coverage and eliminate silos.</li> <li><strong>Policy and Governance:</strong> Establish policies to define the proper use of NHIs and enforce these policies through governance frameworks.</li> </ul><p>In deploying these practices, organizations can establish a more secure environment, enhancing both productivity and trust among stakeholders. Proper NHI management is not merely a technical challenge but a strategic necessity integral to modern cybersecurity frameworks. For further exploration of cloud-native security advancements, readers can delve into the benefits of <a href="https://entro.security/blog/entro-custom-secrets-self-serve-detection-rules-across-code-cloud-and-agents/">custom secrets self-serve detection rules</a>.</p><p>Leveraging strategies that emphasize the importance of NHIs will allow organizations to stay ahead of emerging threats. Where advancements in AI and cloud technologies continue, businesses are poised to refine their security postures and protect their digital assets effectively.</p><p>Where digital offers unparalleled opportunities but also amplifies security risks. Given the increasing reliance on AI and cloud technologies, understanding and addressing these complexities through strategic NHI management safeguards organizational assets. Explore more about the innovative methodologies driving Agentic AI’s role in security through <a href="https://entro.security/blog/keeping-security-in-stride-why-we-built-entros-third-pillar-for-agentic-ai/">our third pillar of Agentic AI</a> research.</p><p>The resilient strategies adopted for NHI management in diverse industries underscore the necessity of a proactive security stance. Organizations are urged to focus on strategic NHI management, propelling them into a future where security is seamlessly integrated with innovation.</p><p>The post <a href="https://entro.security/can-agentic-ai-handle-complex-cloud-native-security-tasks/">Can Agentic AI handle complex cloud-native security tasks</a> appeared first on <a href="https://entro.security/">Entro</a>.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/02/can-agentic-ai-handle-complex-cloud-native-security-tasks/" data-a2a-title="Can Agentic AI handle complex cloud-native security tasks"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fcan-agentic-ai-handle-complex-cloud-native-security-tasks%2F&amp;linkname=Can%20Agentic%20AI%20handle%20complex%20cloud-native%20security%20tasks" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fcan-agentic-ai-handle-complex-cloud-native-security-tasks%2F&amp;linkname=Can%20Agentic%20AI%20handle%20complex%20cloud-native%20security%20tasks" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fcan-agentic-ai-handle-complex-cloud-native-security-tasks%2F&amp;linkname=Can%20Agentic%20AI%20handle%20complex%20cloud-native%20security%20tasks" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fcan-agentic-ai-handle-complex-cloud-native-security-tasks%2F&amp;linkname=Can%20Agentic%20AI%20handle%20complex%20cloud-native%20security%20tasks" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F02%2Fcan-agentic-ai-handle-complex-cloud-native-security-tasks%2F&amp;linkname=Can%20Agentic%20AI%20handle%20complex%20cloud-native%20security%20tasks" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://entro.security/">Entro</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Alison Mack">Alison Mack</a>. Read the original post at: <a href="https://entro.security/can-agentic-ai-handle-complex-cloud-native-security-tasks/">https://entro.security/can-agentic-ai-handle-complex-cloud-native-security-tasks/</a> </p>

Trump Sues IRS For $10 Billion For All Those Taxes He Never Paid

  • Doktor Zoom
  • Published date: 2026-01-31 16:00:40

Gosh, wonder whether the IRS will settle?

Donald Trump is once again suing the federal government in hopes certainty of a great big taxpayer-funded payout. This time hes demanding $10 billion from the IRS to cover the great harm done to hi… [+5102 chars]

HRIC – HRIC Weekly Brief (January 13, 2026)

  • Cindy Carter
  • Published date: 2026-01-31 00:41:55

On Monday, Hong Kong pro-democracy figure Jimmy Lai appeared in court for a mitigation hearing alongside eight other defendants; the newly released 2025 Li Community Digital Activism Annual Report documents digital rights developments amid tightening censorsh…

Top News On Monday, Hong Kong pro-democracy figure Jimmy Lai appeared in court for a mitigation hearing alongside eight other defendants. The hearing is scheduled to last four days. Court watchers,… [+8807 chars]

Blockchain Penetration Testing: Definition, Process, and Tools

  • None
  • Published date: 2026-01-31 00:00:00

None

<div class="elementor-widget-container" morss_own_score="2.0" morss_score="381.5"> <p>Blockchain Penetration Testing simulates real-world cyberattacks on blockchain systems to identify vulnerabilities before attackers can exploit them. </p> <p>On September 14, 2021, the Solana blockchain network went offline for 17 hours during the Grape Protocol IDO (Initial DEX Offering) due to a Distributed Denial-of-Service (DDoS) attack. </p> <p>In distributed blockchain applications, penetration testing frameworks have demonstrated throughput rates up to 717.7 transactions per second with average latencies as low as 0.19 seconds, indicating high efficiency in attack detection scenarios, according to a 2022 study by  Yoganand Kissoon, titled “Detecting Vulnerabilities in Smart Contracts within Blockchain: A Review and Comparative Analysis of Key Approaches”. Blockchain penetration testing features targeted testing, advanced testing techniques, cryptography and tokenomics checks. </p> <p>Over $2.17 billion had been stolen by midyear, with a $1.5 billion exchange hack on Bybit accounting for the majority of the losses, according to The Chain Analysis Crypto Crime Report 2025.</p> <p>The Blockchain Penetration Testing process involves identifying and exploiting vulnerabilities across four key layers: blockchain networks (Layer 1), smart contracts, user wallets, and consensus mechanisms. Testers assess security risks and provide detailed reports with remediation recommendations to prevent irreversible financial loss.</p> <p>Blockchain penetration testing differs from traditional testing due to its focus on decentralised, immutable systems, whereas other types of penetration testing target centralised networks and applications. It addresses blockchain-specific vulnerabilities, such as reentrancy and oracle attacks, unlike SQL injection and XSS in other pentesting types. Specialised tools like Slither and Mythril are used for blockchain analysis, while traditional pentesters rely on tools like Nessus and Burp Suite.</p> <h2>What is Blockchain penetration testing?</h2> <p>Blockchain penetration testing is a controlled simulation of a cyberattack on blockchain systems to identify vulnerabilities in decentralised applications (dApps), nodes, consensus mechanisms, and smart contracts. </p> <figure><img decoding="async" src="data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%201024%20768'%3E%3C/svg%3E" title="Blockchain Penetration Testing: Definition, Process, and Tools 1"></figure> <p>Other names for blockchain penetration include blockchain penetration testing, blockchain security audit, and blockchain security assessment. The term “blockchain penetration testing” emerged in 2014-2015, during the rise of smart contracts, especially as blockchain became more popular.</p> <p>The process focuses on three critical areas. First, Smart Contracts are tested for logic errors and unique vulnerabilities such as Reentrancy attacks and Integer Overflows, which is crucial given that immutable code cannot be easily patched. Second, the Consensus Mechanism is assessed for resilience against network-level threats, including 51% attacks, Sybil attacks, and Double-Spending scenarios. Finally, Decentralised Applications (dApps) are evaluated to identify security gaps in the off-chain components, including APIs, wallet integration points, and user interfaces.</p> <h3>How does blockchain penetration testing work?</h3> <p>Blockchain penetration testing involves mimicking a real-world attack on a complete blockchain ecosystem to identify security gaps before they result in irreversible loss. The process consists of four distinct phases: auditing Smart Contracts for logic errors, assessing Nodes for network-level flaws, analyzing Consensus Mechanisms for resistance to manipulation, and examining Wallets and APIs for integration weaknesses.</p> <p>This comprehensive testing identifies vulnerabilities specific to decentralised systems, including Smart Contract flaws (such as Reentrancy or business logic bugs), Consensus attacks (like 51% attacks or Sybil attacks), and Cryptographic weaknesses (such as insecure key management or weak entropy). It also addresses traditional risks like Denial of Service (DoS) against malicious nodes. The ultimate goal is to validate that the immutable ledger and the assets it secures are resilient against both financial theft and integrity manipulation.</p> <h3>What are the features of blockchain penetration testing? </h3> <p>Six features of blockchain penetration testing are listed below.</p> <ol> <li><strong>Targeted Testing: </strong>Targeted testing focuses on blockchain-specific components such as smart contracts, decentralised application logic and consensus mechanisms. The goal of this targeted testing is to identify and fix blockchain-specific risk (insufficient access controls, irreversible transactions and unique attack vectors (front-running, bridge attacks).</li> <li><strong>Advanced Testing Techniques: </strong>Mutation testing, property-based testing, and fuzz testing are used to discover vulnerabilities in a complex blockchain environment. The security team usually employs model-based and search-based testing to evaluate system behaviour under different scenarios.</li> <li><strong>Layered and Comprehensive Coverage:</strong> Multiple layers of the blockchain stack, including the network, protocol, application, and smart contract layers, are tested during blockchain penetration testing. The purpose of this multi-layer testing is to assess the functional correction and security level of blockchains.</li> <li><strong>Automation and Tool Support: </strong>Automated frameworks and tools are used to test large and complex blockchains efficiently. Results from automated testing are compared with custom frameworks to find vulnerabilities that standard tools often miss.</li> <li><strong>Reporting and Analysis: </strong>A detailed detection report is generated for stakeholders and developers. This report provides coverage analysis, findings from all testing of blockchain functionalities, remediation advice, and business impact analysis.</li> <li><strong>Cryptography and tokenomics check:</strong> Cryptography and tokenomics checks are performed on blockchain to identify security flaws of keys, encryption, signatures, wallets, and economic logic (inflation, token manipulation).</li> </ol> <h2>How to perform blockchain penetration testing?</h2> <p>Blockchain penetration testing involves understanding the blockchain architecture, identifying attack vectors, and testing various blockchain functionalities. Once testing is done, pentesters document all the findings and submit a report with remediation recommendations. </p> <figure><img decoding="async" src="data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%20724%201024'%3E%3C/svg%3E" title="Blockchain Penetration Testing: Definition, Process, and Tools 2"></figure> <p>Listed below are 10 steps of the blockchain penetration testing process.</p> <h3>1. Gather Contracts, Nodes, and Infrastructure Details</h3> <p>The blockchain penetration testing process begins by collecting details of the entire blockchain system, including contracts, nodes, and infrastructure components. Pentesters obtain the source code of smart contracts. They document the configuration of blockchain nodes (validator nodes, full nodes) while collecting deployment addresses and network details. This step also includes mapping infrastructure such as firewalls, off-chain microservices, cloud services, load balancers, and databases. Pentesters rely on GitHub or GitLab to collect version histories, architecture diagrams, and documentation from repositories. </p> <p>The pentesting team uses tools like GitHub and Remix to fetch smart contract source code, while Etherscan helps them track all deployment details across the network. Infrastructure scanning and mapping are typically performed with tools such as Nmap and Nessus. The team collects information about all third-party libraries and dependencies; missing any detail can lead to overlooking a vulnerability in external code.</p> <p>It is important to create an accurate inventory of all blockchain components and systems so that no element or system is left out during a blockchain security audit. A comprehensive inventory list serves as a foundation for upcoming audit stages. </p> <p>Once all component details are collected, the next step is to define the scope and objectives of the blockchain penetration test and to set clear engagement rules.</p> <h3>2. Define Scope, Objectives, Engagement Rules</h3> <p>The blockchain penetration testing team defines the test scope by setting clear boundaries, such as which components will be audited and which are not part of the testing process.  They communicate with clients to establish clear expectations and set engagement rules, such as how vulnerabilities will be reported and which communication protocols will be followed. </p> <p>A decision also needs to be made about methodologies (dynamic testing, static analysis) used in the testing process. The purpose of defining the scope and objectives of pentesting is to ensure smooth cooperation between teams, mitigate legal risks, and avoid misunderstandings during a blockchain security assessment. </p> <p>Pentesters rely on tools like Jira and Notion to organise tasks and track project progress. Additionally, risk assessment frameworks (MITRE, OWASP) guide them through the assessment process. </p> <p>Pentesters obtain formal consent from the client via a consent form that outlines clear objectives (security, performance) and the scope of blockchain penetration testing, along with clear rules of engagement (communication protocols, severity rating model, access requirements).</p> <p>This consent form serves as a green light for the penetration testing team to begin the blockchain security audit process with automated scanning. </p> <h3>3. Scan with Automated Blockchain Scanners</h3> <p>This phase involves deploying automated scanners to rapidly identify known vulnerabilities and inefficiencies within the smart contract code and blockchain infrastructure. The security team utilises Static Application Security Testing (SAST) tools like Slither, Mythril, and Securify to analyse the source code at rest, detecting issues such as integer overflows, reentrancy risks, and gas inefficiencies without executing the program. To complement this, dynamic analysis and fuzzing tools like Echidna and Manticore are employed to test the code’s behaviour under stress by generating random inputs, while runtime simulation platforms like Tenderly allow pentesters to monitor and debug execution flow in real-time.</p> <p>The primary purpose of this automation is to generate a preliminary vulnerability baseline, allowing the team to quickly catch “low-hanging fruit” and prioritise deeper manual review for complex logic. However, since these tools often produce false positives, human verification is essential to validate the findings. The final output of this step is a prioritised list of potential security risks and code quality metrics, which serves as the roadmap for the subsequent, more intensive manual auditing phase.</p> <h3> 4. Audit Smart Contracts for Logic &amp; Reentrancy</h3> <p>The pentesting team perform a manual audit of smart contracts for logic flaws and reentrancy attacks. They first review the contract architecture and inheritance structure, then map all state variables and storage flows. </p> <p>They walk through the entire code of the contract and analyse the logic for business rules, state transitions, and interactions with other contracts. A step-by-step logic analysis is performed on access controls, modifier behaviour, fee calculation, token transfer flows, and administrative functions. In this step, the team also verifies whether access control is correctly implemented and there are no time-based vulnerabilities in the blockchain environment. They also validate invriants, the rules that must always remain true. A comprehensive review of error handling and event emission is conducted before simulating a real-world attack using custom scripts or fuzzers.</p> <p>Tools like Manticore are used to analyse all possible program execution paths of smart contracts with symbolic input, and Tenderly is used for transaction simulation. This stage helps pentesters identify deep logic flaws that automated tools miss. It verifies the robustness of the contract’s functionality in the blockchain system.</p> <p>A list of vulnerabilities, potential exploits and suggestions for improving contract security is generated as an output of this smart contract audit phase. The Pentesting team continue with the analysis of cryptographic algorithms after testing the smart contracts’ functionality. </p> <h3>5. Analyse Cryptography, RNGs, Signature Schemes</h3> <p>Cryptographic algorithms are core components of blockchain systems as they secure transactions, generate randomness and manage keys. The testing team analyses smart contracts’ cryptographic components by examining the security of hash functions (SHA-256 or Keccak-256), signature algorithms (ECDSA or Ed25519), and Random Number Generators (RNGs). </p> <p>Team starts the analysis by identifying all cryptographic primitives, such as hashing, signatures, encryption algorithms, and key derivation, and continues by evaluating on-chain RNG methods (blockhash() randomness, Chainlink VRF). It’s important to validate randomness because validators, miners or contract owners often manipulate it. </p> <p>Pentesters also verify that keys and secrets are properly stored and managed in the blockchain environment, and the signature validation is strong enough to prevent replay attacks. The purpose of cryptographic analysis is to ensure its strength, as weak cryptography allows attackers to predict randomness, bypass authentication, and forge signatures. </p> <p>Tools such as web3.js, ethers.js, and Chainlink’s VRF testing tools are used to test cryptographic processes and identify vulnerabilities. </p> <p>The output of the cryptography analysis step is a report on the strength of cryptographic implementation, a list of discovered vulnerabilities and recommendations for improving the cryptographic process.</p> <p>The next phase after cryptographic analysis is oracle evaluation to test the integrity of external data. </p> <h3>6. Evaluate Oracles, External Data Integrity</h3> <p>Oracles act as the critical bridge between the blockchain and the real world, feeding external data such as stock prices, weather conditions, or random numbers into smart contracts. Because blockchains cannot access this data natively, the integrity of the Oracle is paramount.</p> <p>In this phase, the penetration testing team evaluates the system’s resilience against Oracle Manipulation and data corruption. The process begins by inventorying all data feeds and verifying that the architecture is decentralised. Relying on a single source creates a Single Point of Failure (SPoF) that attackers can easily exploit to trigger false liquidations or drain funds (often seen in Flash Loan attacks).</p> <p>Testers rigorously assess the data validation logic to ensure the smart contract authenticates the source and rejects outliers or tampered data during transmission. Crucially, they test fallback mechanisms to determine how the system behaves if an Oracle goes offline or returns malicious values.</p> <p>While protocols like Chainlink and Band Protocol are the standards for providing data, testers use development frameworks like Hardhat or Foundry to <em>simulate</em> Oracle failures and inject manipulated price data in a forked environment. The final output is a report detailing the system’s resistance to price manipulation and data downtime, ensuring the contract acts correctly even when the outside world provides bad data.</p> <h3>7. Test Consensus, Finality, Economic Attack Vectors</h3> <p>This phase shifts the focus from code vulnerabilities to Game Theory and network economics. The testing team evaluates the underlying consensus mechanism (such as Proof of Stake or Proof of Work) to determine its resilience against existential network threats like 51% Attacks, Sybil Attacks, and Double-Spending scenarios.</p> <p>A critical component of this step is analysing Finality, guaranteeing that once a transaction is confirmed, it is mathematically irreversible. If finality is weak (e.g., probabilistic rather than deterministic), the chain is vulnerable to “reorgs” (chain reorganisations) that can erase recent transactions.</p> <p>Beyond technical exploits, pentesters simulate Economic Attack Vectors. They assess whether it is financially profitable for a malicious actor to bribe validators, exploit “Nothing-at-Stake” problems, or spam the network to force a Denial of Service (DoS).</p> <p>Since attacking a live public network is impossible, teams use Private Testnets (forked environments) and Transaction Simulators (like Hardhat or custom Python models) to model these high-stress scenarios safely. The final output provides a risk assessment of the network’s decentralised integrity and its ability to withstand coordinated financial attacks.</p> <h3>8. Assess Wallets, Key Management, Frontend Interfaces</h3> <p>Assessment of wallets, key management, and frontend interfaces starts by reviewing private key storage, management, and encryption. The pentesting team also assesses the security of backup and recovery mechanisms for private keys. They evaluate frontend interface security by assessing its resilience against common web vulnerabilities (phishing, cross-site scripting/XSS) and ensuring interfaces follow secure coding practices. </p> <p>This step also requires a detailed examination of wallet-to-smart contract interactions. This examination ensures that sensitive operations (signing transactions) within the blockchain system are fully secured. It also involves assessing the strength of authorisation and authentication systems (Multi-Factor Authentication/MFA, biometric verification).</p> <p>The main purpose of wallet and key management evaluation is to ensure that wallets and private keys are properly secured, as vulnerabilities in these components lead to the theft of digital assets or unauthorised access. </p> <p>The pentesting team uses tools like MetaMask and Ledger for wallet security checks, while Burp Suite and OWASP ZAP are useful for testing frontend security. They use ether.js or Web3.js for testing wallet integrations. </p> <p>The output of this step is a detailed security audit of wallets, key management, and user-facing interfaces, with complete identification of vulnerabilities in these areas of blockchain systems. The security team continues API probing after drafting recommendations to improve the user interface and key management. </p> <h3>9. Probe APIs, RPCs, Rate-limits, Leakage</h3> <p>Blockchain nodes and dApps rely heavily on JSON-RPC endpoints and REST APIs to facilitate communication between the user, the node, and the external world. Because these interfaces often control critical node functions, they are prime targets for attackers.</p> <p>In this phase, the penetration testing team probes these endpoints to identify configuration weaknesses, specifically focusing on Improper Access Control on the JSON-RPC interface (often found on port 8545). If unsecured, these endpoints can allow attackers to execute administrative commands, stop the node, or even unlock wallets managed by the node software.</p> <p>Beyond access control, the team rigorously tests Rate Limiting to ensure the node is resilient against Denial-of-Service (DoS) attacks. Without strict limits, an attacker can flood the node with resource-intensive requests (like eth_getLogs), crashing the service and disrupting network synchronisation.</p> <p>Testers also analyse API responses for Information Leakage, ensuring that while blockchain data is public, the node does not inadvertently expose sensitive metadata, such as peering IP addresses, API keys, or unencrypted user PII. Using tools like Burp Suite and Postman for API manipulation, alongside Nmap for port discovery, the team validates that the communication layer is strictly hardened against abuse.</p> <h3>10. Exploit Safely in Isolated Environments; Retest</h3> <p>An exploit refers to safe testing of the blockchain system against vulnerabilities in an isolated environment. In the early stages, the pentesting team identified multiple vulnerabilities (insecure access controls, gas limit issues, XSS, and front-running). </p> <p>In this final step, pentesters aim to exploit all identified vulnerabilities in a controlled manner to understand the severity and impact of these discovered issues. It involves simulating real-world attacks such as flash loans, front-running, and Sybil attacks on the system, and then monitoring how the system responds to them. The exploit is performed in an isolated environment to avoid disruption to real user data or funds. </p> <p>The purpose of exploiting vulnerabilities is to better understand how attackers leverage them. The testing team conducts retesting to ensure that all system vulnerabilities have been successfully patched and that no new issues have arisen during this phase. The ultimate goal of the exploit and retesting phase is to secure the blockchain system from all angles.</p> <p>Tools like Ganache, Foundry, and Hardhat are commonly used to simulate attacks in controlled environments. These tools help pentesters gain a complete understanding of the system response under stress. The blockchain pentesting team has documented a report detailing a successful exploit, including a PoC demonstrating the fixed vulnerabilities, which were retested. </p> <p>Blockchain pentesting can not be performed by everyone in the IT industry. Therefore, companies usually hire a certified professional and a third-party firm offering blockchain penetration testing, even when they have an in-house security team. Blockchain pentesting requires specialised knowledge and expertise in blockchain concepts, smart contract programming and especially problem-solving.</p> <h2>What expertise is required to perform blockchain penetration testing?</h2> <p>Blockchain penetration testing requires specialised expertise in decentralised architecture, blockchain-specific vulnerabilities detection, the irreversible nature of transactions, and specialised tools beyond basic pentesting. </p> <p>Blockchain pentesters usually build a career first in programming or software development, then specialise in penetration testing. They must have a complete understanding of decentralised architecture, including cryptographic principles, smart contract languages (Solana, Solidity), and consensus protocols. They need expertise in identifying vulnerabilities specific to blockchain.</p> <p>Blockchain penetration testers must have a clear understanding of the irreversible nature of blockchain transactions. It is important to understand the economic aspects (governance structures and tokenomics) when working with decentralised finance (DeFi) applications. They must be proficient with specialised blockchain pentesting tools (Slither, Mythril)as well as traditional testing tools to perform thorough testing of a blockchain system. </p> <p>Blockchain penetration testers must have fundamental knowledge of blockchain systems and cryptographic protocols (ECDSA, EdDSA, RSA). They must be skilled in smart contract programming and auditing, wallet/key management security, blockchain-specific testing frameworks (Hardhat, Truffle), specialised tools (Mythril, Slither), DeFi Protocols, and tokenomics.</p> <p>Normal penetration testers can’t perform blockchain penetration testing because they are familiar with the decentralised architecture of the blockchain system and its advanced cryptography protocols. This lack of blockchain-specific knowledge and expertise in smart contracts makes it difficult for a typical pentester to conduct blockchain pentesting.</p> <h3>How much does it cost to perform blockchain penetration testing?</h3> <p>Data on the exact cost of blockchain penetration testing is not available, but the cost of simple penetration testing ranges from £8,000 to £12,000. Factors affecting the price of blockchain penetration testing include asset count (nodes, APIs); scope of project (wide, small), system complexity (simple, third-party integration); testing type (blackbox, whitebox, greybox), compliance requirements; experience of the pentester (beginner, expert) and timeframe (urgent, flexible).</p> <h3>How much time does it take to perform blockchain penetration testing? </h3> <p>The exact timeframe for blockchain penetration testing is not available, but simple penetration testing typically takes 2 to 4 weeks. The precise timeframe of performing blockchain penetration testing is not available, but a typical penetration test takes one to four weeks. Factors influencing the overall timeline of blockchain penetration testing include scope and complexity of project (simple contract, enterprise grade); codebase size (small, large); documentation quality (clear, ambiguous); team communication (quick, delayed); audit type (blackbox, graybox); and number of iterations (single, multiple). </p> <h2>What tools are used to perform blockchain penetration testing?</h2> <p>Blockchain penetration testing tools are specialised security tools used to identify exploitable vulnerabilities, misconfigurations, and weaknesses in blockchain systems. </p> <figure><img decoding="async" src="data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%201024%20768'%3E%3C/svg%3E" title="Blockchain Penetration Testing: Definition, Process, and Tools 3"></figure> <p>Listed below are 10 common tools used to perform blockchain penetration testing.</p> <ul> <li><strong>Mythril:</strong> Mythril is a Blockchain penetration testing tool used to detect vulnerabilities (re-entrancy, overflows) in Ethereum smart contracts. It targets EVM bytecode and Solidity source code through symbolic execution analysis. This tool automatically scans smart contracts for common issues such as unprotected functions, transaction-order dependence, and state inconsistencies.  Both security researchers and developers get quick insights into vulnerabilities from this scanner. This open-source tool is the best for pre-audit and post-deployment security reviews of smart contracts. It integrates seamlessly with CI/CD pipelines and enables pentesters to run automated security checks. The pentesting team uses its advanced analysis modes (taint analysis, control-flow inspection) to evaluate complex contract behaviours.</li> <li><strong>Slither:</strong> Slither is a static analysis tool used in blockchain penetration testing to examine the security quality of Solidity smart contracts. It identifies unsafe coding patterns and security flaws after scanning the codebase. This analysis tool provides detailed insights into vulnerabilities such as arithmetic issues, uninitialised storage variables, and shadowed variables by primarily targeting Solidity source code. Pentesters perform manual review via code insights and dependency graphs of this free and open-source framework. This automated tool is developer-friendly and ideal for CI/CD integration and continuous smart contract security testing.</li> <li><strong>Oyente:</strong> Oyente is a foundational automated analysis tool used in blockchain penetration testing to identify vulnerabilities in Ethereum smart contracts. As one of the earliest tools to utilise symbolic execution, it simulates contract behaviour to detect logical and execution-flow flaws, such as timestamp dependence, reentrancy, and transaction-ordering dependence. The tool provides systematic outputs without requiring deep manual input, making it useful for researchers and early-stage audits. While it paved the way for modern symbolic execution, pentesters typically use Oyente today for educational purposes or specific research contexts, as it established the baseline for detecting fundamental logic flaws in smart contracts.</li> <li><strong>Kurtosis:</strong> Kurtosis is a sophisticated infrastructure testing platform used to validate the security and resilience of blockchain nodes and consensus networks. Unlike smart contract scanners, Kurtosis targets the “Layer 1” infrastructure, allowing pentesters to spin up ephemeral, private testnets that mimic production environments. It is essential for testing Consensus Mechanisms and RPC Interfaces by simulating network partitions, packet drops, and “Sybil” attacks to see how nodes recover. Pentesters use it to verify that a blockchain network remains stable under pressure and that API endpoints (like JSON-RPC) do not leak data or crash under high load. It effectively bridges the gap between unit testing and full-scale testnet deployment.</li> <li><strong>Tenderly: </strong>Tenderly is a real-time on-chain event surveillance and debugging tool used in blockchain penetration testing to monitor critical events across EVM chains. It provides deep visibility into contract behaviour by targeting smart contract execution and state, as well as cross-chain events. This tool is useful for uncovering vulnerabilities such as unexpected state changes, broken invariants, and anomalous transaction patterns. It is used as a runtime guard to detect potential exploitation in production or staging environments. This proactive defence includes an easy-to-use dashboard, serverless Web3 Actions, and webhooks. Pentester defines invariants and alert logic via custom code for automated cross-chain monitoring and alerting. </li> <li><strong>Securify:</strong> Securify is a static-analysis blockchain penetration testing tool for Ethereum smart contracts. It analyses EVM bytecode by building control-flow and data-flow facts using Datalog, then checking them against a set of predefined security patterns. This free scanning tool targets the semantic behaviour of smart contracts and uncovers vulnerabilities such as locked Ether, missing input validation, unrestricted Ether flow, and transaction-ordering dependency (TOD). Pentesters use it to reason about all possible execution paths, as this tool conducts a full, path-sensitive analysis. This open-source, automated tool generates a report on violations or compliance for each security pattern. It is suitable for audits and pre-deployment contract verification.</li> <li><strong>ChainSecurity Suite:</strong> ChainSecurity Suite utilises advanced formal verification techniques, primarily through its VerX engine, to mathematically prove the correctness of smart contracts. Unlike standard scanners that look for known bugs, this tool verifies that a contract adheres strictly to its intended business logic specifications. Pentesters and auditors use it to identify subtle logical errors and functional violations in high-value DeFi protocols. While it requires manual specification of the properties to be proven, it offers a level of assurance that automated bug-hunting tools cannot match.</li> <li><strong>Remix IDE Security Plugins:</strong> Remix IDE Security Plugins are modular extensions for the web-based Remix Ethereum IDE used in blockchain penetration testing for smart contract checks. These plugins integrate analysis tools directly into the IDE. Pentesters can quickly identify vulnerabilities such as unchecked calls, block-timestamp dependence, and poor coding practices using this tool. They examine both the source code and potential compiled behaviours to detect dangerous patterns or anti-patterns with static analysers. Smart contract analysis is done automatically through the security plugin of Remix IDE. However, the pentesting team needs to configure checks, including which plugin to run in Remix. </li> <li><strong>Hardhat with Security Plugins:</strong> Hardhat with Security Plugins provides blockchain penetration testing tools for vulnerability scanning and simulation. These tools are used for static analysis, fuzzing, and property-based testing on Solidity contracts. Pentesters identify re-entrancy or logic bugs via symbolic or fuzz testing. They detect gas inefficiencies and dangerous patterns embedded in code. The pentesting team manually writes testing scripts and sets up tasks in the Hardhat framework while automating testing through security plugins. Hardhat is highly customisable, allowing the blockchain security audit team to choose plugins based on their requirements. It is best used to replicate real-world attack scenarios and validate contract behaviour under stress.</li> <li><strong>Manticore:</strong> Manticore is a symbolic execution tool used in blockchain penetration testing to analyse smart contracts (EVM) and native binaries. It systematically explores possible execution paths by treating inputs and identifying potential failure-effective door states. This tool targets  EVM bytecode (smart contracts on Ethereum) and detects vulnerabilities such as Integer overflows/underflows, unexpected external calls, and assertion violations. This symbolic engine is automated; however, pentesters write and execute custom callbacks and analysis strategies for getting full control. It allows the security audit team to thoroughly explore the program’s state space. This open-source tool is effective for deep security audit, especially when pentesters need to check all execution paths and detect hard-to-trigger bugs.</li> </ul> <h2>How is blockchain penetration testing different from other types of penetration testing?</h2> <p>The difference between blockchain penetration testing and other types of penetration testing lies in architecture, vulnerabilities, attack surface, and the tools used. The architecture of blockchain penetration testing is decentralised and immutable, while the architecture of other penetration testing types is centralised on servers, networks, applications, or APIs.  </p> <p>Blockchain penetration testing focuses on vulnerabilities like re-entrancy, logic flaws, and oracle attacks, whereas other penetration testing types emphasise vulnerabilities like SQLi, XSS, CSRF, and authentication flaws. </p> <p>The attack surface of blockchain penetration testing includes consensus, nodes, tokenomics, governance, cryptography, and state manipulation, while other penetration testing types cover the security issues of apps, APIs, and the network. </p> <p>Blockchain penetration testing requires specialised tools (Slither, Mythril), whereas other penetration testing types use traditional tools (Nessus, Burp Suite).</p> <p>Traditional pentesting allows for rollback or patching after an attack. Still, blockchain’s immutable ledger means vulnerabilities can have permanent consequences, requiring more rigorous pre-deployment testing, according to a 2020 study by Akashdeep Bhardwaj, titled “Penetration testing framework for smart contract Blockchain”.</p> <p>Other types of penetration testing do not need to account for distributed consensus protocols, which are central to blockchain security, according to a 2023 study by Abdullah M. Algarni, titled “A security testing mechanism for detecting attacks in distributed software applications using blockchain”.</p> <p>The combinatorial explosion of feature interactions in blockchains (smart contracts interacting with oracles) is far greater than in most traditional penetration systems, making comprehensive blockchain testing more complex, according to a 2023 study by T. Arts, titled “Testing feature‐rich blockchains”.</p> <h3>What are the benefits of blockchain penetration testing?</h3> <p>Blockchain penetration testing <strong>identifies security flaws, mitigates risk factors, and builds trust among users and stakeholders </strong>by protecting digital assets (networks, smart contracts, dApps).</p> <figure><img decoding="async" src="data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%201024%20768'%3E%3C/svg%3E" title="Blockchain Penetration Testing: Definition, Process, and Tools 4"></figure> <p>Listed below are three main benefits of blockchain penetration testing.</p> <ul> <li><strong>Protect digital assets:</strong> Blockchain penetration protects digital assets (tokens, user funds) by detecting security flaws (weak access control, integer overflows) before smart contract deployment. This early vulnerability detection enables developers to fix them proactively, preventing financial losses and reputational damage.</li> <li><strong>Enhance dApp Reliability:</strong> Blockchain penetration testing enhances the reliability of decentralised applications by validating their resilience against adversarial conditions. Users, investors, and partners trust dApps because they believe dApps are secure and resistant to manipulation or downtime.</li> <li><strong>Maintain Compliance with Regulations:</strong> Regular blockchain penetration testing ensures compliance with the project and with industry security standards and best practices. Security team addresses vulnerabilities proactively (ISO/TC‑307, ISO/IEC 27002) and improves audit outcomes.</li> </ul> <h3>What vulnerabilities are found in blockchain penetration testing?</h3> <p>Blockchain vulnerabilities are weaknesses (in the underlying code, user practices, or network) that can be leveraged by attackers to exploit protocols.</p> <p>Listed below are seven common vulnerabilities found in blockchain penetration testing.</p> <ul> <li><strong>Reentrancy attack:</strong> A reentrancy attack is a smart contract vulnerability that allows an attacker to call a function before it has finished executing repeatedly. This attack enables attackers to repeatedly withdraw funds, manipulate the contract’s state, and cause large-scale, irreversible financial losses.</li> <li><strong>Integer Overflow and Underflow:</strong> Integer Overflow and Underflow are smart contract vulnerabilities that disrupt arithmetic operations by causing them to exceed the maximum or minimum limits of a variable type unexpectedly. Attackers exploit these vulnerabilities to alter token balances, break logic conditions, or control financial mechanisms within smart contracts.</li> <li><strong>Weak access control:</strong> Weak access control is a smart contract vulnerability that leaves privileged functions (minting, pausing, upgrading, transferring ownership) unprotected or improperly restricted. Attackers take mint unlimited tokens, control contract administration, and disrupt the protocol’s core functions in the absence of proper access modifiers. </li> <li><strong>Oracle manipulation:</strong> Oracle manipulation is the exploitation of defects in the blockchain Oracle to feed false data to smart contracts for financial gain. Attackers manipulate off-chain prices through flash loans to distort asset values or trigger forced liquidations in DeFi platforms.</li> <li><strong>51% attack:</strong> A 51% attack is a consensus-level vulnerability that allows attackers to gain control of more than half of a blockchain’s total hashing or staking power. Attackers can censor transactions, halt confirmations, reorganise blocks, or even double-spend tokens after controlling over 50% of the network’s validation capability.</li> <li><strong>Sybil attack:</strong> A sybil attack is a consensus-level vulnerability that allows a single attacker to create multiple fake identities (nodes) to gain an unfair advantage within a network. This attacker gains control over the blockchain network to spread misinformation, manipulate network behaviour, or launch another attack like Denial of Service (DoS) </li> <li><strong>Insecure randomness:</strong> Insecure randomness is a smart contract’s logic vulnerability caused by a predictable and easily manipulated random number generator. This vulnerability allows the chain exploiter to predict or manipulate random outcomes and influence the result in their favour. It leads to unfair wins for manipulators and financial losses for other participants.</li> </ul> <p>Cyberattacks on blockchain systems are rare and difficult, yet still possible through software bugs, consensus manipulation, or protocol issues. While blockchain’s decentralised system is more secure than a centralised one, it’s not entirely immune. The best way to minimise risk is ongoing monitoring, robust coding and network security</p> <h3>Are blockchain systems vulnerable to security risks?</h3> <p>Yes, blockchain systems are vulnerable to security risks such as 51% attacks, smart contract bugs, and double-spending. The following real-world attack cases debunk the myth that blockchain technology is highly secure. </p> <p>In 2016, cybercriminals exploited a vulnerability in the smart contracts of “The DAO” and stole approximately 3.6 million Ether (ETH), worth around £45.64 million to £53.24 million at the time. </p> <p>In January 2019, Ethereum Classic was targeted by multiple 51% and double-spending attacks; approximately £5.09  million worth of ETC was fraudulently spent. </p> <p>In 2021, the Poly Network hack (the largest crypto-related hack to date), a hacker exploited flaws in smart contract code and stole £465.45 million. </p> <p>In 2022, Binance lost £433.54 million after cybercriminals targeted its centralised exchanges.</p> <p>Vulnerabilities in external applications, cloud infrastructure, or permissioned blockchain vendors also compromise the entire system. Additionally, poor key management, phishing, and social engineering attacks target end-users and administrators, according to a 2024 study by Silas Mutie Nzuva, titled “Revisiting Blockchain Technologies and Smart Contracts Security: A Pragmatic Exploration of Vulnerabilities, Threats, and Challenges”.</p> <h3>What is blockchain Technology?</h3> <p>Blockchain is a shared, immutable digital ledger used to record transactions and track assets in a peer-to-peer network transparently.</p> <p>The conceptual roots of blockchain trace back to cryptographic research in the 1970s and 1980s. In the early 1980s, David Chaum worked on cryptographic techniques for digital payments. In 1991, two researchers, Stuart Haber and W. Scott Stornetta, described the concept of a cryptographically secured chain of blocks. In 1997, BitGold (a decentralised digital currency) was introduced by computer scientist Nick Szabo. In 2008, Blockchain received global attention. In 2009, the first Bitcoin transaction occurred by Nakamoto. In 2014, Blockchain 2.0 emerged and was used for applications beyond currency. Today, blockchain is seen as a foundational infrastructure for secure, transparent, and decentralised data management across industries. </p> <p>The purpose of blockchain technology is to create a decentralised, secure, and transparent system with an immutable digital ledger, but without a central authority. Blockchains are fundamentally secure due to cryptography, decentralisation, and consensus mechanisms, but are not 100% immune to threats such as 51% attacks and attacks on smart contracts.</p> <h4>What is the security level of blockchain technology?</h4> <p>Blockchain security is built on cryptographic hashing, decentralisation, consensus mechanisms, an immutable ledger, and transparency. Data is stored across many nodes, making it nearly impossible to hack all at once. The consensus mechanism ensures only valid transactions are added, while the immutable ledger prevents unauthorised edits. Public transaction visibility ensures transparency and accountability.</p> <p>Its multi-layered architecture includes the network, consensus, data, and application layers. The network layer uses peer-to-peer distribution to avoid single points of failure, and the consensus layer ensures consensus on the ledger. The data layer organises blocks using cryptographic links, making tampering visible. The application layer relies on secure smart contract coding and auditing.</p> <p>Hashing ensures blockchain security through one-way encryption and tamper detection. Each block contains a unique hash and the previous block’s hash, making any change immediately detectable. This immutable structure secures data by ensuring transactions cannot be reversed or altered.</p> <h3>Why does blockchain technology need penetration testing? </h3> <p>Blockchain technology needs penetration testing to protect high-value assets, prevent irreversible damage, and identify vulnerabilities (e.g., e-entrancy attacks and integer overflows). </p> <p>Pentesters first detect blockchain-specific threats (gas fee manipulation, front-running, flash loan attacks) by simulating real-world attacks, then neutralise them. Transactions through blockchains are irreversible and final. Therefore, any security gap in the system results in significant financial losses for users and reputational damage to the platform. The penetration testing process maintains the integrity of blockchain technology and keeps the system secure when handling high-value assets.</p> <h3>What is the future of blockchain penetration testing? </h3> <p>The adoption of machine learning (ML) and artificial intelligence (AI) is expected to enhance penetration testing by enabling automated detection and analysis of vulnerabilities in blockchain networks and smart contracts. Penetration testing must adapt to new architectures and attack surfaces, as blockchain applications expand into decentralised energy trading and IoT, according to a 2023 study by Vidya Krishnan Mololoth titled “Blockchain and Machine Learning for Future Smart Grids: A Review”.</p> <p>A pentester should learn about blockchain if they plan to specialise and gain certification in the security audit of blockchain-specific systems, applications, or infrastructure.</p> <p>Security research is moving toward full-stack penetration testing, covering all layers of blockchain architecture, from consensus mechanisms to smart contracts and network protocols, to address complex, multi-layered attack surfaces, according to a 2023 study by Hongsong Chen, titled “Security challenges and defence approaches for blockchain-based services from a full-stack architecture perspective”.</p> <p>The demand for Blockchain penetration testing services has increased as many industries adopt blockchain technology (healthcare, finance, supply chain, and gaming). The ecosystem of blockchain technology is expanding as scalable, high-performing applications emerge across industries. </p> <p>The Global Blockchain Testing Services Market was valued at £8.89 billion ($11.68 billion) in 2024 and is projected to reach £88.78 billion ($116.67 billion) by the end of 2030. Over the forecast period of 2025-2030, the market is projected to grow at a CAGR of 58.45%, according to Virtue Market Research.</p> </div><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/01/blockchain-penetration-testing-definition-process-and-tools/" data-a2a-title="Blockchain Penetration Testing: Definition, Process, and Tools"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fblockchain-penetration-testing-definition-process-and-tools%2F&amp;linkname=Blockchain%20Penetration%20Testing%3A%20Definition%2C%20Process%2C%20and%20Tools" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fblockchain-penetration-testing-definition-process-and-tools%2F&amp;linkname=Blockchain%20Penetration%20Testing%3A%20Definition%2C%20Process%2C%20and%20Tools" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fblockchain-penetration-testing-definition-process-and-tools%2F&amp;linkname=Blockchain%20Penetration%20Testing%3A%20Definition%2C%20Process%2C%20and%20Tools" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fblockchain-penetration-testing-definition-process-and-tools%2F&amp;linkname=Blockchain%20Penetration%20Testing%3A%20Definition%2C%20Process%2C%20and%20Tools" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fblockchain-penetration-testing-definition-process-and-tools%2F&amp;linkname=Blockchain%20Penetration%20Testing%3A%20Definition%2C%20Process%2C%20and%20Tools" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://thecyphere.com">Cyphere</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Harman Singh">Harman Singh</a>. Read the original post at: <a href="https://thecyphere.com/blog/blockchain-penetration-testing/">https://thecyphere.com/blog/blockchain-penetration-testing/</a> </p>

How can Agentic AI transform DevOps security

  • None
  • Published date: 2026-01-31 00:00:00

None

<h2>What is the Role of Agentic AI in DevOps Security?</h2><p>How can organizations ensure the security of machine identities and secrets? A comprehensive security strategy, encompassing Non-Human Identities (NHIs) and Secrets Security Management, is crucial. This necessitates a reimagining of how cybersecurity frameworks can adapt to the rapid advancements in technology, particularly through the integration of <strong>Agentic AI</strong>.</p><h3>Understanding Non-Human Identities (NHIs)</h3><p>NHIs are paramount. They are machine identities that play a pivotal role in maintaining security protocols. Essentially, they act like passports and visas for machines, granting access based on permissions linked to encrypted passwords, tokens, or keys—collectively termed as “secrets.” The effective management of these identities is critical for organizations, especially when they expand their cloud presence.</p><p>Organizations in sectors like financial services, healthcare, and travel must address the growing security gap between development and security teams. This gap arises from a lack of cohesive strategies to manage and secure machine identities’ lifecycle. From discovery and classification to threat detection and remediation, every stage is vital for minimizing risks and ensuring compliance.</p><h3>Agentic AI: A New Frontier in DevOps Security</h3><p>The rise of <a href="https://mykubert.com/blog/tag/agentic-ai/" rel="noopener">Agentic AI</a> introduces a novel approach toward handling DevOps security. Its ability to transform lies in its capacity to offer context-aware security with machine learning capabilities. Unlike point solutions such as secret scanners, Agentic AI provides a comprehensive platform that enhances visibility and control over NHIs.</p><p>Through proactive identification and mitigation of security risks, Agentic AI can reduce the likelihood of breaches and data leaks. Its machine learning algorithms allow for continuous learning from varied data environments, optimizing NHIs management strategies.</p><p>– <strong>Reduced Risk:</strong> Agentic AI helps mitigate potential security threats by proactively identifying loopholes.<br> – <strong>Improved Compliance:</strong> It assists in meeting regulatory requisites through audit trails and policy enforcement.<br> – <strong>Increased Efficiency:</strong> The automation of secrets management enables security teams to allocate resources effectively, focusing on strategic initiatives.</p><h3>Benefits of Enhanced NHI Management</h3><p>Empowering organizations with a centralized system for managing access and governance leads to significant <a href="https://entro.security/blog/how-elastic-scaled-secrets-nhi-security-elastics-playbook-from-visibility-to-automation/" rel="noopener">cost savings</a> and operational efficiencies. Automating secrets rotation and NHIs decommissioning reduces overhead costs, allowing teams to concentrate on innovation and growth.</p><p>The adoption of Agentic AI further supports the diversification of security operations. By offering insights into ownership, permissions, usage patterns, and vulnerabilities, companies can make data-driven decisions, which are invaluable.</p><p>– <strong>Enhanced Visibility and Governance:</strong> A unified view of access management provides detailed insights, empowering organizations to streamline processes.<br> – <strong>Cost Savings:</strong> Automating routine tasks enables companies to allocate financial resources more effectively.</p><h3>Bridging the Gap between Innovation and Security</h3><p>DevOps security is evolving rapidly, and Agentic AI is at the forefront of this transformation. By bridging the gap between security and R&amp;D teams, Agentic AI ensures a secure cloud environment that supports innovation without compromising security protocols.</p><p>One notable development is the <a href="https://www.linkedin.com/posts/swaminathansivasubramanian_linux-foundation-launches-the-agent2agent-activity-7342948437895630848-WXdf" rel="noopener">Agent2Agent framework</a>, which highlights the potential of AI in facilitating seamless communication between various systems and enhancing overall security posture.</p><p>Organizations that adopt such innovative frameworks can better prepare themselves for potential security challenges. By embracing Agentic AI’s capabilities, businesses can create a resilient and secure digital that aligns with their long-term strategic goals.</p><p>By focusing on NHIs and their secrets, companies not only fortify their security strategies but also make significant strides toward aligning technological advancements with security protocols. This holistic approach not only ensures compliance and reduces risk but also fosters an environment that nurtures innovation.</p><p>With Agentic AI, the journey toward a secure and innovative digital environment is made more accessible, offering organizations a robust platform to excel while safeguarding their most critical assets.</p><h3>The Critical Role of Machine Identities in Modern Enterprises</h3><p>What happens when the very mechanisms that protect digital infrastructures become the points of vulnerability themselves? Where businesses scale operations and increase their digital footprint, the reliance on Non-Human Identities (NHIs) becomes more significant, creating both opportunities and challenges. Machine identities, crucial for secure communication and transactions, must be effectively managed to ensure the integrity of cloud environments.</p><p>Securing these identities is akin to safeguarding a complex network of keys and locks. NHIs function like digital keys, enabling software applications to authenticate and communicate securely. However, with the proliferation of cloud services, the sheer volume of NHIs can become overwhelming for organizations, necessitating advanced methodologies like Agentic AI to manage them effectively.</p><h3>Addressing Security Challenges Through Lifecycle Management</h3><p>Can lifecycle management of NHIs transform cybersecurity standards? Managing the lifecycle of machine identities is a cornerstone of effective cybersecurity strategy. Starting with the discovery phase, organizations must first identify all existing NHIs within their cloud infrastructure. This initial step sets the stage for a methodical approach to security.</p><p>Key phases of lifecycle management include:</p><ul> <li><strong>Discovery and Classification:</strong> Uncovering all NHIs to understand their roles and risk levels.</li> <li><strong>Provisioning and Securing:</strong> Ensuring that only authorized entities have access to sensitive data.</li> <li><strong>Monitoring and Detection:</strong> Tracking NHI activities to detect anomalies and potential threats.</li> <li><strong>Rotation and Decommissioning:</strong> Regularly updating secrets associated with NHIs and securely retiring outdated identities.</li> </ul><p>By integrating these phases into a comprehensive framework, businesses are better equipped to detect threats, ensure compliance, and optimize resource allocation.</p><h3>Leveraging Advanced Technologies for Optimal Security</h3><p>How can cutting-edge technologies redefine machine identity management? Agentic AI stands out by offering enhanced capabilities through complex algorithms and machine learning, revolutionizing the approach to NHI management. This advanced technology allows for a streamlined, automated process that identifies potential security threats in real-time.</p><p>By continuously analyzing usage patterns and permissions, Agentic AI provides insights needed to preemptively address vulnerabilities. This proactive stance not only protects against breaches but also aligns with regulatory standards, offering an additional layer of compliance security.</p><h3>Creating a Proactive Culture in Cybersecurity</h3><p>Why is proactivity crucial in increasing cyber threats? Reactive measures are often too late, which is why fostering a culture of proactive security is essential. This cultural shift begins with recognizing the critical importance of NHIs and integrating innovative solutions like Agentic AI into everyday operations.</p><p>The role of security teams evolves from merely troubleshooting to becoming strategic partners. They collaborate across departments to instill a security-first mindset, ensuring that technology and business strategies align with cybersecurity objectives.</p><p>Moreover, the involvement of multidisciplinary teams fosters a holistic understanding of both threats and opportunities, making it possible to better navigate an uncertain. <a href="https://entro.security/blog/agentic-ai-owasp-research/" rel="noopener">Agent-based AI research</a> demonstrates the advantages of such a holistic approach by showcasing how diverse perspectives can lead to robust security solutions.</p><h3>Strategic Implementation for Cloud Security</h3><p>How do organizations effectively embed NHI strategies within their broader security framework? Embedding NHI management within broader organizational security frameworks involves strategic planning and execution. Enterprises must adopt a cloud-centric strategy, focusing on the seamless integration of NHIs into their existing security protocols.</p><p>This requires:</p><ul> <li><strong>Cross-Departmental Collaboration:</strong> Bridging the gap between security and R&amp;D teams to streamline processes.</li> <li><strong>Continuous Education and Training:</strong> Educating teams on the latest technologies and best practices in NHI management.</li> <li><strong>Utilizing Automation Tools:</strong> Implementing automation to reduce human error and increase efficiency.</li> </ul><p>By addressing these areas, organizations create a robust environment capable of not only protecting NHIs but also leveraging them for strategic advantage.</p><h3>Looking Towards the Future of Machine Identity Management</h3><p>What’s next in cybersecurity? With technology continues to advance, so too will the complexities of managing machine identities. The future points toward an increasingly sophisticated use of artificial intelligence and machine learning, with these technologies continue to refine and enhance cybersecurity measures.</p><p>The ongoing commitment to innovation demonstrated by organizations willing to adopt cutting-edge solutions like Agentic AI will pave the way for a more secure digital future. The importance of NHIs in this evolution cannot be overstated, when they will continue to serve as the backbone of safe and reliable digital interactions.</p><p>By investing in comprehensive security strategies and by embracing the latest advancements, enterprises can protect themselves from emerging threats while simultaneously unlocking new opportunities for growth and innovation.</p><p>With machine identities become more integral to operations, the significance of thorough security management becomes all the more crucial—an endeavor that promises to define cybersecurity for years to come.</p><p>The post <a href="https://entro.security/how-can-agentic-ai-transform-devops-security/">How can Agentic AI transform DevOps security</a> appeared first on <a href="https://entro.security/">Entro</a>.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/01/how-can-agentic-ai-transform-devops-security/" data-a2a-title="How can Agentic AI transform DevOps security"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fhow-can-agentic-ai-transform-devops-security%2F&amp;linkname=How%20can%20Agentic%20AI%20transform%20DevOps%20security" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fhow-can-agentic-ai-transform-devops-security%2F&amp;linkname=How%20can%20Agentic%20AI%20transform%20DevOps%20security" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fhow-can-agentic-ai-transform-devops-security%2F&amp;linkname=How%20can%20Agentic%20AI%20transform%20DevOps%20security" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fhow-can-agentic-ai-transform-devops-security%2F&amp;linkname=How%20can%20Agentic%20AI%20transform%20DevOps%20security" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fhow-can-agentic-ai-transform-devops-security%2F&amp;linkname=How%20can%20Agentic%20AI%20transform%20DevOps%20security" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://entro.security/">Entro</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Alison Mack">Alison Mack</a>. Read the original post at: <a href="https://entro.security/how-can-agentic-ai-transform-devops-security/">https://entro.security/how-can-agentic-ai-transform-devops-security/</a> </p>

IoT Penetration Testing: Definition, Process, Tools, and Benefits

  • None
  • Published date: 2026-01-31 00:00:00

None

<div class="elementor-widget-container" morss_own_score="2.0" morss_score="259.5"> <p>IoT penetration testing is a security assessment of the complete IoT ecosystem, from backend systems and cloud services to mobile devices and hardware. It involves a multi-stage simulated attack on IoT devices and their supporting system to identify security risks before attackers can exploit them.</p> <p>Unpatched firmware is responsible for 60% of IoT security breaches, according to the IoT Security Foundation. In 2024, Southern Water experienced a cyber incident affecting around 5–10% of its customers, exposing personal data of customers and employees. The attackers exploited an IoT-based water monitoring system running outdated firmware to gain unauthorised access to internal servers.</p> <p>In 2024, an NHS Trust suffered a data breach after attackers exploited vulnerabilities in connected medical devices to access patient records, affecting thousands of patients. The attackers exploited outdated firmware in IoT-enabled diagnostic equipment to gain entry into the Trust’s network. </p> <p>According to NIST (National Institute of Standards and Technology), IoT security failures cost businesses an average of $330,000 per incident. The Mirai botnet turned unsecured IoT devices into an army of attack machines, launching one of the biggest DDoS attacks ever recorded, according to Kaspersky.</p> <p>IoT penetration testing is characterised by end-to-end testing, multi-layer security assessment, multi-stage attack simulation, and AI integration. </p> <p>The process of conducting a successful IoT penetration test involves preparation and planning, threat modelling, reconnaissance, vulnerability assessment, exploitation, post-exploitation, reporting, remediation, documentation, and continuous improvement. The main tools used for IoT pentesting are NURSE, Wireshark, OWASP ZAP, Nessus, and Nmap. IoT penetration testing improves an organisation’s overall security posture by identifying and proactively fixing vulnerabilities to reduce financial and reputational risks.</p> <p>IoT penetration testing makes IoT devices secure by identifying and fixing vulnerabilities across hardware, firmware, networks, and cloud integrations. It validates real-world attack scenarios, reduces risk, and ensures devices so that organisations remain compliant, resilient, and trustworthy over time.</p> <h2>What is IoT penetration Testing?</h2> <p>IoT penetration testing is a simulated real-world attack on Internet of Things devices and their supporting networks and applications to identify security vulnerabilities (weak passwords, insecure protocols) before attackers can exploit them. It involves a complete assessment of controls and configurations of IoT devices and evaluation of communication protocols and interfaces. Other names of IoT penetration testing are IoT pentesting and IoT security assessment.  </p> <figure><img decoding="async" src="data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%201024%20768'%3E%3C/svg%3E" title="IoT Penetration Testing: Definition, Process, Tools, and Benefits 1"></figure> <p>IoT penetration testing works by defining a clear objective and scope, and then gathering information about devices, networks, and services within IoT ecosystems. Automated vulnerability scanning is combined with manual inspection to find known and unknown vulnerabilities. The real-world impact of discovered vulnerabilities is revealed through exploitation and post-exploitation. This process ends with detailed reporting and remediation recommendations.</p> <p>IoT penetration testing involves testing both hardware and software layers in an IoT ecosystem. It includes testing IoT device security, examining communication protocols, probing physical security, and evaluating mobile/web apps, network configurations, and cloud APIs. </p> <p>The main aim of IoT Penetration testing is to uncover exploitable weaknesses in IoT devices, firmware, communication protocols, and associated infrastructure. This includes both known and unknown (zeroday) vulnerabilities that could compromise confidentiality, integrity, or availability, according to a 2023 study by JeanPaul A. Yaacoub, titled “Ethical hacking for IoT: Security issues, challenges, solutions and recommendations.</p> <p>IoT pentesting helps organisations to assess the security posture of IoT systems through the simulation of a real-world attack scenario. It lets them understand the potential impact of a security threat and the effectiveness of existing security measures. Organisations obtain evidence of a proactive security assessment through IoT penetration testing and use it to ensure compliance with industry standards and regulations.</p> <h3>What are the features of IoT penetration testing? </h3> <p>IoT penetration testing is a multi-layer security assessment that combines automation and AI tools to decompose the attack surface while simulating a multi-stage attack and kill chain.</p> <figure><img decoding="async" src="data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%201024%20768'%3E%3C/svg%3E" title="IoT Penetration Testing: Definition, Process, Tools, and Benefits 2"></figure> <p>Five features of IoT penetration testing are listed below.</p> <ul> <li><strong>Multi-layer security assessment:</strong> IoT penetration testing has a broad attack surface in an IoT system. It targets software, network, firmware, hardware, cloud components, and radio interfaces. </li> <li><strong>Attack surface decomposition:</strong> IoT pentesters systematically map all entry points (communication protocols, cloud interactions, device interfaces) of a possible attack to perform a thorough assessment. </li> <li><strong>Kill Chain and Multi-stage attack simulation:</strong> IoT penetration testing uses modern frameworks (Kali Linux, Pwn tool) to simulate real-world attack chains at multiple stages. It demonstrates that attackers exploit multiple vulnerabilities across devices and networks to exploit confidential data and critical assets. </li> <li><strong>Automation and AI Integration:</strong> IoT penetration testing combines automated frameworks (Metasploit, AttackIQ) with AI and machine learning to make the testing process scalable and efficient. AI integration helps pentesters detect complex attack patterns in interconnected IoT systems effectively.</li> <li><strong>End-to-End Testing:</strong> IoT pentesters perform end-to-end testing, including device-to-cloud, device-to-device, and device-to-mobile. This comprehensive evaluation helps them identify vulnerabilities resulting from component interactions.</li> </ul> <h2>How to perform IoT penetration testing?   </h2> <p>IoT penetration testing is performed by gathering information and conducting reconnaissance of the entire IoT ecosystem, followed by vulnerability scanning, exploitation, and post-exploitation analysis. Pentesters generate a detailed report with remediation suggestions.</p> <p>Listed below are the 10 steps to perform IoT penetration testing.</p> <h3>1. Define IoT Scope, Safety &amp; Legal Rules</h3> <p>IoT pentesting experts define a clear testing scope by specifying which systems, devices, and communication layers are used during testing. They identify in-scope IoT devices, out-of-scope gateways, mobile apps, communication protocols, and cloud platforms. They perform fine-tuned authorised attack vectors such as hardware, network, RF, and firmware. Pentesters obtain written consent and authorisation from the client before starting IoT penetration testing. Rules of engagement and safety constraints are documented at this step to prevent physical damage to devices, data loss, and service disruptions.</p> <p> The IoT pentesting team considers safety rules alongside regulatory and legal requirements to ensure compliance when defining the IoT pentesting scope. The team obtains approval of the scope document, which is well aligned with the business’s security objectives and meets the business’s regulatory needs.</p> <p> IoT pentesting experts follow structured threat modelling frameworks and security standards (OWASP IoT Top 10, ISO 27001, IEC 62443) during this phase.  </p> <p>The IoT pentesting team begins mapping IoT assets after defining the testing scope and obtaining the client’s legal permission.</p> <h3>2. Map IoT Assets &amp; Topology</h3> <p>Mapping IoT assets and topology refers to creating a complete inventory of the IoT ecosystem, which comprises gateways, networks, cloud services, user-facing apps, sensors, and APIs. Pentesters identify and document all connected IoT assets, communication protocols, authentication points, and trust boundaries. They visualise how data flows between all these IoT components. They create a detailed asset inventory and topology diagram highlighting device relationships, exposure points, and dependencies. </p> <p>Pentesters uncover shadow IoT devices, pinpoint high-risk paths, and get a structural foundation for targeted vulnerability analysis. Common tools used for assets and topology mapping are Nmap, Netdisco, Masscan, and network visualisation platforms. </p> <p>Pentesters start enumerating passive Radio Frequency (RF) and network interfaces after getting a clear visual of IoT assets and communication paths. </p> <h3>3. Enumerate Passive RF &amp; Network Interfaces</h3> <p>Enumerating passive RF and network interfaces refers to collecting information about identifying all wireless and network-based communication channels used by IoT devices without actively exploiting them. Pentesters examine real-world behaviour with minimal disruption through enumeration. IoT pentesters passively monitor LoRa, ZWave, Bluetooth, WiFi, Zigbee, and other RF signals. They identify open ports, services, and broadcast communication. They obtain a list of exposed protected interfaces, packet capture files, and protocol inventories from this monitoring.</p> <p> The IoT pentesting team detects unauthorised access to RF points, protocol misconfiguration, and insecure communication that attackers could exploit at this stage. The IoT pentesting team relies on passive enumeration tools such as tcpdump, Kismet, and Wireshark, as well as network reconnaissance utilities. </p> <p>The pentesting team starts firmware analysis to uncover embedded software vulnerabilities after identifying exposed network and wireless interfaces.</p> <h3>4. Acquire Firmware, Unpack &amp; Perform Static/Binary Analysis</h3> <p>Firmware acquisition and static or binary analysis refer to the examination of IoT devices’ internal software to discover security weaknesses without code execution. The IoT pentester obtains firmware data from vendor update portals, over-the-air (OTA) mechanisms, or direct extraction from hardware, then unpacks it to analyse file systems, binaries, and configuration files. They use static analysis to uncover hardcoded credentials, cryptographic keys, logical flaws, insecure services, and outdated libraries embedded within the firmware. </p> <p>The IoT pentesting team obtains vulnerability insight, evidence of insecure design or implementation, alongside extracted firmware components during this phase. Static firmware analysis identifies critical vulnerabilities that usually persist across deployments and can lead to long-term compromise if attackers exploit them. </p> <p>IoT pentesters use tools such as Binwalk, IDA Pro, Ghidra, radare2, and the Firmware Tool Analysis Kit. They start probing into the hardware interface after discovering firmware-level weaknesses.</p> <h3> 5. Probe Hardware Interfaces &amp; Debug Embedded Systems</h3> <p>Probing hardware interfaces and debugging embedded systems involves assessing exposed debug and communication ports that may allow an attacker to bypass software controls. IoT penetration testing experts identify hardware interfaces such as UART, JTAG, SWD, SPI, or I²C, access device consoles, and then test them for authentication bypass or privilege escalation.</p> <p> This hardware penetration testing provides an assessment of the feasibility of physical attacks, as well as evidence of memory dumps and console access. Physical access to hardware interfaces usually leads to full device compromise, especially when protection is weak. Therefore, pentesters probe hardware interfaces and debug embedded systems to address threats such as device theft, tampering, and supply chain risks. Common tools used for hardware analysis include logic analyser, JTAGulator, Bus Pirate, OpenOCD, and USBtoUART adapters. </p> <p>The IoT pentesting team continues with protocol testing after evaluating physical access risk factors.</p> <h3> 6. Test Protocol &amp; Radio Communications</h3> <p>Testing IoT protocols and radio communications involves an active security assessment of the data transmission channels identified during passive enumeration. IoT pentesting professionals analyse protocol implementations such as MQTT, Bluetooth Low Energy, LoRaWAN, CoAP, HTTP/HTTPS, WebSockets, Zigbee, and proprietary RF protocols. These protocols are tested for common weaknesses such as misconfigurations, weak encryption, improper authentication, and replay attacks. IoT pentesters validate protocol-level vulnerabilities, insecure cipher usage, and exploitation paths affecting data confidentiality in this step. </p> <p>Protocol and Radio communication probing help pentesters identify compromised channels that an attacker may intercept, manipulate, or inject malicious commands into IoT systems. The pentesting team uses tools like Bettercap, Scapy, Burp Suite, MQTT Explorer, and RF testing platforms for testing protocols.</p> <p>IoT penetration testers shift their focus to device authentication and authorisation assessments once communication channels have been analysed.</p> <h3> 7. Assess Device Authentication, Authorisation &amp; Session Management</h3> <p>IoT pentesters evaluate how IoT devices authenticate services, users, and other devices and how authorisation and session handling are used across cloud layers, mobile apps, and devices. They review credential storage, certificate usage, role-based access controls, token handling, and session expiration mechanisms.</p> <p>IoT pentesters discover vulnerabilities like privilege escalation paths, authentication bypasses, and weak session controls during this assessment. Poor identity and access management let attackers obtain unauthorised device control that enables data exposure and lateral movements across IoT ecosystems. The IoT pentesting team uses tools like JWT analysis tools, OAuth testing utilities, Burp Suite, Postman, and custom API test scripts for evaluating device authentication and authorisation.</p> <p>The IoT pentesting expert continues with OTA and supply chain testing after validating access controls in IoT ecosystems.</p> <h3>8. Verify OTA Update Mechanisms &amp; Supply Chain Integrity</h3> <p>Verifying Over the Air (OTA) update mechanisms and supply chain integrity refers to checking that firmware updates cannot be tampered with, downgraded, or maliciously injected. IoT pentesters analyse third-party dependency trust, firmware signing, version control, rollback protections, and update delivery channels. Pentesting experts find vulnerabilities such as weak supply chain controls, insecure update processes, and missing signature validation, or weak. </p> <p>Verification of the  OTA update mechanism is important because attackers use compromised mechanisms to deploy persistent malware at scale in an IoT ecosystem. Common tools used for verification are CI/CD security validation techniques, Wireshark, Kismet, and Capsa.</p> <p>The IoT pentesters shift their attention to the evaluation of Sensor data flow and Cloud/API integration, once firmware integrity is validated. </p> <h3>9. Evaluate Sensor Data Flows &amp; Cloud/API Integration</h3> <p>The IoT pentesting team assesses how sensor data is generated, processed, transmitted, stored, and exposed through cloud platforms and API. They analyse API authentication, data validation, rate limiting, encryption, logging, and error handling across cloud services. This analysis helps the pentesting team identify risks of improper data isolation, data leakage, API abuse, and insecure storage. </p> <p>Pentesters evaluate these data flows to identify vulnerabilities that attackers can exploit. These sensor data flows are the primary target for attackers as they contain sensitive operational and personal information.  Common tools used for sensor data flow analysis include Postman, Burp Suite, cloud security scanners, and API fuzzing tools.</p> <p> The IoT pentesting team performs controlled exploitation to create a remediation roadmap after evaluating data flows.</p> <h3> 10. Exploit for Persistence, Backdoor Testing &amp; Produce Remediation Report</h3> <p>The final stage of IoT penetration testing involves controlled exploitation of discovered vulnerabilities to determine whether an attacker can achieve persistence, maintain long-term control of IoT devices and backend systems while implanting backdoors. IoT pentesters use tools like custom exploit frameworks and Metasploit to exploit discovered vulnerabilities in the previous steps. They simulate attacks in a controlled environment to check the real-world impact of each vulnerability. </p> <p>IoT pentesters document a comprehensive report after exploitation. This report includes all discovered vulnerabilities throughout the IoT pentesting process alongside their risk ratings and impact. They add proof of concept, prioritised remediation steps, and business impact in the report to improve IoT ecosystem security posture. </p> <h2>What tools are used to perform IoT penetration testing? </h2> <p><strong>IoT Penetration Testing Tools</strong> are specialised software and hardware utilities designed to identify, exploit, and validate security vulnerabilities (insecure network, weak password) in the IoT ecosystem. </p> <figure><img decoding="async" src="data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%201024%20768'%3E%3C/svg%3E" title="IoT Penetration Testing: Definition, Process, Tools, and Benefits 3"></figure> <p>Ten tools used to perform IoT penetration testing are listed below.</p> <ul> <li><strong>Kismet:</strong> Kismet is a passive wireless and RF network detection tool designed to analyse wireless communication without actively transmitting packets during IoT pentesting. The pentesting team uses Kismet to monitor Zigbee, Bluetooth, WiFi, and other RF protocols. This free, open-source tool runs on Windows, macOS, and Linux and supports Software Defined Radios (SDRs). This IoT stealth assessment tool is effective for hidden network detection, real-time RF visualisation, passive device discovery, and protocol fingerprinting. IoT pentesters use Kismet to detect vulnerabilities such as rogue access points, insecure IoT SSIDs, weak RF configurations, unencrypted wireless traffic, and unauthorised device broadcasts. Kismet is commonly used during the RF and network interface enumeration phase of IoT penetration testing as it mainly targets wireless IoT devices, gateways, and RF-based sensors.</li> <li><strong>NURSE: </strong>NURSE is an IoT firmware and embedded system analysis framework designed to identify vulnerabilities within IoT device software and hardware interactions.  This open-source tool runs on Lunius and is useful in correlating firmware analysis with hardware behaviour. An IoT pentester can gain deep insight into how embedded systems operate at runtime. NURSE mainly targets firmware images, embedded binaries, and device operating systems during analysis of custom or proprietary IoT platforms. It is used during the firmware acquisition and static or binary analysis phase of IoT penetration testing. NURSE helps the pentesting team identify vulnerabilities such as weak cryptographic implementations, firmware logic flaws, hardcoded credentials, insecure system calls, and improper memory handling.</li> <li><strong>Wireshark:</strong> Wireshark is a network protocol analyser designed to capture, inspect, and analyse network and RF traffic in real time during IoT penetration testing. Wireshark is a free and open-source tool available for  Windows, Linux, and macOS. The IoT pentesting team combines custom dissectors with Wireshark to perform deep packet inspection and protocol decoding, while analysing both standard and proprietary traffic. It mainly targets IoT network communications interactions such as device-to-device, device-to-cloud, and device-to-mobile.  IoT pentesters rely on Wireshark during the passive enumeration and protocol testing phases. Common network issues uncovered through Wireshark include insecure protocol implementations,  improper certificate usage, replay attacks, unencrypted data transmission, weak authentication exchanges, and sensitive data leakage.</li> <li><strong>PatrIoT:</strong> PatrIoT is a specialised IoT network and device security assessment tool designed to identify misconfigurations and vulnerabilities across IoT ecosystems. An IoT pentesting team uses it as a network-based assessment platform that supports passive monitoring and active validation. This tool lets the team tailor IoT asset discovery, protocol awareness, behavioural analysis, and risk scoring specifically for connected devices. It is commonly used during the asset mapping, protocol analysis, and risk assessment phases of IoT penetration testing. PatrIoT looks into IoT devices, gateways, and backend services operating across heterogeneous networks. Therefore, it is useful for finding vulnerabilities such as outdated firmware, default configurations, weak access controls, and insecure communication protocols. PatrIOT is effective at identifying anomalous device behaviour, a clear indication of compromise in IoT deployments.</li> <li><strong>Nmap:</strong> Nmap is a network discovery and port scanning tool used during IoT penetration testing to detect running services, exposed network interfaces, active devices, and open ports within the IoT ecosystem. This free, open-source tool provides powerful scripting capabilities via the Nmap Scripting Engine (NSE). This tool targets IoT devices, gateways, routers, and backend servers during the IoT asset mapping and network enumeration phase.  The pentesting team used it to fingerprint IoT devices, detect embedded services, and identify protocol usage even in constrained or segmented networks. Vulnerabilities identified through Nmap include outdated service versions, exposed admin interfaces, open management ports, and insecure services (Telnet, FTP, HTTP). Nmap is effective in highlighting issues that attackers exploit to get unauthorised access, leading to lateral movement within IoT networks.</li> <li><strong>OWASP ZAP: </strong>OWASP ZAP (Zed Attack Proxy) is an open-source web application and API security testing tool used in IoT penetration testing for assessment of cloud dashboards, management portals, and REST APIs. It is a free, cross-platform tool that allows both manual and automated security testing. IoT penetration relies on ZAP’s ability to intercept and analyse API traffic of IoT devices and mobile applications. It is effective for a modern IoT ecosystem that uses web-based control panels.  The pentesting team employs OWASP ZAP during the authentication, authorisation, session management, and API security testing phase. This tool targets IoT web interfaces, cloud management portals, and backend APIs. OWASP ZAP helps detect security issues such as weak authentication flows, improper session handling, broken access controls, insecure API endpoints, injection flaws, and cross-site scripting (XSS).</li> <li><strong>Shodan:</strong> Shodan is a search engine for internet-connected devices used in IoT penetration testing to pinpoint exposed IoT systems across the public internet. This freemium platform has paid plans to use its advanced features. This cloud-based platform runs independently of the operating system. The IoT pentesting team relies on Shodan’s capability to index real-world IoT deployments such as smart devices, cameras, routers, and industrial controllers through ports, banners, and protocol fingerprints. The team relies on Shodan during the reconnaissance and exposure assessment phase of IoT penetration testing. This tool mainly targets internet-facing IoT devices and services and allows pentesters to uncover security vulnerabilities such as default credentials, insecure services, publicly exposed IoT devices, and misconfigured cloud integrations. Shodan is effective in identifying internet-facing vulnerabilities that cybercriminals exploit for unauthorised surveillance. </li> <li><strong>Nessus: </strong>Nessus is a vulnerability scanner used in IoT penetration testing to identify security weaknesses across IoT devices, their operating systems, and supporting infrastructure. It supports Windows, macOS, and Linux. This vulnerability scanner scans embedded operating systems and network services for known Common Vulnerabilities and Exposures/CVEs. This tool scans IoT gateways, embedded Linux devices, network services, and backend systems. Pentesters use Nessus during the vulnerability identification and risk assessment phase because it helps them identify vulnerabilities like insecure services, missing security patches, known firmware flaws, and outdated libraries. </li> <li><strong>Burp Suite: </strong>Burp Suite is a web and API security testing platform used in IoT penetration testing for communication and interaction analysis between cloud services, mobile apps, and IoT devices. It has both free and paid versions. It has a powerful interception proxy that allows IoT pentesters to manipulate API requests, tokens, and payloads used by IoT ecosystems.  Pentesting teams use it during the authentication, session management, API security, and cloud integration testing phase, since it targets IoT APIs, cloud services, and mobile app backends. This tool is effective in finding issues like insecure session handling, parameter tampering, data exposure, API authorisation bypass, and token reuse. </li> <li><strong>Metasploit: </strong>Metasploit is an exploitation and post-exploitation framework designed to validate discovered vulnerabilities and assess real-world attack impact. IoT pentesters use both open-source and commercial editions of this framework during the controlled exploitation, persistence testing, and impact validation phase. This tool runs on Linux, Windows, and macOS. This exploitation tool unlocks extensive exploit modules, payloads, and post-exploitation capabilities tailored for embedded systems and network services. The IoT pentesting team validates vulnerabilities such as remote code execution, privilege escalation, weak service configurations, and insecure firmware services through this tool. Metasploit probes into IoT devices, firmware vulnerabilities, network services, and backend systems, and lets the team demonstrate persistence, backdoor feasibility, and overall risk severity of each vulnerability.</li> </ul> <h3>How much does it cost to perform IoT penetration testing? </h3> <p>The cost to perform IoT penetration testing typically ranges between £6,000 and £60,000+. A simple pentest on a single IoT device costs around £6,000–£9,000, while the cost of testing multiple devices is somewhere between £12,000–£25,000. IoT penetration testing cost for large environments like industrial systems or healthcare IoT is more than £50,000 to £60,000+.</p> <p>The factors affecting the cost of IoT penetration testing include scope and number of IoT devices; the depth of assessment (firmware reverse engineering, RF analysis); the complexity of firmware/hardware design; and the communication protocols and RF technologies in use (MQTT, CoAP, Zigbee). Additional factors contributing to the overall cost of IoT penetration testing are compliance and regulatory obligations, remediation support, and physical access requirements (device teardown, onsite testing).</p> <h3>How much time does it take to perform IoT penetration testing? </h3> <p>It takes 2 to 10 weeks to perform IoT penetration testing. Simple IOT device testing takes 2 to 3 weeks, while complex IoT device testing usually requires 6 weeks. Penetration testing for a single component, like firmware or a mobile app, takes less than 2 weeks. Full IoT ecosystem penetration requires more than 8 weeks.</p> <p>Three main factors affecting the time requirement for IoT penetration testing include the number of IoT devices, the complexity of the overall IoT architecture, and the depth of testing required. Basic assessment focuses on network exposure or cloud security takes 1 to 2 weeks, while comprehensive testing involving static/dynamic analysis, firewall extraction, hardware interface proving, RF/protocol testing, and controlled exploitation takes 8 to 10 weeks. Factors that increase the timeline for conducting IoT penetration testing include the need to test multiple communication technologies, compliance requirements, the use of custom firmware, physical access to devices, retesting, and remediation validation. </p> <h2>What are the benefits of IoT penetration testing for organisations?</h2> <p>IoT penetration testing helps organisations identify and fix vulnerabilities, maintain regulatory compliance, build customer trust and improve the incident response of their IoT ecosystem. </p> <figure><img decoding="async" src="data:image/svg+xml,%3Csvg%20xmlns='http://www.w3.org/2000/svg'%20viewBox='0%200%201024%20768'%3E%3C/svg%3E" title="IoT Penetration Testing: Definition, Process, Tools, and Benefits 4"></figure> <p>Eight benefits of IoT penetration testing for organisations are listed below.</p> <ul> <li><strong>Identify and fix vulnerabilities:</strong> IoT penetration testing helps organisations uncover security weaknesses across IoT devices, network, APIs, cloud platform and firmware. The attack surface of IoT includes hardware, firmware, wireless communications, and physical access points. Organisations identify security issues before attackers and fix these issues to reduce the risk of data breaches, large-scale compromise, and device hijacking.</li> <li><strong>Meet regulatory compliance: </strong>Organisation deploying IoT devices must comply with regulations such as the UK GDPR, Data Protection Act 2018, and the Product Security and Telecommunications Infrastructure (PSTI) Act. IoT Penetration testing helps organisations comply with data privacy regulations like GDPR and HIPAA by assessing security against standards. An IoT pentest keeps all connected devices and personal data in the IoT system safe and well-protected, thereby fulfilling legal requirements.</li> <li><strong>Ensure Information Privacy:</strong> IoT pentesting ensures that data is securely transmitted, stored and accessed across the complete IoT ecosystem. Thereby, it reduces the risk of data privacy violations and maintains information privacy under the UK data protection laws.</li> <li><strong>Improve Incident Response:</strong> IoT penetration testing improves the incident response capability of an organisation by simulating a real-world attack on an IoT system and testing its response and alert capability. Organisations understand how systems respond to threats and make the recovery process and response planning faster and more effective for a real security incident.</li> <li><strong>Build Customer Trust: </strong>IoT penetration testing demonstrates a commitment to security and responsible data handling, thereby building customer trust. Customers and partners expect businesses to provide secure and reliable IoT products, so pentesting meets these expectations and helps organisations maintain long-term customer relationships.</li> <li><strong>Maintain Business Continuity:</strong> IoT penetration testing maintains business continuity by reducing downtime risks through early identification of security weaknesses. This early threat detection lets the organisation proactively fix vulnerable entry points that hackers can exploit to disrupt business operations. </li> <li><strong>Preserve Business Reputation: </strong>IoT penetration testing preserves business reputation by preventing security incidents that often lead to regulatory penalties and loss of market confidence. A security breach of IoT devices usually causes long-term reputation damage if customer data or privacy is violated.</li> <li><strong>Reduce Financial Impact:</strong> IoT pentesting reduces the financial impact of a breach, including product recalls, fines under the UK GDPR (Up to £17.5 million or 4% of global turnover; whichever is higher), legal costs, service downtime, and lost revenue. The cost of IoT pentesting is comparatively lower than these potential losses. Investment in IoT pentest brings ROI in the form of money saved by preventing costly breaches and enabling secure business growth through improving overall security posture. </li> </ul> <h3>How frequently should IoT devices be penetrated? </h3> <p>IoT devices should be penetrated at least annually or after significant changes to IoT systems. Regular, on-time pentesting helps keep IoT devices more secure by enabling organisations to proactively identify vulnerabilities and adjust security controls as devices evolve. </p> <p>Organisations should plan IoT pentests at regular intervals to prevent backdoor disks, reduce attack surface, maintain strong authentication and data protection, while validating secure update mechanisms. This regular pentesting makes IoT devices more resilient while reducing the probability of large-scale compromise over time.</p> <p>IoT devices are physical objects embedded with software, sensors, connectivity, and processing capabilities that let them collect, send, and receive data over the internet or private networks without continuous human intervention. It is important to secure IoT devices because any compromise of such devices leads to sensitive personal and operational data exposure, disrupts essential services, and enables unauthorised remote control. Insecure IoT devices serve as entry points into larger networks, causing regulatory violations, large-scale breaches, and significant reputation and financial damage for organisations, customers, and stakeholders.</p> <h3>What are the main IoT security risks?</h3> <p>IoT security risks are potential threats and vulnerabilities arising from weaknesses in connected devices, communication channels, hardware interfaces, firmware, and supporting cloud or API infrastructure. </p> <p>Listed below are the five most common IoT security risks.</p> <ul> <li><strong>Weak or Hardcoded Credentials: </strong>Many IoT devices still use default, weak, or hardcoded passwords and usernames. Attackers can exploit these easy-to-guess passwords online to get unauthorised access and control over IoT devices.</li> <li><strong>Insecure Network and Data Communication: </strong>Many IoT devices lack secure data transfer and storage practices, such as encryption. Therefore, attackers can easily intercept, read, or modify sensitive information that travels through insecure networks.</li> <li><strong>Insecure APIs and Cloud Interfaces: </strong>Attackers gain unauthorised access to devices, data, or backend systems if IoT systems rely on insecure APIs and cloud platforms for management and data processing.</li> <li><strong>Outdated or Unpatched Firmware: </strong>Outdated or Unpatched firmware of IoT devices makes them vulnerable to known security flaws that become an easy target of cybercriminals for long-term exploitation.</li> <li><strong>Lack of Device Integrity: </strong>Attackers install malicious software on IoT devices that don’t have adequate protection (secure boot, firmware validation). Cybercriminals turn unprotected IoT devices into a botnet to maintain persistent access while disrupting services.</li> </ul> <h3>How to make your IoT devices secure?</h3> <p>Listed below are five ways to make your IoT devices secure.</p> <ul> <li><strong>Set a strong password: </strong>Always set a strong, unique and difficult-to-guess password and two-factor authentication TFA across all IoT devices because cybercriminals exploit weak or default passwords in IoT devices and get access to the overall IoT ecosystem. </li> <li><strong>Enable Data Encryption:</strong> Enable data encryption protocols (HTTPS, TLS) to safeguard data transmission between IOT devices and other network components. Data encryption secures the data transmitted over the web and makes it indecipherable to hackers who may attempt to intercept it.</li> <li><strong>Restrict network access: </strong>Secure IoT devices by restricting network access through firewalls and network segmentation. This restriction ensures that one compromised area won’t disrupt the whole IoT ecosystem, in case of a breach.</li> <li><strong>Implement hardware security:</strong> Implement hardware-level security measures such as secure boot procedures and hardware-assisted encryption. Secure booting stops malicious code from running while protecting IoT devices from firmware updates. Hardware encryption maintains the security of sensitive data and information.</li> <li><strong>Examine Third-party Integrations: </strong>Examine third-party services (cloud platforms, voice assistants) and integration as they might introduce vulnerabilities in your overall IoT ecosystem, if not properly assessed. Due diligence about vendors and their compliance verification is essential to maintain the security of IoT. </li> </ul> <p>IoT penetration testing plays a major role in maintaining the safety and security of IoT devices by proactively identifying vulnerabilities before attackers can exploit them. IT helps organisations validate real-world attack scenarios, ensure compliance and maintain trust and long-term resilience in IoT ecosystems. </p> <h3>What are the best practices for performing IoT penetration testing?</h3> <p>Nine best practices for performing IoT penetration testing are listed below.</p> <ul> <li><strong>Eliminate weak and hardcoded credentials: </strong>Pentesters should eliminate default, weak, and guessable passwords from devices, APIs, and cloud services. It’s better to get rid of exposed admin accounts and missing credential rotations. </li> <li><strong>Secure ecosystem interfaces: </strong>IoT pentesters should perform comprehensive tests on APIs, mobile apps, web dashboards, and cloud integrations to identify issues related to authentication, authorisation, and data exposure.</li> </ul> <ul> <li><strong>Protect data in transit and at rest: </strong>Data should be protected during transit and at rest by validating encryption strength, certificate handling, key management, and secure storage across device and backend layers.</li> <li><strong>Enforce proper authorisation controls:</strong> Enforce proper authorisation controls by preventing unauthorised device controls, and through verification of role-based access and privilege separation.</li> <li><strong>Harden device management capabilities: </strong>IoT penetration testers should harden device management capabilities through a comprehensive assessment of firmware update processes, device lifecycle controls,  OTA mechanisms, and configuration management.</li> <li><strong>Ensure device integrity: </strong>The Pentesting team must verify secure boot, firmware signing, and resistance to malware or unauthorised code execution.</li> <li><strong>Reduce attack surface exposure: </strong>Pentesters should reduce attack surface exposure by identifying issues like open ports,  insecure network configurations, debug interfaces, and unnecessary services.</li> <li><strong>Strengthen physical security controls: </strong>IoT pentesters must look into exposed hardware interfaces and physical tampering risks to maintain physical security controls for devices in public and remote locations.</li> <li><strong>Assess insider and privilege misuse risks:</strong> The pentesting team assesses insider threats and privilege misuse risks by monitoring unauthorised users and third-party vendors while validating access management and logging.</li> </ul> </div><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/01/iot-penetration-testing-definition-process-tools-and-benefits/" data-a2a-title="IoT Penetration Testing: Definition, Process, Tools, and Benefits"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fiot-penetration-testing-definition-process-tools-and-benefits%2F&amp;linkname=IoT%20Penetration%20Testing%3A%20Definition%2C%20Process%2C%20Tools%2C%20and%20Benefits" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fiot-penetration-testing-definition-process-tools-and-benefits%2F&amp;linkname=IoT%20Penetration%20Testing%3A%20Definition%2C%20Process%2C%20Tools%2C%20and%20Benefits" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fiot-penetration-testing-definition-process-tools-and-benefits%2F&amp;linkname=IoT%20Penetration%20Testing%3A%20Definition%2C%20Process%2C%20Tools%2C%20and%20Benefits" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fiot-penetration-testing-definition-process-tools-and-benefits%2F&amp;linkname=IoT%20Penetration%20Testing%3A%20Definition%2C%20Process%2C%20Tools%2C%20and%20Benefits" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fiot-penetration-testing-definition-process-tools-and-benefits%2F&amp;linkname=IoT%20Penetration%20Testing%3A%20Definition%2C%20Process%2C%20Tools%2C%20and%20Benefits" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://thecyphere.com">Cyphere</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Harman Singh">Harman Singh</a>. Read the original post at: <a href="https://thecyphere.com/blog/iot-penetration-testing/">https://thecyphere.com/blog/iot-penetration-testing/</a> </p>

AI-powered penetration testing: Definition, Tools and Process

  • None
  • Published date: 2026-01-31 00:00:00

None

<div class="elementor-widget-container" morss_own_score="2.0" morss_score="309.5"> <p>AI-powered penetration testing is an advanced approach to security testing that uses artificial intelligence, machine learning, and autonomous agents to simulate real-world cyberattacks, identify vulnerabilities, and assess exploitability faster and more intelligently than traditional manual testing.</p> <p>According to Mariia Kozlovska et al. in their research “Artificial intelligence in penetration testing: leveraging AI for advanced vulnerability detection and exploitation”, published on May 2, 2025, Machine learning in penetration testing helps identify hidden security flaws by analysing past attacks and abnormal patterns.</p> <p>According to Richard Fang et al. in their research, “LLM Agents can Autonomously Hack Websites”: The AI agent outperformed 9 out of 10 human penetration testers in a controlled capture-the-flag (CTF) environment. It identified valid vulnerabilities with 82% precision.</p> <p>AI-powered penetration testing includes autonomous reconnaissance, adaptive attack-path modelling, machine-learning-driven risk prioritisation, continuous testing capability and human-led validation. AI pentesting tools include traditional security platforms such as Nmap, Nessus, Burp Suite, Metasploit, and Wireshark, alongside AI-centric tools like PentestGPT, Garak, Counterfit, PyRIT and IBM adversarial robustness toolbox, and a hybrid PTaaS platform such as NetSPI.</p> <p>The main process in AI penetration testing includes asset scoping and AI agent coordination, intelligent reconnaissance, AI-driven vulnerability discovery and exploit validation, post-exploitation, and lateral movement assessment, and AI-generated risk reporting with remediation guidance.</p> <p>AI-powered penetration testing is not the same as normal manual pentesting; rather, it improves it. Traditional pentesting is best at creativity, business logic analysis, and human judgment, while AI improves speed, coverage, correlation, and continuous testing capability. Organisations should use AI-powered penetration testing because modern attack surfaces change rapidly, cloud environments expand continuously, and manual testing alone cannot scale or operate in real time. AI-driven testing helps uncover hidden attack paths, reduce false positives, prioritise meaningful risks, and strengthen security posture faster while still relying on expert human oversight to ensure accuracy and trust.</p> <h2>What is AI-powered penetration testing?</h2> <p>AI-powered penetration testing is an ethical hacking technique that uses artificial intelligence (AI) and machine learning (ML) to automatically simulate real-world cyberattacks on systems, networks, and applications. AI-powered penetration testing uses machine learning, deep learning and reinforcement learning to identify vulnerabilities, exploit weaknesses, and assess security posture more efficiently and continuously.</p> <p>AI-powered penetration testing is also called Autonomous pentesting, Intelligent penetration testing, and Automated ethical hacking. According to Mariia Kozlovska et al. in their research “Artificial intelligence in penetration testing: leveraging AI for advanced vulnerability detection and exploitation”, published on May 2, 2025, Artificial intelligence in automating processes like vulnerability detection and real-world attack simulation helps in generating quicker, more precise results with less dependence on human input.</p> <p>AI-powered penetration testing typically includes intelligent reconnaissance and discovery, automated vulnerability identification, adaptive exploitation techniques, attack path analysis and chaining, continuous testing and monitoring, risk scoring and prioritisation and automated reporting and remediation insights.</p> <h3>How does AI-powered penetration testing work?</h3> <p>AI-powered penetration testing combines automation, machine learning, and intelligent decision-making systems to simulate how a real attacker would operate across networks, applications, and cloud environments.</p> <p>The process starts with automated reconnaissance, where AI maps the target environment, discovers exposed assets, analyses traffic patterns, and detects misconfigurations or weak security controls. Unlike static rule-based scans, the AI continuously learns from previous assessments, adapts to new system behaviours and understands the environment to improve accuracy over time. Once the system understands the environment, AI models analyse system responses, application workflows, and security configurations to identify vulnerabilities. AI also evaluates whether those weaknesses are actually exploitable in real-world environments.</p> <p>The AI then simulates attack behaviour by selecting appropriate attack paths, chaining vulnerabilities together, testing privilege escalation possibilities, and evaluating lateral movement potential. The AI agent attempts an attack using a selected technique and evaluates the outcome. It then adapts its approach and tries alternative strategies based on previous results. Over time, the system learns which methods are more likely to succeed, making its behaviour comparable to that of an intelligent adversary rather than a simple automated scanner, if an attack attempt fails.</p> <p>The goal of AI-powered penetration testing is to make security testing faster, continuous, and more context-aware than periodic manual assessments. It helps organisations uncover complex attack chains that human testers may overlook, reduce false positives, assess which vulnerabilities are truly dangerous, and prioritise remediation based on actual exploit risk rather than theoretical severity scores.</p> <p>AI-powered penetration testing identifies software and infrastructure vulnerabilities, web application flaws, authentication and authorisation weaknesses, misconfigured cloud or network settings, exposed or shadow IT assets, insecure APIs, privilege escalation paths, weak encryption controls, and lateral movement opportunities inside the environment. Different AI techniques are used at different stages, including machine learning-driven AI, agentic AI, generative AI (LLMs) and reinforcement learning.</p> <h2>Who performs AI-driven penetration testing?</h2> <p>An AI-driven penetration tester performs AI-driven penetration testing. An AI-driven penetration tester is a cybersecurity professional who combines traditional ethical-hacking expertise with the ability to operate, validate, and interpret results from an AI-enabled security testing platform. An AI penetration tester works alongside autonomous testing agents and machine-learning-driven tools to simulate realistic attack behaviour, validate findings, and assess how AI-generated attack paths translate into real-world risks.</p> <p>Not every penetration tester can automatically perform AI-powered penetration testing. Any skilled pentester can learn to use AI-driven tools, but the role requires additional competencies such as understanding how AI models make decisions, how automated attack chaining works, and how to differentiate between AI-generated false positives and validated exploit scenarios.</p> <p>The roles and responsibilities of an AI penetration tester typically include planning and scoping assessments, configuring and supervising AI-powered attack simulations, assessing AI-identified vulnerabilities, and determining whether AI-generated exploit chains are realistic and safe to reproduce. They interpret AI-generated insights in a business context, assess real-world exploitability, prioritise risks and provide remediation guidance to engineering and security teams.</p> <p>An AI-driven penetration tester usually comes from a cybersecurity, ethical hacking, or security engineering background, holding certifications such as OSCP, CEH, CREST, GPEN or equivalent practical experience in offensive security. An AI pentester configures AI agents to map environments, discover assets, and simulate attack behaviour while supervising how the AI selects attack strategies, chains vulnerabilities, and evaluates lateral movement or privilege-escalation opportunities. The tester reviews AI findings, assesses exploitability through controlled testing, removes noise or false positives, and refines AI configurations to improve accuracy over time.</p> <h3>Is AI-driven penetration testing possible?</h3> <p>Yes, AI-driven penetration testing is possible, and it is already being used in modern security programs through autonomous testing platforms, ML-driven vulnerability discovery, and agent-based attack simulation.</p> <p>AI cannot fully replace human-driven penetration testing. AI improves speed, coverage, and automation, but human pentesters provide creative adversarial thinking, real-world judgment, ethical responsibility, and business-risk interpretation that AI cannot replicate. Current AI-powered security tools and research outcomes show that AI excels at pattern recognition, reconnaissance, and automated exploit chaining, but limitations appear with ambiguity, novel attack creativity, and environment-specific decision-making.</p> <p>According to Tim Abdiukov in his research “Red teaming in the age of AI-augmented defenders: Evaluating human Vs. machine tactics in professional penetration testing”, published on July 30, 2025, Although AI is crucial when it comes to speed, flexibility and being able to detect patterns, human testers still win in terms of exploiting more complex vulnerabilities, especially in cases simulating human intuition and decision-making.</p> <h2>What are AI-powered penetration testing tools?</h2> <p>AI-powered penetration testing tools are security testing platforms and frameworks that use artificial intelligence, machine learning, autonomous agents, or AI-assisted analysis to discover vulnerabilities, analyse attack paths, simulate exploits, and prioritise risk based on real-world exploitability.</p> <p>AI-powered tools help organisations detect hidden attack chains, reduce false positives, and scale penetration testing across networks, applications, APIs, and cloud environments more efficiently.</p> <p>The top 13 AI-powered penetration testing tools are described below.</p> <h3>Wireshark</h3> <p>Wireshark is a popular, open-source network protocol analyser that captures and inspects live traffic data across networks. Wireshark is widely used within AI-penetration testing workflows, where AI models analyse captured traffic patterns, anomalies, and suspicious communication identified by Wireshark to detect potential vulnerabilities.</p> <p>Wireshark identifies vulnerabilities such as insecure protocols, session hijacking risks, plaintext credentials, malformed packets, and lateral-movement traffic. In AI-powered pentesting, Wireshark data is often fed into ML-based anomaly detection systems to support automated traffic analytics.</p> <p>Wireshark provide deep network visibility and accurate packet telemetry for AI engines to learn attack behaviours. However, its limitations include steep learning curves, manual interpretation requirements, and a lack of native automation or exploit simulation capability.</p> <h3>Nmap</h3> <p>Nmap is an open-source network discovery and port-scanning tool used to identify hosts, open ports, running services, and exposed attack surfaces. Nmap is fast, lightweight, free, highly scalable, and one of the most widely used reconnaissance tools. Nmap identifies vulnerabilities such as open service ports, weak service configurations, outdated software versions, and possible entry points for exploitation. In AI-driven workflows, Nmap outputs feed automated asset discovery, exposure mapping, and attack-path modelling engines.</p> <p>Nmap provides comprehensive network visibility and compatibility with automation tools. The limitation is that Nmap identify exposure but does not perform exploit validation or risk prioritisation on its own without AI or manual analysis.</p> <h3>Nessus</h3> <p>Nessus is a widely used vulnerability assessment scanner that uses signatures, plugins, and risk scoring to detect known vulnerabilities and misconfigurations. AI-assisted correlation and predictive analytics on Nessus results are used by newer integrations and enterprise platforms to make a strong component within AI-powered penetration testing environments.</p> <p>Nessus is a paid, enterprise-grade, highly reliable, and mature platform. Nessus detects known CVEs, outdated software, misconfigurations, missing patches, weak SSL/TLS settings, and privilege weaknesses. In AI pentesting, Nessus findings are often improved with machine-learning-based prioritisation and exploitability analytics. Nessus provide strong vulnerability coverage, standardised reporting, and integration with automated workflows. Nessus rely on known vulnerabilities and has limited capability in detecting logic flaws or novel attack vectors without AI-driven enhancement.</p> <h3>Burp Suite</h3> <p>Burp Suite is a professional web application penetration testing platform used to detect and exploit web vulnerabilities. Although its core engine is manual and scanner-based, recent extensions and plugins integrate AI-assisted pattern detection and automated request analysis.</p> <p>Burp Suite is available in both free and paid editions, widely used by professional pentesters, and highly effective for web app security testing. It identifies vulnerabilities such as SQL injection, XSS, authentication flaws, session weaknesses, insecure APIs, and business logic errors. In AI-driven pentesting, AI tools analyse Burp traffic, automate request mutation, and help detect complex behavioural weaknesses.</p> <p>Burp Suite provide deep application insight, strong testing control, and extensibility. However, the limitations include manual effort requirements, time-intensive workflows, and limited native AI automation without extensions.</p> <h3>Metasploit</h3> <p>Metasploit is an open-source penetration testing framework used to develop, execute, and manage exploit modules. Metasploit is frequently used alongside AI-powered attack automation engines and autonomous exploit testing platforms.</p> <p>Metasploit is an open-source (with paid Pro editions), highly extensible, widely adopted, and ideal for validating exploitability. Metasploit is used to simulate privilege escalation, remote code execution, lateral-movement attack chains and misconfigurations. AI-powered pentesting uses Metasploit to validate whether AI-detected vulnerabilities are realistically exploitable.</p> <p>Metasploit provide practical exploit proof-generation and real-world attack simulation. However, it includes ethical risk if misused, a need for expert supervision, and a lack of autonomous decision-making without AI integration.</p> <h3>PentestGPT</h3> <p>PentestGPT is an AI-powered penetration testing assistant built on large language models that supports testing workflows such as reconnaissance guidance, exploitation reasoning, payload generation, and report drafting. PentestGPT directly uses generative AI to accelerate analyst decision-making.</p> <p>PentestGPT identifies logic weaknesses, payload possibilities, misconfigurations, and testing strategies by interpreting tool outputs. It is used in AI pentesting for reasoning, chaining attack ideas, and explaining findings.</p> <p>Its advantages include analyst productivity, intelligent guidance, and automation of repetitive tasks. However, it relies on prompt quality, a lack of direct exploit execution, and the risk of incorrect assumptions without expert validation.</p> <h3>Garak</h3> <p>Garak is an open-source AI security testing framework designed to identify vulnerabilities, prompt injection attacks, and adversarial behaviours in large language models and AI systems. Garak identifies issues such as prompt leakage, unintended data exposure, unsafe model responses, and model behaviour exploitation paths. In AI-powered pentesting, Garak is used to test the security of AI applications and agentic systems themselves.</p> <p>It includes specialisation in LLM security and open-source accessibility. However, it does not assess networks or infrastructure and is focused only on AI system vulnerabilities.</p> <h3>NetSPI</h3> <p>NetSPI provides enterprise-grade penetration testing-as-a-service platforms that combine automation, machine learning-based risk correlation, and human-led validation. NetSPI identifies cloud, application, network, and API vulnerabilities, while AI engines support risk prioritisation, asset discovery, and continuous testing workflows. It is paid, enterprise-focused, and known for accuracy and expert validation.</p> <p>NetSPI provide scalable testing, a hybrid AI-plus-human model, and strong reporting quality. Limitations include cost and vendor dependency.</p> <h3>Counterfit</h3> <p>Counterfit is an open-source Microsoft security tool used for adversarial ML and AI model vulnerability assessment. Counterfit is designed for testing the robustness of machine-learning systems. It detects weaknesses such as adversarial input manipulation, evasion vulnerabilities, and ML model security gaps. In AI pentesting, it is essential for organisations to secure AI-powered applications.</p> <p>Counterfit provides flexibility, open-source availability, and strong ML-security relevance. However, it has technical complexity and a specialised AI-security scope.</p> <h3>PyRIT</h3> <p>PyRIT (Python Risk Identification Toolkit) is an AI red-teaming and adversarial evaluation framework used to simulate attacks against AI agents and ML pipelines. PyRIT is used to assess how AI systems respond to malicious prompts, adversarial inputs, and system-level exploit attempts.</p> <p>It identifies prompt weaknesses, unsafe automation logic, and system instruction manipulation. In AI pentesting, PyRIT supports security testing of agentic AI systems. PyRIT protects AI systems before deployment. However, it includes experiment-focused design and niche applicability.</p> <h3>Mindgard</h3> <p>Mindgard is a commercial AI security testing platform that focuses on adversarial ML resilience, model robustness, and AI supply chain security. Mindgard uses automation and AI-based evaluation to detect weaknesses in data pipelines and ML environments. It identifies adversarial poisoning risks, data exposure, unsafe inference behaviour, and ML model attack surfaces.</p> <p>Mindgard is paid and enterprise-oriented, with a strong emphasis on AI-system security. It includes automated assessment and risk analytics; however, the platform costs and focuses only on AI rather than full network penetration testing.</p> <h3>Adversarial Robustness Toolbox</h3> <p>ART is an open-source security framework developed by IBM to test ML models against adversarial attacks. ART is one of the most widely used research-grade tools in AI security testing. It detects adversarial input vulnerabilities, evasion attacks, poisoning risks, and model-integrity weaknesses. In AI pentesting, it is used primarily for secure AI research and enterprise ML testing. It includes flexibility, proven reliability, and community adoption. It includes excessive learning requirements and a lack of automation for enterprise workflows.</p> <h3>SatGuard</h3> <p>SatGuard is a security testing framework developed for AI and ML-driven aerospace and satellite systems. It focuses on adversarial testing of space-tech AI applications. It identifies ML manipulation risks, spoofing behaviour, and AI-based control vulnerabilities. SatGuard is high in specialised critical-infrastructure environments but limited in general enterprise penetration testing.</p> <p>It includes niche specialisation and mission-critical security relevance; however, it has narrow applicability and limited general adoption.</p> <h2>How to perform AI-powered penetration testing?</h2> <p>To perform AI-powered penetration testing, organisations combine autonomous security agents, machine learning analytics, and human-led validation to simulate adaptive, real-world attack behaviour in a controlled and ethical environment.</p> <p>The 7 steps to perform AI-powered penetration testing are described below.</p> <ol> <li><strong>Initialise Adaptive AI Agent Coordination &amp; Target Scoping</strong>: Initialising Adaptive AI Agent Coordination &amp; Target Scoping involves defining the scope, assets, and operational boundaries for AI-driven testing. The process starts with identifying target systems, cloud assets, applications, APIs, and network segments. Inputs include asset inventories, architecture diagrams, risk priorities, compliance restrictions, and testing timelines. Tools commonly used at this stage include attack surface management platforms, Nmap, ASM discovery tools, cloud inventory scanners, and AI-agent orchestration dashboards. The AI agents are then assigned roles such as reconnaissance automation, anomaly-pattern detection, exploit-chain exploration, or lateral-movement simulation. The primary considerations include avoiding production disruption, defining safe testing rules, and enabling human-in-the-loop approvals for sensitive actions. This step provides a clearly defined test scope, a mapped asset universe, and an AI-agent testing plan that works adaptively within approved boundaries.</li> <li><strong>Execute Intelligent Reconnaissance &amp; Threat Intelligence Fusion</strong>: AI performs autonomous reconnaissance to understand the environment and correlate external threat intelligence with internal exposure data. The system gathers information about open services, application behaviours, network flows, misconfigurations, and cloud or identity weaknesses. The process uses tools such as Nmap, OSINT feeds, network telemetry, Wireshark captures, and exposure monitoring platforms, while AI models classify and filter noise to avoid redundant or irrelevant findings. AI combine live reconnaissance results with intelligence sources to identify patterns such as risky service exposure, shadow assets, weak authentication points, and suspicious behavioural anomalies. It provides an intelligent attack surface map highlighting high-value entry points, contextual exposure risks, and environment relationships that could enable multi-step attack paths.</li> <li><strong>Perform AI-Driven Vulnerability Assessment &amp; Exploitation</strong>: The system correlates scanner outputs, behavioural signals, and configuration data to predict exploitability and risk impact. Performing AI-driven vulnerability assessment &amp; exploitation includes tools like Nessus, Burp Suite, ML-driven anomaly detectors, and autonomous exploit-validation engines integrated with frameworks like Metasploit under controlled conditions. The process emphasises safe simulation and human validation for critical scenarios. It provides validated vulnerabilities, predicted exploit paths, and prioritised risk insights.</li> <li><strong>Establish Persistent Access Through Intelligent Techniques:</strong> Establishing persistent access through intelligent techniques focuses on assessing whether weaknesses could allow an attacker to maintain presence in a system. The goal is not to maintain access permanently, but to understand risk exposure and resilience controls. AI agents analyse authentication weaknesses, privilege escalation pathways, misconfigured identity roles, and session-management behaviours. Tools may include identity simulators, privilege-access testing utilities, cloud-role analysis frameworks, and AI behavioural modelling. Considerations include strict safety controls, authorisation approvals, and rollback mechanisms to avoid disruption. It provides a resilience assessment that reveals whether persistent access could theoretically be sustained and how such exposure should be mitigated.</li> <li><strong>Conduct Adaptive Post-Exploitation &amp; Lateral Movement</strong>: At post-exploitation and lateral movement, AI models assess how an attacker could pivot across systems if an entry point were compromised. The goal is to understand blast-radius risk and containment effectiveness. The process involves analysing network segmentation, trust relationships, privilege inheritance, and cross-system authentication behaviour. Tools include graph-based attack-path modelling platforms, identity-mapping analytics, and AI-driven lateral movement simulators. The AI adapts based on system responses and highlights how small exposures could escalate into larger security incidents. It provides a contextual view of lateral movement potential and practical remediation priorities.</li> <li><strong>Demonstrate Impact Through Automated Data Exfiltration</strong>: The Impact through automated data exfiltration step focuses on assessing potential data exposure risk in a safe, simulated, and monitored research context. The system assesses where sensitive data resides, how it is accessed, and whether weak controls could enable unauthorised retrieval. Tools may include DLP-aware testing utilities, cloud storage analysis, API behavioural testing, and AI-assisted sensitivity classification. It provides an impact-oriented security report showing which datasets are at risk, how exposure could occur, and what controls are required to prevent it.</li> <li>G<strong>enerate Comprehensive AI-Synthesised Security Intelligence</strong>: In the Comprehensive AI-Synthesised Security Intelligence stage, AI synthesises insights across all phases into a structured, risk-driven security report. Generative AI and analytics engines integrate findings, correlate evidence and translate technical outcomes into business-aligned recommendations. The process produces a report explaining attack-path feasibility, possibility, and impact in clear and actionable language. This process provides contextual risk insights, prioritised remediation plans, defence strength assessments and recommendations for hardening identity, configuration, application, and network controls. Human analysts review and validate conclusions to ensure accuracy, compliance, alignment, and practical feasibility.</li> </ol> <p>AI-powered penetration testing is not strictly better than manual testing; rather, it improves and extends it. AI is stronger at scale, speed, continuous testing, exposure mapping, and exploit-path correlation, while human penetration testers excel at creative thinking, contextual reasoning, business-logic assessment, and ethical judgment.</p> <h3>Manual or AI-powered penetration testing: Which one is the best?</h3> <p>Both manual penetration testing and AI-powered penetration testing are valuable, but the best approach is a hybrid model where AI improves human-led testing rather than replacing it. AI-powered penetration testing is better for speed, scale, continuous testing, and identifying complex attack paths across large environments, while manual testing is best for creative thinking, business-logic flaws, real-world judgment, and ethical oversight. AI helps reduce and automate repetitive tasks, but human expertise is essential for validation and accurate risk interpretation. Therefore, the most effective and reliable approach is AI-assisted, human-led penetration testing.</p> <h3>What vulnerabilities are found in AI-powered penetration testing processes?</h3> <p>AI penetration testing vulnerabilities refer to security weaknesses that appear especially in AI-driven systems, AI-powered penetration testing tools, or environments where autonomous agents assist in security testing.</p> <p>The 19 common AI penetration testing vulnerabilities are described below.</p> <ol> <li><strong>Prompt Injection</strong>: Prompt injection attacks occur when an attacker manipulates AI prompts or model instructions to override safeguards or produce unintended actions. It affects AI assistants, autonomous agents, and AI-driven testing logic, which leads to unsafe outputs or misguided testing activity. AI pentesting detects such attacks by testing prompt resilience and enforcing contextual guardrails.</li> <li><strong>Data Poisoning</strong>: Data poisoning happens when malicious or incorrect data is injected into training sets or the learning feedback loop, which causes models to learn false patterns. It can corrupt vulnerability analysis and exploit interpretation. AI penetration testing helps detect anomalies in the training pipeline and validates model integrity.</li> <li><strong>Model Theft</strong>: Model theft occurs when attackers extract or replicate proprietary AI models through API probing or output inference. It threatens intellectual property and system integrity. The severity of the model theft vulnerability is medium to high. AI pentesting assesses model exposure paths and recommends access-control hardening.</li> <li><strong>Information Leakage</strong>: Information leakage happens when AI outputs reveal sensitive data such as credentials, system paths, or internal logic. It affects confidentiality and system privacy. The severity of the information leakage vulnerability is high. AI pentesting simulates leakage scenarios and assesses response-filtering mechanisms.</li> <li><strong>API Vulnerabilities</strong>: API vulnerabilities occur when AI systems expose insecure endpoints, weak authentication, or excessive permissions. They impact availability and security exposure. AI pentesting scans, validates, and prioritises exploitable AI-API weaknesses.</li> <li><strong>Hallucinations in AI Outputs</strong>: Hallucinations occur when AI generates inaccurate or fabricated findings, which may lead to wrong security conclusions. It affects testing accuracy and trust. AI pentesting reduces risk through human validation and confidence-scoring.</li> <li><strong>Security Guardrail Bypass</strong>: Guardrail bypass occurs when attackers trick AI agents into ignoring safety controls or ethical constraints. It can trigger unsafe system behaviour. AI pentesting stresses guardrails to ensure enforcement under adversarial prompts.</li> <li><strong>Model Inversion</strong>: Model inversion happens when attackers reconstruct training data or sensitive attributes from AI outputs. It threatens privacy and data security. AI pentesting evaluates inversion resistance and strengthens anonymisation controls.</li> <li><strong>Insecure Output Handling</strong>: Insecure output handling occurs when AI outputs are executed, trusted, or reused without review (e.g., auto-executed commands). It increases the risk of exploitation. AI pentesting enforces human-in-the-loop validation and safe-execution workflows.</li> <li><strong>Overreliance: </strong>Overreliance occurs when teams depend too heavily on AI outputs without expert validation. It affects decision accuracy and risk prioritisation. The severity of the overreliance vulnerability is medium. AI pentesting prompts hybrid human-AI review processes to maintain balanced decision-making.</li> <li><strong>Model Denial of Service</strong>: Model DoS occurs when attackers overload AI systems with adversarial queries or complex workloads. Model denial of service affects performance and availability. AI penetration testing stress-tests model resilience under high-load conditions.</li> <li><strong>Excessive Agency</strong>: Excessive agency occurs when autonomous AI agents perform actions beyond the intended scope. Excessive agency affects control and safety. AI pentesting follows the scope permissions and execution-approval controls for penetration testing.</li> <li><strong>Supply Chain Vulnerabilities</strong>: Supply chain vulnerabilities occur from insecure AI libraries, datasets, plug-ins, or model dependencies. They impact operational and deployment security. AI pentesting evaluates dependency risk and validates trusted components.</li> <li><strong>Non-Deterministic Behaviour</strong>: Non-deterministic outputs cause inconsistent test results or unpredictable responses. It affects reliability and repeatability. AI penetration testing applies controlled baselines and cross-validation techniques to improve consistency.</li> <li><strong>False Positives</strong>: AI may misclassify benign behaviour as vulnerabilities, increasing noise and workload. Severity is medium. AI pentesting reduces false positives through correlation, validation, and expert review.</li> <li><strong>Lack of Established Testing Frameworks</strong>: AI testing lacks universally adopted standards in some domains, which leads to inconsistent outcomes. AI penetration testing applies structured methodologies and evidence-based validation practices.</li> <li><strong>Insecure Plug-in Design</strong>: Insecure plug-ins or extensions may execute unsafe actions or expose privileged functions. AI penetration testing assesses plug-in permissions, sandbox isolation, and execution boundaries.</li> <li>Lack of Context Awareness: AI may misinterpret business logic or environment-specific risks without context. The severity of the lack of context awareness vulnerability is medium. AI penetration testing improves context handling through curated datasets and human oversight.</li> <li>Over-permission: Over-permission occurs when AI agents receive broader privileges than required. It increases lateral movement risk. AI pentesting applies least-privilege and fine-grained access controls to reduce the impact or protect against over-permission.</li> </ol> <p>AI improves penetration testing efficiency by automating reconnaissance, reducing false positives, correlating attack paths, prioritising exploitable risks, and enabling continuous security testing at scale. It improves coverage and speed, while human experts assess complex findings and business logic vulnerabilities for accurate, real-world results.</p> <h4>How accurate is AI-powered penetration testing?</h4> <p>AI-powered penetration testing has shown high efficiency and enhanced accuracy, particularly in reconnaissance, vulnerability discovery, and automated attack workflows. Research such as the xOffense framework shows that AI-driven pentesting agents can complete a large portion of penetration testing tasks autonomously, outperforming traditional automation in structured environments. Other studies, including Shell or Nothing, highlight AI’s ability to enhance exploit execution and multi-step attack chaining. However, academic and industry research also note limitations such as false positives, hallucinated findings, and inaccurate severity ratings, reinforcing that human validation remains critical.</p> <p>Security professionals often describe AI as a force multiplier that accelerates scanning, enumeration, and reporting, but not a replacement for skilled penetration testers. Many users report that AI tools generate useful insights quickly, yet still require expert review to validate real-world exploitability and business impact. Overall, both research and community feedback suggest that AI-powered penetration testing is accurate and efficient when used as an augmentation to human expertise, rather than a fully autonomous solution.</p> <h4>What are the features of AI-powered penetration testing tools?</h4> <p>AI-powered penetration testing tools include a set of core features that are generally common across most platforms, regardless of the vendor or implementation.</p> <ol> <li>Automates reconnaissance and scanning: AI-powered tools automatically perform asset discovery, port scanning, service enumeration, and vulnerability identification. This reduces manual effort and speeds up the initial phases of a penetration test.</li> <li>Analyses vulnerabilities intelligently: AI-powered penetration tools use machine learning and contextual analysis to correlate scan results, filter false positives, and identify exploitable weaknesses rather than reporting raw scan data alone.</li> <li>Prioritises risk effectively: AI-driven penetration testing tools assign risk scores based on exploitability, impact, and exposure. This helps security teams focus on the most critical vulnerabilities instead of treating all findings equally.</li> <li>Simulates attack paths: AI penetration testing tools can model attack chains by combining multiple vulnerabilities to show how an attacker could move laterally or escalate privileges within an environment.</li> <li>Adapts to environmental changes: AI continuously learns from configuration changes, new deployments, and emerging vulnerabilities, allowing testing to remain relevant as systems evolve.</li> <li>Generates actionable reports: AI-powered penetration testing tools automatically produce structured reports that include vulnerability descriptions, risk ratings, evidence, and remediation guidance, making results easier to consume by both technical and non-technical stakeholders.</li> <li>Supports continuous testing: Most AI-powered penetration testing tools are designed for recurring or continuous assessments, enabling organisations to validate security posture beyond one-time testing.</li> <li>Augments human testers: AI tools assist penetration testers by accelerating repetitive tasks, suggesting attack techniques, and providing insights, while still allowing human expertise to validate and extend findings.</li> </ol> <p>These generic features make AI-powered penetration testing tools effective at improving speed, coverage, and consistency, while still relying on human oversight for accuracy and context.</p> <h4>What are the misconceptions about AI-powered penetration testing</h4> <p>AI-powered penetration testing is often misunderstood due to marketing hype and a lack of clarity around how these tools actually work in real-world security programs. Below are some of the most common myths, along with the reality and supporting evidence.</p> <p>Myth: AI penetration testing is the same as automated penetration testing</p> <p>Reality: Automated penetration testing relies on predefined scripts and rule-based scanners to identify known vulnerabilities. AI-powered penetration testing goes beyond this by using machine learning, pattern recognition, and adaptive decision-making to correlate findings, prioritise risks, and simulate attacker behaviour over time. AI systems can learn from past tests, adjust attack paths, and reduce false positives, which traditional automation cannot do.</p> <p>Proof: Research such as “Automated Penetration Testing Using Reinforcement Learning” (IEEE) demonstrates that AI models can dynamically select attack strategies based on system responses, rather than following static scan logic used in conventional automated tools.</p> <p>Myth: AI-powered penetration testing eliminates the need for human pentesters</p> <p>Reality: AI enhances penetration testing but does not replace human expertise. AI tools are effective at scale, continuous testing, and data correlation, while human testers are essential for understanding business logic flaws, chaining complex attacks, and validating real-world impact. Most mature security programs use AI as a force multiplier, not a replacement.</p> <p>Proof: Industry studies and practitioner discussions consistently highlight this hybrid approach. For example, academic research published in ACM and practitioner feedback on Reddit’s r/netsec indicate that AI improves efficiency but still requires human oversight for accurate exploitation and contextual risk assessment.</p> <p>Myth: AI-powered penetration testing always produces accurate results</p> <p>Reality: While AI can significantly reduce noise and improve prioritisation, it is only as effective as the data, models, and tuning behind it. Poorly trained AI systems can still generate false positives or miss environment-specific issues. Accuracy improves when AI findings are validated by human testers and aligned with the real infrastructure context.</p> <p>Proof: Research papers analysing AI-based vulnerability detection (such as studies published in IEEE Access) show improved detection rates compared to traditional scanners, but also stress the importance of human validation to avoid over-reliance on automated conclusions.</p> <p>Myth: AI-powered penetration testing is only suitable for large enterprises</p> <p>Reality: AI-driven testing is increasingly accessible to small and mid-sized organisations through cloud-based and PTaaS platforms. These tools reduce manual effort, cost, and testing time, making continuous security testing feasible even for smaller teams.</p> <p>Proof: User discussions on Reddit and Quora frequently mention startups and SMEs adopting AI-assisted testing to compensate for limited internal security resources, especially in cloud-native environments.</p> <h4>What are the ethical challenges in AI-based penetration testing?</h4> <p>The ethical challenges in AI-based penetration testing include authorisation and scope control, data privacy risks, model bias and false confidence, misuse of AI capabilities, transparency of decision-making, and accountability for outcomes. AI-driven tools can rapidly scan, exploit, and correlate vulnerabilities at scale, which increases the risk of testing going beyond approved scopes if strict controls are not enforced. This makes clear authorisation, legal agreements, and continuous scope validation essential. Another major challenge is data privacy, as AI systems may process sensitive logs, credentials, or production data during testing, raising concerns about data storage, retention, and potential exposure.</p> <p>Bias and over-reliance on AI outputs also present ethical risks. AI models are trained on historical data and known attack patterns, which can lead to blind spots, inaccurate risk prioritisation, or false positives being treated as real threats. This can mislead organisations into a false sense of security or cause unnecessary remediation efforts. Additionally, the same AI capabilities used for defensive testing can be repurposed by attackers, creating an ethical responsibility for vendors to implement safeguards that prevent misuse, abuse, or unauthorised replication of offensive techniques.</p> <p>Transparency and accountability further complicate ethical use. AI-powered penetration testing tools often operate as “black boxes,” making it difficult to explain how certain findings were generated or why specific attack paths were prioritised. This lack of explainability can be problematic during audits, legal reviews, or executive decision-making. Ultimately, ethical AI-based penetration testing requires human oversight, clear governance, explainable results, and responsible use policies to ensure that AI enhances security without introducing new legal, operational, or moral risks.</p> </div><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/01/ai-powered-penetration-testing-definition-tools-and-process/" data-a2a-title="AI-powered penetration testing: Definition, Tools and Process"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fai-powered-penetration-testing-definition-tools-and-process%2F&amp;linkname=AI-powered%20penetration%20testing%3A%20Definition%2C%20Tools%20and%20Process" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fai-powered-penetration-testing-definition-tools-and-process%2F&amp;linkname=AI-powered%20penetration%20testing%3A%20Definition%2C%20Tools%20and%20Process" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fai-powered-penetration-testing-definition-tools-and-process%2F&amp;linkname=AI-powered%20penetration%20testing%3A%20Definition%2C%20Tools%20and%20Process" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fai-powered-penetration-testing-definition-tools-and-process%2F&amp;linkname=AI-powered%20penetration%20testing%3A%20Definition%2C%20Tools%20and%20Process" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Fai-powered-penetration-testing-definition-tools-and-process%2F&amp;linkname=AI-powered%20penetration%20testing%3A%20Definition%2C%20Tools%20and%20Process" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://thecyphere.com">Cyphere</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Harman Singh">Harman Singh</a>. Read the original post at: <a href="https://thecyphere.com/blog/ai-penetration-testing/">https://thecyphere.com/blog/ai-penetration-testing/</a> </p>

Washington Post Raid Is a Frightening Reminder: Turn Off Your Phone’s Biometrics Now

  • Nikita Mazurov
  • Published date: 2026-01-30 16:13:06

The search warrant to raid a Washington Post reporter’s home shows how authorities can open your phone without your consent. The post Washington Post Raid Is a Frightening Reminder: Turn Off Your Phone’s Biometrics Now appeared first on The Intercept.

The recent federal raid on the home of Washington Post reporter Hannah Natanson isnt merely an attack by the Trump administration on the free press. Its also a warning to anyone with a smartphone. I… [+4200 chars]

'Our users deserve better' – PrivadoVPN set to leave Switzerland on privacy grounds

PrivadoVPN told TechRadar it's in the process of moving its operations to Iceland. Here's all we know about the move, and what this means for users.

<ul><li>PrivadoVPN told Techradar it is leaving Switzerland on privacy grounds</li><li>The VPN provider is moving to Iceland</li><li>Switzerland may soon expand surveillance obligations on VPNs</li><… [+4214 chars]

How instant UPI apps change small-value payment habits

  • Spotlight Wire
  • Published date: 2026-01-30 09:45:39

The rise of instant UPI apps has revolutionized small-value transactions, eliminating the struggle for exact change and streamlining checkout processes. This speed has fostered a subconscious habit of frequent, smaller digital purchases, altering consumer beh…

The way we handle money has undergone a quiet but profound transformation over the last few years. Not long ago, leaving the house without a bulging wallet full of coins and small notes was unthinkab… [+6622 chars]

10 Best B2B Fintech SSO Solutions in 2026

  • None
  • Published date: 2026-01-30 00:00:00

None

<p>If you’re running a B2B fintech in 2026, you already know that "Enterprise Readiness" isn't just a buzzword—it's the difference between closing a $100k contract and getting stuck in a six-month security audit. Enterprise buyers, especially in banking and finance, won't even look at your demo unless you have SAML, SCIM, and SOC2 compliance baked into your DNA. Building this yourself is a nightmare of edge cases and security risks.</p><p>The landscape of identity management has shifted. No longer is it enough to simply offer a username and password field. In the current high-stakes environment, where 82% of enterprise buyers in Fintech require SOC2 Type II and SAML support before signing a contract (Source: Gartner 2024), your authentication stack is your front door. Choosing the right Single Sign-On (SSO) partner is one of the most critical infrastructure decisions you'll make this year. This guide breaks down the top SSO solutions specifically through the lens of fintech requirements: multi-tenancy, high compliance, and developer speed.</p><h3>Quick Look</h3><ul> <li> <p><strong>SSOJet</strong>: Best for rapid enterprise readiness and <a href="https://ssojet.com/blog/multi-tenant-saas-and-single-sign-on">multi-tenant SaaS</a>.</p> </li> <li> <p><strong>Okta</strong>: Best for massive workforce management and internal security.</p> </li> <li> <p><strong>Auth0</strong>: Best for highly customized developer-led applications.</p> </li> <li> <p><strong>WorkOS</strong>: Best for growth-stage startups needing "Enterprise-Ready" features fast.</p> </li> <li> <p><strong>Microsoft Entra ID</strong>: Best for fintechs embedded in the Microsoft ecosystem.</p> </li> <li> <p><strong>Stytch</strong>: Best for modern, passwordless-first user experiences.</p> </li> <li> <p><strong>Ping Identity</strong>: Best for legacy banking and high-compliance institutional finance.</p> </li> <li> <p><strong>Frontegg</strong>: Best for PLG fintechs with robust self-service needs.</p> </li> <li> <p><strong>Descope</strong>: Best for visual, no-code authentication workflow design.</p> </li> <li> <p><strong>Clerk</strong>: Best for React/Next.js based startups and rapid prototyping.</p> </li> </ul><h3>Comparison Table</h3><table class="border-collapse border border-muted" style="min-width: 100px;"> <colgroup> <col style="min-width: 25px;"> <col style="min-width: 25px;"> <col style="min-width: 25px;"> <col style="min-width: 25px;"></colgroup> <tbody> <tr class="border-b border-muted"> <th class="border border-muted bg-muted px-2 py-1 text-left font-medium" colspan="1" rowspan="1"> <p>Tool Name</p> </th> <th class="border border-muted bg-muted px-2 py-1 text-left font-medium" colspan="1" rowspan="1"> <p>Best For</p> </th> <th class="border border-muted bg-muted px-2 py-1 text-left font-medium" colspan="1" rowspan="1"> <p>Free Plan/Trial</p> </th> <th class="border border-muted bg-muted px-2 py-1 text-left font-medium" colspan="1" rowspan="1"> <p>Starting Price</p> </th> </tr> <tr class="border-b border-muted"> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p><strong>SSOJet</strong></p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>B2B Fintech Startups</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Free Tier Available</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Competitive/Usage-based</p> </td> </tr> <tr class="border-b border-muted"> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p><strong>Okta</strong></p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Large Enterprise Workforce</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Free Trial (30 Days)</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>$2/user/month (Workforce)</p> </td> </tr> <tr class="border-b border-muted"> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p><strong>Auth0</strong></p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Custom Developer Flows</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Free for up to 7k users</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>$35/month (B2C) / Custom (B2B)</p> </td> </tr> <tr class="border-b border-muted"> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p><strong>WorkOS</strong></p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Rapid Enterprise-Readiness</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Free for first connection</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>$125/connection/month</p> </td> </tr> <tr class="border-b border-muted"> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p><strong>Microsoft Entra</strong></p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Microsoft Ecosystem</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Included in M365</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Per-license basis</p> </td> </tr> <tr class="border-b border-muted"> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p><strong>Stytch</strong></p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Passwordless UX</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Free Tier Available</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Usage-based</p> </td> </tr> <tr class="border-b border-muted"> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p><strong>Ping Identity</strong></p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Legacy Banking</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Free Trial</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Custom Enterprise</p> </td> </tr> <tr class="border-b border-muted"> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p><strong>Frontegg</strong></p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>PLG &amp; Tenant Management</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Free Tier Available</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>$99/month</p> </td> </tr> <tr class="border-b border-muted"> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p><strong>Descope</strong></p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Visual Workflows</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Free Tier Available</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Usage-based</p> </td> </tr> <tr class="border-b border-muted"> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p><strong>Clerk</strong></p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>React/Next.js Startups</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>Free Tier Available</p> </td> <td class="border border-muted px-2 py-1" colspan="1" rowspan="1"> <p>$25/month</p> </td> </tr> </tbody> </table><h2>1. SSOJet</h2><p><img decoding="async" src="https://ai-gen-images.compile7.com/screenshots/ssojet.com__20260130_101105.jpg" alt="SSOJet Dashboard" width="100%" align="left" style="width: 100%; display: block;"></p><p><strong>Best for:</strong> B2B Fintech Startups and Scale-ups needing rapid Enterprise-readiness.</p><p><a href="https://ssojet.com/">SSOJet</a> is the modern standard for B2B fintechs because it’s built specifically for the multi-tenant needs of SaaS companies. Unlike legacy tools that treat "customers" as "employees," SSOJet provides a dedicated "Enterprise Readiness" layer that handles SAML, OIDC, and Directory Sync (SCIM) out of the box. For fintechs, its SOC2-ready architecture and developer-first API mean you can offer enterprise-grade auth in days, not months.</p><p>The platform is designed to bridge the gap between complex enterprise requirements and developer speed. It allows fintech founders to close enterprise deals faster without having to build custom authentication infrastructure for every new client. Its multi-tenant architecture is particularly strong, allowing you to isolate customer data and configurations cleanly, which is a common requirement in financial services audits.</p><h3><strong>Pros:</strong></h3><ul> <li> <p>Developer-first API and easy integration with modern frameworks.</p> </li> <li> <p>Built specifically for B2B multi-tenancy (unlike generic B2C tools).</p> </li> <li> <p>Affordable and predictable pricing compared to Okta/Auth0.</p> </li> <li> <p>High focus on security compliance (SOC2 ready).</p> </li> </ul><h3><strong>Cons:</strong></h3><ul> <li> <p>Newer player compared to legacy giants like Ping Identity.</p> </li> <li> <p>Smaller community ecosystem than Auth0.</p> </li> </ul><h3><strong>Pricing Summary:</strong></h3><ul> <li> <p><strong>Free Plan:</strong> 30-day free trial available for any application type, unlimited organizations and users.</p> </li> <li> <p><strong>Paid Plan:</strong> Business Plan starts from $99 per month for 2 SSO connections; Enterprise (Private Cloud) plans available upon contact.</p> </li> </ul><h2>2. Okta Workforce Identity</h2><p><img decoding="async" src="https://ai-gen-images.compile7.com/screenshots/www.okta.com__20260130_101114.jpg" alt="Okta Interface" width="100%" align="left" style="width: 100%; display: block;"></p><p><strong>Best for:</strong> Large Enterprise Fintechs with massive internal workforces.</p><p>Okta is the industry standard for internal employee management. If your fintech is scaling to thousands of employees and needs to manage internal access to thousands of different apps, Okta is the safest bet. Its Workforce Identity Cloud provides a centralized hub for managing every employee's access to internal tools, from Slack to AWS.</p><h3><strong>Pros:</strong></h3><ul> <li> <p>The industry standard with a massive integration catalog.</p> </li> <li> <p>Robust security analytics and threat detection.</p> </li> <li> <p>Unmatched reliability and uptime records.</p> </li> </ul><h3><strong>Cons:</strong></h3><ul> <li> <p>Extremely expensive for smaller teams.</p> </li> <li> <p>Complex setup requires dedicated administrative time.</p> </li> </ul><h3><strong>Pricing Summary:</strong></h3><ul> <li> <p><strong>Free Plan:</strong> 30-day free trial available for both Workforce and Customer Identity platforms.</p> </li> <li> <p><strong>Paid Plan:</strong> Workforce Identity starts from $2 per user/month; Customer Identity starts from $3,000 per month for the Enterprise base platform.</p> </li> </ul><h2>3. Auth0 (by Okta)</h2><p><img decoding="async" src="https://ai-gen-images.compile7.com/screenshots/auth0.com__20260130_101119.jpg" alt="Auth0 Dashboard" width="100%" align="left" style="width: 100%; display: block;"></p><p><strong>Best for:</strong> Highly customized developer-led Fintech applications.</p><p>Auth0 remains the gold standard for developers who need to build highly customized, complex authentication flows. Its "Rules" and "Hooks" allow you to inject custom JavaScript logic into the login process, which is vital for fintechs dealing with complex KYC (Know Your Customer) requirements.</p><h3><strong>Pros:</strong></h3><ul> <li> <p>Great documentation and developer experience.</p> </li> <li> <p>Extremely flexible for complex, logic-heavy auth flows.</p> </li> <li> <p>Universal Login provides a secure, hosted UI.</p> </li> </ul><h3><strong>Cons:</strong></h3><ul> <li> <p>Pricing escalates very quickly with user growth.</p> </li> <li> <p>Support quality has seen complaints post-acquisition.</p> </li> </ul><h3><strong>Pricing Summary:</strong></h3><ul> <li> <p><strong>Free Plan:</strong> Free for up to 7,000 monthly active users (MAUs) with unlimited social connections.</p> </li> <li> <p><strong>Paid Plan:</strong> B2C plans start at $35/month; B2B Enterprise plans require custom quotes.</p> </li> </ul><h2>4. WorkOS</h2><p><img decoding="async" src="https://ai-gen-images.compile7.com/screenshots/workos.com__20260130_101126.jpg" alt="WorkOS Admin Portal" width="100%" align="left" style="width: 100%; display: block;"></p><p><strong>Best for:</strong> Growth-stage SaaS aiming for "Enterprise-Ready" status quickly.</p><p>WorkOS popularized the "API for Enterprise Readiness." It’s designed specifically for SaaS companies that want to add SSO support for their customers without becoming experts in the SAML protocol. Their "Admin Portal" allows your customers' IT admins to configure their own SSO settings via a self-service UI.</p><h3><strong>Pros:</strong></h3><ul> <li> <p>Excellent UI for end-user admins (Self-serve).</p> </li> <li> <p>Fastest path to "Enterprise Ready" status.</p> </li> <li> <p>Great support for Directory Sync (SCIM).</p> </li> </ul><h3><strong>Cons:</strong></h3><ul> <li> <p>Can become a "black box" for deep customization.</p> </li> <li> <p>Pricing per-connection can be high for some business models.</p> </li> </ul><h3><strong>Pricing Summary:</strong></h3><ul> <li> <p><strong>Free Plan:</strong> Free for the first connection; User Management is free for the first 1M users.</p> </li> <li> <p><strong>Paid Plan:</strong> SSO connections start from $125 per connection/month.</p> </li> </ul><h2>5. Microsoft Entra ID</h2><p><img decoding="async" src="https://ai-gen-images.compile7.com/screenshots/www.microsoft.com_en-us_security_business_identity_20260130_101151.jpg" alt="Microsoft Entra ID Portal" width="100%" align="left" style="width: 100%; display: block;"></p><p><strong>Best for:</strong> Fintechs already embedded in the Microsoft/Office 365 ecosystem.</p><p>Microsoft Entra ID is the backbone of most corporate IT environments. If your clients are already using Office 365, the friction for them to adopt your fintech app is significantly reduced.</p><h3><strong>Pros:</strong></h3><ul> <li> <p>Often included in existing enterprise agreements.</p> </li> <li> <p>Top-tier compliance and security certifications.</p> </li> <li> <p>Seamless integration with Windows and Office 365.</p> </li> </ul><h3><strong>Cons:</strong></h3><ul> <li> <p>UI is cluttered and complex.</p> </li> <li> <p>Primarily focused on internal employees rather than external customers.</p> </li> </ul><h3><strong>Pricing Summary:</strong></h3><ul> <li> <p><strong>Free Plan:</strong> Included with Microsoft 365 subscriptions.</p> </li> <li> <p><strong>Paid Plan:</strong> Premium P1 starts at $6 per user/month; P2 starts at $9 per user/month.</p> </li> </ul><h2>6. Stytch</h2><p><img decoding="async" src="https://ai-gen-images.compile7.com/screenshots/stytch.com__20260130_101159.jpg" alt="Stytch Authentication Flow" width="100%" align="left" style="width: 100%; display: block;"></p><p><strong>Best for:</strong> Passwordless-first Fintech apps and modern UX.</p><p>Stytch is a leader in the "passwordless" movement. For modern fintechs looking to reduce friction via magic links, biometrics, and device fingerprinting, Stytch offers a sleek, API-first experience.</p><h3><strong>Pros:</strong></h3><ul> <li> <p>Modern API and focus on reducing user friction.</p> </li> <li> <p>Strong built-in fraud prevention and bot detection.</p> </li> <li> <p>Excellent support for biometrics and magic links.</p> </li> </ul><h3><strong>Cons:</strong></h3><ul> <li> <p>B2B SSO features are newer than their B2C offerings.</p> </li> <li> <p>Smaller enterprise track record than legacy providers.</p> </li> </ul><h3><strong>Pricing Summary:</strong></h3><ul> <li> <p><strong>Free Plan:</strong> Free tier for up to 10,000 monthly active users (MAUs).</p> </li> <li> <p><strong>Paid Plan:</strong> Usage-based pricing; B2B SSO connections start at $125/month.</p> </li> </ul><h2>7. Ping Identity</h2><p><img decoding="async" src="https://ai-gen-images.compile7.com/screenshots/www.pingidentity.com__20260130_101209.jpg" alt="Ping Identity Orchestration" width="100%" align="left" style="width: 100%; display: block;"></p><p><strong>Best for:</strong> Legacy Banking and High-Compliance Financial Institutions.</p><p>Ping Identity is frequently found in the world's largest banks because it supports hybrid cloud deployments and legacy protocols that modern startups usually ignore.</p><h3><strong>Pros:</strong></h3><ul> <li> <p>Deep experience in high-finance and banking.</p> </li> <li> <p>Supports hybrid and on-premise deployments.</p> </li> <li> <p>Unmatched support for legacy security protocols.</p> </li> </ul><h3><strong>Cons:</strong></h3><ul> <li> <p>Very high barrier to entry and cost.</p> </li> <li> <p>Steep learning curve for developers.</p> </li> </ul><h3><strong>Pricing Summary:</strong></h3><ul> <li> <p><strong>Free Plan:</strong> 30-day free trial available.</p> </li> <li> <p><strong>Paid Plan:</strong> Custom Enterprise pricing only; typically starts at $35,000+ annually.</p> </li> </ul><h2>8. Frontegg</h2><p><img decoding="async" src="https://ai-gen-images.compile7.com/screenshots/frontegg.com__20260130_101215.jpg" alt="Frontegg Management UI" width="100%" align="left" style="width: 100%; display: block;"></p><p><strong>Best for:</strong> PLG (Product-Led Growth) Fintechs with self-service needs.</p><p>Frontegg includes self-service tenant management UIs. This allows your users to manage their own teams, roles, and security settings without your intervention.</p><h3><strong>Pros:</strong></h3><ul> <li> <p>End-to-end user management, not just SSO.</p> </li> <li> <p>Excellent self-service UI for end-users.</p> </li> <li> <p>Strong multi-tenancy and organization management.</p> </li> </ul><h3><strong>Cons:</strong></h3><ul> <li> <p>Can feel "over-engineered" for simple use cases.</p> </li> <li> <p>Pricing can be complex due to the breadth of features.</p> </li> </ul><h3><strong>Pricing Summary:</strong></h3><ul> <li> <p><strong>Free Plan:</strong> Free for up to 7,500 monthly active users (MAUs).</p> </li> <li> <p><strong>Paid Plan:</strong> Paid tiers start at $99/month for growing teams.</p> </li> </ul><h2>9. Descope</h2><p><img decoding="async" src="https://ai-gen-images.compile7.com/screenshots/www.descope.com__20260130_101221.jpg" alt="Descope Workflow Builder" width="100%" align="left" style="width: 100%; display: block;"></p><p><strong>Best for:</strong> Visual workflow-based authentication design.</p><p>Descope allows fintech founders to "drag and drop" their authentication flows. Their visual workflow builder allows you to design complex login journeys without writing hundreds of lines of code.</p><h3><strong>Pros:</strong></h3><ul> <li> <p>Rapid prototyping with visual flow builders.</p> </li> <li> <p>Easy to change auth logic without redeploying code.</p> </li> <li> <p>Modern, clean API for integration.</p> </li> </ul><h3><strong>Cons:</strong></h3><ul> <li> <p>Relatively new to the market.</p> </li> <li> <p>Visual approach might be a turn-off for "code-only" purists.</p> </li> </ul><h3><strong>Pricing Summary:</strong></h3><ul> <li> <p><strong>Free Plan:</strong> Free Forever for up to 7,500 monthly active users (MAUs).</p> </li> <li> <p><strong>Paid Plan:</strong> Pro Plan starts from $249 per month.</p> </li> </ul><h2>10. Clerk</h2><p><img decoding="async" src="https://cdn.pseo.one/6853a4a8a2796a91bb994a76/687e6d61f6fe799d28851eff/topics/697c906fa3cd5765cc0c10dd/fd0fa31b-8d6c-49d3-8677-a2b469e3d1f7.webp" width="100%" align="left" style="width: 100%; display: block;"></p><p><strong>Best for:</strong> React/Next.js based Fintech startups.</p><p>Clerk is the fastest way to get a React or Next.js-based fintech up and running with beautiful, pre-built UI components for sign-in and user profiles.</p><h3><strong>Pros:</strong></h3><ul> <li> <p>Fastest setup for modern web frameworks like Next.js.</p> </li> <li> <p>Beautiful, pre-built UI components.</p> </li> <li> <p>Great developer experience and documentation.</p> </li> </ul><h3><strong>Cons:</strong></h3><ul> <li> <p>More focused on B2C/SMB than deep enterprise.</p> </li> <li> <p>Very opinionated; hard to customize deeply.</p> </li> </ul><h3><strong>Pricing Summary:</strong></h3><ul> <li> <p><strong>Free Plan:</strong> Free for up to 10,000 monthly active users (MAUs).</p> </li> <li> <p><strong>Paid Plan:</strong> Pro Plan starts from $25 per month.</p> </li> </ul><h2>Frequently Asked Questions (FAQ)</h2><h3><strong>1. Why is SAML so important for B2B Fintech?</strong></h3><p>SAML is the industry standard for exchanging authentication data. Most enterprise IT departments will not allow their employees to use your app without it, as it allows them to revoke access centrally and enforce corporate security policies.</p><h3><strong>2. What is the difference between SSO and CIAM?</strong></h3><p>SSO is a specific feature that allows a user to log in once. CIAM (Customer Identity and Access Management) is the broader category that includes SSO, but also covers user registration, profile management, and fraud detection.</p><h3><strong>3. Does my fintech really need SCIM?</strong></h3><p>If you are selling to companies with more than 500 employees, yes. SCIM automates the provisioning and deprovisioning of users. When an employee leaves your customer's company, SCIM ensures they are automatically removed from your fintech app.</p><h3><strong>4. How does SSO help with SOC2 compliance?</strong></h3><p>SOC2 requires strict controls over who can access customer data. Professional SSO providers give you detailed audit logs showing exactly who logged in, when, and how they were authenticated, which is essential for auditors.</p><h3><strong>5. Is it cheaper to build or buy SSO?</strong></h3><p>In 2026, it is almost always "buy." Building a secure, multi-tenant SAML integration takes months of senior engineering time. The opportunity cost of not shipping core fintech features while struggling with security protocols is too high for most startups.</p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/01/10-best-b2b-fintech-sso-solutions-in-2026/" data-a2a-title="10 Best B2B Fintech SSO Solutions in 2026"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2F10-best-b2b-fintech-sso-solutions-in-2026%2F&amp;linkname=10%20Best%20B2B%20Fintech%20SSO%20Solutions%20in%202026" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2F10-best-b2b-fintech-sso-solutions-in-2026%2F&amp;linkname=10%20Best%20B2B%20Fintech%20SSO%20Solutions%20in%202026" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2F10-best-b2b-fintech-sso-solutions-in-2026%2F&amp;linkname=10%20Best%20B2B%20Fintech%20SSO%20Solutions%20in%202026" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2F10-best-b2b-fintech-sso-solutions-in-2026%2F&amp;linkname=10%20Best%20B2B%20Fintech%20SSO%20Solutions%20in%202026" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2F10-best-b2b-fintech-sso-solutions-in-2026%2F&amp;linkname=10%20Best%20B2B%20Fintech%20SSO%20Solutions%20in%202026" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://ssojet.com/blog">SSOJet - Enterprise SSO &amp;amp; Identity Solutions</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by SSOJet - Enterprise SSO &amp; Identity Solutions">SSOJet - Enterprise SSO &amp; Identity Solutions</a>. Read the original post at: <a href="https://ssojet.com/blog/best-b2b-fintech-sso-solutions">https://ssojet.com/blog/best-b2b-fintech-sso-solutions</a> </p>

Randall Munroe’s XKCD ‘Conic Sections’

  • None
  • Published date: 2026-01-30 00:00:00

None

<figure class=" sqs-block-image-figure intrinsic "> <p> <img data-stretch="false" data-image="https://images.squarespace-cdn.com/content/v1/5355d604e4b03c3e9896e131/b0ad1674-a1c5-40e3-9502-bd3688af8950/conic_sections.png" data-image-dimensions="288x322" data-image-focal-point="0.5,0.5" alt="" data-load="false" elementtiming="system-image-block" src="https://images.squarespace-cdn.com/content/v1/5355d604e4b03c3e9896e131/b0ad1674-a1c5-40e3-9502-bd3688af8950/conic_sections.png?format=1000w" width="288" height="322" sizes="auto, (max-width: 640px) 100vw, (max-width: 767px) 100vw, 100vw" onload='this.classList.add("loaded")' srcset="https://images.squarespace-cdn.com/content/v1/5355d604e4b03c3e9896e131/b0ad1674-a1c5-40e3-9502-bd3688af8950/conic_sections.png?format=100w 100w, https://images.squarespace-cdn.com/content/v1/5355d604e4b03c3e9896e131/b0ad1674-a1c5-40e3-9502-bd3688af8950/conic_sections.png?format=300w 300w, https://images.squarespace-cdn.com/content/v1/5355d604e4b03c3e9896e131/b0ad1674-a1c5-40e3-9502-bd3688af8950/conic_sections.png?format=500w 500w, https://images.squarespace-cdn.com/content/v1/5355d604e4b03c3e9896e131/b0ad1674-a1c5-40e3-9502-bd3688af8950/conic_sections.png?format=750w 750w, https://images.squarespace-cdn.com/content/v1/5355d604e4b03c3e9896e131/b0ad1674-a1c5-40e3-9502-bd3688af8950/conic_sections.png?format=1000w 1000w, https://images.squarespace-cdn.com/content/v1/5355d604e4b03c3e9896e131/b0ad1674-a1c5-40e3-9502-bd3688af8950/conic_sections.png?format=1500w 1500w, https://images.squarespace-cdn.com/content/v1/5355d604e4b03c3e9896e131/b0ad1674-a1c5-40e3-9502-bd3688af8950/conic_sections.png?format=2500w 2500w" loading="lazy" decoding="async" data-loader="sqs"><figcaption class="image-caption-wrapper"> <p class=""><strong>via the comic artistry and dry wit of Randall Munroe, creator of XKCD</strong></p> </figcaption></p></figure><p><a href="https://www.infosecurity.us/blog/2026/1/30/randall-munroes-xkcd-conic-sections">Permalink</a></p><p> </p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/01/randall-munroes-xkcd-conic-sections/" data-a2a-title="Randall Munroe’s XKCD ‘Conic Sections’"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Frandall-munroes-xkcd-conic-sections%2F&amp;linkname=Randall%20Munroe%E2%80%99s%20XKCD%20%E2%80%98Conic%20Sections%E2%80%99" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Frandall-munroes-xkcd-conic-sections%2F&amp;linkname=Randall%20Munroe%E2%80%99s%20XKCD%20%E2%80%98Conic%20Sections%E2%80%99" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Frandall-munroes-xkcd-conic-sections%2F&amp;linkname=Randall%20Munroe%E2%80%99s%20XKCD%20%E2%80%98Conic%20Sections%E2%80%99" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Frandall-munroes-xkcd-conic-sections%2F&amp;linkname=Randall%20Munroe%E2%80%99s%20XKCD%20%E2%80%98Conic%20Sections%E2%80%99" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Frandall-munroes-xkcd-conic-sections%2F&amp;linkname=Randall%20Munroe%E2%80%99s%20XKCD%20%E2%80%98Conic%20Sections%E2%80%99" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://www.infosecurity.us/">Infosecurity.US</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Marc Handelman">Marc Handelman</a>. Read the original post at: <a href="https://xkcd.com/3189/">https://xkcd.com/3189/</a> </p>

Friday Squid Blogging: New Squid Species Discovered

  • None
  • Published date: 2026-01-30 00:00:00

None

<p>A <a href="https://www.livescience.com/animals/mollusks/very-novel-and-very-puzzling-unknown-species-of-squid-spotted-burying-itself-upside-down-pretending-to-be-a-plant">new species of squid</a>. pretends to be a plant:</p><blockquote> <p>Scientists have filmed a never-before-seen species of deep-sea squid burying itself upside down in the seafloor—a behavior never documented in cephalopods. They captured the bizarre scene while studying the depths of the Clarion-Clipperton Zone (CCZ), an abyssal plain in the Pacific Ocean targeted for deep-sea mining.</p> <p>The team described the encounter in a study published Nov. 25 in the journal <a href="https://esajournals.onlinelibrary.wiley.com/doi/10.1002/ecy.70257"><i>Ecology</i></a>, writing that the animal appears to be an undescribed species of whiplash squid. At a depth of roughly 13,450 feet (4,100 meters), the squid had buried almost its entire body in sediment and was hanging upside down, with its siphon and two long <a href="https://www.livescience.com/difference-arms-tentacles">tentacles</a> held rigid above the seafloor.</p> <p>“The fact that this is a squid and it’s covering itself in mud—it’s novel for squid and the fact that it is upside down,” lead author <a href="https://www.sams.ac.uk/people/research-students/mejia-saenz-alejandra-/">Alejandra Mejía-Saenz</a>, a deep-sea ecologist at the Scottish Association for Marine Science, told Live Science. “We had never seen anything like that in any cephalopods…. It was very novel and very puzzling.”</p> </blockquote><p>As usual, you can also use this squid post to talk about the security stories in the news that I haven’t covered.</p><p><a href="https://www.schneier.com/blog/archives/2024/06/new-blog-moderation-policy.html">Blog moderation policy.</a></p><div class="spu-placeholder" style="display:none"></div><div class="addtoany_share_save_container addtoany_content addtoany_content_bottom"><div class="a2a_kit a2a_kit_size_20 addtoany_list" data-a2a-url="https://securityboulevard.com/2026/01/friday-squid-blogging-new-squid-species-discovered/" data-a2a-title="Friday Squid Blogging: New Squid Species Discovered"><a class="a2a_button_twitter" href="https://www.addtoany.com/add_to/twitter?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Ffriday-squid-blogging-new-squid-species-discovered%2F&amp;linkname=Friday%20Squid%20Blogging%3A%20New%20Squid%20Species%20Discovered" title="Twitter" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_linkedin" href="https://www.addtoany.com/add_to/linkedin?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Ffriday-squid-blogging-new-squid-species-discovered%2F&amp;linkname=Friday%20Squid%20Blogging%3A%20New%20Squid%20Species%20Discovered" title="LinkedIn" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_facebook" href="https://www.addtoany.com/add_to/facebook?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Ffriday-squid-blogging-new-squid-species-discovered%2F&amp;linkname=Friday%20Squid%20Blogging%3A%20New%20Squid%20Species%20Discovered" title="Facebook" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_reddit" href="https://www.addtoany.com/add_to/reddit?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Ffriday-squid-blogging-new-squid-species-discovered%2F&amp;linkname=Friday%20Squid%20Blogging%3A%20New%20Squid%20Species%20Discovered" title="Reddit" rel="nofollow noopener" target="_blank"></a><a class="a2a_button_email" href="https://www.addtoany.com/add_to/email?linkurl=https%3A%2F%2Fsecurityboulevard.com%2F2026%2F01%2Ffriday-squid-blogging-new-squid-species-discovered%2F&amp;linkname=Friday%20Squid%20Blogging%3A%20New%20Squid%20Species%20Discovered" title="Email" rel="nofollow noopener" target="_blank"></a><a class="a2a_dd addtoany_share_save addtoany_share" href="https://www.addtoany.com/share"></a></div></div><p class="syndicated-attribution">*** This is a Security Bloggers Network syndicated blog from <a href="https://www.schneier.com/">Schneier on Security</a> authored by <a href="https://securityboulevard.com/author/0/" title="Read other posts by Bruce Schneier">Bruce Schneier</a>. Read the original post at: <a href="https://www.schneier.com/blog/archives/2026/01/friday-squid-blogging-new-squid-species-discovered.html">https://www.schneier.com/blog/archives/2026/01/friday-squid-blogging-new-squid-species-discovered.html</a> </p>