From 503d1ee76d147b47f6e783d8e3b0a687942a1dea Mon Sep 17 00:00:00 2001
From: Josh <ascetik@gmail.com>
Date: Wed, 13 Nov 2024 10:25:18 -0600
Subject: [PATCH] adding video

---
 ...erate a Vulnerability Report in Faction.md |   2 +-
 .../index.html                                |  25 ++++++++-
 site/blog/archive/2024/index.html             |   2 +
 site/blog/index.html                          |   2 +
 site/search/search_index.json                 |   2 +-
 site/sitemap.xml                              |  52 +++++++++---------
 site/sitemap.xml.gz                           | Bin 644 -> 645 bytes
 7 files changed, 56 insertions(+), 29 deletions(-)

diff --git a/docs/blog/posts/How To Generate a Vulnerability Report in Faction.md b/docs/blog/posts/How To Generate a Vulnerability Report in Faction.md
index a989e8d..3749bde 100644
--- a/docs/blog/posts/How To Generate a Vulnerability Report in Faction.md	
+++ b/docs/blog/posts/How To Generate a Vulnerability Report in Faction.md	
@@ -3,5 +3,5 @@ tags: [ Reporting ]
 date: 2024-10-22
 ---
 
-## Below is video on bow to write a vulnerability report in under 3 minutes using faction.
+## Below is video showing how to write a vulnerability report in under 3 minutes using Faction.
 <iframe width="560" height="315" src="https://www.youtube.com/embed/D897o5Ks7pY?si=YHUbYFgbW2a3uW_y" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
diff --git a/site/blog/2024/10/22/how-to-generate-a-vulnerability-report-in-faction/index.html b/site/blog/2024/10/22/how-to-generate-a-vulnerability-report-in-faction/index.html
index 65c0913..22a7d81 100644
--- a/site/blog/2024/10/22/how-to-generate-a-vulnerability-report-in-faction/index.html
+++ b/site/blog/2024/10/22/how-to-generate-a-vulnerability-report-in-faction/index.html
@@ -79,6 +79,11 @@
     <label class="md-overlay" for="__drawer"></label>
     <div data-md-component="skip">
       
+        
+        <a href="#below-is-video-showing-how-to-write-a-vulnerability-report-in-under-3-minutes-using-faction" class="md-skip">
+          Skip to content
+        </a>
+      
     </div>
     <div data-md-component="announce">
       
@@ -810,6 +815,23 @@
   
   
   
+    <label class="md-nav__title" for="__toc">
+      <span class="md-nav__icon md-icon"></span>
+      Table of contents
+    </label>
+    <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
+      
+        <li class="md-nav__item">
+  <a href="#below-is-video-showing-how-to-write-a-vulnerability-report-in-under-3-minutes-using-faction" class="md-nav__link">
+    <span class="md-ellipsis">
+      Below is video showing how to write a vulnerability report in under 3 minutes using Faction.
+    </span>
+  </a>
+  
+</li>
+      
+    </ul>
+  
 </nav>
                   </div>
                 </div>
@@ -895,7 +917,8 @@
 
   <h1>How To Generate a Vulnerability Report in Faction</h1>
 
-
+<h2 id="below-is-video-showing-how-to-write-a-vulnerability-report-in-under-3-minutes-using-faction">Below is video showing how to write a vulnerability report in under 3 minutes using Faction.</h2>
+<iframe width="560" height="315" src="https://www.youtube.com/embed/D897o5Ks7pY?si=YHUbYFgbW2a3uW_y" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 
 
 
diff --git a/site/blog/archive/2024/index.html b/site/blog/archive/2024/index.html
index 815f879..759d358 100644
--- a/site/blog/archive/2024/index.html
+++ b/site/blog/archive/2024/index.html
@@ -972,6 +972,8 @@ <h1 id="2024">2024</h1>
   </header>
   <div class="md-post__content md-typeset">
     <h2 id="how-to-generate-a-vulnerability-report-in-faction"><a class="toclink" href="../../2024/10/22/how-to-generate-a-vulnerability-report-in-faction/">How To Generate a Vulnerability Report in Faction</a></h2>
+<h3 id="below-is-video-showing-how-to-write-a-vulnerability-report-in-under-3-minutes-using-faction"><a class="toclink" href="../../2024/10/22/how-to-generate-a-vulnerability-report-in-faction/#below-is-video-showing-how-to-write-a-vulnerability-report-in-under-3-minutes-using-faction">Below is video showing how to write a vulnerability report in under 3 minutes using Faction.</a></h3>
+<iframe width="560" height="315" src="https://www.youtube.com/embed/D897o5Ks7pY?si=YHUbYFgbW2a3uW_y" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
     <nav class="md-post__action">
       <a href="../../2024/10/22/how-to-generate-a-vulnerability-report-in-faction/">
         Continue reading
diff --git a/site/blog/index.html b/site/blog/index.html
index 4297d1e..a60e417 100644
--- a/site/blog/index.html
+++ b/site/blog/index.html
@@ -843,6 +843,8 @@
   </header>
   <div class="md-post__content md-typeset">
     <h2 id="how-to-generate-a-vulnerability-report-in-faction"><a class="toclink" href="2024/10/22/how-to-generate-a-vulnerability-report-in-faction/">How To Generate a Vulnerability Report in Faction</a></h2>
+<h3 id="below-is-video-showing-how-to-write-a-vulnerability-report-in-under-3-minutes-using-faction"><a class="toclink" href="2024/10/22/how-to-generate-a-vulnerability-report-in-faction/#below-is-video-showing-how-to-write-a-vulnerability-report-in-under-3-minutes-using-faction">Below is video showing how to write a vulnerability report in under 3 minutes using Faction.</a></h3>
+<iframe width="560" height="315" src="https://www.youtube.com/embed/D897o5Ks7pY?si=YHUbYFgbW2a3uW_y" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
     <nav class="md-post__action">
       <a href="2024/10/22/how-to-generate-a-vulnerability-report-in-faction/">
         Continue reading
