BappDescription.html

<h2>Requirements</h2>
<ul>
<li><b>Linux OS</b></li>
<li>Ensure that Chrome/Chromium installed in a standard location</li>
<li>Obtain the appropriate chromedriver for your OS and version of Chrome (see: http://chromedriver.chromium.org/downloads/version-selection). Note the file location.</li>
</ul>

<p>Adds passive checks to the Burp scanner. The following is a list of items it will look for:</p>
<ul>
<li>Cross-Domain Script Includes (DOM)</li>
<li>JavaScript Missing Subresource Integrity Attributes</li>
<li>CORS Headers Do Not Require Subresource Integrity</li>
<li>Malicious/Vulnerable JavaScript Includes</li>
<li>Subresource Integrity Failed Validation</li>
<li>Cross-Domain Script Includes where DNS Resolution Fails</li>
</ul>
<p>It does this by looking at the HTML received and loads the DOM via a headless Chromium instance using Selenium.</p>

<h2>Configuration</h2>
<p>A "JavaScript Security" tab will appear in your burp session which allows you to configure two things:</p>
<ul>
<li>The path to the chromedriver binary you want to use. This defaults to the bundled version appropriate for your operating system. Setting a chromedriver here will override the default.</li>
<li>The delay before evaluating the DOM (in seconds). As all of the JavaScript is gathered and run, the DOM may change over time. For advanced pages or slow connections, you might want to bump this up, but passive scans will take longer. The default, which I've had luck with, is 10 seconds.</li>
<p>It is possible to load indicators of compromise (IOCs) as JSON files through the GUI tab. Examples are provided in the intel folder.</p>

<h2>Execution</h2>
<p>When you run passive checks, the checks installed will run. Any output or errors will appear on the Extender/Extensions tab under "JavaScript Security -- SRI and Threat Intel".</p>