<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DevSecOps tools on Kuldeep Pisda</title><link>https://kdpisda.in/tag/devsecops-tools/</link><description>Recent content in DevSecOps tools on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 29 Nov 2025 12:39:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/devsecops-tools/index.xml" rel="self" type="application/rss+xml"/><item><title>12 Essential Application Security Testing Tools for 2025</title><link>https://kdpisda.in/12-essential-application-security-testing-tools-for-2025/</link><pubDate>Sat, 29 Nov 2025 12:39:00 +0530</pubDate><guid>https://kdpisda.in/12-essential-application-security-testing-tools-for-2025/</guid><description>&lt;p&gt;It started with a weird log entry. A seemingly harmless error that, after hours of digging, turned out to be a potential security hole. It was a wake up call. As developers, we are focused on shipping features, but what happens when the pressure to deliver creates blind spots? This is not just a story about a bug; it is about realizing that our CI/CD pipelines needed a better gatekeeper. We had a problem, and the solution required a systematic way to catch these issues before they reached production, turning a manual, reactive process into an automated, proactive one.&lt;/p&gt;</description></item></channel></rss>