diff --git a/site/search/search_index.json b/site/search/search_index.json
index 2eb4ab5..d8afd07 100644
--- a/site/search/search_index.json
+++ b/site/search/search_index.json
@@ -1 +1 @@
-{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Welcome to FACTION","text":"<p>PenTesting Report Generation and Collaboration Engine </p> <p>FACTION is your entire assessment workflow in a box. With FACTION you can:</p> <ol> <li> <p>Automate pen testing and security assessment Reports</p> </li> <li> <p>Peer review and track changes for reports</p> </li> <li> <p>Create customized DOCX templates for different assessment types and retests</p> </li> <li> <p>Real-time collaboration with assessors via the web app and Burp Suite Extensions</p> </li> <li> <p>Customizable vulnerability templates with over 75 prepopulated</p> </li> <li> <p>Easily manage assessment teams and track progress across your organization</p> </li> <li> <p>Track vulnerability remediation efforts with custom SLA warnings and alerts \u00a0</p> </li> <li> <p>Full Rest API to integrate with other tools\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0</p> </li> </ol> <p>Other Features:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0</p> <ol> <li> <p>LDAP Integration\u00a0 \u00a0 \u00a0 \u00a0</p> </li> <li> <p>OAUTH2.0 Integration</p> </li> <li> <p>SMTP integration\u00a0</p> </li> <li> <p>Extendable with Custom Plugins similar to Burp Extender.</p> </li> <li> <p>Custom Report Variables</p> </li> </ol> <p>Want to see it in action? -&gt; Faction Video Overview</p>","tags":[]},{"location":"#quick-setup","title":"Quick Setup","text":"<p>Requirements - Java JDK11  - Maven (for building the project)</p> <p>Run the following commands to build the war file and deploy it to the docker container.  <pre><code>git clone git@github.com:factionsecurity/faction.git\ncd faction\nmvn clean compile war:war\ndocker-compose up --build\n</code></pre></p> <p>Once the containers are up you can navigate to http://127.0.0.1:8080 to access your FACTION instance.  On the first boot, it will ask you to create an admin account. </p>","tags":[]},{"location":"#import-the-vulnerability-templates","title":"Import the Vulnerability Templates","text":"<ol> <li>Navigate to Admin -&gt; Default Vulnerabilities</li> <li>Click Import from Faction</li> </ol>","tags":[]},{"location":"#customize-reports","title":"Customize reports","text":"<p>You can find out more information about creating your own custom report templates here: Customize Report Templates</p>","tags":[]},{"location":"#burp-suite-extension","title":"Burp Suite Extension","text":"<p>Burp Suite Extensions</p>","tags":[]},{"location":"#dont-want-to-host-it-yourself","title":"Don't want to host it yourself?","text":"<p>We can provide hosting for your instance. All instances are single tenants so you don't have to worry about sharing infrastructure with untrusted parties. Hosted versions also come with other features like enhanced reporting. Navigate to https://www.factionsecurity.com to learn more. </p>","tags":[]},{"location":"#screenshots","title":"Screenshots","text":"<p>Vulnerability Templates </p> <p>Assessment Scheduling </p> <p>Peer Review and Track Changes </p>","tags":[]},{"location":"Custom%20Security%20Report%20Templates/","title":"Custom Security Report Templates","text":"<p>The Faction Report Designer allows you to create custom security report templates for each assessment type. When building reports you need to use the variables listed below. Entering these into your DOCX reports will auto-replace the assessment and vulnerability text when the report is generated. You can even use the same variables in many of the assessor input fields outside of the report template (like Risk Assessment Summaries) and it will auto-populate the fields when the report is generated.</p> <p>You can download the sample templates here:  Sample Templates </p> <p>Note</p> <p>You should disable spellcheck in your template document while adding variables. The spellcheck can cause the variables to contain attributes that will make the variable unrecognizable to the Faction document parser. </p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#general-variables","title":"GENERAL VARIABLES:","text":"<p>All of these variables can be used anywhere in the DOCX template. Those with a star \u2b50\ufe0f can be used in the web interface to assist in creating common reusable templates.</p> <ul> <li>${TOC}\u00a0\u2013 Placeholder for the Table of Contents</li> <li>${summary1}\u00a0\u2013 The high level summary</li> <li>${summary2}\u00a0\u2013 The objective and scope</li> <li>${asmtId}\u00a0\u2013 Internal Database ID \u2b50\ufe0f</li> <li>${asmtAppid}\u00a0\u2013 The assigned Application ID \u2b50\ufe0f</li> <li>${asmtName}\u00a0\u2013 The Assessment Name \u2b50\ufe0f</li> <li>${asmtAssessor}\u00a0\u2013 The first assessor assigned to the assessment \u2b50\ufe0f</li> <li>${asmtAssessor_Email}\u00a0\u2013 The first assessor email address \u2b50\ufe0f</li> <li>${asmtAssessors_Lines}\u00a0\u2013 All Assessors split into lines \u2b50\ufe0f</li> <li>${asmtAssessors_Comma}\u00a0\u2013 All Assessors split into a comma delimited list \u2b50\ufe0f</li> <li>${asmtAssessor_Bullets}\u00a0\u2013 All Assessors split into a bulleted list \u2b50\ufe0f</li> <li>${remediation}\u00a0\u2013 The Remediation Person assigned to the assessment \u2b50\ufe0f</li> <li>${riskCount*}\u00a0\u2013 The number of findings at the RiskLevel 0-9 \u2b50\ufe0f</li> <li>${riskTotal}\u00a0\u2013 The total number of findings at all RiskLevels \u2b50\ufe0f</li> <li>${asmtTeam}\u00a0\u2013 The Assessor Team Name \u2b50\ufe0f</li> <li>${asmtType}\u00a0\u2013 The Type of the Assessment \u2b50\ufe0f</li> <li>${asmtStart}\u00a0\u2013 The Start date of the assessment \u2b50\ufe0f</li> <li>${asmtEnd}\u00a0\u2013 The End date of the assessment \u2b50\ufe0f</li> <li>${asmtAccessKey}\u00a0\u2013 Guid to access the client retest queue. \u2b50\ufe0f</li> <li>${today}\u00a0\u2013 Day the report is generated \u2b50\ufe0f</li> <li>${cfXXXXXX}\u00a0\u2013 Custom Fields are ones you specify in the admin interface. These are all prefixed with \u201ccf\u201d \u2b50\ufe0f</li> <li>${totalOpenVulns} - Can be used in retest reports to show a count of open vulnerabilities.  (Since 1.3)</li> <li>${totalClosedVulns} - Can be used in retest reports to show the total count of closed vulnerabilities. (Since 1.3)</li> </ul>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#vulnerability-tables-variables","title":"VULNERABILITY TABLES VARIABLES:","text":"<p>These are only available inside tables.</p> <ul> <li>${vulnTable}\u00a0\u2013 This defines a table to be a vulnerability listing table.</li> <li>${vulnTable Section_Name}\u00a0\u2013 This defines a table to be a vulnerability listing table for a section of vulnerabilities. See Reporting Sections(Paid Only Feature).</li> <li>${vulnName}\u00a0\u2013 The Vulnerability name</li> <li>${rec}\u00a0\u2013\u00a0Vulnerability Recommendation</li> <li>${desc}\u00a0\u2013\u00a0Vulnerability Description</li> <li>${category}\u00a0\u2013 Category of the vulnerability</li> <li>${severity}\u00a0\u2013 Severity of each vulnerability.</li> <li>${likelihood}\u00a0\u2013 Likelihood of the vulnerability</li> <li>${impact}\u00a0\u2013 Impact of the vulnerability</li> <li>${cvssScore}\u00a0\u2013 CVSS score of the vulnerability (Since v1.2)</li> <li>${cvssString}\u00a0\u2013 CVSS vector of the vulnerability (Since v1.2)</li> <li>${count}\u00a0\u2013 Row Count of the vulnerability</li> <li>${tracking}\u00a0\u2013 Tracking number of the vulnerability</li> <li>${vid}\u00a0\u2013 Vulnerability internal database id</li> <li>${openedAt} - The date the vulnerability began tracking (Since 1.3)</li> <li>${closedAt} - The date the vulnerability was closed (no longer tracked) (Since 1.3)</li> <li>${remediationStatus} - Displays only \"Open\" or \"Closed\" (Since 1.3)</li> <li>${cfXXXXXX}\u00a0\u2013 Custom Fields are ones you specify in the admin interface. These are all prefixed with \u201ccf\u201d</li> <li>${color \u00a0key=value,key=value}\u00a0\u2013 The color of the text is based on key-value pairs.\u00a0See below for how to set up colors.</li> <li>${cells key=value,key=value}\u00a0\u2013 The color of the table cell is based on key-value pairs.\u00a0\u00a0See below for how to set up colors.</li> <li>${loop}\u00a0\u2013 This variable tells the report generator which row will be repeated.</li> <li>${loop-*}\u00a0\u2013 This allows multiple rows to be repeated. Example ${loop-1} will repeat the row but the one below it.</li> <li>${details}\u00a0\u2013 This will insert screenshots and exploit steps for each vulnerability.</li> <li>${noIssuesText} - This is the default text displayed in the section if no vulnerabilities are reported. (Since 1.3.28)</li> </ul>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#example-table-summary-table","title":"Example Table Summary Table","text":"${vulnTable} ${color Critical=C00000,High=FFC000} ID Finding Name Impact Severity ${loop} ${count}. ${vulnName} ${impact} ${severity}","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#example-table-detail-table","title":"Example Table Detail Table","text":"${vulnTable} ${cells Critical=8064a2,High=c0504d,Medium=e68e00, Low=33D7FF,Recommended=081417,Informational=657376} ${loop-5} ## 1\u00a0 ${vulnName} ${severity} CVSS: ${cvssString} ${cvssScore} Category: ${category} Description:${desc} Recommendation:${rec} ${details} <p>**Why is the heading yellow?!?! Check here</p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#vulnerability-block-variables","title":"VULNERABILITY BLOCK VARIABLES:","text":"<p>For when you do not want to use tables to display your vulnerability information. You can use the following variables for inserting vulnerability information outside of a table</p> <ul> <li>${fiBegin} / ${fiEnd}\u00a0\u2013 Block to repeat against all findings.</li> <li>${fiBegin Section_Name} / ${fiEnd Section_Name}\u00a0\u2013 Block to repeat a section of findings. See  Reporting Sections (Paid Only Feature)</li> <li>${vulnName}\u00a0\u2013 The Vulnerability name</li> <li>${rec}\u00a0\u2013\u00a0Vulnerability Recommendation</li> <li>${desc}\u00a0\u2013\u00a0Vulnerability Description</li> <li>${category}\u00a0\u2013 Category of the vulnerability</li> <li>${severity}\u00a0\u2013 Severity of each vulnerability.</li> <li>${likelihood}\u00a0\u2013 Likelihood of the vulnerability</li> <li>${impact}\u00a0\u2013 Impact of the vulnerability</li> <li>${cvssScore}\u00a0\u2013 CVSS score of the vulnerability (Since 1.2)</li> <li>${cvssString}\u00a0\u2013 CVSS vector of the vulnerability (Since 1.2)</li> <li>${count}\u00a0\u2013 Row Count of the vulnerability</li> <li>${tracking}\u00a0\u2013 Tracking number of the vulnerability</li> <li>${vid}\u00a0\u2013 Vulnerability internal database id</li> <li>${openedAt} - The date the vulnerability began tracking (Since 1.3)</li> <li>${closedAt} - The date the vulnerability was closed (no longer tracked) (Since 1.3)</li> <li>${remediationStatus} - Displays only \"Open\" or \"Closed\" (Since 1.3)</li> <li>${cfXXXXXX}\u00a0\u2013 Custom Fields are ones you specify in the admin interface. These are all prefixed with \u201ccf\u201d</li> <li>${details}\u00a0\u2013 This will insert screenshots and exploit steps for each vulnerability.</li> <li>${color \u00a0key=value,key=value}\u00a0\u2013 The color of the text is based on key-value pairs.\u00a0See below for how to set up colors.</li> <li>${fill key=value,key=value}\u00a0\u2013 The color of the background elements is based on key-value pairs.\u00a0\u00a0See below for how to set up colors.</li> <li>${noIssuesText} - This is the default text displayed in the section if no vulnerabilities are reported. (Since 1.3.28) </li> </ul>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#example-block-findings","title":"Example Block Findings","text":"<p>**Why is the heading yellow?!?! Check here</p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#reporting-sections-enterprisepaid-feature","title":"Reporting Sections (Enterprise/Paid Feature)","text":"<p>You can put findings into different sections of your report for paid versions and certain sponsored tiers of Faction. You may want to use sections if you are doing different types of pen tests in one report and need to keep these sections separated. For example, you can segregate findings into  Application Security and Network Security Sections. </p> <p>To use sections you need to create the section names in the Faction Report Designer: </p> <p>Once the sections are created in the UI, you can add them to the report in two ways.  1. Vulnerability Block Variables: <code>${fiBegin Your_Section_Name}</code>/<code>${fiEnd Your_Section_Name} 2. Vulnerability Table Variables:</code>${vulnTable Your_Section_Name}`</p> <p>Below is an example of how the template variables work:</p> <p></p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#css-formatting","title":"CSS FORMATTING:","text":"<p>All of the text generated from Faction is HTML. You can control how it is rendered in the DOCX format using the CSS editor in the Report Designer. You will need to set the CSS to match your report templates. Things like font and size will need to match. Images will need to be forced to resize to the correct dimensions to fit in your reports.</p> <p></p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#setting-severity-colors","title":"SETTING SEVERITY COLORS:","text":"<p>When building reports you most likely will set the text or cell to the color that matches the severity of the finding. To achieve this in FACTION you need to set a default color in the docx template that matches the severity category (i.e. Overall, Likelihood, and Impact). These default colors are in the table below:</p> Category Color Hex Overall Severity #FAC701 Likelihood #FAC702 Impact #FAC703 <p>For Example, a table in MS Word below has pre-filled the color codes for each severity name and category.</p> <p></p> <p>Right-click the overall severity variable,\u00a0${severity}; you can see the default hex code for this color is #FAC701. Likelihood would be set to #FAC02, and Impact would be set to #FAC703.</p> <p></p> <p>Setting the background color for cells works in much the same way. Notice we use the ${cells} variable instead.</p> <p></p> <p>Right-click on the cell and set the color you may only want to use the Overall severity option but you can have multiple cells with each category if you wish.</p> <p></p> <p>Below is an example of the generated report table with colors replaced.</p> <p></p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Variables/","title":"Custom Variables","text":"<p>You can use custom variables to add additional features to Faction. These variables can be used to add additional information to vulnerabilities like a CVSS score or to populate additional data in reports like \"product owner\", \"cost center\", etc. </p> <p>Note</p> <p>Faction 1.2 and above has CVSS Scoring built in. You can still use this information as a guide to add your own custom variables. </p>","tags":["Reporting","Customize"]},{"location":"Custom%20Variables/#adding-a-cvss-score","title":"Adding a CVSS Score","text":"<p>As of Faction version 1.1.25.1, Faction does not have CVSS scores built in but you can add your own easily.  </p>","tags":["Reporting","Customize"]},{"location":"Custom%20Variables/#step-1-add-custom-fields-in-admin","title":"Step 1 : Add Custom Fields in Admin","text":"<p>Navigate to Admin -&gt; Settings and add two Custom Fields: CVSS3.1 and CVSS String with variable names <code>cvss3</code> and <code>cvssstring</code>.</p> <p></p> <p>The Name will be what is displayed in the UI and the variable name will be used in the report template. We want to apply this to Vulnerability so that it will be available when we add vulnerabilities to the assessment.</p>","tags":["Reporting","Customize"]},{"location":"Custom%20Variables/#step-2-update-the-report-template","title":"Step 2: Update the Report Template","text":"<p>We need to change our report template to include the new variables in the vulnerability section of the template. In this case, we already have a table with vulnerability information and we need to add another row to this table with the new variables. The default template can be downloaded here.</p> <p></p> <p>Notice all custom field variables are pre-populated with <code>cf</code>.  If we defined a custom field with a variable of <code>cvss3</code> then the reporting variable will be <code>${cfcvss3}</code>. </p> <p>Note: We needed to change the <code>loop</code> variable to inform the Faction reporting engine that the number of rows in the table has changed from 4 to 5. If you are not changing the number of rows then this update is not necessary. </p>","tags":["Reporting","Customize"]},{"location":"Custom%20Variables/#step-3-add-a-new-vulnerability-to-the-assessment","title":"Step 3: Add a New Vulnerability to the Assessment","text":"<p>When you add a vulnerability to the assessment the custom fields will be available in the form as shown below:</p> <p></p> <p>Entering the CVSS score will be automatically saved and a report can now be generated with these new Fields. </p> <p></p>","tags":["Reporting","Customize"]},{"location":"Faction%20App%20Store%20Extensions/","title":"Faction App Store Extensions","text":"<p>Below is a List of Approved Faction Extensions. These all work with Faction 1.2+</p> Name Developer URL Faction Jira Integration Faction Security https://github.com/factionsecurity/Faction-Jira-Extension Faction Vulnerability Bar Chart Faction Security https://github.com/factionsecurity/Faction-Vulnerability-Bar-Chart","tags":["App Store","API"]},{"location":"Faction%20App%20Store%20Extensions/#submit-an-extension","title":"Submit an Extension","text":"<p>Send an email to develop [ at ] factionsecurity [dot] com with a link to your github and a brief explanation of what it does. </p>","tags":["App Store","API"]},{"location":"Faction%20Severity%20Rating%20and%20CVSS%20Scoring/","title":"Faction Severity Rating and CVSS Scoring","text":"<p>Native: </p> <p>CVSS: </p> <p>FACTION's severity rankings are easily customizable to how you perform assessments. You can even create different severity options for the type of assessment. </p> <p>FACTION has 3 options to choose:</p> <ol> <li>Native Severity - This is simply High, Medium, Low, etc type rankings. Faction let you set up to 10 levels and can rename them to anything that works for your process. </li> <li>CVSS 3.1 - This option enables First.org CVSS 3.1 Severity Scoring and was introduced in FACTION 1.2</li> <li>CVSS 4.0 = This option enables First.org CVSS 4.0 Scoring and was introduced in FACTION 1.2</li> </ol>","tags":["CVSS","Vulnerability","Core Features"]},{"location":"Faction%20Severity%20Rating%20and%20CVSS%20Scoring/#native-severity-ranking","title":"Native Severity Ranking","text":"<p> By default, assessments are enabled with Native Severity Ranking. You can choose up to 10 levels. The most common severity names are pre-populated when you install FACTION. You are free to change these names to anything you wish. If your process uses a different nomenclature then you can change <code>Critical</code> to  <code>P1</code> and <code>High</code> to <code>P2</code> for example. </p> <p>You can find this setting in Templates -&gt; Default Vulnerabilities.</p> <p>When Native Severity Ranking is enabled, the following options are available when adding a new vulnerability: </p>","tags":["CVSS","Vulnerability","Core Features"]},{"location":"Faction%20Severity%20Rating%20and%20CVSS%20Scoring/#changing-the-severity-scoring-system","title":"Changing the Severity Scoring System","text":"<p>The severity scoring system is set for each assessment type. You can change this or create new assessment types by navigating to Admin -&gt; Settings:</p> <p></p> <p>Notice above that each assessment has a different scoring system. To change the assessment scoring system then simply click the <code>edit</code> button an select the scoring system from the drop-down.</p> <p></p>","tags":["CVSS","Vulnerability","Core Features"]},{"location":"Faction%20Severity%20Rating%20and%20CVSS%20Scoring/#cvss-31-and-40-severity-ranking","title":"CVSS 3.1 and 4.0 Severity Ranking","text":"<p>When changing the scoring system to CVSS 3.1 or 4.0, it changes the vulnerability UI and adds CVSS Calculators to the page. </p> <p></p> <p>Clicking on the calculator button next to the CVSS Vector will open a dialog that will build the CVSS vector for you and update the score.  </p>","tags":["CVSS","Vulnerability","Core Features"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/","title":"How to Use BurpSuite with Faction","text":"<p>Faction has a tight integration with BurpSuite and you can now find our extension in the BApp Store. Here are a few things you can do with the Faction Burp Integration. 1. See your assessment and retest queues. 2. Instant access to your assessment scope and other details. 3. View all findings you and your co-pentesters are reporting. 4. Replay payloads from other pentesters. 5. Add issues in Faction directly from BurpSuite. </p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#install-the-burp-faction-integration","title":"Install the Burp Faction Integration","text":"<p>You can install the Faction Integration directly from the BApp store.  1. Open Burp then Click Extensions-&gt;BApp Store 3. Search for Faction 4. Click Install</p> <p></p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#set-up-faction","title":"Set Up Faction","text":"<p>In BurpSuite navigate to the Faction tab after you have installed the Faction Integration. From here you need to enter the URL and API key for your user. </p> <p>The URL will be your domain plus <code>api</code>. Ex <code>https://faction-test.factionsecurity.com/api</code></p> <p></p> <p>You can retrieve your API Key in Faction by accessing your profile in the upper right corner of the Faction Web Interface.  </p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#access-your-assessment-queue","title":"Access Your Assessment Queue","text":"<p>Now that Faction is configured you should be able to see you current assessment queue as shown below:</p> <p></p> <p>Clicking on an assessment will show you the scope, any vulnerabilities that have been reported, and notes that your team has shared with you. </p> <p></p> <p>If you select one of the vulnerabilities you can see its full details including screenshots.</p> <p></p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#enter-findings-into-faction-from-burp","title":"Enter Findings into Faction From Burp","text":"<p>Lets say you find an XSS attack and have verified it with BurpSuite. You can add the finding to Faction without ever leaving Burp. Just select the request or response that you want to enter into the report and select \"Add New Finding\" as shown below:</p> <p></p> <p>Now you will be presented with the vulnerability findings dialog. Here you can search for an existing vulnerability template to auto populate the details and recommendations. </p> <p>Next ensure its being sent to the right assessment. The option will default to the last assessment you selected in the previous section on Access your Assessment Queue</p> <p>Next you have several options. </p> <ul> <li>Select the severity or leave the default</li> <li>Check or uncheck to include the request and/or response. When checked it will include these options in code blocks in the final report.</li> <li>\"Snip cookies\" when checked will remove all cookies from being added to the report and replace them with <code>[...snip...]</code></li> <li>\"Extract Selection\" when checked will only add the portion of the code you selected in Burp to the report. This is most useful trying to only show the reflected script in the response instead of the full response. </li> <li>Exploit Steps can be included and supports MarkDown Syntax. Note Screenshots are available though the Burp Extension currently. For this you still need to add them to the Web UI. </li> </ul> <p></p> <p>Now you can click Save to add it to Faction. All this allows issues to be added seamlessly without breaking your flow. The final result will look something like this.</p> <p></p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#replay-findings","title":"Replay Findings","text":"<p>The Faction Burp Integration has the ability to replay findings if you included the request in the details. Notice the hyperlink above the request when you select a vulnerability in the Faction BurpSuite Integration. </p> <p></p> <p>If you click the hyperlink it will add it to your Burp Repeater. This allows you to replay your own findings and findings from your co-pentesters. The same feature is available for retests!</p> <p></p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#add-scan-findings","title":"Add Scan Findings","text":"<p>Anything found in the BurpSuite Scanner can be added directly into Faction using the BurpSuite Integration as well. Just select the issues you want to add and then choose \"Send Issues to Faction\"</p> <p></p> <p>Below shows that all issues were combined into two distinct issues.</p> <p></p> <p>Notice that if you select more than one of the same issue that it will aggregate the URLs into one finding:</p> <p></p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#wrapping-up","title":"Wrapping Up","text":"<p>All of these features have been implemented to make adding issues to pen-testing reports easy and to not break your flow. Nothing worse that being in the zone and then have stop to mess with report formatting or ensuring you capture all the right data in your notes to use later. With Faction you can just add the issues as you find them and move on with your pentest. </p>","tags":["burpsuite","integrations","api"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/","title":"Importing Your Vulnerability Templates Via the API","text":"<p>You may have developed your own vulnerability templates over the years, or you may prefer editing them in another editor such as Obsidian or Sublime, rather than using the web interface. Regardless of your approach, Faction enables you to upload your templates in CSV and JSON formats via the API. Additionally, reports can be generated in markdown, HTML, or a combination of both.</p> <p>The api docs can be found on your instance by navigating to  https: //YourHost/api-docs: </p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#generating-an-api-key","title":"Generating an API Key","text":"<p>You must have the <code>API Key</code> permission on your user to use the API. It it not set by default.  </p> <p>After enabling the setting, you can access your API Key by navigating to your profile, located in the upper right corner of the Faction interface. Simply clicking anywhere inside the API key box will reveal the key to you. </p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#csv-file-structure","title":"CSV File Structure","text":"Id* Name Category Id* Category Name* Description Recommendation Severity Id Impact Id Likelihood Id active <p>If the ID field is empty, a new vulnerability will be created. If the ID field is populated, it will overwrite the vulnerability with the same ID.</p> <p>If the Category ID is missing, the categoryName field is required. If a category with the same name exists, the existing category will be used.</p> <p>If the categoryName does not match an existing category, a new category will be created.</p> <p>If the Category ID is populated, the Category Name field is ignored.</p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#example-1-create-a-new-vulnerability-template-in-csv","title":"Example 1: Create a New Vulnerability Template in CSV","text":"<p>Example CSV <pre><code>,\"Cross Site Scripting\",, Unvalidated Input, \"XSS is Bad and stuff..\\n```\\nCode snippet\\n```\", \"Fix it! here is a link [here](https://www.a.b.com)\", 4, 4,4,true\n</code></pre></p> <p>The provided example will create a new template for cross-site scripting. Here are a few key points to note:</p> <ol> <li> <p>The first column (ID column) is left blank. Since there is no ID specified, a new template will be created.</p> </li> <li> <p>The third column (Category ID) is also blank, so Faction will refer to the fourth column (Category Name). If <code>Unvalidated Input</code> is not already a category in Faction, it will be created.</p> </li> <li> <p>The Description and Recommendation fields are written in markdown syntax. Ensure that these columns are enclosed in double quotes (<code>\"</code>) and that new lines are properly escaped (<code>\\n</code>).</p> </li> <li> <p>The severity IDs must correspond to the severity levels configured in Faction. You can find these numbers in Admin-&gt;Settings-&gt; Risk Level Settings. The default severity levels are: Critical (5), High (4), Medium (3), Low (2), Recommended (1), Informational (0). Ensure that the severity IDs match these levels accordingly.</p> </li> </ol> <p>Submit through the API <pre><code>curl -X 'POST' \\ \n'http://localhost:8080/api/vulnerabilities/csv/default' \\ \n-H 'accept: application/json' \\ \n-H 'FACTION-API-KEY: 6be51daa-6f6f-42d3-8b04-b924a0045eff' \\ \n-H 'Content-Type: text/plain' \\ \n-d ',\"Cross Site Scripting\",, Unvalidated Input, \"XSS is Bad and stuff..\\n```\\nCode snippet\\n```\", \"Fix it! here is a link [here](https://www.a.b.com)\", 4, 4,4,true'\n</code></pre></p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#example-2-updating-a-vulnerability-template-in-csv","title":"Example 2: Updating a Vulnerability Template in CSV","text":"<p>First, you need to download the current list of vulnerabilities from the API.</p> <p>Get a CSV List of Default Vulnerabilities <pre><code>curl -X 'GET' \\ \n'http://localhost:8080/api/vulnerabilities/csv/default' \\ \n-H 'accept: text/csv' \\ \n-H 'FACTION-API-KEY: 6be51daa-6f6f-42d3-8b04-b924a0045eff'\n</code></pre></p> <p>Example Response: <pre><code>\"2\",\"Generic Vulnerability\",\"2\",\"Uncategorized\",\"\",\"\",\"4\",\"4\",\"4\",\"true\" \"18\",\"Cross Site Scripting\",\"4\",\"Unvalidated Input\",\"&lt;p&gt;XSS is Bad and stuff..&lt;/p&gt; &lt;pre&gt;&lt;code&gt;Code snippet &lt;/code&gt;&lt;/pre&gt; &lt;br /&gt;\",\"&lt;p&gt;Fix it! here is a link &lt;a href=\"\"https://www.a.b.com\"\"&gt;here&lt;/a&gt;&lt;/p&gt; &lt;br /&gt;\",\"4\",\"4\",\"4\",\"true\"\n</code></pre></p> <p>Now to Update a Template Let's update the Cross Site Scripting Template by changing the description to the following. <pre><code>XSS is fun to exploit with this code snippet\\n ```\\nSnipity snip\\n```\n</code></pre></p> <p>The API Request would look like this: <pre><code>curl -X 'POST' \\ \n'http://localhost:8080/api/vulnerabilities/csv/default' \\ \n-H 'accept: application/json' \\ \n-H 'FACTION-API-KEY: 6be51daa-6f6f-42d3-8b04-b924a0045eff' \\ \n-H 'Content-Type: text/plain' \\ \n-d '\"18\",\"Cross Site Scripting\",\"4\",\"Unvalidated Input\",\"XSS is fun to exploit with this code snippet\\n ```\\nSnipity snip\\n```\",\"&lt;p&gt;Fix it! here is a link &lt;a href=\"\"https://www.a.b.com\"\"&gt;here&lt;/a&gt;&lt;/p&gt; &lt;br /&gt;\",\"4\",\"4\",\"4\",\"true\"'\n</code></pre></p> <p>Now if we pull the list again the results look like this: Request <pre><code>curl -X 'GET' \\ \n'http://localhost:8080/api/vulnerabilities/csv/default' \\ \n-H 'accept: text/csv' \\ \n-H 'FACTION-API-KEY: 6be51daa-6f6f-42d3-8b04-b924a0045eff'\n</code></pre></p> <p>Response <pre><code>\"2\",\"Generic Vulnerability\",\"2\",\"Uncategorized\",\"\",\"\",\"4\",\"4\",\"4\",\"true\" \"18\",\"Cross Site Scripting\",\"4\",\"Unvalidated Input\",\"&lt;p&gt;XSS is fun to exploit with this code snippet&lt;/p&gt; &lt;pre&gt;&lt;code&gt;Snipity snip &lt;/code&gt;&lt;/pre&gt; &lt;br /&gt;\",\"&lt;p&gt;Fix it! here is a link &lt;a href=\"\"https://www.a.b.com\"\"&gt;here&lt;/a&gt;&lt;/p&gt; &lt;br /&gt; &lt;br /&gt;\",\"4\",\"4\",\"4\",\"true\"\n</code></pre></p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#json-file-structure","title":"JSON File Structure","text":"<pre><code>  [\n      {\n        \"Id\": 2,\n        \"Name\": \"Generic Vulnerability\",\n        \"CategoryId\": 2,\n        \"CategoryName\": \"Uncategorized\",\n        \"Description\": \"\",\n        \"Recommendation\": \"\",\n        \"SeverityId\": 4,\n        \"LikelihoodId\": 4,\n        \"ImpactId\": 4,\n        \"Active\": true\n      }\n  ]\n</code></pre> <p>If the ID is missing, a new vulnerability will be created. If the ID is populated, it will overwrite the vulnerability with the same ID.</p> <p>If the Category ID is missing, the categoryName is required. If a category with the same name exists, the existing category will be used.</p> <p>If the categoryName does not match an existing category, a new category will be created.</p> <p>If the Category ID is populated, the Category Name field is ignored.</p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#example-1-create-all-new-vulnerability-template-in-json","title":"Example 1: Create All New Vulnerability Template in JSON","text":"<p>Example JSON</p> <pre><code>[\n    {\n        \"Name\": \"Cross Site Scripting\",\n        \"CategoryName\": \"Unvalidated Input\",\n        \"Description\": \"XSS is Bad and stuff..\\n```\\nCode snippet\\n```\",\n        \"Recommendation\": \"Fix it! here is a link [here](https://www.a.b.com)\",\n        \"LikelihoodId\": 4,\n        \"ImpactId\": 4,\n        \"SeverityId\": 4,\n        \"Active\": true\n    }\n]\n</code></pre> <p>The provided example will create a new template for cross-site scripting. Here are a few key points to note:</p> <ol> <li> <p>The ID is missing. Since there isn't an ID to relate it, a new template will be created.</p> </li> <li> <p>The CategoryId is missing, so Faction will need to look at the CategoryName. If <code>Unvalidated Input</code> is not already a category, then Faction will create it.</p> </li> <li> <p>The Description and Recommendation fields are written in markdown syntax.</p> </li> <li> <p>Ensure that the severity IDs match the severity levels you have set in Faction. You can find these numbers in Admin-&gt;Settings-&gt; Risk Level Settings. The defaults are Critical (5), High (4), Medium (3), Low (2), Recommended (1), Informational (0).</p> </li> </ol> <p>The API Request looks like this to add this vulnerability template: <pre><code>curl -X 'POST' \\ \n'http://localhost:8080/api/vulnerabilities/default' \\ \n-H 'accept: application/json' \\ \n-H 'FACTION-API-KEY: a0d2fff7-7462-458c-ba7b-d93d99b7280a' \\ \n-H 'Content-Type: application/json' \\ \n-d '[ \n    { \n        \"Name\": \"Cross Site Scripting\", \n        \"CategoryName\": \"Unvalidated Input\", \n        \"Description\": \"XSS is Bad and stuff..\\n```\\nCode snippet\\n```\",\n        \"Recommendation\": \"Fix it! here is a link [here](https://www.a.b.com)\",\n        \"LikelihoodId\": 4, \n        \"ImpactId\": 4, \n        \"SeverityId\": 4, \n        \"Active\": true \n    } \n]'\n</code></pre></p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#example-2-updating-a-vulnerability-template-in-json","title":"Example 2: Updating a Vulnerability Template in JSON","text":"<p>First, you need to download the current list of vulnerabilities from the API.</p> <p>Get a JSON List of Default Vulnerabilities <pre><code>curl -X 'GET' \\ \n'http://localhost:8080/api/vulnerabilities/default' \\ \n-H 'accept: application/json' \\ \n-H 'FACTION-API-KEY: a0d2fff7-7462-458c-ba7b-d93d99b7280a'\n</code></pre></p> <p>Response: <pre><code>[\n  {\n    \"CategoryId\": 2,\n    \"ImpactId\": 4,\n    \"Active\": true,\n    \"Description\": \"\",\n    \"CategoryName\": \"Uncategorized\",\n    \"LikelihoodId\": 4,\n    \"Id\": 2,\n    \"Recommendation\": \"\",\n    \"SeverityId\": 4,\n    \"Name\": \"Generic Vulnerability\"\n  },\n  {\n    \"CategoryId\": 4,\n    \"ImpactId\": 4,\n    \"Active\": true,\n    \"Description\": \"XSS is Bad and stuff..\\n```\\nCode snippet\\n```\",\n    \"CategoryName\": \"Unvalidated Input\",\n    \"LikelihoodId\": 4,\n    \"Id\": 5,\n    \"Recommendation\": \"Fix it! here is a link [here](https://www.a.b.com)\",\n    \"SeverityId\": 4,\n    \"Name\": \"Cross Site Scripting\"\n  }\n]\n</code></pre></p> <p>Now to Update a Template Let's update the Cross-Site Scripting Template by changing the description to the following. <pre><code>XSS is fun to exploit with this code snippet\\n ```\\nSnipity snip\\n```\n</code></pre></p> <p>The API Request would look like this: <pre><code>curl -X 'POST' \\\n  'http://localhost:8080/api/vulnerabilities/default' \\\n  -H 'accept: application/json' \\\n  -H 'FACTION-API-KEY: a0d2fff7-7462-458c-ba7b-d93d99b7280a' \\\n  -H 'Content-Type: application/json' \\\n  -d '[ {\n    \"CategoryId\": 4,\n    \"ImpactId\": 4,\n    \"Active\": true,\n    \"Description\": \"XSS is fun to exploit with this code snippet\\n ```\\nSnipity snip\\n```\",\n    \"CategoryName\": \"Unvalidated Input\",\n    \"LikelihoodId\": 4,\n    \"Id\": 5,\n    \"Recommendation\": \"Fix it! here is a link [here](https://www.a.b.com)\",\n    \"SeverityId\": 4,\n    \"Name\": \"Cross Site Scripting\"\n  }]'\n</code></pre></p> <p>Now if we pull the list again the results look like this: Request <pre><code>curl -X 'GET' \\ \n'http://localhost:8080/api/vulnerabilities/default' \\ \n-H 'accept: text/csv' \\ \n-H 'FACTION-API-KEY: 6be51daa-6f6f-42d3-8b04-b924a0045eff'\n</code></pre></p> <p>Response <pre><code>[\n  {\n    \"CategoryId\": 2,\n    \"ImpactId\": 4,\n    \"Active\": true,\n    \"Description\": \"\",\n    \"CategoryName\": \"Uncategorized\",\n    \"LikelihoodId\": 4,\n    \"Id\": 2,\n    \"Recommendation\": \"\",\n    \"SeverityId\": 4,\n    \"Name\": \"Generic Vulnerability\"\n  },\n  {\n    \"CategoryId\": 4,\n    \"ImpactId\": 4,\n    \"Active\": true,\n    \"Description\": \"&lt;p&gt;XSS is fun to exploit with this code snippet&lt;/p&gt;\\n&lt;pre&gt;&lt;code&gt;Snipity snip\\n&lt;/code&gt;&lt;/pre&gt;\\n&lt;br /&gt;\",\n    \"CategoryName\": \"Unvalidated Input\",\n    \"LikelihoodId\": 4,\n    \"Id\": 5,\n    \"Recommendation\": \"&lt;p&gt;Fix it! here is a link &lt;a href=\\\"https://www.a.b.com\\\"&gt;here&lt;/a&gt;&lt;/p&gt;\\n&lt;br /&gt;\",\n    \"SeverityId\": 4,\n    \"Name\": \"Cross Site Scripting\"\n  }\n]\n</code></pre></p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#using-swagger","title":"Using Swagger","text":"<p>Instead of using CURL as show above you can use the API docs pages to submit directly to your API to test things out. </p> <p>Just navigate to <code>https: //YourHost/api-docs</code> and select any of the API's available. You will need your API Key that can be found in your profile.</p> <p>Below is an example of using swagger to update a Template with JSON. </p>","tags":["API","Core Features","Vulnerability"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/","title":"Integrate Faction into OIDC Solutions","text":"<p>Faction seamlessly integrates with your existing enterprise authentication solutions, ensuring a smooth and secure user experience. Leveraging widely adopted solutions such as LDAP and OIDC, Faction effortlessly integrates into any enterprise environment. Our platform is designed to adapt to your authentication infrastructure, providing a hassle-free implementation process and enhancing the overall efficiency of your organization\u2019s security framework. With Faction, you can trust in a unified and streamlined authentication experience tailored to your enterprise needs.</p> <p>The article will walk through the steps needed to integrate\u00a0Faction\u00a0into\u00a0Google Auth, Auth0, or Ping Identity</p>","tags":["Authentication","Core Features"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/#google-oidc-setup","title":"Google OIDC Setup","text":"<ol> <li>Log into your company\u2019s\u00a0Google API Console.</li> <li>Click on\u00a0Credentials\u00a0from the left navigation.</li> <li>Click\u00a0+ Create Credentials\u00a0from the top navigation.</li> <li>Select\u00a0OAuth Client ID.</li> <li>Select\u00a0Web Application\u00a0as the application type.</li> <li>Name the application something specific like\u00a0Faction OIDC Integration.\u00a0But the name does not matter.</li> <li>Under\u00a0Authorized redirect URLs\u00a0click\u00a0+ ADD URI.</li> <li>Enter the domain of your Faction Instance and append\u00a0/oauth/callback?client_name=OidcClient\u00a0to the path. Example: If you used Faction to host the site your URL would look like this:     https://furry-hyena-1111.factionsecurity.com/oauth/callback?client_name=OidcClient</li> <li>Then Click\u00a0Create.</li> <li>Take Note of the\u00a0Client Id\u00a0and\u00a0Client Secret. This will be used later in the Faction Admin Section.</li> </ol> <p>Your Setup should look like the following: </p>","tags":["Authentication","Core Features"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/#auth0-oauth-setup","title":"Auth0 OAuth Setup","text":"<ol> <li>Log into your\u00a0Auth0 Console.</li> <li>Select\u00a0Applications\u00a0in the left navigation.</li> <li>Click\u00a0+ Create Application</li> <li>Select\u00a0Regular Web Application. </li> <li>Name it something like\u00a0Faction OAuth Integration.</li> <li>Click\u00a0Create.</li> <li>Ignore the Quick Start screen and Click\u00a0Settings.</li> <li>In the\u00a0Allowed Callback URLs, enter the domain of your Faction Instance and append\u00a0/oauth/callback?client_name=OidcClient\u00a0to the path.  Example: If you used\u00a0Faction\u00a0to host the site your URL would look like: https://furry-hyena-1111.factionsecurity.com/oauth/callback?client_name=OidcClient </li> <li>Take Note of the\u00a0Client Id\u00a0and\u00a0Client Secret. This will be used later in the Faction Admin.</li> <li>Scroll down to the bottom and Click\u00a0Advanced\u00a0and then\u00a0Endpoints</li> <li>Take note of the\u00a0OpenId Configuration\u00a0URL     </li> </ol>","tags":["Authentication","Core Features"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/#ping-identity-setup","title":"Ping Identity Setup","text":"<ol> <li>Log into Ping Identity Console</li> <li>Select Applications.</li> <li>Add a New Application.</li> <li>Give the Application a name like Faction.</li> <li>Select OIDC Web App.</li> <li>Click Save.     </li> <li>Open the newly created application and select the Configuration tab:    </li> <li>Click the Edit Button in the upper right corner</li> <li>Scroll down to the Redirect URI Section and enter your Host Name with the path <code>/oauth/*</code>. (Example: <code>https://furry-hyena-1111.factionsecurity.com/oauth/*</code>)</li> <li>Click Enable Redirect Patterns.     </li> <li>Click Save.</li> <li>Scroll up to the top of the configuration.</li> <li>Expend URLs and take note of the the OIDC Discovery Endpoint. This will be used later in the Configure Faction Section. </li> <li>Take Note of the Client Id and the Client Secret. These will be used in the Configure Faction Section</li> <li>Click the Attribute Mappings tab.</li> <li>Add email as an attribute.     </li> <li>Click Save.</li> </ol>","tags":["Authentication","Core Features"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/#configure-faction","title":"Configure Faction","text":"<ol> <li>Log into\u00a0Faction\u00a0as an admin user.</li> <li>Navigate to\u00a0Admin\u00a0-&gt;\u00a0Users.</li> <li>In the\u00a0OAuth2.0 Configuration\u00a0enter the Client Id you noted earlier from either Auth0, Google, or Ping.</li> <li>Enter the\u00a0Client Secret\u00a0you noted earlier.</li> <li>Enter the\u00a0Discovery URL\u00a0as follows:<ol> <li>Google: https://accounts.google.com/.well-known/openid-configuration </li> <li>Auth0:\u00a0Enter the\u00a0Open Id Configuration\u00a0URL you noted in step 11 above.</li> <li>Ping: Enter the OIDC Discovery Endpoint from step 13 above. </li> </ol> </li> <li>Click\u00a0Save </li> </ol>","tags":["Authentication","Core Features"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/#adding-an-oauth-user","title":"Adding an OAuth User","text":"<ol> <li>Under\u00a0Admin -&gt; Users, Click\u00a0Add User.</li> <li>The Username should be part of the user\u2019s email address before the @ symbol. If the email is\u00a0test.user@yourcompany.com\u00a0then the username is test.user</li> <li>\u2b50\ufe0fLeave the Password Field Blank.\u2b50\ufe0f</li> <li>Enter the\u00a0First\u00a0and\u00a0Last\u00a0name.</li> <li>Enter the\u00a0email\u00a0address that is used by the OAuth solution to authenticate the user.</li> <li>Select\u00a0OAuth 2.0\u00a0as the Authentication Method.</li> <li>Click\u00a0Save Changes.</li> </ol> <p>When the new user reaches the Login Screen they can enter just their username without a password and click\u00a0Login. Faction will redirect the user to the configured Authentication Provider and redirect back.</p>","tags":["Authentication","Core Features"]},{"location":"Managed%20FACTION%20Setup/","title":"Managed FACTION Setup","text":"<p>Below are the Minimal Faction Setup Instructions required to get you all set up and ready to start collaborating on assessments in just a few minutes. With a Faction managed account, we host the servers and maintain the updates for you. Your instance will be hosted in a single-tenant environment to ensure your data is secure. With just a few clicks you will be up and running in minutes. </p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#create-your-managed-account","title":"Create Your Managed Account","text":"<p>Every account that gets created will get its own single-tenant instance. To create a new instance go to\u00a0https://portal.factionsecurity.com,\u00a0Create an Account, and Select a tier that meets your team's needs.</p> <p></p> <p>This will begin creating your instance of Faction. Wait until the spinner shows a green checkbox before you attempt to access your site. You can then click the URL in the site list to take you to your new Faction Instance.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#create-an-admin-user","title":"Create an Admin User","text":"<p>The first time you access Faction you will be presented with a page to create your admin account. Here you need to enter basic information about the user and the option to create a team.\u00a0Hacking Team\u00a0is the default.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#adding-default-vulnerability-templates","title":"Adding Default Vulnerability Templates","text":"<p>The Faction Default vulnerability database is what makes generating reports quick and painless for pen-testing teams. You can upload your templates or start with an open-source list from\u00a0https://github.com/factionsecurity/data</p> <p>To add the VulnDB data into Faction just navigate to\u00a0Admin-&gt;\u00a0Default Vulnerabilities\u00a0and click\u00a0Update from VulnDB. This will import all of their vulnerabilities and set default Categories for the vulnerabilities.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#setting-custom-risk-levels-optional","title":"Setting Custom Risk Levels (Optional)","text":"<p>By default, Faction adds\u00a0Critical,\u00a0High,\u00a0Medium,\u00a0Low,\u00a0Recommended, and\u00a0Informational\u00a0risk levels but you have up to 9 that can be set and the defaults can be changed to anything that works for your environment. For instance,\u00a0Critical\u00a0can be changed to\u00a0Priority 1.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#vulnerability-tracking-and-remediation-slas","title":"Vulnerability Tracking and Remediation SLAs","text":"<p>Different Tiers allow enhanced features within Faction. The\u00a0Teams Tier\u00a0and above have verification and vulnerability tracking enabled. In\u00a0Admin Settings\u00a0you can set custom times to alert when the vulnerability needs to be remediated based on its risk setting. For instance, you can set a reminder that a\u00a0Critical\u00a0vulnerability needs to be remediated 30 days after it's reported and set a past due date of 60 days. This will trigger Faction to alert the correct teams that important issues are close to being past due to ensure issues get closed on time and are never forgotten.</p> <p>Any values that are missing a date will not be tracked by Faction.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#assessment-checklists","title":"Assessment Checklists","text":"<p>For some assessments, you will want to add checklists to ensure all critical issues are tested. Below is an example of some potential checks that might need to happen on every assessment to ensure applications are tested consistently.</p> <p></p> <p>Once the above is created it will be available in assessments where the assessor can pass/fail the checklist item and even add notes related to why it failed or why it\u2019s not necessary for the application being tested.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#additional-configuration-options","title":"Additional Configuration Options","text":"<p>The higher-level tiers allow you to configure other options like LDAP and OAuth. You can find additional information below on these settings:</p> <ul> <li>Integrate Faction Into OAuth Solutions</li> <li>Customizing Faction for Self Hosting</li> <li>Extending Faction</li> </ul>","tags":["Cloud Hosted","Setup"]},{"location":"Remediation%20Tracking%2C%20Custom%20SLAs%2C%20Retests/","title":"Remediation Tracking, Custom SLAs, Retests","text":"<p>FACTION has remediation tracking built in! When you close out an assessment all the vulnerabilities in that assessment start tracking based on your custom SLAs. With the custom SLAs you can set reminders when a vulnerabilities is approaching a due data and another when the it is past due. </p>","tags":["Remediation","Retests","Core Features"]},{"location":"Remediation%20Tracking%2C%20Custom%20SLAs%2C%20Retests/#setting-custom-slas","title":"Setting Custom SLAs","text":"<p>Navigate to Templates -&gt; Default Vulnerabilities. Here you find a table that lets you set your vulnerability tracking times.  </p> <p>Each vulnerability severity level will have a Warning date and a Past Due date. These are measured in days after the assessment is completed. All empty inputs represent Untracked issues. </p> <p>In the above screenshot, Critical vulnerabilities will have a remediation due date that is 60 days and a warning set at 30 days after the assessment is completed.  High vulnerabilities are expected to be remediated in 120 days and have a warning at 60 days after assessment completion.  Note that all other vulnerabilities are not tracked by FACTION because the inputs are all blank. </p>","tags":["Remediation","Retests","Core Features"]},{"location":"Remediation%20Tracking%2C%20Custom%20SLAs%2C%20Retests/#remediation-dashboards-and-retests","title":"Remediation Dashboards and Retests","text":"<p>You can see the status of all past and approaching due dates in the Remediation Queue.  </p> <p>This dashboard allows assessment teams to easily see all issues that require remediation and the current state of the vulnerability. </p> <p>In the above screenshot, there is one issue that is Past Due and several others that are close to being past due. Clicking on the past due issue lets you easily schedule it for retest as shown below: </p>","tags":["Remediation","Retests","Core Features"]},{"location":"Remediation%20Tracking%2C%20Custom%20SLAs%2C%20Retests/#adding-follow-up-notes","title":"Adding Follow Up Notes","text":"<p>You can add notes to all tracked vulnerabilities. You can add follow-up notes from the development teams, annotate delays in schedules, or other information you might need later to stay on top of the remediation. </p> <p>The Note History stores not only notes but also tracks the passing and failing of retests. </p>","tags":["Remediation","Retests","Core Features"]},{"location":"Self-Hosted%20FACTION%20Setup/","title":"Self Hosted FACTION Setup","text":"<p>If you decide to self-host Faction instead of using the\u00a0Managed Solution\u00a0then you will need to ensure you include the proper Environment variables so that Faction integrates into your environment.</p>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#requirements","title":"Requirements","text":"<ul> <li>Tomcat 9</li> <li>Java 11</li> <li>Mongo 7</li> <li>maven</li> </ul>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#option-1-docker-compose","title":"Option 1:  Docker Compose","text":"<p>Download the code from GitHub and run the following commands <pre><code>git clone git@github.com:factionsecurity/faction.git\ncd faction\nmvn clean compile war:war\ndocker-compose up --build\n</code></pre></p>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#updating-faction","title":"Updating Faction","text":"<p>New releases can be found here. You can either pull a new release of Faction and build it yourself as shown above or If you don't want to perform the Maven install you can download the <code>faction.war</code> file directly and put it into the targets folder. </p>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#option-2-install-tomcat-and-mongo","title":"Option 2: Install Tomcat and Mongo","text":"<p>Check back, instructions will be updated soon</p>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#custom-environment-variables","title":"Custom Environment Variables","text":"<pre><code>## Mongo Database configs \n\nFACTION_MONGO_HOST=127.0.0.1. #requireed \nFACTION_MONGO_DATABASE=faction #required \nFACTION_MONGO_USER=faction_mongo_user #optional \nFACTION_MONGO_PASSWORD=faction_mongo_pass #optional \nFACTION_MONGO_AUTH_DATABASE=admin #optional \n\nFACTION_SECRET_KEY=faction_encryption_key #required \n\nFACTION_REPORT_STORAGE=aws #optional \nFACTION_BUCKET_NAME=your-bucket #optional \nFACTION_TIER=teams #required \nFACTION_USERS=100 #optional \n\nFACTION_SMTP_SERVER=smtp.server.com #optional \nFACTION_SMTP_USER=sysadmin #optional \nFACTION_SMTP_PORT=587 #optional\n</code></pre>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#mongo-database-variables","title":"Mongo Database Variables","text":"<ul> <li>FACTION_MONGO_HOST\u00a0(Required):     This is the hostname or ip address where your mongo database i location</li> <li>FACTION_MONGO_DATABASE\u00a0(Required):     The name of the mongo database. This can be anything you want. On initial loading of the application it will create the database and all collections.</li> <li>FACTION_MONGO_USER\u00a0(O_ptional_):     If you use authentication (and you should) then this user has access to the database.</li> <li>FACTION_MONGO_PASSWORD\u00a0(Optional):     Only required if you use the FACTION_MONGO_USER environment variable.</li> <li>FACTION_MONGO_AUTH_DATABASE\u00a0(Optional):     The default authentication database is\u00a0admin.\u00a0If you want to use another then you can use this variable.</li> </ul>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#other-variables","title":"Other Variables","text":"<ul> <li>FACTION_SECRET_KEY\u00a0(Required):     This is the key used for all symmetric key encryption.</li> <li>FACTION_REPORT_STORAGE\u00a0(Optional):     This variable has two options:\u00a0local\u00a0or\u00a0aws. If you include\u00a0aws\u00a0then you also need to set\u00a0AWS_ACCESS_KEY_ID\u00a0and\u00a0AWS_SECRET_ACCESS_KEY\u00a0and create the an s3 bucket location in AWS.\u00a0You can also use IAM permissions instead of including the AWS Keys.      When using\u00a0local\u00a0\u00a0the default directory location is\u00a0/opt/faction.\u00a0If this variable is not set,\u00a0local\u00a0will be used as default.</li> <li>FACTION_BUCKET_NAME\u00a0(Optional):     S3 Bucket Name to to store Faction files.</li> <li>FACTION_TIER\u00a0(Required):     Only use the value\u00a0team\u00a0here</li> <li>FACTION_USERS\u00a0(Required):     The user limit. you can set this to any value that makes sense for your organization.</li> </ul>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#email-variables","title":"Email Variables","text":"<p>These settings (FACTION_SMTP_SERVER, FACTION_SMTP_USER&lt; FACTION_SMTP_PORT) are just used for the initial setup of Faction. They will be overridden when you save or test emails in the admin settings pages. This is useful for doing deployments in Kubernetes or ECS.</p>","tags":["Self Hosted","Setup"]},{"location":"Table%20of%20Contents%20Numbering/","title":"Table of Contents Numbering","text":"<p>Faction's open-source versions will not automatically update the Table of Contents page numbering though the hyperlinks all work as expected.  You can do this manually by clicking the table and selecting Update Field on the generated report.  </p> <p>The enterprise versions of Faction will automatically update the numbering for you as well as provide other additional reporting features like different finding sections (i.e. Application Security Pen Test Findings Section and Network Security Findings Section) and DOCX and PDF export options.  </p> <p>Contact us here to learn more.</p>","tags":["Reporting","Enterprise","Paid Feature","Managed"]},{"location":"Using%20Markdown%20in%20Reports/","title":"Using Markdown in Reports","text":"<p>When exploiting a vulnerability in a penetration test it is important to capture your attack steps quickly and thoroughly so you don't have to spend extra time remembering and re-validating what you did when it's time to report on the finding. Nothing can break your flow more than having to stop what you are doing to format text, fix hyperlinks, or build numbered lists of steps. Markdown is one of the quickest ways to type formatted text and capture these details effortlessly. </p> <p>Pro Tip!</p> <p>The API fully supports Markdown. This makes it easy to develop automated tools that can add issues or other text to Faction with formatted text via the API. </p> <p>Faction supports markdown by default in all editors. Here are some examples of how you can use markdown:</p>","tags":["Markdown","Reporting","Core Features","Burp Suite"]},{"location":"Using%20Markdown%20in%20Reports/#exploit-steps","title":"Exploit Steps","text":"<p>Entering exploit steps is easier with markdown. You can enter the following text and it will automatically show you the formated view on the right.  <pre><code>__Steps to Reproduce__:\n1. Go to the home page.\n2. Click Login.\n3. Enter `&lt;script&gt;alert(123);&lt;/script&gt;` in the username parameter. \n</code></pre></p> <p></p>","tags":["Markdown","Reporting","Core Features","Burp Suite"]},{"location":"Using%20Markdown%20in%20Reports/#faction-burp-suite-extension","title":"Faction Burp Suite Extension","text":"<p>If you find a vulnerability while using the Faction Burp extension, you can add the finding and all details directly through the extension. Below is an example of cross-site scripting: </p> <p>In Burp Suite, select the request and select Add New Finding: </p> <p>A dialog box will open that lets you search for the vulnerability type (in this case Cross Site Scripting) and allow you to enter your details on how to recreate the exploit. </p> <p></p> <p>Now if we navigate back into Faction and view the details we will see the exploit steps displayed in rich text. </p> <p></p>","tags":["Markdown","Reporting","Core Features","Burp Suite"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/","title":"Using the Faction Burp Suite Extension","text":"<p>The Faction BurpSuite Extension makes much of what is available in the Web UI available right inside Burp Suite. With this extension, you can:</p> <ul> <li>Access all assessments and retests assigned to you</li> <li>Access Assessment notes</li> <li>Create and update findings </li> <li>Extract parts of the request and responses to add to the assessment report</li> <li>Add finding details in markdown</li> <li>Replay requests you or other assessors have reported</li> </ul>","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#configure-the-extension","title":"Configure the Extension","text":"<p>You can download the extension here . We also hoping to have it added to the BApp store soon. </p> <p>Once installed in Burp, Navigate to the config tab. You need two things to configure:</p> <ol> <li>Your API key- This can be found in the Faction Web UI, under your profile (top upper right). If you do not have an API key then your administrator needs to give you the API permission.</li> <li>API URL - The API URL is most commonly something like <code>https://myserver.com/api</code>. If you login to something different like <code>http://myserver.com:8080/myfaction</code>, then your API URL will be <code>http://myserver.com:8080/myfaction/api</code></li> </ol> <p>Once configured, It should look something like this: </p>","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#severity-mapping","title":"Severity Mapping","text":"<p>Severity Mapping is used to convert vulnerability severities that Burp Suite Reports to the custom severities you set in Faction. More on setting custom severities can be found here</p> <p>Let's say your process requires that Criticals are called P1s and Highs are called P2s. Burp's Vulnerability Scanner finds a Critical issue that you want to report in Faction. You can now simply right-click the finding and add it to Faction and the extension will map the Critical to P1. </p>","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#viewing-the-queues","title":"Viewing the Queues","text":"<p>When you select Queues you will see both your assessments (left) and retests (right) queue. You can select an item in either table to view the data. This gives you all the information you need to start your assessment or verification without even logging into the Web UI. </p>","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#selecting-an-assessment","title":"Selecting an Assessment","text":"<p>From the Queues page, select your currently working assessment. This will set this assessment as the default assessment for all other dialog boxes, for example when adding a new vulnerability it will be reported in this assessment. </p> <p>Once you select the assessment in the table, click Assessment. Now you will see the scope and shared notes about the assessment. </p> <p></p> <p>This keeps all the common information about the assessment handy, like in-scope URLs, test credentials, and even notes you want to share with other assessors on the same project. </p>","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#enter-a-new-finding","title":"Enter a New Finding","text":"","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#update-an-existing-finding","title":"Update an Existing Finding","text":"","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#selecting-a-retest","title":"Selecting a Retest","text":"","tags":["Burp Suite","API","Penetration Testing"]},{"location":"tags/","title":"Tags","text":"","tags":[]},{"location":"tags/#api","title":"API","text":"<ul> <li>Faction App Store Extensions</li> <li>Importing Your Vulnerability Templates Via the API</li> <li>Using the Faction Burp Suite Extension</li> <li>App Store Extension API</li> <li>JIRA App Integration Example</li> <li>REST API</li> </ul>","tags":[]},{"location":"tags/#app-store","title":"App Store","text":"<ul> <li>Faction App Store Extensions</li> <li>App Store Extension API</li> <li>JIRA App Integration Example</li> <li>Faction App Store</li> </ul>","tags":[]},{"location":"tags/#authentication","title":"Authentication","text":"<ul> <li>Integrate Faction into OIDC Solutions</li> </ul>","tags":[]},{"location":"tags/#boilerplate","title":"Boilerplate","text":"<ul> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#burp-suite","title":"Burp Suite","text":"<ul> <li>Using Markdown in Reports</li> <li>Using the Faction Burp Suite Extension</li> </ul>","tags":[]},{"location":"tags/#cvss","title":"CVSS","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> </ul>","tags":[]},{"location":"tags/#cloud-hosted","title":"Cloud Hosted","text":"<ul> <li>Managed FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#core-features","title":"Core Features","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> <li>Importing Your Vulnerability Templates Via the API</li> <li>Integrate Faction into OIDC Solutions</li> <li>Remediation Tracking, Custom SLAs, Retests</li> <li>Using Markdown in Reports</li> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#customize","title":"Customize","text":"<ul> <li>Custom Security Report Templates</li> <li>Custom Variables</li> </ul>","tags":[]},{"location":"tags/#customizing","title":"Customizing","text":"<ul> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#enterprise","title":"Enterprise","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#managed","title":"Managed","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#markdown","title":"Markdown","text":"<ul> <li>Using Markdown in Reports</li> </ul>","tags":[]},{"location":"tags/#paid-feature","title":"Paid Feature","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#penetration-testing","title":"Penetration Testing","text":"<ul> <li>Using the Faction Burp Suite Extension</li> </ul>","tags":[]},{"location":"tags/#remediation","title":"Remediation","text":"<ul> <li>Remediation Tracking, Custom SLAs, Retests</li> </ul>","tags":[]},{"location":"tags/#reporting","title":"Reporting","text":"<ul> <li>Custom Security Report Templates</li> <li>Custom Variables</li> <li>Table of Contents Numbering</li> <li>Using Markdown in Reports</li> <li>How To Generate a Vulnerability Report in Faction</li> </ul>","tags":[]},{"location":"tags/#retests","title":"Retests","text":"<ul> <li>Remediation Tracking, Custom SLAs, Retests</li> </ul>","tags":[]},{"location":"tags/#self-hosted","title":"Self Hosted","text":"<ul> <li>Self Hosted FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#setup","title":"Setup","text":"<ul> <li>Managed FACTION Setup</li> <li>Self Hosted FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#variables","title":"Variables","text":"<ul> <li>Custom Security Report Templates</li> </ul>","tags":[]},{"location":"tags/#vulnerability","title":"Vulnerability","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> <li>Importing Your Vulnerability Templates Via the API</li> </ul>","tags":[]},{"location":"tags/#api_1","title":"api","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]},{"location":"tags/#burpsuite","title":"burpsuite","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]},{"location":"tags/#hello-world","title":"hello world","text":"<ul> <li>Hello World</li> </ul>","tags":[]},{"location":"tags/#integrations","title":"integrations","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]},{"location":"APIS/App%20Store%20Extension%20API/","title":"App Store Extension API","text":"","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#introduction","title":"Introduction","text":"<p>Faction has an API similar to what you might find in BurpSuite Extensions. You can create custom modules in jar files and upload them to the Faction AppStore. Once uploaded, Faction will perform your custom processing when certain events are triggered like finalizing and assessment, creating a report, or failing a retest. </p> <p>You can even extend things like the Application Inventory Search so that it queries an external database to return results before scheduling assessments.</p> <p>You can download an example\u00a0Extension here.</p> <p>Below is a list of the current Hooks:</p>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#faction-extension-apis","title":"Faction Extension APIs","text":"","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#application-inventory-extension","title":"Application Inventory Extension","text":"<p><pre><code>public class MyPlugin extends BaseExtension implements com.faction.extender.ApplicationInventory{\n\n    @Override\n    public InventoryResult[] search(String arg0, String arg1) {\n\n        return null;\n    }\n}\n</code></pre> - Triggers on Assessment Scheduling and will then query external sources instead of the local database. - Can search based on Application ID or Application name. It will return an InventoryResult Object (explained later)</p>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#assessment-manager-extension","title":"Assessment Manager Extension","text":"<p><pre><code>public class MyPlugin extends BaseExtension implements com.faction.extender.AssessmentManager{\n\n    @Override\n    public AssessmentManagerResult assessmentChange(Assessment arg0, List&lt;Vulnerability&gt; arg1, Operation arg2) {\n\n        return null;\n    }\n\n}\n</code></pre> Typical use case scenario: When an assessor finalizes an assessment this module can send all the vulnerabilities to another tracking system like JIRA and return the tracking numbers to Faction.</p> <ul> <li>Triggers on Assessment Create, Update, Delete, Finalized, Peer Review Created, Peer Review Complete, Peer Review Accepted</li> <li>Accepts the Triggered Assessment and List of vulnerabilities associated with the assessment.</li> <li>Returns AssessmentManagerResult, that is the updated Assessment and updated List of vulnerabilities</li> <li>If the return object is null Faction will not update locally</li> </ul>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#update-reports","title":"Update Reports","text":"<p><pre><code>public class VulnerabilityBarChart extends BaseExtension implements com.faction.extender.ReportManager {\n\n    @Override\n    public String reportCreate(Assessment asmt, List&lt;Vulnerability&gt; vulns, String reportText) {\n\n    return reportText;\n\n}\n</code></pre> This method triggers every time a report is created or regenerated. It can be used to for you to add custom variables to reports and update those variables with HTML. An example of this can be found here which demonstrates how to add bar charts to vulnerability reports. </p> <ul> <li>Triggers on report create or regenerate</li> <li>Can update Text in reports</li> <li>Output can be HTML or raw text</li> <li>If returns null then nothing will be changed by this extension</li> </ul>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#vulnerability-manager-extension","title":"Vulnerability\u00a0Manager Extension","text":"<p><pre><code>public class MyPlugin extends BaseExtension extends BaseExtension implements com.faction.extender.VulnerabilityManager{\n\n    @Override\n    public Vulnerability vulnChange(Assessment arg0, Vulnerability arg1, Operation arg2) {\n        // TODO Auto-generated method stub\n        return null;\n    }\n}\n</code></pre> Typical use case scenario: When an assessor creates or updates a vulnerability the module can send\u00a0the\u00a0vulnerability to another tracking system like JIRA and return the tracking\u00a0number to Faction.</p> <ul> <li>Triggers on Assessment Create, Update, Delete</li> <li>Accepts the Triggered Assessment and vulnerability that is being processed.</li> <li>Returns\u00a0the updated vulnerability</li> <li>If the return object is null then Faction will not update locally</li> </ul>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#verificationretest-manager-extension","title":"Verification(Retest) Manager Extension","text":"<pre><code>public class MyPlugin extends BaseExtension extends BaseExtension implements com.faction.extender.VerificationManager{\n\n    @Override\n    public void verificationChange(User arg0, Vulnerability arg1, String arg2, Date arg3, Date arg4, Operation arg5) {\n\n    }\n}\n</code></pre> <ul> <li>Triggers on\u00a0Pass, Fail, Cancel, Assigned</li> <li>Accepts the Triggered\u00a0Assigned User, Vulnerability Assigned, Start and end dates for the verification.</li> <li>Returns\u00a0the updated vulnerability</li> </ul>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#additional-resources","title":"Additional Resources","text":"<ul> <li>Building a JIRA Extension</li> </ul>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/","title":"JIRA App Integration Example","text":"<p>Faction can extend its functionality on the server side. If you are familiar with writing BurpSuite extensions then this process should be somewhat familiar to you. If you are not it\u2019s OK. We will walk through the specifics below.</p> <p>In this example, we will create a JIRA plugin that will create issues for each vulnerability when the assessment is finalized.</p> <p>The source code for this example can be\u00a0downloaded here.</p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#extension-requirements","title":"Extension Requirements","text":"<ol> <li>Create a new Eclipse Maven Java Project.</li> <li>Modify your\u00a0pom.xml\u00a0file to enable the Faction Extender API and ensure your manifest includes Title, Version, Author, and URL as shown below.  <pre><code>&lt;project xmlns=\"http://maven.apache.org/POM/4.0.0\"\n    xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n    xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd\"&gt;\n    &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;\n\n    &lt;groupId&gt;faction-jira-extension&lt;/groupId&gt;\n    &lt;artifactId&gt;faction-jira-extension&lt;/artifactId&gt;\n    &lt;version&gt;1.0&lt;/version&gt;\n    &lt;name&gt;Faction Jira Extension&lt;/name&gt;\n    &lt;dependencies&gt;\n        &lt;dependency&gt;\n            &lt;groupId&gt;com.factionsecurity&lt;/groupId&gt;\n            &lt;artifactId&gt;faction-extender&lt;/artifactId&gt;\n            &lt;version&gt;2.5&lt;/version&gt;\n        &lt;/dependency&gt;\n    &lt;/dependencies&gt;\n    &lt;build&gt;\n        &lt;plugins&gt;\n            &lt;plugin&gt;\n                &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;\n                &lt;configuration&gt;\n                    &lt;descriptorRefs&gt;\n                        &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;\n                    &lt;/descriptorRefs&gt;\n                    &lt;archive&gt;\n                        &lt;manifestEntries&gt;\n                            &lt;Title&gt;${project.name}&lt;/Title&gt;\n                            &lt;Version&gt;${project.version}&lt;/Version&gt;\n                            &lt;Author&gt;Josh Summitt&lt;/Author&gt;\n                            &lt;URL&gt;https://www.factionsecurity.com&lt;/URL&gt;\n                        &lt;/manifestEntries&gt;\n                    &lt;/archive&gt;\n                &lt;/configuration&gt;\n            &lt;/plugin&gt;\n        &lt;/plugins&gt;\n    &lt;/build&gt;\n&lt;/project&gt;\n</code></pre></li> <li>Create the following folders and files. They can be empty for now. We will fill this out in the next section below.      The maven-assembly-plugin will ensure your manifest is set up correctly for Faction to be able to import your extension with the proper information.</li> </ol>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#extension-file-and-folder-requirements","title":"Extension File and Folder Requirements","text":"<p>We need to update the extension resources from Step 3 above. Below is a description of the files. </p> <ul> <li><code>resources/META-INF/resouces/config.json</code> : This file is a JSON key-value pair of options you want to be configurable by the end user. These options become input boxes in the Faction App Store UI. </li> <li><code>resources/META-INF/resources/description.md</code> : This is the extension description and help files that will be displayed when the extension is loaded in the Faction App Store UI</li> <li><code>resources/META-INF/resources/logo.png</code>: This is a PNG log that will be displayed as the Apps icon in the Faction App Store UI</li> <li><code>resources/META-INF/services/*</code>: This file is required for Faction to be able to load your extension. </li> </ul>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#configjson","title":"config.json","text":"<p>These are the key value pairs that will display in the Faction App Store UI and allow users to make changes that affect the behavior of the extensions. For a Jira plugin you would want the API, the Jira Host and the Jira Username configured. That would look like the following <pre><code>{\n    \"Jira Host\" : {\n        \"type\": \"text\",\n        \"value\": \"https://yourhost.com\"\n        },\n    \"Jira API Key\" : {\n        \"type\": \"password\",\n        \"value\": \"your api key\"\n        },\n    \"Jira Email\": {\n        \"type\" : \"text\",\n        \"value\": \"your@email.com\"\n    }\n}\n</code></pre></p> <p>Any values you set in your extension will be the \"Default\" values that will display to the end user. They can be blank if you do not what to set a predefined value. </p> <p>The <code>type</code> attribute can only be <code>text</code> or <code>password</code>. <code>password</code> attributes  are not displayed in the UI when the user enters the data and do not get returned to the UI once saved. </p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#descriptionmd","title":"description.md","text":"<p>This is where you describe your extension to end users and support most markdown elements. You should use this to fully describe what the extension does, why the user should install it,  and how the end user should configure it to work correctly. </p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#logopng","title":"logo.png","text":"<p>This will be the logo in a PNG format that will display as an icon for your project. </p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#services","title":"services","text":"<p>The <code>resources/META-INF/services/</code> files have a specific naming convention so that Faction can load your classes. The file must be named one of the following:</p> <ul> <li><code>com.faction.extender.AssessmentManager</code></li> <li><code>com.faction.extender.ApplicationInventory</code></li> <li><code>com.faction.extender.ReportManager</code></li> <li><code>com.faction.extender.VerificationManager</code></li> <li><code>com.faction.extender.VulnerabilityManager</code></li> </ul> <p>The content of each file is the name of your class that instantiates this functionality. In this example, we are only triggering the AssessmentManager therefore the file name would be <code>com.faction.extender.AssessmentManager</code> and the contents of the file would be <code>org.faction.JiraPlugin</code></p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#create-the-jira-plugin-class","title":"Create The Jira Plugin Class","text":"<p>Now that the basic set up is complete we can create our Jira Class that actually does something! </p> <p>Create a Class named\u00a0JiraPlugin\u00a0in\u00a0src/main/java. This class will implement\u00a0\u00a0com.fuse.extender.AssessmentManager\u00a0as shown below. This code will trigger whenever a change happens to an assessment. You can use the\u00a0Operation\u00a0enum to control what happens as different events change the assessment.</p> <pre><code>package org.faction;\n\npublic class JiraPlugin extends BaseExtension implements com.faction.extender.AssessmentManager{\n     @Override\n     public AssessmentManagerResult assessmentChange(Assessment assessment, List&lt;Vulnerability&gt; vulnerabilities, Operation arg2) {\n         AssessmentManagerResult result = new AssessmentManagerResult();\n        return result\n     }\n}\n</code></pre> <p>Note that above it returns\u00a0AssessmentManagerResult.\u00a0This object will update Faction\u2019s database if the values change when this function returns. If you Return\u00a0null\u00a0it will NOT update Faction and only just send/process information.</p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#send-this-issues-to-jira-on-assessment-finalized","title":"Send this Issues to Jira on Assessment Finalized","text":"<p>Now we have a basic functional block of code we need to make it perform the action of sending all vulnerabilities to Jira only when the assessment is finalized. To do this we create an if statement that checks the Operation enum equals Finalized and then sends the issues with our custom function <code>sendVulnerabilityToJira()</code>. We then get the tracking ID from Jira and update Faction so the tracking ID's are in sync. </p> <pre><code>import com.fuse.elements.Assessment;\nimport com.fuse.elements.Vulnerability;\n\npublic class JiraPlugin extends BaseExtension implements com.faction.extender.AssessmentManager{\n\n    @Override\n    public AssessmentManagerResult assessmentChange(Assessment assessment, List&lt;Vulnerability&gt; vulns, Operation opcode) {\n        String project =\"KAN\";  //Default Jira Project Name.\n\n        if(opcode == Operation.Finalize) {\n            //Integration into vulnerability management system\n            for(Vulnerability vuln : vulns) {\n                //this can update vulns and send the updated values back into Faction\n                String issueId = sendVulnerbilityToJira(vuln, project);\n                if(issueId != null) {\n                    vuln.setTracking(issueId); //Update Faction's Tracking ID\n                }\n            }\n        }\n        AssessmentManagerResult result = new AssessmentManagerResult();\n        result.setAssessment(assessment);\n        result.setVulnerabilities(vulns);\n        return result; //Send back the updated results\n    }\n}\n</code></pre> <p>You can see the full implementation here</p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#install-it-in-your-faction","title":"Install It In Your Faction","text":"<p>Build the jar file by running: <pre><code>mvn clean compile assembly:single\n</code></pre></p> <p>This will create a jar file named\u00a0something like JiraPlugin-0.0.1-SNAPSHOT-jar-with-dependencies.jar\u00a0in your ./target folder.\u00a0</p> <p>Upload it to Admin-&gt;App Store-&gt;Install Extension. It should display like this: </p> <p>If all looks good, click install. </p> <p>It will be installed initially as disabled. You can configure it before you enable it by clicking on the extension in the list: </p> <p>Once you configure the settings you can enable it. </p> <p>Now when an assessment is finalized it will add All the findings to JIRA as shown in the following screenshot:</p> <p></p>","tags":["API","App Store"]},{"location":"APIS/REST%20API/","title":"REST API","text":"<p>The Rest API enables you to integrate FACTION into your unique environment. With the API you can:</p> <ol> <li>Add vulnerabilities from other tools</li> <li>Upload your custom vulnerability templates</li> <li>Schedule Assessments and Retests</li> <li>Track remediation </li> <li>Manage Users</li> <li>and much more. </li> </ol> <p>The easiest way to access the REST API for your faction instance is to click on your profile in the top right corner. Here you will find a link to the Swagger API docs and access to your API Key</p> <p></p> <p>If you select \"Click here for API docs\" it will redirect you to the Swagger docs for your Faction Instance. You can use this page to make requests to the API directly in the browser. </p> <p></p>","tags":["API"]},{"location":"blog/2024/03/25/faction-app-store/","title":"Faction App Store","text":"<p>\u2728 We are excited to release the first iteration of the Faction App Store! \u2728</p> <p>The App Store is where developers can build custom integrations with Faction. These can be anything from sending vulnerabilities to external bug trackers to adding custom graphics to your automated pentest reports! </p> <p>We want to make this process really easy and took inspiration from Burp Suite on the design. If you have ever made an extension for Burp then you should be able to get up and running pretty quickly. </p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#what-can-be-extended","title":"What Can Be Extended?","text":"<p>With this initial release, you can extend Faction by:</p> <ul> <li>Including your own application inventory database to the application search features and populate results in Faction like the Application ID, Distribution Lists, and Application Name. </li> <li>Triggers when an assessment state changes (created, updated, or finalized). You can use this to send emails to a distribution list that an assessment has been scheduled for certain dates. When the assessment is finalized you can choose to send only the vulnerabilities of a certain criticality to an external tracking system as well as send to different tracking systems depending on the type of assessment. </li> <li>Triggers when a vulnerability state is changed. When a tracked vulnerability is retested and pass/fail, you can create a custom workflow and alert key stakeholders that the issue succeeded or failed. </li> <li>Update reports when they are generated. You can use this to add custom variables to your reporting templates and replace the contents with data from an external system or add custom charts and graphics to give your reports a more polished look. </li> </ul> <p>The full documentation on the API can be found here</p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#custom-settings","title":"Custom Settings","text":"<p>Extensions are built so that you can add your own configuration options that can be stored in the Faction Database. Things like a user-editable hostname or API key can be configured in your extension. Based on how you set up your configuration you can make data like passwords and API keys hidden in the UI and encrypted at rest. </p> <p></p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#extension-chain","title":"Extension Chain","text":"<p>Extensions can be chained in any order. Once you add apps and enable them in Faction, the UI allows you to drag the extension to anywhere in the list. This allows you to create one extension that processes data and returns a result that can be processed by the next extension. </p> Before Order Change After Order Change <p>You can use this to create one extension that returns a JIRA Tracking number for all vulnerabilities in the finalized assessment, they take those numbers and process them into another system and on and on down the chain. </p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#example-extensions","title":"Example Extensions","text":"<p>You can review the source code for our initial apps here. This list will grow over time but currently, there are 2 (JIRA Integration, Vulnerability Bar Charts). </p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#submit-your-own","title":"Submit Your Own","text":"<p>We can't think of everything! We encourage developers to submit their own extensions and we will add them to our list of Approved Extensions. Send an email to develop [ at ] factionsecurity [dot] com with a link to your GitHub and a brief explanation of what it does. </p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#conclusion","title":"Conclusion","text":"<p>We hope you enjoy the new  App Store and other new features that are part of this 1.2 Release. Faction is open-source and free to use. Please leave us feedback in either our GitHub Discussion Boards or by submitting Issues. </p> <p>If you want to help support the project and ensure its longevity then consider being a sponsor... It's good karma!  \u2764\ufe0f</p> <p>Sponsor Options</p> <ul> <li>GitHub Sponsor</li> <li>Patreon</li> <li>Open Collective</li> </ul>","tags":["App Store"]},{"location":"blog/2024/03/16/faction-boilerplates/","title":"Faction Boilerplates","text":"<p>If you have been doing penetration testing for any length of time you probably have a personal database of vulnerability descriptions, recommendations as well as other text snippets you will inject into various places of your reports. What if, Instead of keeping these in separate files on various computers, they were all included in your reporting software?!@! \ud83e\udd2f</p> <p>Faction IS your database for global boilerplate, default vulnerability templates, personal flare, and just about anything else you can imagine (well...sorta \ud83e\udd14). Let's walk through how this is done.</p>","tags":["Core Features","Boilerplate","Customizing"]},{"location":"blog/2024/03/16/faction-boilerplates/#vulnerability-templates","title":"Vulnerability Templates","text":"<p>Let's start with the obvious.... Faction includes over 75 default vulnerability templates when you start. These vulnerability templates include both descriptions and recommendations and are fully customizable by you. You can start with our templates or upload your own as described here.</p> <p>When writing your report, type the name of the vulnerability and it will auto-populate in the UI as shown below: </p> <p>Once selected your report will automatically include the severity of the finding, the description, and the recommendation! \ud83d\udca5 Something that would have taken you 30 min to an hour is complete in just a few seconds. </p> <p>These are fully editable in the Default Vulnerabilities section. You can add new ones, update the pre-packaged ones, or delete them all and upload all your own with the Faction API.</p>","tags":["Core Features","Boilerplate","Customizing"]},{"location":"blog/2024/03/16/faction-boilerplates/#assessment-templates","title":"Assessment Templates","text":"<p>Faction has the option of creating global and personal boilerplates that you can easily add to your reports. Global templates are shared with everyone while personal templates are only available to you. </p>","tags":["Core Features","Boilerplate","Customizing"]},{"location":"blog/2024/03/16/faction-boilerplates/#global-assessment-templates","title":"Global Assessment Templates","text":"<p>In Faction, Navigate to Templates -&gt; Assessment Templates. Here you have the option to create text that will be available to all assessors in the platform. This is useful for creating things like Different High-Level Summaries for different report types or adding common risk summaries. </p> <p></p> <p>Notice you can include most faction variables in your templates and they will be auto-populated in the generated report. </p> <p>As the security assessor, you can easily add these to different sections of your report. Below is a screen-share of using Global Templates in your reports. </p>","tags":["Core Features","Boilerplate","Customizing"]},{"location":"blog/2024/03/16/faction-boilerplates/#user-assessment-templates","title":"User Assessment Templates","text":"<p>User Assessment Templates work the same as the Global Assessment Templates but are specific to your user account. This can allow you to add your own flare to a report that you might not want to share with the rest of the team. </p> <p>To add a User Template just start typing into any of Faction's text editors and then click the Save button in the Template section. Note that User Templates have a different icon beside them in the Template List. </p> <p>Below is a walk though of how you would add User templates to save and later recall user-defined boilerplate text.  </p>","tags":["Core Features","Boilerplate","Customizing"]},{"location":"blog/2024/03/15/hello-world/","title":"Hello World","text":"<p>Hey! Just starting the FACTION blog. Stay tuned here for new updates, tips, and tricks on getting the most out of FACTION. \ud83c\udf89</p> <p>FACTION 1.2 will be released this month (March'24) with loads of new features. The most notable features are the inclusion of the Faction App Store which will make it simple for developers to write extensions and integrations. </p> <p></p>","tags":["hello world"]},{"location":"blog/archive/2024/","title":"2024","text":""},{"location":"tags/","title":"Tags","text":"","tags":[]},{"location":"tags/#api","title":"API","text":"<ul> <li>Faction App Store Extensions</li> <li>Importing Your Vulnerability Templates Via the API</li> <li>Using the Faction Burp Suite Extension</li> <li>App Store Extension API</li> <li>JIRA App Integration Example</li> <li>REST API</li> </ul>","tags":[]},{"location":"tags/#app-store","title":"App Store","text":"<ul> <li>Faction App Store Extensions</li> <li>App Store Extension API</li> <li>JIRA App Integration Example</li> <li>Faction App Store</li> </ul>","tags":[]},{"location":"tags/#authentication","title":"Authentication","text":"<ul> <li>Integrate Faction into OIDC Solutions</li> </ul>","tags":[]},{"location":"tags/#boilerplate","title":"Boilerplate","text":"<ul> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#burp-suite","title":"Burp Suite","text":"<ul> <li>Using Markdown in Reports</li> <li>Using the Faction Burp Suite Extension</li> </ul>","tags":[]},{"location":"tags/#cvss","title":"CVSS","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> </ul>","tags":[]},{"location":"tags/#cloud-hosted","title":"Cloud Hosted","text":"<ul> <li>Managed FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#core-features","title":"Core Features","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> <li>Importing Your Vulnerability Templates Via the API</li> <li>Integrate Faction into OIDC Solutions</li> <li>Remediation Tracking, Custom SLAs, Retests</li> <li>Using Markdown in Reports</li> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#customize","title":"Customize","text":"<ul> <li>Custom Security Report Templates</li> <li>Custom Variables</li> </ul>","tags":[]},{"location":"tags/#customizing","title":"Customizing","text":"<ul> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#enterprise","title":"Enterprise","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#managed","title":"Managed","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#markdown","title":"Markdown","text":"<ul> <li>Using Markdown in Reports</li> </ul>","tags":[]},{"location":"tags/#paid-feature","title":"Paid Feature","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#penetration-testing","title":"Penetration Testing","text":"<ul> <li>Using the Faction Burp Suite Extension</li> </ul>","tags":[]},{"location":"tags/#remediation","title":"Remediation","text":"<ul> <li>Remediation Tracking, Custom SLAs, Retests</li> </ul>","tags":[]},{"location":"tags/#reporting","title":"Reporting","text":"<ul> <li>Custom Security Report Templates</li> <li>Custom Variables</li> <li>Table of Contents Numbering</li> <li>Using Markdown in Reports</li> <li>How To Generate a Vulnerability Report in Faction</li> </ul>","tags":[]},{"location":"tags/#retests","title":"Retests","text":"<ul> <li>Remediation Tracking, Custom SLAs, Retests</li> </ul>","tags":[]},{"location":"tags/#self-hosted","title":"Self Hosted","text":"<ul> <li>Self Hosted FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#setup","title":"Setup","text":"<ul> <li>Managed FACTION Setup</li> <li>Self Hosted FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#variables","title":"Variables","text":"<ul> <li>Custom Security Report Templates</li> </ul>","tags":[]},{"location":"tags/#vulnerability","title":"Vulnerability","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> <li>Importing Your Vulnerability Templates Via the API</li> </ul>","tags":[]},{"location":"tags/#api_1","title":"api","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]},{"location":"tags/#burpsuite","title":"burpsuite","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]},{"location":"tags/#hello-world","title":"hello world","text":"<ul> <li>Hello World</li> </ul>","tags":[]},{"location":"tags/#integrations","title":"integrations","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]}]}
\ No newline at end of file
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Welcome to FACTION","text":"<p>PenTesting Report Generation and Collaboration Engine </p> <p>FACTION is your entire assessment workflow in a box. With FACTION you can:</p> <ol> <li> <p>Automate pen testing and security assessment Reports</p> </li> <li> <p>Peer review and track changes for reports</p> </li> <li> <p>Create customized DOCX templates for different assessment types and retests</p> </li> <li> <p>Real-time collaboration with assessors via the web app and Burp Suite Extensions</p> </li> <li> <p>Customizable vulnerability templates with over 75 prepopulated</p> </li> <li> <p>Easily manage assessment teams and track progress across your organization</p> </li> <li> <p>Track vulnerability remediation efforts with custom SLA warnings and alerts \u00a0</p> </li> <li> <p>Full Rest API to integrate with other tools\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0</p> </li> </ol> <p>Other Features:\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0</p> <ol> <li> <p>LDAP Integration\u00a0 \u00a0 \u00a0 \u00a0</p> </li> <li> <p>OAUTH2.0 Integration</p> </li> <li> <p>SMTP integration\u00a0</p> </li> <li> <p>Extendable with Custom Plugins similar to Burp Extender.</p> </li> <li> <p>Custom Report Variables</p> </li> </ol> <p>Want to see it in action? -&gt; Faction Video Overview</p>","tags":[]},{"location":"#quick-setup","title":"Quick Setup","text":"<p>Requirements - Java JDK11  - Maven (for building the project)</p> <p>Run the following commands to build the war file and deploy it to the docker container.  <pre><code>git clone git@github.com:factionsecurity/faction.git\ncd faction\nmvn clean compile war:war\ndocker-compose up --build\n</code></pre></p> <p>Once the containers are up you can navigate to http://127.0.0.1:8080 to access your FACTION instance.  On the first boot, it will ask you to create an admin account. </p>","tags":[]},{"location":"#import-the-vulnerability-templates","title":"Import the Vulnerability Templates","text":"<ol> <li>Navigate to Admin -&gt; Default Vulnerabilities</li> <li>Click Import from Faction</li> </ol>","tags":[]},{"location":"#customize-reports","title":"Customize reports","text":"<p>You can find out more information about creating your own custom report templates here: Customize Report Templates</p>","tags":[]},{"location":"#burp-suite-extension","title":"Burp Suite Extension","text":"<p>Burp Suite Extensions</p>","tags":[]},{"location":"#dont-want-to-host-it-yourself","title":"Don't want to host it yourself?","text":"<p>We can provide hosting for your instance. All instances are single tenants so you don't have to worry about sharing infrastructure with untrusted parties. Hosted versions also come with other features like enhanced reporting. Navigate to https://www.factionsecurity.com to learn more. </p>","tags":[]},{"location":"#screenshots","title":"Screenshots","text":"<p>Vulnerability Templates </p> <p>Assessment Scheduling </p> <p>Peer Review and Track Changes </p>","tags":[]},{"location":"Custom%20Security%20Report%20Templates/","title":"Custom Security Report Templates","text":"<p>The Faction Report Designer allows you to create custom security report templates for each assessment type. When building reports you need to use the variables listed below. Entering these into your DOCX reports will auto-replace the assessment and vulnerability text when the report is generated. You can even use the same variables in many of the assessor input fields outside of the report template (like Risk Assessment Summaries) and it will auto-populate the fields when the report is generated.</p> <p>You can download the sample templates here:  Sample Templates </p> <p>Note</p> <p>You should disable spellcheck in your template document while adding variables. The spellcheck can cause the variables to contain attributes that will make the variable unrecognizable to the Faction document parser. </p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#general-variables","title":"GENERAL VARIABLES:","text":"<p>All of these variables can be used anywhere in the DOCX template. Those with a star \u2b50\ufe0f can be used in the web interface to assist in creating common reusable templates.</p> <ul> <li>${TOC}\u00a0\u2013 Placeholder for the Table of Contents</li> <li>${summary1}\u00a0\u2013 The high level summary</li> <li>${summary2}\u00a0\u2013 The objective and scope</li> <li>${asmtId}\u00a0\u2013 Internal Database ID \u2b50\ufe0f</li> <li>${asmtAppid}\u00a0\u2013 The assigned Application ID \u2b50\ufe0f</li> <li>${asmtName}\u00a0\u2013 The Assessment Name \u2b50\ufe0f</li> <li>${asmtAssessor}\u00a0\u2013 The first assessor assigned to the assessment \u2b50\ufe0f</li> <li>${asmtAssessor_Email}\u00a0\u2013 The first assessor email address \u2b50\ufe0f</li> <li>${asmtAssessors_Lines}\u00a0\u2013 All Assessors split into lines \u2b50\ufe0f</li> <li>${asmtAssessors_Comma}\u00a0\u2013 All Assessors split into a comma delimited list \u2b50\ufe0f</li> <li>${asmtAssessor_Bullets}\u00a0\u2013 All Assessors split into a bulleted list \u2b50\ufe0f</li> <li>${remediation}\u00a0\u2013 The Remediation Person assigned to the assessment \u2b50\ufe0f</li> <li>${riskCount*}\u00a0\u2013 The number of findings at the RiskLevel 0-9 \u2b50\ufe0f</li> <li>${riskTotal}\u00a0\u2013 The total number of findings at all RiskLevels \u2b50\ufe0f</li> <li>${asmtTeam}\u00a0\u2013 The Assessor Team Name \u2b50\ufe0f</li> <li>${asmtType}\u00a0\u2013 The Type of the Assessment \u2b50\ufe0f</li> <li>${asmtStart}\u00a0\u2013 The Start date of the assessment \u2b50\ufe0f</li> <li>${asmtEnd}\u00a0\u2013 The End date of the assessment \u2b50\ufe0f</li> <li>${asmtAccessKey}\u00a0\u2013 Guid to access the client retest queue. \u2b50\ufe0f</li> <li>${today}\u00a0\u2013 Day the report is generated \u2b50\ufe0f</li> <li>${cfXXXXXX}\u00a0\u2013 Custom Fields are ones you specify in the admin interface. These are all prefixed with \u201ccf\u201d \u2b50\ufe0f</li> <li>${totalOpenVulns} - Can be used in retest reports to show a count of open vulnerabilities.  (Since 1.3)</li> <li>${totalClosedVulns} - Can be used in retest reports to show the total count of closed vulnerabilities. (Since 1.3)</li> </ul>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#vulnerability-tables-variables","title":"VULNERABILITY TABLES VARIABLES:","text":"<p>These are only available inside tables.</p> <ul> <li>${vulnTable}\u00a0\u2013 This defines a table to be a vulnerability listing table.</li> <li>${vulnTable Section_Name}\u00a0\u2013 This defines a table to be a vulnerability listing table for a section of vulnerabilities. See Reporting Sections(Paid Only Feature).</li> <li>${vulnName}\u00a0\u2013 The Vulnerability name</li> <li>${rec}\u00a0\u2013\u00a0Vulnerability Recommendation</li> <li>${desc}\u00a0\u2013\u00a0Vulnerability Description</li> <li>${category}\u00a0\u2013 Category of the vulnerability</li> <li>${severity}\u00a0\u2013 Severity of each vulnerability.</li> <li>${likelihood}\u00a0\u2013 Likelihood of the vulnerability</li> <li>${impact}\u00a0\u2013 Impact of the vulnerability</li> <li>${cvssScore}\u00a0\u2013 CVSS score of the vulnerability (Since v1.2)</li> <li>${cvssString}\u00a0\u2013 CVSS vector of the vulnerability (Since v1.2)</li> <li>${count}\u00a0\u2013 Row Count of the vulnerability</li> <li>${tracking}\u00a0\u2013 Tracking number of the vulnerability</li> <li>${vid}\u00a0\u2013 Vulnerability internal database id</li> <li>${openedAt} - The date the vulnerability began tracking (Since 1.3)</li> <li>${closedAt} - The date the vulnerability was closed (no longer tracked) (Since 1.3)</li> <li>${remediationStatus} - Displays only \"Open\" or \"Closed\" (Since 1.3)</li> <li>${cfXXXXXX}\u00a0\u2013 Custom Fields are ones you specify in the admin interface. These are all prefixed with \u201ccf\u201d</li> <li>${color \u00a0key=value,key=value}\u00a0\u2013 The color of the text is based on key-value pairs.\u00a0See below for how to set up colors.</li> <li>${cells key=value,key=value}\u00a0\u2013 The color of the table cell is based on key-value pairs.\u00a0\u00a0See below for how to set up colors.</li> <li>${loop}\u00a0\u2013 This variable tells the report generator which row will be repeated.</li> <li>${loop-*}\u00a0\u2013 This allows multiple rows to be repeated. Example ${loop-1} will repeat the row but the one below it.</li> <li>${details}\u00a0\u2013 This will insert screenshots and exploit steps for each vulnerability.</li> <li>${noIssuesText} - This is the default text displayed in the section if no vulnerabilities are reported. (Since 1.3.28)</li> </ul>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#example-table-summary-table","title":"Example Table Summary Table","text":"${vulnTable} ${color Critical=C00000,High=FFC000} ID Finding Name Impact Severity ${loop} ${count}. ${vulnName} ${impact} ${severity}","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#example-table-detail-table","title":"Example Table Detail Table","text":"${vulnTable} ${cells Critical=8064a2,High=c0504d,Medium=e68e00, Low=33D7FF,Recommended=081417,Informational=657376} ${loop-5} ## 1\u00a0 ${vulnName} ${severity} CVSS: ${cvssString} ${cvssScore} Category: ${category} Description:${desc} Recommendation:${rec} ${details} <p>**Why is the heading yellow?!?! Check here</p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#vulnerability-block-variables","title":"VULNERABILITY BLOCK VARIABLES:","text":"<p>For when you do not want to use tables to display your vulnerability information. You can use the following variables for inserting vulnerability information outside of a table</p> <ul> <li>${fiBegin} / ${fiEnd}\u00a0\u2013 Block to repeat against all findings.</li> <li>${fiBegin Section_Name} / ${fiEnd Section_Name}\u00a0\u2013 Block to repeat a section of findings. See  Reporting Sections (Paid Only Feature)</li> <li>${vulnName}\u00a0\u2013 The Vulnerability name</li> <li>${rec}\u00a0\u2013\u00a0Vulnerability Recommendation</li> <li>${desc}\u00a0\u2013\u00a0Vulnerability Description</li> <li>${category}\u00a0\u2013 Category of the vulnerability</li> <li>${severity}\u00a0\u2013 Severity of each vulnerability.</li> <li>${likelihood}\u00a0\u2013 Likelihood of the vulnerability</li> <li>${impact}\u00a0\u2013 Impact of the vulnerability</li> <li>${cvssScore}\u00a0\u2013 CVSS score of the vulnerability (Since 1.2)</li> <li>${cvssString}\u00a0\u2013 CVSS vector of the vulnerability (Since 1.2)</li> <li>${count}\u00a0\u2013 Row Count of the vulnerability</li> <li>${tracking}\u00a0\u2013 Tracking number of the vulnerability</li> <li>${vid}\u00a0\u2013 Vulnerability internal database id</li> <li>${openedAt} - The date the vulnerability began tracking (Since 1.3)</li> <li>${closedAt} - The date the vulnerability was closed (no longer tracked) (Since 1.3)</li> <li>${remediationStatus} - Displays only \"Open\" or \"Closed\" (Since 1.3)</li> <li>${cfXXXXXX}\u00a0\u2013 Custom Fields are ones you specify in the admin interface. These are all prefixed with \u201ccf\u201d</li> <li>${details}\u00a0\u2013 This will insert screenshots and exploit steps for each vulnerability.</li> <li>${color \u00a0key=value,key=value}\u00a0\u2013 The color of the text is based on key-value pairs.\u00a0See below for how to set up colors.</li> <li>${fill key=value,key=value}\u00a0\u2013 The color of the background elements is based on key-value pairs.\u00a0\u00a0See below for how to set up colors.</li> <li>${noIssuesText} - This is the default text displayed in the section if no vulnerabilities are reported. (Since 1.3.28) </li> </ul>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#example-block-findings","title":"Example Block Findings","text":"<p>**Why is the heading yellow?!?! Check here</p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#reporting-sections-enterprisepaid-feature","title":"Reporting Sections (Enterprise/Paid Feature)","text":"<p>You can put findings into different sections of your report for paid versions and certain sponsored tiers of Faction. You may want to use sections if you are doing different types of pen tests in one report and need to keep these sections separated. For example, you can segregate findings into  Application Security and Network Security Sections. </p> <p>To use sections you need to create the section names in the Faction Report Designer: </p> <p>Once the sections are created in the UI, you can add them to the report in two ways.  1. Vulnerability Block Variables: <code>${fiBegin Your_Section_Name}</code>/<code>${fiEnd Your_Section_Name} 2. Vulnerability Table Variables:</code>${vulnTable Your_Section_Name}`</p> <p>Below is an example of how the template variables work:</p> <p></p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#css-formatting","title":"CSS FORMATTING:","text":"<p>All of the text generated from Faction is HTML. You can control how it is rendered in the DOCX format using the CSS editor in the Report Designer. You will need to set the CSS to match your report templates. Things like font and size will need to match. Images will need to be forced to resize to the correct dimensions to fit in your reports.</p> <p></p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Security%20Report%20Templates/#setting-severity-colors","title":"SETTING SEVERITY COLORS:","text":"<p>When building reports you most likely will set the text or cell to the color that matches the severity of the finding. To achieve this in FACTION you need to set a default color in the docx template that matches the severity category (i.e. Overall, Likelihood, and Impact). These default colors are in the table below:</p> Category Color Hex Overall Severity #FAC701 Likelihood #FAC702 Impact #FAC703 <p>For Example, a table in MS Word below has pre-filled the color codes for each severity name and category.</p> <p></p> <p>Right-click the overall severity variable,\u00a0${severity}; you can see the default hex code for this color is #FAC701. Likelihood would be set to #FAC02, and Impact would be set to #FAC703.</p> <p></p> <p>Setting the background color for cells works in much the same way. Notice we use the ${cells} variable instead.</p> <p></p> <p>Right-click on the cell and set the color you may only want to use the Overall severity option but you can have multiple cells with each category if you wish.</p> <p></p> <p>Below is an example of the generated report table with colors replaced.</p> <p></p>","tags":["Reporting","Customize","Variables"]},{"location":"Custom%20Variables/","title":"Custom Variables","text":"<p>You can use custom variables to add additional features to Faction. These variables can be used to add additional information to vulnerabilities like a CVSS score or to populate additional data in reports like \"product owner\", \"cost center\", etc. </p> <p>Note</p> <p>Faction 1.2 and above has CVSS Scoring built in. You can still use this information as a guide to add your own custom variables. </p>","tags":["Reporting","Customize"]},{"location":"Custom%20Variables/#adding-a-cvss-score","title":"Adding a CVSS Score","text":"<p>As of Faction version 1.1.25.1, Faction does not have CVSS scores built in but you can add your own easily.  </p>","tags":["Reporting","Customize"]},{"location":"Custom%20Variables/#step-1-add-custom-fields-in-admin","title":"Step 1 : Add Custom Fields in Admin","text":"<p>Navigate to Admin -&gt; Settings and add two Custom Fields: CVSS3.1 and CVSS String with variable names <code>cvss3</code> and <code>cvssstring</code>.</p> <p></p> <p>The Name will be what is displayed in the UI and the variable name will be used in the report template. We want to apply this to Vulnerability so that it will be available when we add vulnerabilities to the assessment.</p>","tags":["Reporting","Customize"]},{"location":"Custom%20Variables/#step-2-update-the-report-template","title":"Step 2: Update the Report Template","text":"<p>We need to change our report template to include the new variables in the vulnerability section of the template. In this case, we already have a table with vulnerability information and we need to add another row to this table with the new variables. The default template can be downloaded here.</p> <p></p> <p>Notice all custom field variables are pre-populated with <code>cf</code>.  If we defined a custom field with a variable of <code>cvss3</code> then the reporting variable will be <code>${cfcvss3}</code>. </p> <p>Note: We needed to change the <code>loop</code> variable to inform the Faction reporting engine that the number of rows in the table has changed from 4 to 5. If you are not changing the number of rows then this update is not necessary. </p>","tags":["Reporting","Customize"]},{"location":"Custom%20Variables/#step-3-add-a-new-vulnerability-to-the-assessment","title":"Step 3: Add a New Vulnerability to the Assessment","text":"<p>When you add a vulnerability to the assessment the custom fields will be available in the form as shown below:</p> <p></p> <p>Entering the CVSS score will be automatically saved and a report can now be generated with these new Fields. </p> <p></p>","tags":["Reporting","Customize"]},{"location":"Faction%20App%20Store%20Extensions/","title":"Faction App Store Extensions","text":"<p>Below is a List of Approved Faction Extensions. These all work with Faction 1.2+</p> Name Developer URL Faction Jira Integration Faction Security https://github.com/factionsecurity/Faction-Jira-Extension Faction Vulnerability Bar Chart Faction Security https://github.com/factionsecurity/Faction-Vulnerability-Bar-Chart","tags":["App Store","API"]},{"location":"Faction%20App%20Store%20Extensions/#submit-an-extension","title":"Submit an Extension","text":"<p>Send an email to develop [ at ] factionsecurity [dot] com with a link to your github and a brief explanation of what it does. </p>","tags":["App Store","API"]},{"location":"Faction%20Severity%20Rating%20and%20CVSS%20Scoring/","title":"Faction Severity Rating and CVSS Scoring","text":"<p>Native: </p> <p>CVSS: </p> <p>FACTION's severity rankings are easily customizable to how you perform assessments. You can even create different severity options for the type of assessment. </p> <p>FACTION has 3 options to choose:</p> <ol> <li>Native Severity - This is simply High, Medium, Low, etc type rankings. Faction let you set up to 10 levels and can rename them to anything that works for your process. </li> <li>CVSS 3.1 - This option enables First.org CVSS 3.1 Severity Scoring and was introduced in FACTION 1.2</li> <li>CVSS 4.0 = This option enables First.org CVSS 4.0 Scoring and was introduced in FACTION 1.2</li> </ol>","tags":["CVSS","Vulnerability","Core Features"]},{"location":"Faction%20Severity%20Rating%20and%20CVSS%20Scoring/#native-severity-ranking","title":"Native Severity Ranking","text":"<p> By default, assessments are enabled with Native Severity Ranking. You can choose up to 10 levels. The most common severity names are pre-populated when you install FACTION. You are free to change these names to anything you wish. If your process uses a different nomenclature then you can change <code>Critical</code> to  <code>P1</code> and <code>High</code> to <code>P2</code> for example. </p> <p>You can find this setting in Templates -&gt; Default Vulnerabilities.</p> <p>When Native Severity Ranking is enabled, the following options are available when adding a new vulnerability: </p>","tags":["CVSS","Vulnerability","Core Features"]},{"location":"Faction%20Severity%20Rating%20and%20CVSS%20Scoring/#changing-the-severity-scoring-system","title":"Changing the Severity Scoring System","text":"<p>The severity scoring system is set for each assessment type. You can change this or create new assessment types by navigating to Admin -&gt; Settings:</p> <p></p> <p>Notice above that each assessment has a different scoring system. To change the assessment scoring system then simply click the <code>edit</code> button an select the scoring system from the drop-down.</p> <p></p>","tags":["CVSS","Vulnerability","Core Features"]},{"location":"Faction%20Severity%20Rating%20and%20CVSS%20Scoring/#cvss-31-and-40-severity-ranking","title":"CVSS 3.1 and 4.0 Severity Ranking","text":"<p>When changing the scoring system to CVSS 3.1 or 4.0, it changes the vulnerability UI and adds CVSS Calculators to the page. </p> <p></p> <p>Clicking on the calculator button next to the CVSS Vector will open a dialog that will build the CVSS vector for you and update the score.  </p>","tags":["CVSS","Vulnerability","Core Features"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/","title":"How to Use BurpSuite with Faction","text":"<p>Faction has a tight integration with BurpSuite and you can now find our extension in the BApp Store. Here are a few things you can do with the Faction Burp Integration. 1. See your assessment and retest queues. 2. Instant access to your assessment scope and other details. 3. View all findings you and your co-pentesters are reporting. 4. Replay payloads from other pentesters. 5. Add issues in Faction directly from BurpSuite. </p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#install-the-burp-faction-integration","title":"Install the Burp Faction Integration","text":"<p>You can install the Faction Integration directly from the BApp store.  1. Open Burp then Click Extensions-&gt;BApp Store 3. Search for Faction 4. Click Install</p> <p></p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#set-up-faction","title":"Set Up Faction","text":"<p>In BurpSuite navigate to the Faction tab after you have installed the Faction Integration. From here you need to enter the URL and API key for your user. </p> <p>The URL will be your domain plus <code>api</code>. Ex <code>https://faction-test.factionsecurity.com/api</code></p> <p></p> <p>You can retrieve your API Key in Faction by accessing your profile in the upper right corner of the Faction Web Interface.  </p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#access-your-assessment-queue","title":"Access Your Assessment Queue","text":"<p>Now that Faction is configured you should be able to see you current assessment queue as shown below:</p> <p></p> <p>Clicking on an assessment will show you the scope, any vulnerabilities that have been reported, and notes that your team has shared with you. </p> <p></p> <p>If you select one of the vulnerabilities you can see its full details including screenshots.</p> <p></p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#enter-findings-into-faction-from-burp","title":"Enter Findings into Faction From Burp","text":"<p>Lets say you find an XSS attack and have verified it with BurpSuite. You can add the finding to Faction without ever leaving Burp. Just select the request or response that you want to enter into the report and select \"Add New Finding\" as shown below:</p> <p></p> <p>Now you will be presented with the vulnerability findings dialog. Here you can search for an existing vulnerability template to auto populate the details and recommendations. </p> <p>Next ensure its being sent to the right assessment. The option will default to the last assessment you selected in the previous section on Access your Assessment Queue</p> <p>Next you have several options. </p> <ul> <li>Select the severity or leave the default</li> <li>Check or uncheck to include the request and/or response. When checked it will include these options in code blocks in the final report.</li> <li>\"Snip cookies\" when checked will remove all cookies from being added to the report and replace them with <code>[...snip...]</code></li> <li>\"Extract Selection\" when checked will only add the portion of the code you selected in Burp to the report. This is most useful trying to only show the reflected script in the response instead of the full response. </li> <li>Exploit Steps can be included and supports MarkDown Syntax. Note Screenshots are available though the Burp Extension currently. For this you still need to add them to the Web UI. </li> </ul> <p></p> <p>Now you can click Save to add it to Faction. All this allows issues to be added seamlessly without breaking your flow. The final result will look something like this.</p> <p></p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#replay-findings","title":"Replay Findings","text":"<p>The Faction Burp Integration has the ability to replay findings if you included the request in the details. Notice the hyperlink above the request when you select a vulnerability in the Faction BurpSuite Integration. </p> <p></p> <p>If you click the hyperlink it will add it to your Burp Repeater. This allows you to replay your own findings and findings from your co-pentesters. The same feature is available for retests!</p> <p></p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#add-scan-findings","title":"Add Scan Findings","text":"<p>Anything found in the BurpSuite Scanner can be added directly into Faction using the BurpSuite Integration as well. Just select the issues you want to add and then choose \"Send Issues to Faction\"</p> <p></p> <p>Below shows that all issues were combined into two distinct issues.</p> <p></p> <p>Notice that if you select more than one of the same issue that it will aggregate the URLs into one finding:</p> <p></p>","tags":["burpsuite","integrations","api"]},{"location":"How%20to%20Use%20BurpSuite%20with%20Faction/#wrapping-up","title":"Wrapping Up","text":"<p>All of these features have been implemented to make adding issues to pen-testing reports easy and to not break your flow. Nothing worse that being in the zone and then have stop to mess with report formatting or ensuring you capture all the right data in your notes to use later. With Faction you can just add the issues as you find them and move on with your pentest. </p>","tags":["burpsuite","integrations","api"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/","title":"Importing Your Vulnerability Templates Via the API","text":"<p>You may have developed your own vulnerability templates over the years, or you may prefer editing them in another editor such as Obsidian or Sublime, rather than using the web interface. Regardless of your approach, Faction enables you to upload your templates in CSV and JSON formats via the API. Additionally, reports can be generated in markdown, HTML, or a combination of both.</p> <p>The api docs can be found on your instance by navigating to  https: //YourHost/api-docs: </p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#generating-an-api-key","title":"Generating an API Key","text":"<p>You must have the <code>API Key</code> permission on your user to use the API. It it not set by default.  </p> <p>After enabling the setting, you can access your API Key by navigating to your profile, located in the upper right corner of the Faction interface. Simply clicking anywhere inside the API key box will reveal the key to you. </p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#csv-file-structure","title":"CSV File Structure","text":"Id* Name Category Id* Category Name* Description Recommendation Severity Id Impact Id Likelihood Id active <p>If the ID field is empty, a new vulnerability will be created. If the ID field is populated, it will overwrite the vulnerability with the same ID.</p> <p>If the Category ID is missing, the categoryName field is required. If a category with the same name exists, the existing category will be used.</p> <p>If the categoryName does not match an existing category, a new category will be created.</p> <p>If the Category ID is populated, the Category Name field is ignored.</p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#example-1-create-a-new-vulnerability-template-in-csv","title":"Example 1: Create a New Vulnerability Template in CSV","text":"<p>Example CSV <pre><code>,\"Cross Site Scripting\",, Unvalidated Input, \"XSS is Bad and stuff..\\n```\\nCode snippet\\n```\", \"Fix it! here is a link [here](https://www.a.b.com)\", 4, 4,4,true\n</code></pre></p> <p>The provided example will create a new template for cross-site scripting. Here are a few key points to note:</p> <ol> <li> <p>The first column (ID column) is left blank. Since there is no ID specified, a new template will be created.</p> </li> <li> <p>The third column (Category ID) is also blank, so Faction will refer to the fourth column (Category Name). If <code>Unvalidated Input</code> is not already a category in Faction, it will be created.</p> </li> <li> <p>The Description and Recommendation fields are written in markdown syntax. Ensure that these columns are enclosed in double quotes (<code>\"</code>) and that new lines are properly escaped (<code>\\n</code>).</p> </li> <li> <p>The severity IDs must correspond to the severity levels configured in Faction. You can find these numbers in Admin-&gt;Settings-&gt; Risk Level Settings. The default severity levels are: Critical (5), High (4), Medium (3), Low (2), Recommended (1), Informational (0). Ensure that the severity IDs match these levels accordingly.</p> </li> </ol> <p>Submit through the API <pre><code>curl -X 'POST' \\ \n'http://localhost:8080/api/vulnerabilities/csv/default' \\ \n-H 'accept: application/json' \\ \n-H 'FACTION-API-KEY: 6be51daa-6f6f-42d3-8b04-b924a0045eff' \\ \n-H 'Content-Type: text/plain' \\ \n-d ',\"Cross Site Scripting\",, Unvalidated Input, \"XSS is Bad and stuff..\\n```\\nCode snippet\\n```\", \"Fix it! here is a link [here](https://www.a.b.com)\", 4, 4,4,true'\n</code></pre></p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#example-2-updating-a-vulnerability-template-in-csv","title":"Example 2: Updating a Vulnerability Template in CSV","text":"<p>First, you need to download the current list of vulnerabilities from the API.</p> <p>Get a CSV List of Default Vulnerabilities <pre><code>curl -X 'GET' \\ \n'http://localhost:8080/api/vulnerabilities/csv/default' \\ \n-H 'accept: text/csv' \\ \n-H 'FACTION-API-KEY: 6be51daa-6f6f-42d3-8b04-b924a0045eff'\n</code></pre></p> <p>Example Response: <pre><code>\"2\",\"Generic Vulnerability\",\"2\",\"Uncategorized\",\"\",\"\",\"4\",\"4\",\"4\",\"true\" \"18\",\"Cross Site Scripting\",\"4\",\"Unvalidated Input\",\"&lt;p&gt;XSS is Bad and stuff..&lt;/p&gt; &lt;pre&gt;&lt;code&gt;Code snippet &lt;/code&gt;&lt;/pre&gt; &lt;br /&gt;\",\"&lt;p&gt;Fix it! here is a link &lt;a href=\"\"https://www.a.b.com\"\"&gt;here&lt;/a&gt;&lt;/p&gt; &lt;br /&gt;\",\"4\",\"4\",\"4\",\"true\"\n</code></pre></p> <p>Now to Update a Template Let's update the Cross Site Scripting Template by changing the description to the following. <pre><code>XSS is fun to exploit with this code snippet\\n ```\\nSnipity snip\\n```\n</code></pre></p> <p>The API Request would look like this: <pre><code>curl -X 'POST' \\ \n'http://localhost:8080/api/vulnerabilities/csv/default' \\ \n-H 'accept: application/json' \\ \n-H 'FACTION-API-KEY: 6be51daa-6f6f-42d3-8b04-b924a0045eff' \\ \n-H 'Content-Type: text/plain' \\ \n-d '\"18\",\"Cross Site Scripting\",\"4\",\"Unvalidated Input\",\"XSS is fun to exploit with this code snippet\\n ```\\nSnipity snip\\n```\",\"&lt;p&gt;Fix it! here is a link &lt;a href=\"\"https://www.a.b.com\"\"&gt;here&lt;/a&gt;&lt;/p&gt; &lt;br /&gt;\",\"4\",\"4\",\"4\",\"true\"'\n</code></pre></p> <p>Now if we pull the list again the results look like this: Request <pre><code>curl -X 'GET' \\ \n'http://localhost:8080/api/vulnerabilities/csv/default' \\ \n-H 'accept: text/csv' \\ \n-H 'FACTION-API-KEY: 6be51daa-6f6f-42d3-8b04-b924a0045eff'\n</code></pre></p> <p>Response <pre><code>\"2\",\"Generic Vulnerability\",\"2\",\"Uncategorized\",\"\",\"\",\"4\",\"4\",\"4\",\"true\" \"18\",\"Cross Site Scripting\",\"4\",\"Unvalidated Input\",\"&lt;p&gt;XSS is fun to exploit with this code snippet&lt;/p&gt; &lt;pre&gt;&lt;code&gt;Snipity snip &lt;/code&gt;&lt;/pre&gt; &lt;br /&gt;\",\"&lt;p&gt;Fix it! here is a link &lt;a href=\"\"https://www.a.b.com\"\"&gt;here&lt;/a&gt;&lt;/p&gt; &lt;br /&gt; &lt;br /&gt;\",\"4\",\"4\",\"4\",\"true\"\n</code></pre></p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#json-file-structure","title":"JSON File Structure","text":"<pre><code>  [\n      {\n        \"Id\": 2,\n        \"Name\": \"Generic Vulnerability\",\n        \"CategoryId\": 2,\n        \"CategoryName\": \"Uncategorized\",\n        \"Description\": \"\",\n        \"Recommendation\": \"\",\n        \"SeverityId\": 4,\n        \"LikelihoodId\": 4,\n        \"ImpactId\": 4,\n        \"Active\": true\n      }\n  ]\n</code></pre> <p>If the ID is missing, a new vulnerability will be created. If the ID is populated, it will overwrite the vulnerability with the same ID.</p> <p>If the Category ID is missing, the categoryName is required. If a category with the same name exists, the existing category will be used.</p> <p>If the categoryName does not match an existing category, a new category will be created.</p> <p>If the Category ID is populated, the Category Name field is ignored.</p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#example-1-create-all-new-vulnerability-template-in-json","title":"Example 1: Create All New Vulnerability Template in JSON","text":"<p>Example JSON</p> <pre><code>[\n    {\n        \"Name\": \"Cross Site Scripting\",\n        \"CategoryName\": \"Unvalidated Input\",\n        \"Description\": \"XSS is Bad and stuff..\\n```\\nCode snippet\\n```\",\n        \"Recommendation\": \"Fix it! here is a link [here](https://www.a.b.com)\",\n        \"LikelihoodId\": 4,\n        \"ImpactId\": 4,\n        \"SeverityId\": 4,\n        \"Active\": true\n    }\n]\n</code></pre> <p>The provided example will create a new template for cross-site scripting. Here are a few key points to note:</p> <ol> <li> <p>The ID is missing. Since there isn't an ID to relate it, a new template will be created.</p> </li> <li> <p>The CategoryId is missing, so Faction will need to look at the CategoryName. If <code>Unvalidated Input</code> is not already a category, then Faction will create it.</p> </li> <li> <p>The Description and Recommendation fields are written in markdown syntax.</p> </li> <li> <p>Ensure that the severity IDs match the severity levels you have set in Faction. You can find these numbers in Admin-&gt;Settings-&gt; Risk Level Settings. The defaults are Critical (5), High (4), Medium (3), Low (2), Recommended (1), Informational (0).</p> </li> </ol> <p>The API Request looks like this to add this vulnerability template: <pre><code>curl -X 'POST' \\ \n'http://localhost:8080/api/vulnerabilities/default' \\ \n-H 'accept: application/json' \\ \n-H 'FACTION-API-KEY: a0d2fff7-7462-458c-ba7b-d93d99b7280a' \\ \n-H 'Content-Type: application/json' \\ \n-d '[ \n    { \n        \"Name\": \"Cross Site Scripting\", \n        \"CategoryName\": \"Unvalidated Input\", \n        \"Description\": \"XSS is Bad and stuff..\\n```\\nCode snippet\\n```\",\n        \"Recommendation\": \"Fix it! here is a link [here](https://www.a.b.com)\",\n        \"LikelihoodId\": 4, \n        \"ImpactId\": 4, \n        \"SeverityId\": 4, \n        \"Active\": true \n    } \n]'\n</code></pre></p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#example-2-updating-a-vulnerability-template-in-json","title":"Example 2: Updating a Vulnerability Template in JSON","text":"<p>First, you need to download the current list of vulnerabilities from the API.</p> <p>Get a JSON List of Default Vulnerabilities <pre><code>curl -X 'GET' \\ \n'http://localhost:8080/api/vulnerabilities/default' \\ \n-H 'accept: application/json' \\ \n-H 'FACTION-API-KEY: a0d2fff7-7462-458c-ba7b-d93d99b7280a'\n</code></pre></p> <p>Response: <pre><code>[\n  {\n    \"CategoryId\": 2,\n    \"ImpactId\": 4,\n    \"Active\": true,\n    \"Description\": \"\",\n    \"CategoryName\": \"Uncategorized\",\n    \"LikelihoodId\": 4,\n    \"Id\": 2,\n    \"Recommendation\": \"\",\n    \"SeverityId\": 4,\n    \"Name\": \"Generic Vulnerability\"\n  },\n  {\n    \"CategoryId\": 4,\n    \"ImpactId\": 4,\n    \"Active\": true,\n    \"Description\": \"XSS is Bad and stuff..\\n```\\nCode snippet\\n```\",\n    \"CategoryName\": \"Unvalidated Input\",\n    \"LikelihoodId\": 4,\n    \"Id\": 5,\n    \"Recommendation\": \"Fix it! here is a link [here](https://www.a.b.com)\",\n    \"SeverityId\": 4,\n    \"Name\": \"Cross Site Scripting\"\n  }\n]\n</code></pre></p> <p>Now to Update a Template Let's update the Cross-Site Scripting Template by changing the description to the following. <pre><code>XSS is fun to exploit with this code snippet\\n ```\\nSnipity snip\\n```\n</code></pre></p> <p>The API Request would look like this: <pre><code>curl -X 'POST' \\\n  'http://localhost:8080/api/vulnerabilities/default' \\\n  -H 'accept: application/json' \\\n  -H 'FACTION-API-KEY: a0d2fff7-7462-458c-ba7b-d93d99b7280a' \\\n  -H 'Content-Type: application/json' \\\n  -d '[ {\n    \"CategoryId\": 4,\n    \"ImpactId\": 4,\n    \"Active\": true,\n    \"Description\": \"XSS is fun to exploit with this code snippet\\n ```\\nSnipity snip\\n```\",\n    \"CategoryName\": \"Unvalidated Input\",\n    \"LikelihoodId\": 4,\n    \"Id\": 5,\n    \"Recommendation\": \"Fix it! here is a link [here](https://www.a.b.com)\",\n    \"SeverityId\": 4,\n    \"Name\": \"Cross Site Scripting\"\n  }]'\n</code></pre></p> <p>Now if we pull the list again the results look like this: Request <pre><code>curl -X 'GET' \\ \n'http://localhost:8080/api/vulnerabilities/default' \\ \n-H 'accept: text/csv' \\ \n-H 'FACTION-API-KEY: 6be51daa-6f6f-42d3-8b04-b924a0045eff'\n</code></pre></p> <p>Response <pre><code>[\n  {\n    \"CategoryId\": 2,\n    \"ImpactId\": 4,\n    \"Active\": true,\n    \"Description\": \"\",\n    \"CategoryName\": \"Uncategorized\",\n    \"LikelihoodId\": 4,\n    \"Id\": 2,\n    \"Recommendation\": \"\",\n    \"SeverityId\": 4,\n    \"Name\": \"Generic Vulnerability\"\n  },\n  {\n    \"CategoryId\": 4,\n    \"ImpactId\": 4,\n    \"Active\": true,\n    \"Description\": \"&lt;p&gt;XSS is fun to exploit with this code snippet&lt;/p&gt;\\n&lt;pre&gt;&lt;code&gt;Snipity snip\\n&lt;/code&gt;&lt;/pre&gt;\\n&lt;br /&gt;\",\n    \"CategoryName\": \"Unvalidated Input\",\n    \"LikelihoodId\": 4,\n    \"Id\": 5,\n    \"Recommendation\": \"&lt;p&gt;Fix it! here is a link &lt;a href=\\\"https://www.a.b.com\\\"&gt;here&lt;/a&gt;&lt;/p&gt;\\n&lt;br /&gt;\",\n    \"SeverityId\": 4,\n    \"Name\": \"Cross Site Scripting\"\n  }\n]\n</code></pre></p>","tags":["API","Core Features","Vulnerability"]},{"location":"Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/#using-swagger","title":"Using Swagger","text":"<p>Instead of using CURL as show above you can use the API docs pages to submit directly to your API to test things out. </p> <p>Just navigate to <code>https: //YourHost/api-docs</code> and select any of the API's available. You will need your API Key that can be found in your profile.</p> <p>Below is an example of using swagger to update a Template with JSON. </p>","tags":["API","Core Features","Vulnerability"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/","title":"Integrate Faction into OIDC Solutions","text":"<p>Faction seamlessly integrates with your existing enterprise authentication solutions, ensuring a smooth and secure user experience. Leveraging widely adopted solutions such as LDAP and OIDC, Faction effortlessly integrates into any enterprise environment. Our platform is designed to adapt to your authentication infrastructure, providing a hassle-free implementation process and enhancing the overall efficiency of your organization\u2019s security framework. With Faction, you can trust in a unified and streamlined authentication experience tailored to your enterprise needs.</p> <p>The article will walk through the steps needed to integrate\u00a0Faction\u00a0into\u00a0Google Auth, Auth0, or Ping Identity</p>","tags":["Authentication","Core Features"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/#google-oidc-setup","title":"Google OIDC Setup","text":"<ol> <li>Log into your company\u2019s\u00a0Google API Console.</li> <li>Click on\u00a0Credentials\u00a0from the left navigation.</li> <li>Click\u00a0+ Create Credentials\u00a0from the top navigation.</li> <li>Select\u00a0OAuth Client ID.</li> <li>Select\u00a0Web Application\u00a0as the application type.</li> <li>Name the application something specific like\u00a0Faction OIDC Integration.\u00a0But the name does not matter.</li> <li>Under\u00a0Authorized redirect URLs\u00a0click\u00a0+ ADD URI.</li> <li>Enter the domain of your Faction Instance and append\u00a0/oauth/callback?client_name=OidcClient\u00a0to the path. Example: If you used Faction to host the site your URL would look like this:     https://furry-hyena-1111.factionsecurity.com/oauth/callback?client_name=OidcClient</li> <li>Then Click\u00a0Create.</li> <li>Take Note of the\u00a0Client Id\u00a0and\u00a0Client Secret. This will be used later in the Faction Admin Section.</li> </ol> <p>Your Setup should look like the following: </p>","tags":["Authentication","Core Features"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/#auth0-oauth-setup","title":"Auth0 OAuth Setup","text":"<ol> <li>Log into your\u00a0Auth0 Console.</li> <li>Select\u00a0Applications\u00a0in the left navigation.</li> <li>Click\u00a0+ Create Application</li> <li>Select\u00a0Regular Web Application. </li> <li>Name it something like\u00a0Faction OAuth Integration.</li> <li>Click\u00a0Create.</li> <li>Ignore the Quick Start screen and Click\u00a0Settings.</li> <li>In the\u00a0Allowed Callback URLs, enter the domain of your Faction Instance and append\u00a0/oauth/callback?client_name=OidcClient\u00a0to the path.  Example: If you used\u00a0Faction\u00a0to host the site your URL would look like: https://furry-hyena-1111.factionsecurity.com/oauth/callback?client_name=OidcClient </li> <li>Take Note of the\u00a0Client Id\u00a0and\u00a0Client Secret. This will be used later in the Faction Admin.</li> <li>Scroll down to the bottom and Click\u00a0Advanced\u00a0and then\u00a0Endpoints</li> <li>Take note of the\u00a0OpenId Configuration\u00a0URL     </li> </ol>","tags":["Authentication","Core Features"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/#ping-identity-setup","title":"Ping Identity Setup","text":"<ol> <li>Log into Ping Identity Console</li> <li>Select Applications.</li> <li>Add a New Application.</li> <li>Give the Application a name like Faction.</li> <li>Select OIDC Web App.</li> <li>Click Save.     </li> <li>Open the newly created application and select the Configuration tab:    </li> <li>Click the Edit Button in the upper right corner</li> <li>Scroll down to the Redirect URI Section and enter your Host Name with the path <code>/oauth/*</code>. (Example: <code>https://furry-hyena-1111.factionsecurity.com/oauth/*</code>)</li> <li>Click Enable Redirect Patterns.     </li> <li>Click Save.</li> <li>Scroll up to the top of the configuration.</li> <li>Expend URLs and take note of the the OIDC Discovery Endpoint. This will be used later in the Configure Faction Section. </li> <li>Take Note of the Client Id and the Client Secret. These will be used in the Configure Faction Section</li> <li>Click the Attribute Mappings tab.</li> <li>Add email as an attribute.     </li> <li>Click Save.</li> </ol>","tags":["Authentication","Core Features"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/#configure-faction","title":"Configure Faction","text":"<ol> <li>Log into\u00a0Faction\u00a0as an admin user.</li> <li>Navigate to\u00a0Admin\u00a0-&gt;\u00a0Users.</li> <li>In the\u00a0OAuth2.0 Configuration\u00a0enter the Client Id you noted earlier from either Auth0, Google, or Ping.</li> <li>Enter the\u00a0Client Secret\u00a0you noted earlier.</li> <li>Enter the\u00a0Discovery URL\u00a0as follows:<ol> <li>Google: https://accounts.google.com/.well-known/openid-configuration </li> <li>Auth0:\u00a0Enter the\u00a0Open Id Configuration\u00a0URL you noted in step 11 above.</li> <li>Ping: Enter the OIDC Discovery Endpoint from step 13 above. </li> </ol> </li> <li>Click\u00a0Save </li> </ol>","tags":["Authentication","Core Features"]},{"location":"Integrate%20Faction%20into%20OIDC%20Solutions/#adding-an-oauth-user","title":"Adding an OAuth User","text":"<ol> <li>Under\u00a0Admin -&gt; Users, Click\u00a0Add User.</li> <li>The Username should be part of the user\u2019s email address before the @ symbol. If the email is\u00a0test.user@yourcompany.com\u00a0then the username is test.user</li> <li>\u2b50\ufe0fLeave the Password Field Blank.\u2b50\ufe0f</li> <li>Enter the\u00a0First\u00a0and\u00a0Last\u00a0name.</li> <li>Enter the\u00a0email\u00a0address that is used by the OAuth solution to authenticate the user.</li> <li>Select\u00a0OAuth 2.0\u00a0as the Authentication Method.</li> <li>Click\u00a0Save Changes.</li> </ol> <p>When the new user reaches the Login Screen they can enter just their username without a password and click\u00a0Login. Faction will redirect the user to the configured Authentication Provider and redirect back.</p>","tags":["Authentication","Core Features"]},{"location":"Managed%20FACTION%20Setup/","title":"Managed FACTION Setup","text":"<p>Below are the Minimal Faction Setup Instructions required to get you all set up and ready to start collaborating on assessments in just a few minutes. With a Faction managed account, we host the servers and maintain the updates for you. Your instance will be hosted in a single-tenant environment to ensure your data is secure. With just a few clicks you will be up and running in minutes. </p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#create-your-managed-account","title":"Create Your Managed Account","text":"<p>Every account that gets created will get its own single-tenant instance. To create a new instance go to\u00a0https://portal.factionsecurity.com,\u00a0Create an Account, and Select a tier that meets your team's needs.</p> <p></p> <p>This will begin creating your instance of Faction. Wait until the spinner shows a green checkbox before you attempt to access your site. You can then click the URL in the site list to take you to your new Faction Instance.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#create-an-admin-user","title":"Create an Admin User","text":"<p>The first time you access Faction you will be presented with a page to create your admin account. Here you need to enter basic information about the user and the option to create a team.\u00a0Hacking Team\u00a0is the default.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#adding-default-vulnerability-templates","title":"Adding Default Vulnerability Templates","text":"<p>The Faction Default vulnerability database is what makes generating reports quick and painless for pen-testing teams. You can upload your templates or start with an open-source list from\u00a0https://github.com/factionsecurity/data</p> <p>To add the VulnDB data into Faction just navigate to\u00a0Admin-&gt;\u00a0Default Vulnerabilities\u00a0and click\u00a0Update from VulnDB. This will import all of their vulnerabilities and set default Categories for the vulnerabilities.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#setting-custom-risk-levels-optional","title":"Setting Custom Risk Levels (Optional)","text":"<p>By default, Faction adds\u00a0Critical,\u00a0High,\u00a0Medium,\u00a0Low,\u00a0Recommended, and\u00a0Informational\u00a0risk levels but you have up to 9 that can be set and the defaults can be changed to anything that works for your environment. For instance,\u00a0Critical\u00a0can be changed to\u00a0Priority 1.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#vulnerability-tracking-and-remediation-slas","title":"Vulnerability Tracking and Remediation SLAs","text":"<p>Different Tiers allow enhanced features within Faction. The\u00a0Teams Tier\u00a0and above have verification and vulnerability tracking enabled. In\u00a0Admin Settings\u00a0you can set custom times to alert when the vulnerability needs to be remediated based on its risk setting. For instance, you can set a reminder that a\u00a0Critical\u00a0vulnerability needs to be remediated 30 days after it's reported and set a past due date of 60 days. This will trigger Faction to alert the correct teams that important issues are close to being past due to ensure issues get closed on time and are never forgotten.</p> <p>Any values that are missing a date will not be tracked by Faction.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#assessment-checklists","title":"Assessment Checklists","text":"<p>For some assessments, you will want to add checklists to ensure all critical issues are tested. Below is an example of some potential checks that might need to happen on every assessment to ensure applications are tested consistently.</p> <p></p> <p>Once the above is created it will be available in assessments where the assessor can pass/fail the checklist item and even add notes related to why it failed or why it\u2019s not necessary for the application being tested.</p> <p></p>","tags":["Cloud Hosted","Setup"]},{"location":"Managed%20FACTION%20Setup/#additional-configuration-options","title":"Additional Configuration Options","text":"<p>The higher-level tiers allow you to configure other options like LDAP and OAuth. You can find additional information below on these settings:</p> <ul> <li>Integrate Faction Into OAuth Solutions</li> <li>Customizing Faction for Self Hosting</li> <li>Extending Faction</li> </ul>","tags":["Cloud Hosted","Setup"]},{"location":"Remediation%20Tracking%2C%20Custom%20SLAs%2C%20Retests/","title":"Remediation Tracking, Custom SLAs, Retests","text":"<p>FACTION has remediation tracking built in! When you close out an assessment all the vulnerabilities in that assessment start tracking based on your custom SLAs. With the custom SLAs you can set reminders when a vulnerabilities is approaching a due data and another when the it is past due. </p>","tags":["Remediation","Retests","Core Features"]},{"location":"Remediation%20Tracking%2C%20Custom%20SLAs%2C%20Retests/#setting-custom-slas","title":"Setting Custom SLAs","text":"<p>Navigate to Templates -&gt; Default Vulnerabilities. Here you find a table that lets you set your vulnerability tracking times.  </p> <p>Each vulnerability severity level will have a Warning date and a Past Due date. These are measured in days after the assessment is completed. All empty inputs represent Untracked issues. </p> <p>In the above screenshot, Critical vulnerabilities will have a remediation due date that is 60 days and a warning set at 30 days after the assessment is completed.  High vulnerabilities are expected to be remediated in 120 days and have a warning at 60 days after assessment completion.  Note that all other vulnerabilities are not tracked by FACTION because the inputs are all blank. </p>","tags":["Remediation","Retests","Core Features"]},{"location":"Remediation%20Tracking%2C%20Custom%20SLAs%2C%20Retests/#remediation-dashboards-and-retests","title":"Remediation Dashboards and Retests","text":"<p>You can see the status of all past and approaching due dates in the Remediation Queue.  </p> <p>This dashboard allows assessment teams to easily see all issues that require remediation and the current state of the vulnerability. </p> <p>In the above screenshot, there is one issue that is Past Due and several others that are close to being past due. Clicking on the past due issue lets you easily schedule it for retest as shown below: </p>","tags":["Remediation","Retests","Core Features"]},{"location":"Remediation%20Tracking%2C%20Custom%20SLAs%2C%20Retests/#adding-follow-up-notes","title":"Adding Follow Up Notes","text":"<p>You can add notes to all tracked vulnerabilities. You can add follow-up notes from the development teams, annotate delays in schedules, or other information you might need later to stay on top of the remediation. </p> <p>The Note History stores not only notes but also tracks the passing and failing of retests. </p>","tags":["Remediation","Retests","Core Features"]},{"location":"Self-Hosted%20FACTION%20Setup/","title":"Self Hosted FACTION Setup","text":"<p>If you decide to self-host Faction instead of using the\u00a0Managed Solution\u00a0then you will need to ensure you include the proper Environment variables so that Faction integrates into your environment.</p>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#requirements","title":"Requirements","text":"<ul> <li>Tomcat 9</li> <li>Java 11</li> <li>Mongo 7</li> <li>maven</li> </ul>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#option-1-docker-compose","title":"Option 1:  Docker Compose","text":"<p>Download the code from GitHub and run the following commands <pre><code>git clone git@github.com:factionsecurity/faction.git\ncd faction\nmvn clean compile war:war\ndocker-compose up --build\n</code></pre></p>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#updating-faction","title":"Updating Faction","text":"<p>New releases can be found here. You can either pull a new release of Faction and build it yourself as shown above or If you don't want to perform the Maven install you can download the <code>faction.war</code> file directly and put it into the targets folder. </p>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#option-2-install-tomcat-and-mongo","title":"Option 2: Install Tomcat and Mongo","text":"<p>Check back, instructions will be updated soon</p>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#custom-environment-variables","title":"Custom Environment Variables","text":"<pre><code>## Mongo Database configs \n\nFACTION_MONGO_HOST=127.0.0.1. #requireed \nFACTION_MONGO_DATABASE=faction #required \nFACTION_MONGO_USER=faction_mongo_user #optional \nFACTION_MONGO_PASSWORD=faction_mongo_pass #optional \nFACTION_MONGO_AUTH_DATABASE=admin #optional \n\nFACTION_SECRET_KEY=faction_encryption_key #required \n\nFACTION_REPORT_STORAGE=aws #optional \nFACTION_BUCKET_NAME=your-bucket #optional \nFACTION_TIER=teams #required \nFACTION_USERS=100 #optional \n\nFACTION_SMTP_SERVER=smtp.server.com #optional \nFACTION_SMTP_USER=sysadmin #optional \nFACTION_SMTP_PORT=587 #optional\n</code></pre>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#mongo-database-variables","title":"Mongo Database Variables","text":"<ul> <li>FACTION_MONGO_HOST\u00a0(Required):     This is the hostname or ip address where your mongo database i location</li> <li>FACTION_MONGO_DATABASE\u00a0(Required):     The name of the mongo database. This can be anything you want. On initial loading of the application it will create the database and all collections.</li> <li>FACTION_MONGO_USER\u00a0(O_ptional_):     If you use authentication (and you should) then this user has access to the database.</li> <li>FACTION_MONGO_PASSWORD\u00a0(Optional):     Only required if you use the FACTION_MONGO_USER environment variable.</li> <li>FACTION_MONGO_AUTH_DATABASE\u00a0(Optional):     The default authentication database is\u00a0admin.\u00a0If you want to use another then you can use this variable.</li> </ul>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#other-variables","title":"Other Variables","text":"<ul> <li>FACTION_SECRET_KEY\u00a0(Required):     This is the key used for all symmetric key encryption.</li> <li>FACTION_REPORT_STORAGE\u00a0(Optional):     This variable has two options:\u00a0local\u00a0or\u00a0aws. If you include\u00a0aws\u00a0then you also need to set\u00a0AWS_ACCESS_KEY_ID\u00a0and\u00a0AWS_SECRET_ACCESS_KEY\u00a0and create the an s3 bucket location in AWS.\u00a0You can also use IAM permissions instead of including the AWS Keys.      When using\u00a0local\u00a0\u00a0the default directory location is\u00a0/opt/faction.\u00a0If this variable is not set,\u00a0local\u00a0will be used as default.</li> <li>FACTION_BUCKET_NAME\u00a0(Optional):     S3 Bucket Name to to store Faction files.</li> <li>FACTION_TIER\u00a0(Required):     Only use the value\u00a0team\u00a0here</li> <li>FACTION_USERS\u00a0(Required):     The user limit. you can set this to any value that makes sense for your organization.</li> </ul>","tags":["Self Hosted","Setup"]},{"location":"Self-Hosted%20FACTION%20Setup/#email-variables","title":"Email Variables","text":"<p>These settings (FACTION_SMTP_SERVER, FACTION_SMTP_USER&lt; FACTION_SMTP_PORT) are just used for the initial setup of Faction. They will be overridden when you save or test emails in the admin settings pages. This is useful for doing deployments in Kubernetes or ECS.</p>","tags":["Self Hosted","Setup"]},{"location":"Table%20of%20Contents%20Numbering/","title":"Table of Contents Numbering","text":"<p>Faction's open-source versions will not automatically update the Table of Contents page numbering though the hyperlinks all work as expected.  You can do this manually by clicking the table and selecting Update Field on the generated report.  </p> <p>The enterprise versions of Faction will automatically update the numbering for you as well as provide other additional reporting features like different finding sections (i.e. Application Security Pen Test Findings Section and Network Security Findings Section) and DOCX and PDF export options.  </p> <p>Contact us here to learn more.</p>","tags":["Reporting","Enterprise","Paid Feature","Managed"]},{"location":"Using%20Markdown%20in%20Reports/","title":"Using Markdown in Reports","text":"<p>When exploiting a vulnerability in a penetration test it is important to capture your attack steps quickly and thoroughly so you don't have to spend extra time remembering and re-validating what you did when it's time to report on the finding. Nothing can break your flow more than having to stop what you are doing to format text, fix hyperlinks, or build numbered lists of steps. Markdown is one of the quickest ways to type formatted text and capture these details effortlessly. </p> <p>Pro Tip!</p> <p>The API fully supports Markdown. This makes it easy to develop automated tools that can add issues or other text to Faction with formatted text via the API. </p> <p>Faction supports markdown by default in all editors. Here are some examples of how you can use markdown:</p>","tags":["Markdown","Reporting","Core Features","Burp Suite"]},{"location":"Using%20Markdown%20in%20Reports/#exploit-steps","title":"Exploit Steps","text":"<p>Entering exploit steps is easier with markdown. You can enter the following text and it will automatically show you the formated view on the right.  <pre><code>__Steps to Reproduce__:\n1. Go to the home page.\n2. Click Login.\n3. Enter `&lt;script&gt;alert(123);&lt;/script&gt;` in the username parameter. \n</code></pre></p> <p></p>","tags":["Markdown","Reporting","Core Features","Burp Suite"]},{"location":"Using%20Markdown%20in%20Reports/#faction-burp-suite-extension","title":"Faction Burp Suite Extension","text":"<p>If you find a vulnerability while using the Faction Burp extension, you can add the finding and all details directly through the extension. Below is an example of cross-site scripting: </p> <p>In Burp Suite, select the request and select Add New Finding: </p> <p>A dialog box will open that lets you search for the vulnerability type (in this case Cross Site Scripting) and allow you to enter your details on how to recreate the exploit. </p> <p></p> <p>Now if we navigate back into Faction and view the details we will see the exploit steps displayed in rich text. </p> <p></p>","tags":["Markdown","Reporting","Core Features","Burp Suite"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/","title":"Using the Faction Burp Suite Extension","text":"<p>The Faction BurpSuite Extension makes much of what is available in the Web UI available right inside Burp Suite. With this extension, you can:</p> <ul> <li>Access all assessments and retests assigned to you</li> <li>Access Assessment notes</li> <li>Create and update findings </li> <li>Extract parts of the request and responses to add to the assessment report</li> <li>Add finding details in markdown</li> <li>Replay requests you or other assessors have reported</li> </ul>","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#configure-the-extension","title":"Configure the Extension","text":"<p>You can download the extension here . We also hoping to have it added to the BApp store soon. </p> <p>Once installed in Burp, Navigate to the config tab. You need two things to configure:</p> <ol> <li>Your API key- This can be found in the Faction Web UI, under your profile (top upper right). If you do not have an API key then your administrator needs to give you the API permission.</li> <li>API URL - The API URL is most commonly something like <code>https://myserver.com/api</code>. If you login to something different like <code>http://myserver.com:8080/myfaction</code>, then your API URL will be <code>http://myserver.com:8080/myfaction/api</code></li> </ol> <p>Once configured, It should look something like this: </p>","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#severity-mapping","title":"Severity Mapping","text":"<p>Severity Mapping is used to convert vulnerability severities that Burp Suite Reports to the custom severities you set in Faction. More on setting custom severities can be found here</p> <p>Let's say your process requires that Criticals are called P1s and Highs are called P2s. Burp's Vulnerability Scanner finds a Critical issue that you want to report in Faction. You can now simply right-click the finding and add it to Faction and the extension will map the Critical to P1. </p>","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#viewing-the-queues","title":"Viewing the Queues","text":"<p>When you select Queues you will see both your assessments (left) and retests (right) queue. You can select an item in either table to view the data. This gives you all the information you need to start your assessment or verification without even logging into the Web UI. </p>","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#selecting-an-assessment","title":"Selecting an Assessment","text":"<p>From the Queues page, select your currently working assessment. This will set this assessment as the default assessment for all other dialog boxes, for example when adding a new vulnerability it will be reported in this assessment. </p> <p>Once you select the assessment in the table, click Assessment. Now you will see the scope and shared notes about the assessment. </p> <p></p> <p>This keeps all the common information about the assessment handy, like in-scope URLs, test credentials, and even notes you want to share with other assessors on the same project. </p>","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#enter-a-new-finding","title":"Enter a New Finding","text":"","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#update-an-existing-finding","title":"Update an Existing Finding","text":"","tags":["Burp Suite","API","Penetration Testing"]},{"location":"Using%20the%20Faction%20Burp%20Suite%20Extension/#selecting-a-retest","title":"Selecting a Retest","text":"","tags":["Burp Suite","API","Penetration Testing"]},{"location":"tags/","title":"Tags","text":"","tags":[]},{"location":"tags/#api","title":"API","text":"<ul> <li>Faction App Store Extensions</li> <li>Importing Your Vulnerability Templates Via the API</li> <li>Using the Faction Burp Suite Extension</li> <li>App Store Extension API</li> <li>JIRA App Integration Example</li> <li>REST API</li> </ul>","tags":[]},{"location":"tags/#app-store","title":"App Store","text":"<ul> <li>Faction App Store Extensions</li> <li>App Store Extension API</li> <li>JIRA App Integration Example</li> <li>Faction App Store</li> </ul>","tags":[]},{"location":"tags/#authentication","title":"Authentication","text":"<ul> <li>Integrate Faction into OIDC Solutions</li> </ul>","tags":[]},{"location":"tags/#boilerplate","title":"Boilerplate","text":"<ul> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#burp-suite","title":"Burp Suite","text":"<ul> <li>Using Markdown in Reports</li> <li>Using the Faction Burp Suite Extension</li> </ul>","tags":[]},{"location":"tags/#cvss","title":"CVSS","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> </ul>","tags":[]},{"location":"tags/#cloud-hosted","title":"Cloud Hosted","text":"<ul> <li>Managed FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#core-features","title":"Core Features","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> <li>Importing Your Vulnerability Templates Via the API</li> <li>Integrate Faction into OIDC Solutions</li> <li>Remediation Tracking, Custom SLAs, Retests</li> <li>Using Markdown in Reports</li> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#customize","title":"Customize","text":"<ul> <li>Custom Security Report Templates</li> <li>Custom Variables</li> </ul>","tags":[]},{"location":"tags/#customizing","title":"Customizing","text":"<ul> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#enterprise","title":"Enterprise","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#managed","title":"Managed","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#markdown","title":"Markdown","text":"<ul> <li>Using Markdown in Reports</li> </ul>","tags":[]},{"location":"tags/#paid-feature","title":"Paid Feature","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#penetration-testing","title":"Penetration Testing","text":"<ul> <li>Using the Faction Burp Suite Extension</li> </ul>","tags":[]},{"location":"tags/#remediation","title":"Remediation","text":"<ul> <li>Remediation Tracking, Custom SLAs, Retests</li> </ul>","tags":[]},{"location":"tags/#reporting","title":"Reporting","text":"<ul> <li>Custom Security Report Templates</li> <li>Custom Variables</li> <li>Table of Contents Numbering</li> <li>Using Markdown in Reports</li> <li>How To Generate a Vulnerability Report in Faction</li> </ul>","tags":[]},{"location":"tags/#retests","title":"Retests","text":"<ul> <li>Remediation Tracking, Custom SLAs, Retests</li> </ul>","tags":[]},{"location":"tags/#self-hosted","title":"Self Hosted","text":"<ul> <li>Self Hosted FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#setup","title":"Setup","text":"<ul> <li>Managed FACTION Setup</li> <li>Self Hosted FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#variables","title":"Variables","text":"<ul> <li>Custom Security Report Templates</li> </ul>","tags":[]},{"location":"tags/#vulnerability","title":"Vulnerability","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> <li>Importing Your Vulnerability Templates Via the API</li> </ul>","tags":[]},{"location":"tags/#api_1","title":"api","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]},{"location":"tags/#burpsuite","title":"burpsuite","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]},{"location":"tags/#hello-world","title":"hello world","text":"<ul> <li>Hello World</li> </ul>","tags":[]},{"location":"tags/#integrations","title":"integrations","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]},{"location":"APIS/App%20Store%20Extension%20API/","title":"App Store Extension API","text":"","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#introduction","title":"Introduction","text":"<p>Faction has an API similar to what you might find in BurpSuite Extensions. You can create custom modules in jar files and upload them to the Faction AppStore. Once uploaded, Faction will perform your custom processing when certain events are triggered like finalizing and assessment, creating a report, or failing a retest. </p> <p>You can even extend things like the Application Inventory Search so that it queries an external database to return results before scheduling assessments.</p> <p>You can download an example\u00a0Extension here.</p> <p>Below is a list of the current Hooks:</p>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#faction-extension-apis","title":"Faction Extension APIs","text":"","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#application-inventory-extension","title":"Application Inventory Extension","text":"<p><pre><code>public class MyPlugin extends BaseExtension implements com.faction.extender.ApplicationInventory{\n\n    @Override\n    public InventoryResult[] search(String arg0, String arg1) {\n\n        return null;\n    }\n}\n</code></pre> - Triggers on Assessment Scheduling and will then query external sources instead of the local database. - Can search based on Application ID or Application name. It will return an InventoryResult Object (explained later)</p>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#assessment-manager-extension","title":"Assessment Manager Extension","text":"<p><pre><code>public class MyPlugin extends BaseExtension implements com.faction.extender.AssessmentManager{\n\n    @Override\n    public AssessmentManagerResult assessmentChange(Assessment arg0, List&lt;Vulnerability&gt; arg1, Operation arg2) {\n\n        return null;\n    }\n\n}\n</code></pre> Typical use case scenario: When an assessor finalizes an assessment this module can send all the vulnerabilities to another tracking system like JIRA and return the tracking numbers to Faction.</p> <ul> <li>Triggers on Assessment Create, Update, Delete, Finalized, Peer Review Created, Peer Review Complete, Peer Review Accepted</li> <li>Accepts the Triggered Assessment and List of vulnerabilities associated with the assessment.</li> <li>Returns AssessmentManagerResult, that is the updated Assessment and updated List of vulnerabilities</li> <li>If the return object is null Faction will not update locally</li> </ul>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#update-reports","title":"Update Reports","text":"<p><pre><code>public class VulnerabilityBarChart extends BaseExtension implements com.faction.extender.ReportManager {\n\n    @Override\n    public String reportCreate(Assessment asmt, List&lt;Vulnerability&gt; vulns, String reportText) {\n\n    return reportText;\n\n}\n</code></pre> This method triggers every time a report is created or regenerated. It can be used to for you to add custom variables to reports and update those variables with HTML. An example of this can be found here which demonstrates how to add bar charts to vulnerability reports. </p> <ul> <li>Triggers on report create or regenerate</li> <li>Can update Text in reports</li> <li>Output can be HTML or raw text</li> <li>If returns null then nothing will be changed by this extension</li> </ul>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#vulnerability-manager-extension","title":"Vulnerability\u00a0Manager Extension","text":"<p><pre><code>public class MyPlugin extends BaseExtension extends BaseExtension implements com.faction.extender.VulnerabilityManager{\n\n    @Override\n    public Vulnerability vulnChange(Assessment arg0, Vulnerability arg1, Operation arg2) {\n        // TODO Auto-generated method stub\n        return null;\n    }\n}\n</code></pre> Typical use case scenario: When an assessor creates or updates a vulnerability the module can send\u00a0the\u00a0vulnerability to another tracking system like JIRA and return the tracking\u00a0number to Faction.</p> <ul> <li>Triggers on Assessment Create, Update, Delete</li> <li>Accepts the Triggered Assessment and vulnerability that is being processed.</li> <li>Returns\u00a0the updated vulnerability</li> <li>If the return object is null then Faction will not update locally</li> </ul>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#verificationretest-manager-extension","title":"Verification(Retest) Manager Extension","text":"<pre><code>public class MyPlugin extends BaseExtension extends BaseExtension implements com.faction.extender.VerificationManager{\n\n    @Override\n    public void verificationChange(User arg0, Vulnerability arg1, String arg2, Date arg3, Date arg4, Operation arg5) {\n\n    }\n}\n</code></pre> <ul> <li>Triggers on\u00a0Pass, Fail, Cancel, Assigned</li> <li>Accepts the Triggered\u00a0Assigned User, Vulnerability Assigned, Start and end dates for the verification.</li> <li>Returns\u00a0the updated vulnerability</li> </ul>","tags":["API","App Store"]},{"location":"APIS/App%20Store%20Extension%20API/#additional-resources","title":"Additional Resources","text":"<ul> <li>Building a JIRA Extension</li> </ul>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/","title":"JIRA App Integration Example","text":"<p>Faction can extend its functionality on the server side. If you are familiar with writing BurpSuite extensions then this process should be somewhat familiar to you. If you are not it\u2019s OK. We will walk through the specifics below.</p> <p>In this example, we will create a JIRA plugin that will create issues for each vulnerability when the assessment is finalized.</p> <p>The source code for this example can be\u00a0downloaded here.</p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#extension-requirements","title":"Extension Requirements","text":"<ol> <li>Create a new Eclipse Maven Java Project.</li> <li>Modify your\u00a0pom.xml\u00a0file to enable the Faction Extender API and ensure your manifest includes Title, Version, Author, and URL as shown below.  <pre><code>&lt;project xmlns=\"http://maven.apache.org/POM/4.0.0\"\n    xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"\n    xsi:schemaLocation=\"http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd\"&gt;\n    &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;\n\n    &lt;groupId&gt;faction-jira-extension&lt;/groupId&gt;\n    &lt;artifactId&gt;faction-jira-extension&lt;/artifactId&gt;\n    &lt;version&gt;1.0&lt;/version&gt;\n    &lt;name&gt;Faction Jira Extension&lt;/name&gt;\n    &lt;dependencies&gt;\n        &lt;dependency&gt;\n            &lt;groupId&gt;com.factionsecurity&lt;/groupId&gt;\n            &lt;artifactId&gt;faction-extender&lt;/artifactId&gt;\n            &lt;version&gt;2.5&lt;/version&gt;\n        &lt;/dependency&gt;\n    &lt;/dependencies&gt;\n    &lt;build&gt;\n        &lt;plugins&gt;\n            &lt;plugin&gt;\n                &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;\n                &lt;configuration&gt;\n                    &lt;descriptorRefs&gt;\n                        &lt;descriptorRef&gt;jar-with-dependencies&lt;/descriptorRef&gt;\n                    &lt;/descriptorRefs&gt;\n                    &lt;archive&gt;\n                        &lt;manifestEntries&gt;\n                            &lt;Title&gt;${project.name}&lt;/Title&gt;\n                            &lt;Version&gt;${project.version}&lt;/Version&gt;\n                            &lt;Author&gt;Josh Summitt&lt;/Author&gt;\n                            &lt;URL&gt;https://www.factionsecurity.com&lt;/URL&gt;\n                        &lt;/manifestEntries&gt;\n                    &lt;/archive&gt;\n                &lt;/configuration&gt;\n            &lt;/plugin&gt;\n        &lt;/plugins&gt;\n    &lt;/build&gt;\n&lt;/project&gt;\n</code></pre></li> <li>Create the following folders and files. They can be empty for now. We will fill this out in the next section below.      The maven-assembly-plugin will ensure your manifest is set up correctly for Faction to be able to import your extension with the proper information.</li> </ol>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#extension-file-and-folder-requirements","title":"Extension File and Folder Requirements","text":"<p>We need to update the extension resources from Step 3 above. Below is a description of the files. </p> <ul> <li><code>resources/META-INF/resouces/config.json</code> : This file is a JSON key-value pair of options you want to be configurable by the end user. These options become input boxes in the Faction App Store UI. </li> <li><code>resources/META-INF/resources/description.md</code> : This is the extension description and help files that will be displayed when the extension is loaded in the Faction App Store UI</li> <li><code>resources/META-INF/resources/logo.png</code>: This is a PNG log that will be displayed as the Apps icon in the Faction App Store UI</li> <li><code>resources/META-INF/services/*</code>: This file is required for Faction to be able to load your extension. </li> </ul>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#configjson","title":"config.json","text":"<p>These are the key value pairs that will display in the Faction App Store UI and allow users to make changes that affect the behavior of the extensions. For a Jira plugin you would want the API, the Jira Host and the Jira Username configured. That would look like the following <pre><code>{\n    \"Jira Host\" : {\n        \"type\": \"text\",\n        \"value\": \"https://yourhost.com\"\n        },\n    \"Jira API Key\" : {\n        \"type\": \"password\",\n        \"value\": \"your api key\"\n        },\n    \"Jira Email\": {\n        \"type\" : \"text\",\n        \"value\": \"your@email.com\"\n    }\n}\n</code></pre></p> <p>Any values you set in your extension will be the \"Default\" values that will display to the end user. They can be blank if you do not what to set a predefined value. </p> <p>The <code>type</code> attribute can only be <code>text</code> or <code>password</code>. <code>password</code> attributes  are not displayed in the UI when the user enters the data and do not get returned to the UI once saved. </p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#descriptionmd","title":"description.md","text":"<p>This is where you describe your extension to end users and support most markdown elements. You should use this to fully describe what the extension does, why the user should install it,  and how the end user should configure it to work correctly. </p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#logopng","title":"logo.png","text":"<p>This will be the logo in a PNG format that will display as an icon for your project. </p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#services","title":"services","text":"<p>The <code>resources/META-INF/services/</code> files have a specific naming convention so that Faction can load your classes. The file must be named one of the following:</p> <ul> <li><code>com.faction.extender.AssessmentManager</code></li> <li><code>com.faction.extender.ApplicationInventory</code></li> <li><code>com.faction.extender.ReportManager</code></li> <li><code>com.faction.extender.VerificationManager</code></li> <li><code>com.faction.extender.VulnerabilityManager</code></li> </ul> <p>The content of each file is the name of your class that instantiates this functionality. In this example, we are only triggering the AssessmentManager therefore the file name would be <code>com.faction.extender.AssessmentManager</code> and the contents of the file would be <code>org.faction.JiraPlugin</code></p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#create-the-jira-plugin-class","title":"Create The Jira Plugin Class","text":"<p>Now that the basic set up is complete we can create our Jira Class that actually does something! </p> <p>Create a Class named\u00a0JiraPlugin\u00a0in\u00a0src/main/java. This class will implement\u00a0\u00a0com.fuse.extender.AssessmentManager\u00a0as shown below. This code will trigger whenever a change happens to an assessment. You can use the\u00a0Operation\u00a0enum to control what happens as different events change the assessment.</p> <pre><code>package org.faction;\n\npublic class JiraPlugin extends BaseExtension implements com.faction.extender.AssessmentManager{\n     @Override\n     public AssessmentManagerResult assessmentChange(Assessment assessment, List&lt;Vulnerability&gt; vulnerabilities, Operation arg2) {\n         AssessmentManagerResult result = new AssessmentManagerResult();\n        return result\n     }\n}\n</code></pre> <p>Note that above it returns\u00a0AssessmentManagerResult.\u00a0This object will update Faction\u2019s database if the values change when this function returns. If you Return\u00a0null\u00a0it will NOT update Faction and only just send/process information.</p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#send-this-issues-to-jira-on-assessment-finalized","title":"Send this Issues to Jira on Assessment Finalized","text":"<p>Now we have a basic functional block of code we need to make it perform the action of sending all vulnerabilities to Jira only when the assessment is finalized. To do this we create an if statement that checks the Operation enum equals Finalized and then sends the issues with our custom function <code>sendVulnerabilityToJira()</code>. We then get the tracking ID from Jira and update Faction so the tracking ID's are in sync. </p> <pre><code>import com.fuse.elements.Assessment;\nimport com.fuse.elements.Vulnerability;\n\npublic class JiraPlugin extends BaseExtension implements com.faction.extender.AssessmentManager{\n\n    @Override\n    public AssessmentManagerResult assessmentChange(Assessment assessment, List&lt;Vulnerability&gt; vulns, Operation opcode) {\n        String project =\"KAN\";  //Default Jira Project Name.\n\n        if(opcode == Operation.Finalize) {\n            //Integration into vulnerability management system\n            for(Vulnerability vuln : vulns) {\n                //this can update vulns and send the updated values back into Faction\n                String issueId = sendVulnerbilityToJira(vuln, project);\n                if(issueId != null) {\n                    vuln.setTracking(issueId); //Update Faction's Tracking ID\n                }\n            }\n        }\n        AssessmentManagerResult result = new AssessmentManagerResult();\n        result.setAssessment(assessment);\n        result.setVulnerabilities(vulns);\n        return result; //Send back the updated results\n    }\n}\n</code></pre> <p>You can see the full implementation here</p>","tags":["API","App Store"]},{"location":"APIS/JIRA%20App%20Integration%20Example/#install-it-in-your-faction","title":"Install It In Your Faction","text":"<p>Build the jar file by running: <pre><code>mvn clean compile assembly:single\n</code></pre></p> <p>This will create a jar file named\u00a0something like JiraPlugin-0.0.1-SNAPSHOT-jar-with-dependencies.jar\u00a0in your ./target folder.\u00a0</p> <p>Upload it to Admin-&gt;App Store-&gt;Install Extension. It should display like this: </p> <p>If all looks good, click install. </p> <p>It will be installed initially as disabled. You can configure it before you enable it by clicking on the extension in the list: </p> <p>Once you configure the settings you can enable it. </p> <p>Now when an assessment is finalized it will add All the findings to JIRA as shown in the following screenshot:</p> <p></p>","tags":["API","App Store"]},{"location":"APIS/REST%20API/","title":"REST API","text":"<p>The Rest API enables you to integrate FACTION into your unique environment. With the API you can:</p> <ol> <li>Add vulnerabilities from other tools</li> <li>Upload your custom vulnerability templates</li> <li>Schedule Assessments and Retests</li> <li>Track remediation </li> <li>Manage Users</li> <li>and much more. </li> </ol> <p>The easiest way to access the REST API for your faction instance is to click on your profile in the top right corner. Here you will find a link to the Swagger API docs and access to your API Key</p> <p></p> <p>If you select \"Click here for API docs\" it will redirect you to the Swagger docs for your Faction Instance. You can use this page to make requests to the API directly in the browser. </p> <p></p>","tags":["API"]},{"location":"blog/2024/03/25/faction-app-store/","title":"Faction App Store","text":"<p>\u2728 We are excited to release the first iteration of the Faction App Store! \u2728</p> <p>The App Store is where developers can build custom integrations with Faction. These can be anything from sending vulnerabilities to external bug trackers to adding custom graphics to your automated pentest reports! </p> <p>We want to make this process really easy and took inspiration from Burp Suite on the design. If you have ever made an extension for Burp then you should be able to get up and running pretty quickly. </p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#what-can-be-extended","title":"What Can Be Extended?","text":"<p>With this initial release, you can extend Faction by:</p> <ul> <li>Including your own application inventory database to the application search features and populate results in Faction like the Application ID, Distribution Lists, and Application Name. </li> <li>Triggers when an assessment state changes (created, updated, or finalized). You can use this to send emails to a distribution list that an assessment has been scheduled for certain dates. When the assessment is finalized you can choose to send only the vulnerabilities of a certain criticality to an external tracking system as well as send to different tracking systems depending on the type of assessment. </li> <li>Triggers when a vulnerability state is changed. When a tracked vulnerability is retested and pass/fail, you can create a custom workflow and alert key stakeholders that the issue succeeded or failed. </li> <li>Update reports when they are generated. You can use this to add custom variables to your reporting templates and replace the contents with data from an external system or add custom charts and graphics to give your reports a more polished look. </li> </ul> <p>The full documentation on the API can be found here</p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#custom-settings","title":"Custom Settings","text":"<p>Extensions are built so that you can add your own configuration options that can be stored in the Faction Database. Things like a user-editable hostname or API key can be configured in your extension. Based on how you set up your configuration you can make data like passwords and API keys hidden in the UI and encrypted at rest. </p> <p></p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#extension-chain","title":"Extension Chain","text":"<p>Extensions can be chained in any order. Once you add apps and enable them in Faction, the UI allows you to drag the extension to anywhere in the list. This allows you to create one extension that processes data and returns a result that can be processed by the next extension. </p> Before Order Change After Order Change <p>You can use this to create one extension that returns a JIRA Tracking number for all vulnerabilities in the finalized assessment, they take those numbers and process them into another system and on and on down the chain. </p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#example-extensions","title":"Example Extensions","text":"<p>You can review the source code for our initial apps here. This list will grow over time but currently, there are 2 (JIRA Integration, Vulnerability Bar Charts). </p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#submit-your-own","title":"Submit Your Own","text":"<p>We can't think of everything! We encourage developers to submit their own extensions and we will add them to our list of Approved Extensions. Send an email to develop [ at ] factionsecurity [dot] com with a link to your GitHub and a brief explanation of what it does. </p>","tags":["App Store"]},{"location":"blog/2024/03/25/faction-app-store/#conclusion","title":"Conclusion","text":"<p>We hope you enjoy the new  App Store and other new features that are part of this 1.2 Release. Faction is open-source and free to use. Please leave us feedback in either our GitHub Discussion Boards or by submitting Issues. </p> <p>If you want to help support the project and ensure its longevity then consider being a sponsor... It's good karma!  \u2764\ufe0f</p> <p>Sponsor Options</p> <ul> <li>GitHub Sponsor</li> <li>Patreon</li> <li>Open Collective</li> </ul>","tags":["App Store"]},{"location":"blog/2024/03/16/faction-boilerplates/","title":"Faction Boilerplates","text":"<p>If you have been doing penetration testing for any length of time you probably have a personal database of vulnerability descriptions, recommendations as well as other text snippets you will inject into various places of your reports. What if, Instead of keeping these in separate files on various computers, they were all included in your reporting software?!@! \ud83e\udd2f</p> <p>Faction IS your database for global boilerplate, default vulnerability templates, personal flare, and just about anything else you can imagine (well...sorta \ud83e\udd14). Let's walk through how this is done.</p>","tags":["Core Features","Boilerplate","Customizing"]},{"location":"blog/2024/03/16/faction-boilerplates/#vulnerability-templates","title":"Vulnerability Templates","text":"<p>Let's start with the obvious.... Faction includes over 75 default vulnerability templates when you start. These vulnerability templates include both descriptions and recommendations and are fully customizable by you. You can start with our templates or upload your own as described here.</p> <p>When writing your report, type the name of the vulnerability and it will auto-populate in the UI as shown below: </p> <p>Once selected your report will automatically include the severity of the finding, the description, and the recommendation! \ud83d\udca5 Something that would have taken you 30 min to an hour is complete in just a few seconds. </p> <p>These are fully editable in the Default Vulnerabilities section. You can add new ones, update the pre-packaged ones, or delete them all and upload all your own with the Faction API.</p>","tags":["Core Features","Boilerplate","Customizing"]},{"location":"blog/2024/03/16/faction-boilerplates/#assessment-templates","title":"Assessment Templates","text":"<p>Faction has the option of creating global and personal boilerplates that you can easily add to your reports. Global templates are shared with everyone while personal templates are only available to you. </p>","tags":["Core Features","Boilerplate","Customizing"]},{"location":"blog/2024/03/16/faction-boilerplates/#global-assessment-templates","title":"Global Assessment Templates","text":"<p>In Faction, Navigate to Templates -&gt; Assessment Templates. Here you have the option to create text that will be available to all assessors in the platform. This is useful for creating things like Different High-Level Summaries for different report types or adding common risk summaries. </p> <p></p> <p>Notice you can include most faction variables in your templates and they will be auto-populated in the generated report. </p> <p>As the security assessor, you can easily add these to different sections of your report. Below is a screen-share of using Global Templates in your reports. </p>","tags":["Core Features","Boilerplate","Customizing"]},{"location":"blog/2024/03/16/faction-boilerplates/#user-assessment-templates","title":"User Assessment Templates","text":"<p>User Assessment Templates work the same as the Global Assessment Templates but are specific to your user account. This can allow you to add your own flare to a report that you might not want to share with the rest of the team. </p> <p>To add a User Template just start typing into any of Faction's text editors and then click the Save button in the Template section. Note that User Templates have a different icon beside them in the Template List. </p> <p>Below is a walk though of how you would add User templates to save and later recall user-defined boilerplate text.  </p>","tags":["Core Features","Boilerplate","Customizing"]},{"location":"blog/2024/03/15/hello-world/","title":"Hello World","text":"<p>Hey! Just starting the FACTION blog. Stay tuned here for new updates, tips, and tricks on getting the most out of FACTION. \ud83c\udf89</p> <p>FACTION 1.2 will be released this month (March'24) with loads of new features. The most notable features are the inclusion of the Faction App Store which will make it simple for developers to write extensions and integrations. </p> <p></p>","tags":["hello world"]},{"location":"blog/2024/10/22/how-to-generate-a-vulnerability-report-in-faction/","title":"How To Generate a Vulnerability Report in Faction","text":"","tags":["Reporting"]},{"location":"blog/2024/10/22/how-to-generate-a-vulnerability-report-in-faction/#below-is-video-showing-how-to-write-a-vulnerability-report-in-under-3-minutes-using-faction","title":"Below is video showing how to write a vulnerability report in under 3 minutes using Faction.","text":"","tags":["Reporting"]},{"location":"blog/archive/2024/","title":"2024","text":""},{"location":"tags/","title":"Tags","text":"","tags":[]},{"location":"tags/#api","title":"API","text":"<ul> <li>Faction App Store Extensions</li> <li>Importing Your Vulnerability Templates Via the API</li> <li>Using the Faction Burp Suite Extension</li> <li>App Store Extension API</li> <li>JIRA App Integration Example</li> <li>REST API</li> </ul>","tags":[]},{"location":"tags/#app-store","title":"App Store","text":"<ul> <li>Faction App Store Extensions</li> <li>App Store Extension API</li> <li>JIRA App Integration Example</li> <li>Faction App Store</li> </ul>","tags":[]},{"location":"tags/#authentication","title":"Authentication","text":"<ul> <li>Integrate Faction into OIDC Solutions</li> </ul>","tags":[]},{"location":"tags/#boilerplate","title":"Boilerplate","text":"<ul> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#burp-suite","title":"Burp Suite","text":"<ul> <li>Using Markdown in Reports</li> <li>Using the Faction Burp Suite Extension</li> </ul>","tags":[]},{"location":"tags/#cvss","title":"CVSS","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> </ul>","tags":[]},{"location":"tags/#cloud-hosted","title":"Cloud Hosted","text":"<ul> <li>Managed FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#core-features","title":"Core Features","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> <li>Importing Your Vulnerability Templates Via the API</li> <li>Integrate Faction into OIDC Solutions</li> <li>Remediation Tracking, Custom SLAs, Retests</li> <li>Using Markdown in Reports</li> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#customize","title":"Customize","text":"<ul> <li>Custom Security Report Templates</li> <li>Custom Variables</li> </ul>","tags":[]},{"location":"tags/#customizing","title":"Customizing","text":"<ul> <li>Faction Boilerplates</li> </ul>","tags":[]},{"location":"tags/#enterprise","title":"Enterprise","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#managed","title":"Managed","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#markdown","title":"Markdown","text":"<ul> <li>Using Markdown in Reports</li> </ul>","tags":[]},{"location":"tags/#paid-feature","title":"Paid Feature","text":"<ul> <li>Table of Contents Numbering</li> </ul>","tags":[]},{"location":"tags/#penetration-testing","title":"Penetration Testing","text":"<ul> <li>Using the Faction Burp Suite Extension</li> </ul>","tags":[]},{"location":"tags/#remediation","title":"Remediation","text":"<ul> <li>Remediation Tracking, Custom SLAs, Retests</li> </ul>","tags":[]},{"location":"tags/#reporting","title":"Reporting","text":"<ul> <li>Custom Security Report Templates</li> <li>Custom Variables</li> <li>Table of Contents Numbering</li> <li>Using Markdown in Reports</li> <li>How To Generate a Vulnerability Report in Faction</li> </ul>","tags":[]},{"location":"tags/#retests","title":"Retests","text":"<ul> <li>Remediation Tracking, Custom SLAs, Retests</li> </ul>","tags":[]},{"location":"tags/#self-hosted","title":"Self Hosted","text":"<ul> <li>Self Hosted FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#setup","title":"Setup","text":"<ul> <li>Managed FACTION Setup</li> <li>Self Hosted FACTION Setup</li> </ul>","tags":[]},{"location":"tags/#variables","title":"Variables","text":"<ul> <li>Custom Security Report Templates</li> </ul>","tags":[]},{"location":"tags/#vulnerability","title":"Vulnerability","text":"<ul> <li>Faction Severity Rating and CVSS Scoring</li> <li>Importing Your Vulnerability Templates Via the API</li> </ul>","tags":[]},{"location":"tags/#api_1","title":"api","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]},{"location":"tags/#burpsuite","title":"burpsuite","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]},{"location":"tags/#hello-world","title":"hello world","text":"<ul> <li>Hello World</li> </ul>","tags":[]},{"location":"tags/#integrations","title":"integrations","text":"<ul> <li>How to Use BurpSuite with Faction</li> </ul>","tags":[]}]}
\ No newline at end of file
diff --git a/site/sitemap.xml b/site/sitemap.xml
index acb424a..36bd069 100644
--- a/site/sitemap.xml
+++ b/site/sitemap.xml
@@ -2,132 +2,132 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
     <url>
          <loc>https://docs.factionsecurity.com/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Custom%20Security%20Report%20Templates/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Custom%20Variables/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Faction%20App%20Store%20Extensions/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Faction%20Severity%20Rating%20and%20CVSS%20Scoring/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/How%20to%20Use%20BurpSuite%20with%20Faction/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Importing%20Your%20Vulnerability%20Templates%20Via%20the%20API/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Integrate%20Faction%20into%20OIDC%20Solutions/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Managed%20FACTION%20Setup/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Remediation%20Tracking%2C%20Custom%20SLAs%2C%20Retests/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Self-Hosted%20FACTION%20Setup/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Table%20of%20Contents%20Numbering/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Using%20Markdown%20in%20Reports/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/Using%20the%20Faction%20Burp%20Suite%20Extension/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/tags/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/APIS/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/APIS/App%20Store%20Extension%20API/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/APIS/JIRA%20App%20Integration%20Example/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/APIS/REST%20API/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/blog/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/blog/2024/03/25/faction-app-store/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/blog/2024/03/16/faction-boilerplates/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/blog/2024/03/15/hello-world/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/blog/2024/10/22/how-to-generate-a-vulnerability-report-in-faction/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/blog/archive/2024/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
     <url>
          <loc>https://docs.factionsecurity.com/tags/</loc>
-         <lastmod>2024-10-31</lastmod>
+         <lastmod>2024-11-13</lastmod>
          <changefreq>daily</changefreq>
     </url>
 </urlset>
\ No newline at end of file
diff --git a/site/sitemap.xml.gz b/site/sitemap.xml.gz
index 30036ea95e98c339e8c67b334012c5987704767a..dd49dd2ad23741989ed390f5fda8eb9ca8e0ebba 100644
GIT binary patch
literal 645
zcmV;00($))iwFqS(lloR|8r?{Wo=<_E_iKh0OeP~Zrd;nz4t4E06Qv5(skH|G)0!R
zXoj^N;<Uhyip|(UWzm!9y8Zi7wwGpyU3OA1A1sBTh4)B4QJP&mmuBz;&TF*i!^vno
z9Dq$R(>6aJ-fynN$Kl2NWL7)lfd=es{rRvUsy<8EG|k9sf>Kp}gf5ppE%=9*y-|)w
zpN8|30Y71ZZq`0CgXui1;(3`2Q$O0Nlo*1Cw04?aMk$tZCWG7ISISd~*?c;lz88~;
zn4GdpZ#!^H3uSZIIruftlr}Fjd0^?_$UUBaLbj|uVfk)4PI@a(*HED&o@}73j3V&I
zK;S_+t+pm=uveXp(Jrbg1f9?UkC)E`HWco0fKPyR*4K(678p;I&G@~1NRr@?qGNN!
zWUjGcoP_+k_aOyeYF8yS%bn+qrh<o_aKtQDWl(CDfS*{qAcNXiaB8bfm!Q3d!+%-@
z(na97__2zam?g-aYP0cHciOfIyIXx-h9W~#Q{<YtQC8&;lyS9KZdP}<t$L`gBF4Oi
z5;Cp&m~Wg)AKMBGF@I|p-xt0!t$~Y+VopK=W+$%E(~%`&6WST$#9fFyvLq}88Q<3B
z79!tY?|ru`-6;2%VbiI1f41;PfV|r#-!`AnAVSgfJ!0RoBc?(sk2%uZf|A(b{pFk%
zeFJU5e_O2=`?KcnmfE4ed{%refY=$VFOyC5vECZYV}}<|$nmM1p2^-vsHze^6!x)T
zpM2P3-=a3)qQ9K}3I9wMU<`@|oym>@^<*rkQ(0gm2t^LzVnHC3csjgf2-o&>p{>|O
fe`9L7DVG-d2|AAdd;4w&4>W%T+l+)lLK6T0bre9r

literal 644
zcmV-~0(<=*iwFqw^&)2i|8r?{Wo=<_E_iKh0OeOvZ`v>re($e9NP9F6be*;ds2Bs4
zX>BJ0mG)?oBeCk(nSE*KzwbH8fIaMGPe#i_Y>tcdeRucy?D6fPP`wwhP8vPw4+l}d
z2RbpS)Y+uJ-7MM1{_XT?Tv_D+d*rO$q@N>}pE<AVdf+5NAxbweHsdbI>4)Q;kw=41
z{pnSY9=||4Yo4(($<(jnXqnU`Zm<^#5(EcHWhK525>xOo_ipE335SJAr=w`}o(&^*
zJtUXTcIKAkLT9kI@N1e1sb0tY%+kW)M?C+8Y+gAu#k)}ycUGFNp)?k0vVo#h0>NDZ
zfhS?5*r}kwE?XO+ot32zIvNW!E)EFV7w%<%kAZa7)rvq87)^vu={<jnWABg{OXh&d
z+?kqiqM_H;`4oJqY#CQ1cbeA{a~e9r0kc>YUa4&Yewxa98B|Jx6+5Zg1RXW(|C7R#
z&OOK3k5$OTG(u)YlZ{i|N!=vuarJfXi_EAB1J}&G&>{n`jOA>;Sv@{9>cOfE81otm
zNTujvzOf>CZYs>j{M0VK&s=L-0~HsBoP-$Ep4}OT7nX>PZ)b$l?0w`7NkXHS@k3SY
zAn^Tl>)KuEUfAc<)UA4tXA5@$$lGo5wE6f3;ftp05yzGtFclP8$dRTN6o(G)FXy!2
z8)yUm+iE>Ko;82B)E52XAn05Gp)*)7;!W_e-YJuX4$q_D(KR34@Xm*cvSiK|_N8DS
zemG*^8L7Yqe>wdV{teGTDZ^@GReBMqhY=r*cy4NjhGpO{76?qRm-9;ovrSKDQnP*V
eH>QT0ut_dopyl|#x9?_ffYUee){YZG6951~RX$e$