<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Daily Cyber Insights]]></title><description><![CDATA[Daily Cyber Insights]]></description><link>https://dailycyberinsights.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Fri, 20 Nov 2026 19:24:40 GMT</lastBuildDate><atom:link href="https://dailycyberinsights.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Continuous vs Annual Pentest in a CI/CD World: Are You Testing Often Enough?]]></title><description><![CDATA[Continuous vs annual pentest: Explore why traditional yearly security assessments may not keep up with modern application changes and deployments.]]></description><link>https://dailycyberinsights.hashnode.dev/continuous-vs-annual-pentest-in-a-ci-cd-world-are-you-testing-often-enough</link><guid isPermaLink="true">https://dailycyberinsights.hashnode.dev/continuous-vs-annual-pentest-in-a-ci-cd-world-are-you-testing-often-enough</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[information security]]></category><category><![CDATA[technology]]></category><category><![CDATA[penetration testing]]></category><category><![CDATA[DevSecOps]]></category><category><![CDATA[Web Development]]></category><category><![CDATA[Security]]></category><category><![CDATA[business]]></category><dc:creator><![CDATA[Abrar Bin Habib]]></dc:creator><pubDate>Tue, 17 Nov 2026 16:18:51 GMT</pubDate><content:encoded><![CDATA[<p>Modern development teams do not always release software once or twice a year.</p>
<p>With CI/CD pipelines, teams can deploy application updates frequently. A single application may receive multiple code changes, dependency updates, API modifications, and configuration changes within a short period.</p>
<p>But security testing does not always follow the same release cycle.</p>
<p>This creates an important discussion around <strong>continuous vs annual pentest</strong>.</p>
<h2>The mismatch between development and security testing</h2>
<p>Consider a development team that deploys updates every week.</p>
<p>The organization performs a penetration test once a year.</p>
<p>The assessment may identify vulnerabilities in the tested version of the application. Developers then work on remediation, and the organization receives a clearer picture of its security weaknesses.</p>
<p>However, the application continues to evolve after the assessment.</p>
<p>A new API endpoint may introduce an unexpected access-control issue. An authentication change may affect session management. A third-party dependency may introduce a new security concern.</p>
<p>These examples do not mean every deployment creates a vulnerability. They demonstrate why the security condition of an application can change after a scheduled assessment.</p>
<h2>Where does continuous penetration testing fit?</h2>
<p>Continuous penetration testing aims to provide more frequent security assessments as applications and infrastructure change.</p>
<p>It can complement development workflows by helping organizations identify weaknesses without relying entirely on a single annual testing window.</p>
<p>However, continuous testing should not be confused with running automated vulnerability scans repeatedly.</p>
<p>A meaningful testing strategy needs appropriate scope, security expertise, validation of findings, and a process for prioritizing and fixing vulnerabilities.</p>
<h2>Should every CI/CD pipeline include continuous pentesting?</h2>
<p>Not necessarily in the same way.</p>
<p>The right approach depends on the application's risk, deployment frequency, architecture, exposure, and existing security controls.</p>
<p>Some organizations may benefit from testing around significant releases, while others may require more frequent assessment.</p>
<p>The important thing is to avoid treating an annual report as a permanent guarantee of application security.</p>
<p>If your team is evaluating continuous vs annual pentest, there are several practical differences worth understanding before choosing a testing strategy.</p>
<p>Penough explores those differences and explains why one pentest a year may leave organizations exposed:</p>
<p><a href="https://penough.com/blog/continuous-penetration-testing-why-one-pentest-a-year-leaves-you-exposed/">Read the complete guide to continuous penetration testing</a></p>
]]></content:encoded></item><item><title><![CDATA[Why traditional security awareness is failing against new phishing techniques]]></title><description><![CDATA[Discover the new phishing techniques attackers are using in 2026, from AI voice notes to fake portals, & learn how to spot them before it's too late.]]></description><link>https://dailycyberinsights.hashnode.dev/why-traditional-security-awareness-is-failing-against-new-phishing-techniques</link><guid isPermaLink="true">https://dailycyberinsights.hashnode.dev/why-traditional-security-awareness-is-failing-against-new-phishing-techniques</guid><category><![CDATA[phishing]]></category><category><![CDATA[cybersecurity]]></category><category><![CDATA[#infosec]]></category><category><![CDATA[securityawareness]]></category><dc:creator><![CDATA[Abrar Bin Habib]]></dc:creator><pubDate>Sat, 14 Nov 2026 15:15:11 GMT</pubDate><content:encoded><![CDATA[<p>If you think phishing is just a badly spelled email from a fake prince, you are going to fall victim to the <strong>new phishing techniques</strong> attackers are using in 2026.</p>
<p>Attackers are now using AI-generated voice notes, highly targeted SMS messages (smishing), and fake login portals that look identical to your actual company intranet. Because these attacks bypass basic spam filters, human error is at an all-time high.</p>
<p>In this <a href="https://penough.com/blog/phishing-in-2026-new-tactics-attackers-are-using-and-how-to-spot-them/">latest article</a>, the most common spam email domains of 2026 are broken down, along with the exact steps teams need to take to spot these attacks before it's too late.</p>
]]></content:encoded></item><item><title><![CDATA[How secure is your bank's ATM network, really?]]></title><description><![CDATA[Discover how ATM key injection and jackpotting attacks bypass normal transactions, and learn how banks can secure these high-impact attack surfaces.]]></description><link>https://dailycyberinsights.hashnode.dev/how-secure-is-your-bank-s-atm-network-really</link><guid isPermaLink="true">https://dailycyberinsights.hashnode.dev/how-secure-is-your-bank-s-atm-network-really</guid><category><![CDATA[cybersecurity]]></category><category><![CDATA[atm machine]]></category><category><![CDATA[bank]]></category><category><![CDATA[Security]]></category><category><![CDATA[injection]]></category><dc:creator><![CDATA[Abrar Bin Habib]]></dc:creator><pubDate>Sat, 14 Nov 2026 14:56:01 GMT</pubDate><content:encoded><![CDATA[<p>When we think of ATM hacks, we usually picture skimmers or stolen cards. But there is a much more sophisticated threat lurking inside the machine: <strong>ATM key injection</strong>.</p>
<p>This type of attack targets the ATM middleware and the communication between the software and the cash dispenser hardware. Instead of just stealing customer data, attackers use key injection to bypass the normal transaction process entirely—tricking the machine into dispensing cash without a valid card (often called "jackpotting").</p>
<p>Securing an ATM is not just about physical locks; it requires hardening the endpoint, monitoring the network, and strictly managing cryptographic keys.</p>
<p>I recently wrote a deep dive on how these high-impact attack surfaces work, the reality of jackpotting, and how banks can defend against them.</p>
<p><strong>Read the full breakdown</strong> <a href="https://penough.com/blog/atm-security-from-cash-dispensers-to-high-impact-attack-surfaces/"><strong>here</strong></a></p>
]]></content:encoded></item></channel></rss>