2021
Tracking & managing your vulnerability write-ups / templates can be difficult – particularly when you might have thousands of write-ups.
To make life easier for you and your pentest teams - AttackForge now supports new vulnerability libraries:
- Main Vulnerability Library - Centralized library for your approved vulnerability write-ups
- Imported Vulnerabilities Library - Centralized library for your write-ups from tools & scanners
- Project Vulnerabilities Library - Project-related write-ups
Main Vulnerabilities
- This is the primary source of your vulnerability write-ups.
- It contains 1300+ pre-loaded vulnerabilities that come with AttackForge. You can also add your own.
- This library is shared, which means any user on a project with permissions to create vulnerabilities for the project, will be able to use any of the vulnerabilities in this library.
Imported Vulnerabilities
- This is where you can find all of the vulnerabilities you have imported from various tools & scanners.
- This library is shared, which means any user on a project with permissions to create vulnerabilities for the project, will be able to use any of the vulnerabilities in this library.
Project Vulnerabilities
- This is where you can access vulnerability write-ups that are designated to specific projects.
- This is useful if you have project-specific or sensitive data which you would like to segregate from the Main and Imported libraries which are shared libraries.
Your pentest teams now have an option to select which library they would like to use when creating a new vulnerability on a project, or when importing vulnerabilities.
Project Vulnerabilities are designated to specific projects.
This is useful if you have project-specific or sensitive data which you would like to segregate from the Main and Imported libraries which are shared libraries.
Vulnerabilities in this library must be assigned/linked to at least one (1) project. They can be assigned to more than one project, if it would be relevant to do so.
Only users with access to the linked project(s) will be able to use these write-ups when creating a new vulnerability, and only on the linked projects.
Users with access to this library will only be able to view & modify vulnerability write-ups for which the user has access to at least one (1) of the linked projects.
By default, Admins will be able to see all write-ups/templates in this library.
You can easily re-assign vulnerabilities between libraries using the page menu options in the Vulnerability Library module.
This can be used to retrospectively transition your imported write-ups into the Imported Vulnerabilities library.
AttackForge now supports ability to create custom fields & forms in the user interface.
This can help to capture information which is relevant to your organization, customers & vulnerabilities.
Custom fields can be accessed in the application, in JSON exports and also via the Self-Service API.
You can create custom fields & forms for the following:
- Project Request
- Project Creation
- Vulnerability Library (write-up)
- Vulnerability (on project)
To set custom fields, you must be an Administrator. You can create & manage your custom fields from the Administration module.
You can set custom fields from the Vulnerabilities and Projects tabs inside Configuration.
AttackForge supports the following custom field types:
- Input field - display a single-line input box within the relevant forms
- Text Area - displays a multi-line input box within the relevant forms. Text area can be resized by the user within the form if additional space is needed.
- Select - displays a drop-down menu with a single item select within the relevant forms.
- Multi-Select - displays a drop-down menu with a multi-item select within the relevant forms. User can select one or more options.
- Datepicker - displays a calendar where the user can select a single date.
For each field, you can set the following options:
- Key - This the name of the field (e.g. database field name).
- Placeholder Value - This is the default value that will be displayed in the forms.
- Label - This is the label that will be displayed in the form for this field, as well as in the tables.
- Required - This is used to determine whether the field is mandatory or optional in the forms.
- Display in Tables - This is used to determine whether the field will be displayed as a new column in the relevant tables within the application.
- Hide Condition - This is used to create a condition to hide the field, until such condition is met.
Hide Conditions can be used to add simple or complex logic into your forms.
For example, you can add logic to only display a field once a user has made a selection in a previous field.
Or you can extend this logic to check for certain values which have been selected.
Hide Conditions fully support JavaScript methods and boolean logic.
This means you can create highly customised forms which are suited to your needs.
You can also choose to display custom fields in relevant tables within the application.
Every custom field is available to use in ReportGen as well as the Self-Service REST and Events APIs.
For detailed guidance on how to create and use custom fields, please check the following support article:
https://support.attackforge.com/attackforge-enterprise/getting-started/custom-fields-and-forms
You can now also disable existing fields for new project requests.
Combining with custom fields, this means you can create a fully custom project request / intake form based on the questions you need from your customers.
Your admins can disable existing fields for new project requests via the Administration module.
- Manage access control for your groups’ projects in one place
You can now easily add & remove projects for a group via Groups module:
- New global dashboard summary boxes
There are new global dashboard summary boxes:
- Projects Overrun
- Projects Ready for Retest
- Open Critical Vulnerabilities
- Open High Vulnerabilities
- Open Medium Vulnerabilities
- Open Low Vulnerabilities
- Added Bulk Update Closed Fixed & Risk Accepted options for vulnerabilities
- Toggle unique vulnerabilities globally
You can now toggle between Unique and All vulnerabilities across entire application.
- Link a group to Portfolio
When configuring your Portfolios and Streams - you can select a group or multiple groups and assign their projects to a Stream.
- Set recipients on review notes
- Notifications on new user registrations & invitations
Admins now receive email notifications every time a new user is registered or created in the application.
- Project Coordinators can now filter schedule by users
Project coordinators can now filter the schedule per user in the Schedule module.
- Increased file upload limit & improved experience for low bandwidth uploads
The file upload limit has been increased to allow for larger files to be uploaded.
Changes have also been made to allow for users with low bandwidth internet connections to upload large files without timeout.
- Project percentage completion across all projects
- Tables filter now shows at top
Column filters within tables has been moved to the top row, to improve UX when filtering
- Tables now support horizontal scroll
Various tables in the application now support horizontal scrolling. This provides better experience viewing & filtering data in tables.
- Project request status page update
When viewing a project request, the latest status has been moved to the top of the page along with any supporting information.
In this release, we have added new tags to ReportGen – providing even more datapoints you can access in your custom reports.
The following tags have been added:
- {projectDuration} – project duration in days i.e. difference between start & end dates
- This tag as available at top-level
- {#assets_equally_affected_full_details} – contains all details for affected assets when using RemoveDuplicatePOCs option in your template.
- This tag is available in in the following sections:
- {#retestingHistory}
- {#vulnerabilities}
- {#criticalVulnerabilities}
- {#highVulnerabilities}
- {#mediumVulnerabilities}
- {#lowVulnerabilities}
- {#infoVulnerabilities}
- {#completedTestcases}
- {#inProgressTestcases}
- {#notTestedTestcases}
- {#notApplicableTestcases}
- {#passedTestcases}
- {#failedTestcases}
- {#remediatedTestcases}
- {#abuseCases}
- {#assetVulnerabilityMapping}
We have also launched a new tutorial video which covers the basics on how to set up a new template, create tables, insert images, access custom fields, and more.
You can access the tutorial video from here: https://support.attackforge.com/attackforge-enterprise/modules/reporting#available-tags-for-individual-reports
From this release, users with Upload permissions to a project can now also:
- Create notes on a project
- This can be used to capture test credentials and other information directly as a note
- Users will only be able to view & modify their own notes
Also users with Edit permissions to a project can now also:
- Update project test window
- Add additional email recipients for automated vulnerability emails (if enabled by Admins / Project Coordinators)
- Add additional email recipients for daily start/stop testing notifications
For an up-to-date list of all user-related permissions, please check Access Control Matrix on our support site: https://support.attackforge.com/attackforge-enterprise/access-control-matrix
In this release, we have improved our Self-Service REST & Events APIs to provide more flexibility and options when interacting with AttackForge.
We have created the following new APIs:
- New REST method: UploadVulnerabilityEvidence
- This can be used to upload evidence files for a vulnerability. It is useful when importing vulnerabilities from external systems for each bug bounty systems.
- For details on how it works, please visit https://support.attackforge.com/attackforge-enterprise/modules/self-service-restful-api/uploadvulnerabilityevidence
- New Events notification: ProjectCreated
- This event is generated when a new project has been created.
- For details on how it works, please visit https://support.attackforge.com/attackforge-enterprise/modules/self-service-events-api/project-create
- New Events notification: ProjectUpdated
- This event is generated when a project has been updated.
- For details on how it works, please visit https://support.attackforge.com/attackforge-enterprise/modules/self-service-events-api/project-updated
We have also updated the following APIs:
- REST GetProjectById, GetProjects & GetProjectsByGroup to include following new fields:
- project_organization_code
- project_vulnerability_code
- project_scoring
- project_team_notifications
- project_admin_notifications
- project_total_assets
- project_critical_open_vulnerabilities
- project_critical_ready_for_retest_vulnerabilities
- project_critical_closed_vulnerabilities
- project_high_open_vulnerabilities
- project_high_ready_for_retest_vulnerabilities
- project_high_closed_vulnerabilities
- project_medium_open_vulnerabilities
- project_medium_ready_for_retest_vulnerabilities
- project_medium_closed_vulnerabilities
- project_low_open_vulnerabilities
- project_low_ready_for_retest_vulnerabilities
- project_low_closed_vulnerabilities
- project_info_open_vulnerabilities
- project_info_ready_for_retest_vulnerabilities
- project_info_closed_vulnerabilities
- project_custom_fields (new custom fields)
- REST GetVulnerabilityById, GetVulnerabilities, GetVulnerabilitiesByAssetName, GetVulnerabilitiesByGroup + EVENTS VulnerabilityCreated, VulnerabilityUpdated to include following new fields:
- vulnerability_custom_fields (new custom fields)
- vulnerability_library_custom_fields (new custom fields)
- vulnerability_project_custom_fields (new custom fields)
Portfolios help you to track & monitor the progress of your penetration testing programs.
Want to know how your internal systems compare to your external systems? Or wanting to track security posture for your applications or compliance requirements? Portfolios makes this easy!
Portfolios represent high-level grouping for segments within your pentesting program(s).
Every portfolio is made up of Work Streams (Streams) – a collection of pentests which focus on specific areas within your portfolio.
Portfolios and Streams can help you track Business-as-Usual (BAU) pentesting and better understand where to focus your time and resources more effectively.
Projects can be assigned to many streams and portfolios. This ensures you are tracking the right vulnerabilities, across your enterprise. See examples below:
Portfolios can help you to answer the following questions. Check out our blog on Portfolios to read how.
- What is the exposure of our Internet facing applications? How many critical vulnerabilities are currently open on these platforms?
- How can we be sure that each business division has pentested everything they need to have tested?
- How are platforms fixing vulnerabilities? Is it done within the required timeframes agreed in our internal policies or set by external regulators?
- How do our applications compare between 1st quarter and 2nd quarter? Are we getting any better?
- How are different business divisions and platforms comparing against each other? Where are you going to focus resources for next period?
- Which external suppliers are lagging?
Every Portfolio and Stream has a unique dashboard which includes details on vulnerabilities, projects & assets - helping you make more informed business decisions when it comes to tracking and remediation.
Using Portfolios, you can reduce the amount of time you spend reporting to your boards, executives, committees, and auditors!
Portfolios is currently only available to Administrators on AttackForge Enterprise.
With this release, we are launching an entirely new Self-Service API – Events API.
Events API provides you with real-time notifications on important events, such as new vulnerabilities discovered or testing progress updates.
Events API helps you to easily automate workflows. It’s perfect for customisations and integrations into your enterprise ecosystem.
For example, you want vulnerabilities to be raised in both ServiceNow & JIRA immediately when they are discovered, and emails to be sent to relevant teams so they can action it. This is now possible using the Events API!
Events API complements our existing RESTful API. You can combine both APIs to have seamless two-way integrations and workflows between AttackForge and your tools.
Events API allows you to:
- Receive real-time notifications on new vulnerabilities – automatically export them into your vulnerability management and/or ticketing systems.
- Update your applications with live testing & vulnerability feeds.
- Notified immediately when vulnerabilities are ready for retesting, closed or re-opened.
- Know exactly when changes are happening on your projects, for example when testing starts and stops.
- Receive audit logs for users in real-time.
Every event contains the same level of details information you can find in our Self-Service RESTful API.
Getting started with the Events API is a breeze and takes only minutes to set up.
We have done the hard work for you – you can access our production-ready example clients within AttackForge or directly from our GitHub repository.
Our example clients are available in NodeJS, Python, Java, .NET and Go – providing flexibility for your engineering teams.
Getting started with any client is as simple as 1,2,3!
- 1.Download the client from our GitHub repository
- 2.Install the dependencies (single command)
- 3.Run the client & start receiving events
If you’re interested in seeing a live demo of the Events API in action – reach out to us to schedule it in!
In this release, we have launched a new workflow to help make QA easy for your vulnerabilities. Introducing Review Notes!
Your pentest team can now create & reply to Review Notes for each of your vulnerabilities, as they perform QA.
Email notifications are enabled to ensure that people are made aware when they need to action changes for a vulnerability.
To perform efficient reviews & QA, you can select multiple vulnerabilities that you wish to review, and then add review notes to each vulnerability one-by-one. Best of all - you can do all of this from just one screen!
Once you have finished reviewing all vulnerabilities, you will see the Next option is no longer available - meaning you have reached the end of the review.
AttackForge ReportGen is by far the easiest to use reporting tool available right now – and it’s made even easier with its “no code” design, allowing your teams to create new reporting templates quickly and with minimal knowledge/effort required.
In this release, we have launched a library of ReportGen templates that you can use to create powerful custom reports out-of-the-box.
Every template comes with an example end-result so you can see the finished product.
The templates included in this release are:
- Asset Report
- Auditor / 3rd Party Report
- Critical & High Vulnerabilities Report
- Executive Report
- Internal & External Findings Report
- Pentest Report
- Retest Report
- Technical Report
- Testing Progress Report
- Web App & Infrastructure Report
Templates are provided in DOCX format. You can adjust each template to your desire/requirements, then upload back into AttackForge when ready to use on you projects.
You can also access sample project data files (JSON) to test your own templates with.
- You can now bulk select many or all assets to delete on a project.
- AttackForge will prevent deleting any assets with exiting vulnerabilities.
- Every time you export or sync a vulnerability with JIRA, the evidence/screenshots/files are now also exported/synced to JIRA.
- This makes it easier for your engineering teams to access screenshots to help them reproduce & fix vulnerabilities fast!
- The Executive Summary now supports ability to upload files.
- This reduces the manual effort required to insert screenshots into your reports for the executive summary.
- You can now add captions to each of your images in the report.
- Captions will be automatically applied in ReportGen and displayed under the images.
- You can now create custom names for each round of resting.
- Administrators can now see all vulnerabilities for a given asset in the Assets module.
- This makes is fast & easy to identify all known vulnerabilities for an asset.
- You can now assign multiple test suites to users during project creation.
- This eliminates the manual effort of assigning users to multiple test suites.
This release is jam-packed with updates to the user experience, to make AttackForge experience even better for you and your customers.
- Projects will now display a status of Overrun and Retest in the projects & various modules.
- This helps to quickly identify projects which require immediate attention.
- Overrun status applies when a project has exceeded the test window, and the test cases have not yet been completed.
- Retest status applies when a project has all test cases completed, and at least one vulnerability is flagged as ready for retesting.
- You can now collapse vulnerabilities into unique vulnerabilities, and toggle back to individual vulnerabilities.
- This helps to determine how many types of vulnerabilities have been discovered.
- You can now see the affected project when viewing vulnerabilities in the global dashboard.
- To improve experience for your customers, Admins can now enable/update progress notifications on behalf of your users.
- Progress notifications provide daily/weekly breakdowns of projects, vulnerabilities and testing progress – essential for your busy project managers and platform leads.
- You can now see which vulnerabilities were not retested for a new retest round, in addition to the vulnerabilities which were retested.
- This can help to identify vulnerabilities which need further attention.
- Admins can now view and restore users. All user data is preserved on restore.
- We have published an Access Control Matrix on our support site to help your teams with setting up the right levels of access for your users and projects.
- We have redesigned the Reporting Module interface to make it easier to select multiple projects and to download custom reports, as well as access new template library and uploaded/available templates.
In this release, we have introduced new global tenant configuration options, to help you personalize and improve your AttackForge experience even further.
You can start using these new options via the Configuration section in the Administration module.
- Vulnerabilities – Add Placeholder Steps to Reproduce/Proof of Concept for all new vulnerabilities
- Vulnerabilities – Add Placeholder Notes for all new vulnerabilities
- Users – Enable/Disable Local Authentication
- Users – Enable/Disable SSO Authentication
This release includes updates to ReportGen – to help you create tailored, custom on-demand reports to meet your reporting requirements, and to reduce the time wasted on manually adjusting reports.
The updates in this release include:
- New Filter – FilterBy
- New Metatags
You can use this filter in order to extract filtered data for vulnerabilities using various conditions.
This filter is useful if you are creating custom sections in your reports, for example a section for ‘Web App Vulnerabilities’ or ‘Infrastructure Vulnerabilities’.
Currently the following conditions are supported:
- filterBy:'AffectedAssetReportGenTags'
- This filter can be used to retrieve a list of vulnerabilities which have affected assets that meet conditions in their ReportGen tags.
- filterBy:'AffectedAssetReportGenTags-CountVulns'
- This filter can be used to retrieve a count of vulnerabilities which have affected assets that meet conditions in their ReportGen tags.
We have introduced the following new tags & updates to existing tags:
- {#retestingHistory} --> {retesting_custom_round_name} - custom round name (optional)
- {#retestingHistory} --> {retesting_custom_status_name} - custom status name (optional)
- {#retestingHistory} --> {#vulnerabilities} – Forty-seven (x47) new tags for vulnerabilities retested on the retesting round
- {#retestingHistory} --> {#vulnerabilitiesNotTested} – Forty-seven (x47) new tags for vulnerabilities not retested on the retesting round
In this release we have made updates to the Self-Service RESTful API to improve the data points available to you for vulnerabilities and test cases.
- GetVulnerabilities, GetVulnerabilitiesByAssetName, GetVulnerabilitiesByGroup, GetVulnerabilityById & GetProjectVulnerabilitiesById received the following new fields:
- vulnerability_alternate_id
- vulnerability_cvssv3_vector
- vulnerability_cvssv3_base_score
- vulnerability_cvssv3_temporal_score
- vulnerability_cvssv3_environmental_score
- vulnerability_steps_to_reproduce_HTML
- vulnerability_remediation_notes
- vulnerability_project_code
- vulnerability_project_groups
- vulnerability_evidence
- vulnerability_custom_fields
- vulnerability_library_custom_fields
- vulnerability_project_custom_fields
- GetProjectTestcasesById received the following new fields:
- locked
Themes have been a popular feature for AttackForge, with now Fourteen (x14) themes supported!
In this release we have introduced five new themes: Midnight Ocean, Predator, BumbleBee, Purple Panther & Nebula
MIDNIGHT OCEAN
PREDATOR
BUMBLEBEE
PURPLE PANTHER
NEBULA
In this release we have introduced the ability for AttackForge Pro users to add more test suites to a project after the project has been created.
In this release we have introduced the ability for AttackForge Free & Pro users to invite their connected team members to their projects, at time of project creation.
In this release we have a significant number of improvements we have made to AttackForge to enhance the experience for you and your users.
These improvements are a direct result of the feedback from our customers over the recent months, and includes the following:
You can now invite your entire project team during the project creation or approval process, and assign their roles, test suites & manage their notifications – in one easy step!
You can define the following for each project team member:
- Access Level
- Set the access level for the user on the project. This can be either View, Upload & Edit.
- Project Role
- Set the users' project role on the project e.g. pentester, customer, developer, etc.
- Email Notifications
- Set the emails which the user will receive on the project.
- Assign to Test Suite
- Assign the user to a test suite. The user will be assigned to each of the test cases loaded on the project for the nominated test suite.
AttackForge now supports an alternative vulnerability code that is configurable and used to generate user-friendly unique vulnerability identifiers for all vulnerabilities on the project.
For example, if you set a vulnerability code as SEC01 - the first vulnerability created on the project will have an alternate user-friendly unique identifier of SEC01-1. The next vulnerability will be SEC02-2 and so on.
You can update the vulnerability code on a project at any time, so long as it's a unique value (has not been used on any other projects) and is between three (3) to eight (8) characters in length.
When you update a vulnerability code on a project - all of the existing IDs for any of the projects' vulnerabilities will also be updated to match.
You can now validate the project code to check whether an existing project exists using the same code.
You can also fetch the latest project code, to help with sequencing.
.png?alt=media&token=44bca14f-dd31-485e-a603-abfe7658f566)
You can now set & control which email notifications a user will receive on a project.
Project Team Notifications are intended to help keep you informed throughout the lifecycle of a project. For example, you can choose to be notified when testing has commenced or stopped daily, when new vulnerabilities are discovered, or when a project is on-hold - plus more.
To receive these notifications, you must be a member on a project team. Your administrators and project coordinators will invite you to the relevant project teams. In addition, project-level notifications must be enabled on the project. Your administrators and project coordinators will configure this for you, per project.
The Project Team Notifications include the following:
- No Emails - Under normal circumstances, you will not receive any email notifications for any projects you are a team member.
- All Emails - You will receive all enabled emails for all projects you are a team member.
- Daily Start/Stop Testing - You will receive notifications each time a team member starts or stops testing each day, where this option is enabled on the project.
- New Critical Vulnerability - You will receive notifications each time a team member discovers a new critical vulnerability, where this option is enabled on the project.
- New High Vulnerability - You will receive notifications each time a team member discovers a new high vulnerability, where this option is enabled on the project.
- New Medium Vulnerability - You will receive notifications each time a team member discovers a new medium vulnerability, where this option is enabled on the project.
- New Low Vulnerability - You will receive notifications each time a team member discovers a new low vulnerability, where this option is enabled on the project.
- New Informational Vulnerability - You will receive notifications each time a team member discovers a new informational vulnerability, where this option is enabled on the project.
- Project Role Updated - You will receive notifications each time your role on a project has been updated, where this option is enabled on the project.
- Project On-Hold/Off-Hold - You will receive notifications each time the project is placed on-hold or off-hold, where this option is enabled on the project.
- Retest Completed - You will receive notifications each time a round of retesting has been completed, where this option is enabled on the project.
A user can choose to opt-out of project email notifications via Notifications module.
If you decide to disable certain types of emails, even when they are enabled for you on the project - you will not receive them. You ultimately control the project notifications you will receive.
However, under certain circumstances - an administrator or project coordinator may decide to force an email to be sent, for example new critical vulnerability that you should be aware of. Your administrators and project coordinators will configure any forced emails, per project.
We have also introduced new email notifications when a users’ role on a project is changed, and we also now include their role on the project invitation email.
We have introduced links in all emails which provide a friendly URL that will redirect the user to the relevant page on AttackForge, even if they are not yet logged in.
This helps to improve user experience by allowing the user to access a project, vulnerability, or event - with a single click!
This feature is also fully compatible with Single-Sign-On.
When creating a new user via Users module, the user will now receive a welcome email that can be configured via Administration module.
You can configure this email to contain a warm welcome message, or instructions on how to access the portal.
The email supports full HTML.
We have included extra column on Projects table to include project team.
This helps to easily find & search who is on which projects.
We have included a new table which helps to separate which users are on a project team, and which users have access to the project via their group memberships.
This makes it easier to know who is actively involved with the project.
We have included an additional column with the Resolution status when viewing project vulnerabilities.
This helps to quickly determine whether a vulnerability has been resolved, and also the reason it was resolved – for example had been fixed, risk accepted, etc.
.png?alt=media&token=e8d08ab6-62d1-4573-b7c3-d30b5d45dcde)
When setting a vulnerability as Ready for Retesting, you can now add a remediation note at the same time – to help pentesters understand what fixes were put in place.
We have also included the following UX improvements in this release:
- Admins can now Personalize Analytics for Other Users
- Performance Enhancements on downloading JSON Exports & Using ReportGen
- Major Bug Fixes in Various Parts of the Application, including when Creating/Editing Vulnerabilities in Projects & Library
- Upgraded Library to Handle Conversion of HTML-to-Text addressing number of Issues in Reports
- Pop-Up Warning Alert Now Included When Attempting Bulk Updates
- Improvements in Filtering & Comparison in Analytics
AttackForge provides a rich set of global tenant configuration options - allowing you to customize your workflows, features & user experience.
In this release, we have made these options available to you via the Administration module – allowing you to customize your tenant on-demand!
You can personalize your email templates, change workflows, introduce or remove fields, set default values, configure your security settings – and much more!
The list of supported configuration options is regularly updated and can be found on our support site: https://support.attackforge.com/attackforge-enterprise/configuration-options
You can access the following Configuration modules from the Administration module in your AttackForge tenant:
- Emails
- Vulnerabilities
- Projects
- Reporting
- Modules
- Integrations
- Users
- Security
- Miscellaneous
In our previous May release, we introduced a new Notifications module to provide centralized & dashboard-style email notifications to keep your teams informed even whilst on the go.
In this release, we have extended this module to include Daily & Weekly Project Updates, as well as Daily & Weekly Admin Updates.
We have also included more information in these emails such as Projects Overrun, Projects Completed, and more detailed information for each project.
Every email notification is designed to provide important information relating to projects, vulnerabilities & user activity.
You can access Notifications via the global menu.
In this release, we have introduced new global tenant configuration options, to help you personalize and improve your AttackForge experience even further.
You can start using these new options via the Configuration section in the Administration module.
- Projects – New Organization Code field for Projects
- Emails – Create Custom Email Subject & Body for Invited Users
- Vulnerabilities – Enable/Disable Severity Field in Vulnerability Library
- Vulnerabilities – Enable/Disable Likelihood of Exploitation Field in Vulnerability Library
- Vulnerabilities – Enable/Disable CVSS Scoring Fields in Vulnerability Library
- Modules – Enable/Disable Project Request Workflow
This release is action-packed with updates to ReportGen – to help you create tailored, custom on-demand reports to meet your reporting requirements, and to reduce the time wasted on manually adjusting reports.
The updates in this release include:
- New Filter – Store
- New Filter – FindVuln
- New Reporting Option - Remove Duplicate Proof-of-Concepts/Steps to Reproduce
- New Reporting Option - Remove Duplicate Evidence
- New Metatags
For more information please visit https://support.attackforge.com/attackforge-enterprise/modules/reporting
You can store custom data in arbitrarily defined tags using this filter.
For example we can create a new custom tag called 'AllVulns' and reference it, along with its data, later in the template.
This is useful if you are dynamically creating custom subsections/tables to reference in your report.
You can use this filter to find a vulnerability based on a Title & Priority.
This option can be set at the beginning of your template in order to remove duplicate Proof-of-Concepts/Steps to Reproduce for vulnerabilities which have multiple affected assets and each affected asset has the same POC & Notes.
This option is useful to reduce duplicate entries where the POCs/Notes are the same, significantly reducing report size and making content more useful to the reader.
This option can be set at the beginning of your template in order to remove duplicate Evidence for vulnerabilities which have already used/included the evidence within the Proof-of-Concept or Notes for any of affected assets, for example the screenshots have already appeared in-line within the Proof-of-Concept or Notes.
This option is useful to reduce duplicate evidence displaying, significantly reducing report size and making content more useful to the reader.
We have introduced the following new tags & updates to existing tags:
- {#affected_asset} --> {alternate_id} - user-friendly id associated with the vulnerability, set via project settings
- {#assetVulnerabilityMapping} - list of all assets on the project mapped to their vulnerabilities
- {asset} - asset name
- {#vulnerabilities} - list of all vulnerabilities the asset is affected by
- {vulnerability} - vulnerability title
- {priority} - priority of the vulnerability e.g. Critical, High, Medium, Low, Info
- {status} - remediation status e.g. Fixed / Not Fixed
- {#vulnerabilityDetails}
- {#vulnerabilityCustomTags} - you can define & use custom tags/fields in ReportGen. For more details check out Creating Custom Fields within ReportGen Reports
- {title} - title of the vulnerability
- {priority} - priority of the vulnerability e.g. Critical, High, Medium, Low, Info
- {remediation_status} - either Open or Closed. Only Closed if all affected assets are also Closed.
- {description} - description of the vulnerability
- {attack_scenario} - attack scenario for the vulnerability
- {remediation_recommendation} - remediation recommendation for the vulnerability
- {cvssv3_vector} - includes the CVSS v3.1 vector string e.g. /AV/...
- {cvssv3_base_score} - includes the CVSS v3.1 base score e.g. 10.0
- {cvssv3_temporal_score} - includes the CVSS v3.1 temporal score e.g. 10.0
- {cvssv3_environmental_score} - includes the CVSS v3.1 environmental score e.g. 10.0
- {testcases} - list of all the linked test cases to the vulnerability
- {#tags} - list of all tags
- {.} - tag
- {#affected_asset} - details for the affected asset - see {#assetVulnerabilityMapping} - {asset}
- {#assetCustomTags} - you can define & use custom tags/fields in ReportGen. For more details check out Creating Custom Fields within Individual Reports
- {alternate_id} - user-friendly id associated with the vulnerability, set via project settings
- {asset} - asset name
- {remediation_status} - includes the remediation status of the vulnerability for the affected asset e.g. Open / Ready for Retest on <DATE> / Closed on <DATE>
- {#remediation_notes} - list of all remediation notes for this affected asset
- {created} - date stamp when remediation note was created
- {note} - remediation note details
- {#notes} - list of all notes for this affected asse
- {note} - note details
- {%inlineScreenshot} - display inline images where they are included in the note
- {#proof_of_concept} - details for proof of concept / steps to reproduce
- {text} - proof of concept / steps to reproduce
- {%inlineScreenshot} - display inline images where they are included in the note
- {#proof_of_concept_raw} - details for proof of concept / steps to reproduce in RAW HTML format (verbatim).
- {#assets_equally_affected_title} - in order to cut-down report size, de-duplication is performed for each asset where #notes and #proof_of_concept are the same. This tag is used to display the heading for this section e.g. LIST OF ASSETS EQUALLY AFFECTED
- {#assets_equally_affected} - in order to cut-down report size, de-duplication is performed for each asset where #notes and #proof_of_concept are the same. This tag is used to display the names of all the assets which have the same POC & Notes as the vulnerability above.
- {.} - asset name
- {#affected_assets} - list of all affected assets for this vulnerability
- {#assetCustomTags} - you can define & use custom tags/fields in ReportGen. For more details check out Creating Custom Fields within Individual Reports
- {asset} - asset name
- {remediation_status} - includes the remediation status of the vulnerability for the affected asset e.g. Open / Ready for Retest on <DATE> / Closed on <DATE>
- {#remediation_notes} - list of all remediation notes for this affected asset
- {created} - date stamp when remediation note was created
- {note} - remediation note details
- {#notes} - list of all notes for this affected asset
- {note} - note details
- {%inlineScreenshot} - display inline images where they are included in the note
- {#proof_of_concept} - details for proof of concept / steps to reproduce