2023
You can now configure view & edit access controls for your custom fields, and apply them to individual roles, groups or users.
This opens a world of new possibilities, for example:
- Create custom project request forms for different customers, teams, business units or individual users
- Personalize your project request forms to your customers’ needs and requirements
- Set up tailored forms for your pentest-as-a-service (PTaaS) to match your customers’ needs or subscription-level
- Have custom project fields for admin-eyes only, or for pentesters – without your customers seeing them
- Set project budgets; admin notes; integration fields – ensure confidentiality with access controls
- Configure project-level information for only your project coordinators or pentesters to see
- Define custom vulnerability and writeup fields for different pentest teams
- Create personalized vulnerability and writeup forms for infrastructure teams, application teams, remediation teams, etc.
- Configure custom vulnerability and writeup fields for different customers
- Control what vulnerability information is shared with which customers or teams
- Assign custom asset and portfolio fields for different customers
- Configure information that is only relevant for specific customer assets or portfolios
You can also preview what your users can see using the ‘view-as’ feature.
This can help you to easily and quickly configure and manage your access controls.
All custom field access controls are also honored via the APIs, so unauthorized users cannot view or edit custom fields they are not supposed to.
You can now configure custom fields with the following types:
- Table
- Rich-text
- User(s)
- Group(s)
These new types allow you to capture information on projects, vulnerabilities, assets, writeups, portfolios and test cases in ways never seen before in AttackForge.
Combining these new custom field types with the new ability to set access controls on custom fields, you can have this information available only to people with need-to-know.
- Table custom fields
Table custom fields are a great way to collect and use data in AttackForge and in your reports which is in a tabular format.
For example, you may be performing a configuration or firewall review and the data from your tools only outputs into CSV or tables.
Now you can easily import that data from the APIs, edit the data in the application, and display the data in your reports.
- Rich-text custom fields
Rich-text custom fields have been one of the most requested custom field types – and its finally here!
You can set up rich-text enabled custom fields to use for your writeups or vulnerabilities, and best of all – it is supported in reports as well, so you can have custom styled fields easily and effortlessly showing for your customers. This also means you can enter data using lists, or create sections in your data using headings, or even highlight code snippets.
- User custom fields
User custom fields open the door to possibilities to assign users in AttackForge to projects or vulnerabilities.
For example, you may want to create Peer Review and Tech Review fields on your vulnerabilities and assign users accordingly.
Or you may want to associate a Level 1 Owner and a Level 2 Owner to certain vulnerabilities. This is all now possible.
User custom fields support single-select and multi-select, for cases when either one or many users can be assigned.
- Group custom fields
Group custom fields also opens many possibilities, such as assigning groups to vulnerabilities.
For example, you may want to associate a particular group to a vulnerability who are tasked with responsibility to fix it.
Group custom fields support single-select and multi-select, for cases when either one or many groups can be assigned.
We have added support for a new category of custom fields – test cases.
You can now define custom fields on your test cases and have this information available to your pentesters or customers.
We have also extended support for this new category in the Self-Service APIs.
You can now assign a custom information message to display in the information panel when users are completing your custom fields.
This is useful to help guide users on what information to enter in or select when filling in forms within your AttackForge.
You can now reorder your custom fields using drag-and-drop or clicking on the up and down buttons.
This makes it easy and efficient to set up your forms the way you need them to look.
You can now configure access controls on your reporting templates. This makes it possible to:
- Have different reports for different customers
- Personalize reports to your customers needs, for example add their logo or only the data that they need
- Separate reports that your security team uses to that of your customers
- Tailor reports for different business units, without conflict!
You can now delegate the ability to add test suites and abuse cases on projects to other roles and users.
This makes it possible to now allow your pentesters to have authority to perform this action when needed.
These delegations can be applied to entire roles from Administration page, or to individual users via the User --> Access --> Delegations feature.
You can now configure custom rules for your pentesters to use when performing an import of vulnerabilities.
These rules work as dynamic custom parser actions, telling AttackForge how to map the imported vulnerability to a correct entry in your chosen writeups library.
It’s a great timesaver and made even more efficient now that you can save predefined rules and let your pentesters chose the relevant rule (and extend upon it) when importing.
Custom rules can be configured in Administration --> Vulnerabilities.
You can now configure a custom background color for your login page.
We have just released our biggest update ever (v2.6) for AttackForge ReportGen: The ultimate pentest reporting tool!
This release includes a new Pentest Report Template (v3); support for charts; four (4) new functions; three (3) new filters; new options; new styles, new variables and updates to existing filters and functions add even more power to your reports!
All examples mentioned in these release notes can be found on the homepage of the ReportGen tool.
This release introduces a new contemporary pentest reporting template - showcasing the possibilities now available in ReportGen v2.5+.
The new Pentest Report Template v3 includes:
- Logic for a multi-phase project e.g. Web App Pentest + Infrastructure
- Redesigned Executive Summary, using custom Charts
- Redesigned Summary Findings
- Redesigned Vulnerability Details with more information and enhancements
- Redesigned Test Cases Details
This new template can be downloaded directly from within the ReportGen tool.
You can now create custom charts in your reports! The following charts are supported:
- Vertical Bar Charts
- Horizontal Bar Charts
- Pie Charts
- Donut Charts
Charts work with any data. You can create charts for your vulnerabilities, exec summary, test cases, attack chains or even categorize your data.
Charts also support Scope and Variables.
Every chart comes with configuration options (e.g. colors, font sizes, spacing, etc.) so you can configure and style the chart to your preferences.
A Dictionary is a flat list of key:value pairs. It can be useful for capturing dynamic data, or for grouping data.
You can refer to the Dictionary anywhere you need it in your report.
Dictionary is supported on the following Functions: $declare, $push, $assign, and $keys.
- Example 1: Using a Dictionary to count all affected assets for every vulnerability, then prints the count alongside the vulnerability name.
- Example 2: Using a Dictionary to store every phase of testing e.g. Web App, Ext. Infrastructure, Int. Infrastructure etc. along with each vulnerability associated to each phase of testing, then print the phase and its vulnerabilities.
We have made it possible to now combine Filters with your Functions!
This can be achieved in two (2) different ways:
- Example 1: Using a Filter inside the Function
- Example 2: Chaining a Filter to the output of a Function
For AttackForge Core and Enterprise users, you can now style your vulnerability descriptions, attack scenarios and remediation recommendations!
These tags will render a styled version based on the style set in-app using the WYSIWYG editor.
To switch over to the new styled tags, update your template to include the new tags.
{@description_styled}
{@attack_scenario_styled}
{@remediation_recommendation_styled}
We have added support for two (2) new styles:
- AF Normal which can be used to create a custom style for normal text inserted via the {@..._styled} tags.
- AF List which can be used to create a custom style for bullet and numbered lists inserted via the {@..._styled} tags.
These new styles provide the ability to have custom formatting for how your normal text and lists are displayed in your reports when using the {@..._styled} tags.
To get started, create two new styles inside your Word template with the names 'AF Normal' and 'AF List'. Then apply a format to these styles.
When ReportGen builds your report, it will automatically map to these styles for you.
This option can be set against the {@proof_of_concept_styled} tag in order to adjust how the filename or caption is displayed under an image.
- image_description: caption - will display the caption if it exists, otherwise will display nothing.
- image_description: prefer-caption - will display the caption if it exists, otherwise will display filename.
- image_description: caption - will display the filename.
- image_description: none - will display no caption or filename.
You can use this new filter to retrieve the value for a Dictionary.
- Example: Using a Dictionary to count all affected assets for every vulnerability, then prints the count alongside the vulnerability name.
Use this function to check if you are in the first iteration of a loop.
For example, if you want to add a section heading BEFORE printing the vulnerability titles.
Another example is if you want to check if it IS NOT the first iteration of a loop.
Use this function to check if you are in the last iteration of a loop.
For example, if you want to add an extra line break after every vulnerability title except for the last.
Another example is if you want to check if it IS the last iteration of a loop.
Use this function to print the current index of the loop you are iterating over.
You can use this filter to search for a value in a string and return the results (substring) if found.
You can use this filter to access an item in an array using its index number.
We have now made it easy to perform a custom sort based on your custom tags or custom fields!
You can now select one or more vulnerabilities, can create a custom report with only that selection.
This is useful when you need to get a report out to different teams, with only the context for vulnerabilities which are relevant to that team.
We have now added rich-text support for your writeups!
You can now have more detailed and styled information for your vulnerabilities.
You can also include the styled versions in your reports using the following tags:
- {@description_styled}
- {@attack_scenario_styled}
- {@remediation_recommendation_styled}
You can now independently configure CVSS Baseline, Temporal and Environmental scores for your writeups.
Simply select the relevant option from the drop-down when creating or editing your writeups.
The score will be used as a baseline when creating new vulnerabilities.
You can now link vulnerabilities from one project to another.
This is useful when you want multiple projects to have a view of a particular vulnerability, or set of vulnerabilities, for example to consolidate for a round of retesting.
Linking vulnerabilities does not duplicate/clone the vulnerability, therefore your dashboards and analytics will be preserved.
Also, when linking vulnerabilities, any changes on the vulnerability, for example its set to Closed, will be applicable to all projects it is linked to.
This makes it easy to fix it in one place, and have the results propagate everywhere.
However, if you intend to create a clone of a vulnerability, you can do that using the duplicate vulnerability feature instead.
You can now set your table preferences for when viewing test cases on a project.
This includes ability to configure:
- Default page size
- Default sort column
- Default sort order
- Which columns to display (including custom fields), and in which order
You can now specify which delimiters you want to use on your Affected Endpoints when creating a new vulnerability.
This is useful if you have a delimited list which is not using commas, semi-colons or line separated; and is URL encoding friendly as you can switch semi-colon off.
AttackForge will also now show you how many vulnerabilities are going to be created based on your Asset and Affected Endpoint selections.
You can now opt-into preserving the tags on your vulnerabilities when using the import vulnerabilities feature.
This is different to the standard behaviour which inherits the tags from the writeup it is matched with during import.
This is useful if your vulnerabilities have unique tags which you need to preserve.
This option can be enabled in the import parameters section, prior to importing.
We have updated Qualys parser to include support for the new Web Application Scan XML format.
When you duplicate a vulnerability, you now no longer need to specify the asset.
This makes it easy to select a bunch of vulnerabilities and create an exact clone of the vulnerabilities.
You can then re-assign them to other projects if needed or adjust them using bulk actions.
When viewing vulnerabilities in tables, you can now click on the View System Id button to see the system id for each vulnerability.
You can then toggle it back to view the custom id.
When viewing vulnerabilities in tables, you can now click on the View Date button to switch the view from a countdown (e.g. 5 days) to an actual date.
We have now grouped all Self-Service APIs to make them easy to categorize, and also included a search bar to make it easy to find particular APIs.
Now when you rename an image you have uploaded to your vulnerabilities, AttackForge will automatically update your proof of concept for you, saving you the hassle of having to manually change that to reflect the new image name.
When you import vulnerabilities, you can now filter your selection down using tags.
This is useful for selecting certain vulnerabilities only, for example only exploitable vulnerabilities based on properties in the tags; or only patching or operating system related vulnerabilities.
We have now updated the documentation on our Support Centre to include full mappings for hide expressions, and examples for each data type and system field.
This makes it easier to create custom logic to hide your form fields, and only show them when the logic conditions are met.
For more information, please visit https://support.attackforge.com/attackforge-enterprise/getting-started/custom-fields-and-forms#hide-expressions-conditions
We have updated the user experience when exporting vulnerabilities from a project into your JIRA project.
Now it will preserve your data in case there are any errors, so you can make quick changes. We have also improved the error handling and provided a new look form.
The project dashboard will now include informational vulnerabilities by default.
You can also opt to switch it off to not display them in case there are too many informational vulnerabilities on the project
When a new vulnerability is created, the event is now registered in the revision history.
In this release, we have improved our Self-Service REST APIs to provide more flexibility and options when interacting with AttackForge.
We have updated all relevant APIs to now support string arrays and arrays of objects for custom fields.
This makes it possible to import data in various formats, for example:
- Strings
- Strings are used to store data for Input fields, Text Area fields, Date-picker fields, Select fields and Rich-Text fields
- String Array (string[])
- String Arrays are used to store data for Multi-Select fields, User fields and Group fields
- Array of Objects
- Array of Objects are used to store data in tabular format for Table fields.
Custom fields do not need to be configured in the administration settings in order to be created or updated via the APIs.
However, if the custom field Key matches one that is already defined in the admin settings, it will be automatically typed to that setting when presented in the user interface.
For full details on what is supported, with examples, please visit https://support.attackforge.com/attackforge-enterprise/getting-started/custom-fields-and-forms#using-custom-fields-with-apis
We have updated the following APIs to support the ability to provide a created parameter, which overrides the default created timestamp.
- Create Vulnerability
- Create Vulnerability Bulk
- Create Vulnerability With Library
This allows you to set the date and time when a vulnerability was created, which is useful if importing historical vulnerabilities.
We have added support for advanced query filtering for REST endpoints: Get Vulnerability Library Writeups
Advanced query filtering is used to select the exact data set you would like the API to return. The filter works like a database query, where you can specify fields & operators - these help to narrow down the results to the data you would need. This filter is only supported for selected API endpoints. Please check the documentation for each endpoint for more details.
For example, you can use this filter to return:
Writeups with title SQL Injection:
curl -G -X GET 'https://YOURAFTENANT/api/ss/library' --data-urlencode 'q={title: { $eq: "SQL Injection" }}' -H 'Host: localhost:3000' -H 'X-SSAPI-KEY: ***' -H 'Content-Type: application/json' -H 'Connection: close'Writeups with the tag pluginID:53360:
curl -G -X GET 'https://YOURAFTENANT/api/ss/library' --data-urlencode 'q={tags: { $in: "pluginID:53360" }}' -H 'Host: localhost:3000' -H 'X-SSAPI-KEY: ***' -H 'Content-Type: application/json' -H 'Connection: close'Writeups with the custom field NessusID and value 53360:
curl -G -X GET 'https:// YOURAFTENANT/api/ss/library' --data-urlencode 'q={custom_fields.name: { $eq: "NessusID" }, custom_fields.value: { $eq: "53360" }}' -H 'Host: localhost:3000' -H 'X-SSAPI-KEY: ***' -H 'Content-Type: application/json' -H 'Connection: close'The query filter supports the following operators:
- And
- Or
- Equals
- Not Equals
- In
- Not In
- Greater Than
- Greater Than or Equals
- Less Than
- Less Than or Equals
- Regular Expression
The query filter also supports datetime function, which allows you to modify the time and date to suit your query requirements.
For example, you could ask it to show you all writeups in past 24 hours or past 7 days.
For more information on how advanced query filtering works, please visit https://support.attackforge.com/attackforge-enterprise/modules/self-service-restful-api/advanced-query-filter
We have added the option to get all groups if the user is an admin user, instead of just the default behavior which is to return my groups.
We have updated this endpoint to have an option to exclude binaries from the response, for example data related to evidence files for vulnerabilities.
This is useful for integrations where the evidence data is not needed.
AttackForge Version 2 is now generally available for Enterprise and Core customers!
AttackForge Version 2 sets an even higher benchmark for Pentest Management Platforms; further improving the way security and engineering teams, service providers, and customers interact and collaborate with each other on pentesting projects and programs.
We have redesigned the user interface to make it simpler to perform daily tasks, whilst providing more flexibility when you need it.
We have also made significant improvements to address feedback from customers over the years.
Some of the changes to AttackForge includes:
- Overall improvements to efficiency of daily workflows for pentesters, security managers, engineering and application teams.
- Redesigned user interface to make it faster and easier to perform many tasks, as well as addressed many previously reported limitations in version 1 interface.
- Lays the framework for many of the future roadmap enhancements we have planned for AttackForge.
- Reduced the number of screens and clicks required to perform many workflows.
- Performance improvements when using the application.
- Analytics has been improved to provide more information and comparison options.
- Portfolios has been redesigned to make it easier to track and analyze different portfolios and streams.
- Projects have been overhauled to have new dashboards; easy-to-access options; new quick actions; modals for easy data entry and access to data.
- New Vulnerabilities module, providing greater insights into your vulnerabilities.
- Administration has been redesigned to make it easier to apply configuration options.
- Self-service API documentation is now Open API v3 compliant, including more API reference documentation inside the application.
- More options in more places i.e., you can archive/clone projects from multiple areas, download reports from multiple areas, etc.
- Addressed feedback on wording and terminology to make user interface more consistent.
- New user interface components for rich-text editors, tables, dashboards, menus, forms, etc.
- And much more!..
Our Support Centre has been updated for version 2.
You can find more information at https://support.attackforge.com/attackforge-enterprise/getting-started
We have just released version 2.5 for AttackForge ReportGen: The ultimate pentest reporting tool!
This release includes six (6) new filters; three (3) new functions; and updates to existing filters.
You can use this new filter to resize images. It works by setting a max-width value in pixels. The height will be automatically adjusted to match the same ratio.
Example resizing images in Steps to Reproduce (Proof of Concept) to 300 pixels wide:
{#vulnerabilities}
{#affected_assets}
{#proof_of_concept}
{%inlineScreenshot | resize:[“300”]}
{/}{/}{/}
Example resizing images in styled Steps to Reproduce (Proof of Concept) to 300 pixels wide:
{#vulnerabilities}
{#affected_assets}
{@proof_of_concept_styled | resize:[“300”]}
{/}{/}
You can use this new filter to replace data.
And you wanted to remove the https:// part, so it appears as follows: application.com
You could do the following:
{#vulnerabilities}
{#affected_assets}
{asset | replace:[“https://”,“”]}
{/}{/}
You can use this new filter with a regular expression to replace data.
You could do the following:
{#vulnerabilities}
{#affected_assets}
{asset | replaceRegExp:[“[?].*”,“”]}
{/}{/}
You can use this new filter to split data based on a separator - and return a list of items.
For example, assuming you have tags in this format: tag1:value
And you only want to show the right-hand-side (value), you could do the following:
{#vulnerabilities}
{#tags}
{$declare[tagSplitCounter][0]}
{#this | split:[“:”]}
{#$greaterThan[tagSplitCounter][0]}{.}{/}
{#$equals[tagSplitCounter][0]}{$increment[tagSplitCounter][1]}{/}
{/}{/}{/}
This example makes use of this filter to split the tag based on colon (:) as the separator. It also uses functions as a way to instruct the logic to skip over the first iteration of the loop (tag1) and then print everything after that (value).
You can use the splitRegExp function to split data based on a Regular Expression separator - and return a list of items.
For example, if you wanted to only display the 1st paragraph of the vulnerability description, you could do the following:
{#vulnerabilities}
{title}
{$declare[SplitDecriptionOnParagraph][1]}
{#description | splitRegExp:[“\n\n“]}
{#$lessThanOrEqual[SplitDecriptionOnParagraph][1]}{.}{/}{$increment[SplitDecriptionOnParagraph][1]}
{/}{/}
You can use this new filter trim the whitespace before and after a tag as follows:
{#title | trim}
We have updated the Includes and Excludes filters to include support for Scope and Variables.
Includes Scope Example:
{#projectCustomFields}
{#customer_name}
{#projectGroups}
{#name | includes:[“%(../customer_name)”]}
Customer {customer_name} has access to this project.
{/}{/}{/}{/}
Includes Variables Example:
{$declare[CustomerName][“”]}
{#projectCustomFields}
{#customer_name}
{$assign[CustomerName][“%(customer_name)”]}
{/}{/}
{#projectGroups}
{#name | includes:[“$(CustomerName)”]}
Customer {$value[CustomerName]} has access to this project.
{/}{/}
You can use the new $includes function to check if a value exists or does not exist (excludes) within a variable.
To check if data exists:
{#$includes[variable][value]}{/}
To check if data does not exist (excludes):
{^$includes[variable][value]}{/}
The following example creates a unique list of affected asset names, then prints the list.
{$declare[UniqueAssets][[]]}
{#vulnerabilities}
{#affected_assets}
{^$includes[UniqueAssets]["%(asset)"]}
{$push[UniqueAssets]["%(asset)"]}
{/}{/}{/}
{#$value[UniqueAssets]}
{.}
{/}
You can use the new $append function to append data to an existing variable.
{$append[variable][value]}
Example below will create a new variable, then append the vulnerability title to it.
{$declare[VulnTitle]["Title: "]}
{#vulnerabilities[0]}
{$append[VulnTitle]["%(./)"]}
{/}
{$value[VulnTitle]}
You can use the new $sort function to sort the data within a variable.
To observe the variables available for sorting - use the $help function.
Example 1: Sort A List
{#$sort[UniqueAffectedEndpoints][":asc"]}{/}
Example 1: Single-Key Sort
{#$sort[UniqueAffectedEndpoints]["af_sys_affected_endpoint:desc"]}{/}
Example 2: Multi-Key Sort
{#$sort[UniqueOWASPTop10Vulns]["priority:asc","title:desc"]}{/}
Sometimes vulnerabilities are assigned for retesting, only to discover that engineers have jumped the gun and further adjustments might be needed before they are retested.
Customers/Engineers can now reassign vulnerabilities as Not Ready for Retesting in such cases.
Assignment of vulnerabilities as Ready for Retesting and Not Ready for Retesting can now be applied in bulk by customers.
The project request form is an integral part of the pentest project lifecycle. It is the important first step of the process, where customers can request a new project or assessment.
We have now made it possible to add hide conditions against the system fields.
This means you can extend the logic of your project request form to customise when and how the system fields are displayed during a new project request.
This provides more personalisation and better user experience for your customers.
Following on from the enhancement above, we have taken this one step further to now support ability to disable all system fields in project request form, if desired.
This allows you to create a fully custom project request form, tailored to your needs, without any implicit fields for your customers to complete.
In this release, we have improved our Self-Service REST APIs to provide more flexibility and options when interacting with AttackForge.
This endpoint can be used to clone an existing project. This is an effective way to:
- Prepare for a new round of testing
- Track vulnerabilities for specific assets across projects
- Focus retesting on open vulnerabilities
When cloning a project, the new project will get access to:
- Project settings, which can be adjusted for the new project - this includes name, codes, test suites, scope, email templates, portfolios, custom fields & project team
- Project workspace, included all notes & files previously uploaded / created (OPTIONAL)
- Project notes previously created (excluding private notes) (OPTIONAL)
- Executive summary, including uploaded files (OPTIONAL)
You can also select which vulnerabilities (if any) you would like to carry forward into the new project. This is useful for performing a retest on existing vulnerabilities, as part of the new round of testing.
For full details on how to use this endpoint, please visit https://support.attackforge.com/attackforge-enterprise/modules/self-service-restful-api/cloneproject
We have added support for advanced query filtering for REST endpoints: GetVulnerabilities, GetProjectVulnerabilities, GetVulnerabilitiesByAssetName, GetVulnerabilitiesByGroup
Advanced query filtering is used to select the exact data set you would like the API to return. The filter works like a database query, where you can specify fields & operators - these help to narrow down the results to the data you would need. This filter is only supported for selected API endpoints. Please check the documentation for each endpoint for more details.
For example, you can use this filter to return:
Critical or High vulnerabilities only:
curl -G -X GET 'https://YOURAFETENANT/api/ss/vulnerabilities' --data-urlencode 'q={ priority: { $in: ["Critical", "High" ] } }' -H 'Host: localhost:3000' -H 'X-SSAPI-KEY: ***' -H 'Content-Type: application/json' -H 'Connection: close'
Open Critical or Open High vulnerabilities only:
curl -G -X GET 'https://YOURAFETENANT/api/ss/vulnerabilities' --data-urlencode 'q={ $and: [ { priority: { $in: [ "Critical", "High" ] } }, { status: { $eq: "Open" } } ] }' -H 'Host: localhost:3000' -H 'X-SSAPI-KEY: ***' -H 'Content-Type: application/json' -H 'Connection: close'
Critical or High Ready for Retest vulnerabilities only:
curl -G -X GET 'https://YOURAFETENANT/api/ss/vulnerabilities' --data-urlencode 'q={ $and: [ { priority: { $in: [ "Critical", "High" ] } }, { is_retest: { $eq: "Yes" } } ] }' -H 'Host: localhost:3000' -H 'X-SSAPI-KEY: ***' -H 'Content-Type: application/json' -H 'Connection: close'
Critical or High vulnerabilities discovered in past 24 hours:
curl -G -X GET 'https://YOURAFETENANT/api/ss/vulnerabilities' --data-urlencode 'q={ $and: [ { priority: { $in: [ "Critical", "High" ] } }, { status: { $eq: "Open" } }, { created: { $gte: datetime("now", "-1 days") } } ] }' -H 'Host: localhost:3000' -H 'X-SSAPI-KEY: ***' -H 'Content-Type: application/json' -H 'Connection: close'
The query filter supports the following operators:
- And
- Or
- Equals
- Not Equals
- In
- Not In
- Greater Than
- Greater Than or Equals
- Less Than
- Less Than or Equals
- Regular Expression
The query filter also supports datetime function, which allows you to modify the time and date to suit your query requirements.
For example, you could ask it to show you all vulnerabilities in past 24 hours or past 7 days; or filter all vulnerabilities with SLA expiring in next 24 hours or next 7 days.
For more information on how advanced query filtering works, please visit https://support.attackforge.com/attackforge-enterprise/modules/self-service-restful-api/advanced-query-filter
We have added support for querying projects by specific asset(s) which were in-scope for testing, for REST endpoint: GetProjects
This is useful if you need to perform analysis on which projects a given asset was tested, or if it has not yet been tested.
The filter supports:
- exact name match
- partial name match
- case sensitive match
- case insensitive match
- single asset
- multiple assets
- any combination of the above
For more information, please visit https://support.attackforge.com/attackforge-enterprise/modules/self-service-restful-api/getprojects
Last modified 23d ago