CloneProject
This method can be used for the following: Create a new project from an existing project you have Edit access to.
Parameters
The following URL, Headers and Parameters are required for requests to this API endpoint. Where a parameter is optional, it will be indicated. Otherwise treat all parameters as mandatory.
Headers
Query
id (string)
Id of the project you are cloning from. You must have access to this project.
Example:
name (string) (optional)
Name of the project. Will default to the cloned project name if not supplied.
Example:
code (string) (optional)
Project code. Will default to the cloned project code if not supplied.
Example:
groups (array of strings) (optional)
Groups to link to the project. Must match exact group names or ids. Will default to the cloned project groups if not supplied. Supply an empty list - [] - to link to no groups.
Example:
startDate (string)
Project start date. Must be UTC string e.g. 2021-06-03T23:15:33.008Z.
Example:
endDate (string)
Project end date. Must be UTC string e.g. 2021-06-03T23:15:33.008Z.
Example:
scoringSystem (string) (optional)
Scoring system to be used on the project. Must be either Manual or CVSSv3.1. Will default to the cloned project scoring system if not supplied.
Example:
scope (array of strings) (optional)
Project scope / assets to be tested. Include name of asset or the asset Id if using the assets module. Will default to the cloned project scope if not supplied.
Example:
asset_library_ids (array of strings) (optional)
Asset libraries to map scope against. Only applicable if creating new assets.
Example:
testsuites (array of strings) (optional)
Test suites to assign to the project. Must match exact testsuite names or ids. Will default to the cloned project test suites if not supplied.
Example:
organization_code (string) (optional)
Project organization code. Will default to the cloned project organization code if not supplied. Supply an empty string - "" - to assign no organization code.
Example:
vulnerability_code (string) (optional)
Vulnerability code for user friendly vulnerability ids. Must be unique per project, 3-8 characters in length.
Example:
team_notifications (array of strings) (optional)
Project team notifications. Must include one or more of the following: critical, high, medium, low, info, retest, reopened, closed. Will default to the cloned project team notifications if not supplied. Supply an empty list - [] - to set no project team notifications.
Example:
admin_notifications (array of strings) (optional)
Admin notifications. Must include one or more of the following: retest, reopened, closed. Will default to the cloned project admin notifications if not supplied. Supply an empty list - [] - to set no admin notifications.
Example:
start_stop_testing_email (string) (optional)
Email body for daily start & stop testing notifications. Will default to the cloned project email body for daily start & stop testing notifications if not supplied.
Example:
start_stop_testing_email_additional_recipients (array of strings) (optional)
Additional email recipients for daily start & stop testing notifications. Must be a list of email addresses. Will default to the cloned project additional email recipients for daily start & stop testing notifications if not supplied. Supply an empty list - [] - to set no additional email recipients for daily start & stop testing notifications.
Example:
new_vulnerability_email_type (string) (optional)
Individual or Grouped emails to be sent for new vulnerabilities. Must include one of the following: individual, group. Will default to the cloned project new vulnerability email type if not supplied.
Example:
new_vulnerability_email (string) (optional)
Email body for new vulnerability discovered notifications. Will default to the cloned project email body for new vulnerability discovered notifications if not supplied.
Example:
new_vulnerability_email_additional_recipients (array of strings) (optional)
Additional email recipients for new vulnerability discovered notifications. Must be a list of email addresses. Will default to the cloned project additional email recipients for new vulnerability discovered notifications if not supplied. Supply an empty list - [] - to set no additional email recipients for new vulnerability discovered notifications.
Example:
forced_emails (array of strings) (optional)
Force emails to project team. Must include one or more of the following: all_emails, daily_start_stop_testing, new_critical_vulnerability, new_high_vulnerability, new_medium_vulnerability, new_low_vulnerability, new_info_vulnerability, vulnerability_ready_for_retesting, vulnerability_reopened, vulnerability_closed, project_role_updated, project_hold, retest_completed. Will default to the cloned project forced emails if not supplied. Supply an empty list - [] - to set no forced emails.
Example:
sla_activation (string) (optional)
Apply vulnerability SLAs automatically or manually. Must be either "automatic" or "manual". Will default to the cloned project SLA activation option if not supplied.
Example:
custom_fields (array of objects) (optional)
Custom fields. Must include a key and value. Key must be unique and letters, numbers and underscores only. Will default to the cloned project custom fields if not supplied. Supply an empty list - [] - to set no custom fields.
For more information visit https://support.attackforge.com/attackforge-enterprise/getting-started/custom-fields-and-forms#using-custom-fields-with-apis
Example:
portfolio_streams (array of objects) (optional)
Enter a list of Portfolio & Stream Ids to link this project to. Stream must be part of the Portfolio. Will default to the cloned project linked portfolio streams if not supplied. Supply an empty list - [] - to set no linked portfolio streams.
Example:
features (object) (optional)
Configure features on the project. Roles must be either client, consultant or librarymod. Minimum Project Access Level must be either View, Upload or Edit.
Example:
pages (object) (optional)
Configure pages on the project. Roles must be either client, consultant or librarymod. Project Access Level must be either View, Upload or Edit.
Example:
link_vulnerabilities (object) (optional)
Link vulnerabilities from the cloned project to the new project. You can select vulnerabilities by their remediation status, priority or by providing their ids. Each option will stack i.e. open:true is all open vulnerabilities, open:true + critical:true is all open critical vulnerabilities.
Example:
options (object) (optional)
Cloning options.
Example:
Example
The following example is a cURL request to clone a new project.
Request
Include API Token instead of stars in 'X-SSAPI-KEY: ***************************************' parameter.
Response
Response contains a project object.
Last updated