Defining a Job with a Service
Follow the steps in Define a Job until you have the inventory:netstat Action in the Jobs view.
Next, we'll add in our Service. Then from the Actions list, select download:file.
You should now see placards for both inventory:netstat and download:file in the Jobs view.
At the bottom the download:file placard in the drop-down menu select "Download to HQ" (or whatever you decided to call your Service).
The path you entered when you created your Service will appear in the placard as shown below.
Go ahead and finish creating the Job by clicking on the green 'Create Job' button.
This Job will complete the following tasks:
On each assigned BrazenAgent:
Download and execute the action
Put the results in the .\results folder, which is then cached by the BrazenAgent
On the BrazenAgent assigned to the Service:
Request all the results from the previous Actions
All results are still cached on the BrazenAgents, so the data is routed through BrazenCloud and to the BrazenAgent executing the Service
This uses the download command
Copies all of the results into the specified folder
Once the Job completes, you will see a positive result in the Jobs screen. In the example screenshot, you can see that the Job ran on 2 BrazenAgents.
To view the output of the 'Download to HQ' Job, we can navigate to the C:\BrazenCloudResults folder on the BrazenAgent that we selected for the Service when it was created.
In this screenshot, the contents of the directory have been displayed in PowerShell using gci, which is an alias for Get-ChildItem.
We can see that the Job results have appeared in the expected directory with each result in its own zip file with a naming convention that combines the hostname with the BrazenAgent ID.
The format of the results is defined by the Action. While they are all delivered as zips by BrazenCloud, the contents of the zip file is dependent on how the Action was authored.
Diagram
Here is a diagram to illustrate how the Service works in this Job:
Last updated