<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tarun Bansal on The Trail of Bits Blog</title><link>https://miscreants.github.io/blog.trailofbits.com/authors/tarun-bansal/</link><description>Recent content in Tarun Bansal on The Trail of Bits Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 22 Mar 2024 09:00:28 -0400</lastBuildDate><atom:link href="https://miscreants.github.io/blog.trailofbits.com/authors/tarun-bansal/index.xml" rel="self" type="application/rss+xml"/><item><title>Why fuzzing over formal verification?</title><link>https://miscreants.github.io/blog.trailofbits.com/2024/03/22/why-fuzzing-over-formal-verification/</link><pubDate>Fri, 22 Mar 2024 09:00:28 -0400</pubDate><guid>https://miscreants.github.io/blog.trailofbits.com/2024/03/22/why-fuzzing-over-formal-verification/</guid><description>We recently introduced our new offering, invariant development as a service. A recurring question that we are asked is, &amp;ldquo;Why fuzzing instead of formal verification?&amp;rdquo; And the answer is, &amp;ldquo;It&amp;rsquo;s complicated.&amp;rdquo; We use fuzzing for most of our audits but have used formal verification methods in the […]</description></item></channel></rss>