A DEPLOYMENT consists of:
- Scenario (optional)
- Elastic Test Asset (optional)
- Custom Properties
To create a Deployment:
- On the main menu, click the Add button next to Deployments, this will open the Deployment Builder
Note: If you don’t see the “Add” button, notify your project owner(s) that you need permissions in your project
Step 1: Add a Scenario (Optional)
A scenario contains an ordered list of system to deploy into one of your cloudspaces. Some Test Assets when deployed will be automatically executed against the systems in your scenario (e.g. Nessus or Web Exploitation scans). If you are creating a deployment to run a Fortify or Sonar Test Asset, a scenario is not needed. Similarly, if you are running a Nessus Test Asset against systems already deployed, you do not need a scenario.
- To add a scenario, click “Scenarios” on the main menu, browse to or search for your scenario. Click here if you need to create a scenario.
- Click on the scenario
- On the scenario page, click Add to Deployment Builder
Step 2: Add a Test Asset (Optional)
A test asset is automatically executed on one of the Elastic Test Tools (ETTs):
- Web Exploitation Suite**
- Test Script (Linux)
- Test Script (Powershell)
- soapUI Community**
ETTs marked by
** can be automatically executed against a scenario, in the deployment. Otherwise, a scenario is not required in the deployment to run your test asset.
To create and add a test asset:
- From the main menu, select “Tests”, browse to or search for your test asset or a community-provided test asset. Click here for instructions on creating a custom test asset. Also see the CONS3RT Github page for sample test assets for each Elastic Test Tool
- Click on the test asset
- On the test asset page, click Add to Deployment Builder
Step 3: Add Custom Properties and Save your Deployment
After adding a Scenario and/or Test Asset, click back into the deployment builder by clicking the number next to “Deployments” on the main menu.
- Review your scenario and/or test asset, and click Next
- Add a name and optionally a description, click Next
- (Optional) Add Custom Properties as key-value pairs. More info about custom properties
Some Elastic Test Tools take custom properties, such as
nessus.targets to configure target IP addresses for the Nessus/ACAS scanner. Custom properties can also be useful information to provided to your installation scripts, such as a DNS server IP address, credential info, a license server IP address, a log level, and much more. Any key-value pairs added here will be available on each system in the deployment in the deployment properties files. Here are some sample properties:
nessus.targets=192.168.10.200 PrimaryDNS=192.168.11.75 mySecretPassword=abcde12345 LICENSE_SERVER=10.220.103.160 LOG_LEVEL=debug
- Click the Finish button once these steps have been completed, or click Finish & Launch to also immediately jump to the Run wizard.
Step 4: Launch your Deployment
- From the Main Nav menu, select “Deployments”, browse to or search for your deployment
- Click the Launch button, and select your options defined here in the Run Wizard
- Now just relax, get some other stuff done, and wait for the email notification when your Run has completed!
Review this process with our video tutorials: