AutoTask Integration
- Sneha B A (Unlicensed)
- Amrutha Bolad (Unlicensed)
- Vrushali Parkar
CyberCNS supports AutoTask PSA integration to add value using existing ticketing system functionality. It can be used to notify and manage security assessments reported by CyberCNS.
Select Integration
This screen will likely change as we add more integrations.
Navigate to Global Settings() > Integrations and choose AutoTask from the integrations listed here.
It will lead to adding credentials for your AutoTask Instance. Please provide details as requested.
Enter Credentials
Enter Name: Choose a name of your choice for the credential to be added.
Enter Username: Enter a Username for the credential to be added.
Enter Password: Enter the password for the credential to be added.
How to generate the AutoTask password refer to this link https://kb.clouddepot.com/knowledge/autotask-api-user-credentials.
Please use the custom ( Internal Integration) option for CyberCNS
4. Enter API Integration Code: Enter the API Integration Code for the credential to be added.
The below image is used to add the API User with an Email address, Username, and password. Here the Tracking Identification Number is identified as Integration Code.
So here the Tracking Identification Number is used as Integration Code while adding the Auto Task Credential.
To get notifications from Webhook, Please click on https://ww1.autotask.net/help/developerhelp/Content/APIs/Webhooks/WEBHOOKS.htm and tick the check box.
Enter the Email to receive the notifications from Webhook. When manually closing the ticket in the AutoTask portal, it will also close in the CyberCNS portal. Please grant the Create webhook permission to the API user, and select the checkbox.
Likewise, multiple credentials can be added using the '+' sign.
Once all the above details are provided, SAVE the data.
Default Template
When the credentials are added, an option to add the Default Template is seen.
Instead of selecting a template each time for ticket creation in Integration action, we can add a default template here for a that specific integration.
Click on Default Template post credentials are added successfully.
In the Default template, choose the Service Board ID, Service Types, Service subtypes, Service Items, Select status for Ticket Creation, Select a status for Ticket Closing, and Priority Id.
Click on Save once all the fields are selected.
When the template is added successfully, under the credentials section next to the credential name will get a green tick mark() to indicate it is using a default template.
Company Mapping
In Company Mapping, there are three rules to be set. Those are Event Set, Integration Profile, and Manage Company Mapping.
Under the Event Set, click on +Add to add the Alert Rule.
Here a set of Events are to be set to get notified. Those events are categorized under Agent, Company, Asset, Ports, Remediation, and AD Audit.
Enter the Event Name and select the category of an Event as required.
Every category has a set of events/ alerts under them which needs to be selected as per requirements.
e.g. Asset category has below-listed alerts and selection of all or any is allowed.
The Ports category has the below-listed alerts, and the selection of all or anyone is allowed.
For the Remediation category, selection of Remediation by Company OR Remediation by Assets OR Remediation by Product, Remediation by Asset and Product is allowed, and Enable Remediation for Critical and High Severity(Select any one of them).
To Enable Tickets for Remediations with EPSS, one of the Remediation plan need to be selected from the Remediation Group.
For the Vulnerability & Azure error category, the below-listed alert, and selection is allowed.
For the AD Audit category, the below-listed alerts are available and selection of all or any is allowed. (Make sure to select the needed as it will create tickets based on the events).
For Azure AD Audit and Unquoted Service Path, the below-listed alert, and selection is allowed.
For the Reports, the below-listed alerts and selections are allowed.
Choose the listed events to set up CyberCNS Alerting as required.
Choose the Vulnerability alerting events that should be notified on selected channels.
Once the above details are selected, click on Save.
There is an option to Edit, Delete, and Set as default for the Notification Rules using the Action column. The listed Notification Rule can be edited and deleted if needed.
For setting the created Event as the default, select the option Set as Default.
To confirm the Set as the default action column, select Yes or No in the confirmation dialogue box.
Once the event is set to default, under the Is Default column can see the status of it.
Integration Profile
Users will be able to set notification rules from integrations right away for conditions listed under it.
Under the Integration Profile, click on +Add to add the Integration Rule.
Enter the Name, Select the credential, and fill out all of the required fields in the Integration Parameters.
Once the below details are provided, click on Save.
There is an option to Edit, Delete, and Set as default under the Integration Rules using the Action column. The listed Integration Rule can be edited and deleted if needed.
For setting the newly created Event as the default, select the option Set as Default.
To confirm the Set t as the default action, select Yes or No in the confirmation dialogue box.
Manage Company Mapping
Click on Manage Company Mapping.
Choose AutoTask Credentials from the dropdown and click on + Add to add Integration Mapping for specific companies.
In New Company Mapping, choose the AutoTask Credential which is listed. (These are to be added under the Integration section for AutoTask).
One of these two options could be selected
Import Companies from AutoTask:- To import multiple companies listed under AutoTask to CyberCNS at a time.
Map Existing Company to an AutoTask company:- To map an existing company in CyberCNS to the existing company under AutoTask company.
To import multiple companies from AutoTask, choose Import Companies from AutoTask, and click on Next.
In the below image, the company can be searched using the search option given.
The Page Size shows the rows per page that can be displayed for search results and the Page shows the number of pages that can be displayed for a search result.
Click on Get Companies to show the list of the companies as requested in the search column.
Once searched as per the choice or the requirement it displays the search result in the Select Companies dropdown.
In case you want to manually search the company, you can simply click on the drop-down of AutoTask Companies and it will list all companies available under AutoTask.
Once the company is selected, it shows as an additional entry below. It can be deleted or click on Next to proceed further.
In case the local company is already created in CyberCNS and is to be mapped with ConnectWise company, then select Map Existing Company to AutoTask company and click on Next.
As shown in the below image, select the Local company( CyberCNS) by using a dropdown or with the search bar as per the requirement so it will map the companies accordingly.
Please choose/select the Create Ticket option only if you need the tickets to be generated using AutoTask integration.
Now click on Finish to import all the selected AutoTask companies. This completes importing companies from AutoTask.
To push the configuration of an asset to be pushed to Autotask, select Enable Configuration from the section here before saving the company mapping.
If Enable Configuration is selected, the assets configuration information captured in ConnectSecure is automatically pushed by creating a new configuration under the Autotask mapped company.
Please choose/select the Enable Configuration option only if asset configurations are required under Autotask.
To get the alerts select the Event Set and Integration Profile and click on Add. Multiple alerts can be added.
Click on +Add to Map Existing Company to AutoTask company.
In case the local company is already created in CyberCNS and is to be mapped with AutoTask company, then select Map Existing Company to AutoTask company and click on Next.
As shown in the below image, select the Local company and AutoTask company by using a dropdown or with the search bar as per the requirement.
Once the company is selected click on + and ‘Add' to select the company map of all the selected AutoTask companies.
If the Enable Configuration option is selected, the asset configurations that have been set up using ConnectSecure will be automatically pushed by creating a new configuration under the Autotask mapped company.
To get the alerts select the Event Set and Integration Profile and click on Add. Multiple alerts can be added.
Please choose/select the Enable Configuration option only if asset configurations are required using Autotask integration and click Add.
Please choose/select the Create Tickets Notification option only if no notifications are required using this integration.
Once the Autotask alerts are enabled, select the Event Set, and the Integration Profile, and click on Add to the record.
Delete the Integration profile in case not required using the bin icon as shown below.
Once all the fields are provided, Click on Finish to map all the selected AutoTask companies.
Once the company mapping is done it will create the configuration items per company assets in the Autotask CRM> Configuration items and show the updated asset details, newly added asset details, and Last scan times.
If the company mapping has been deleted from our CyberCNS end the configuration items will show as inactive.
Selected companies are shown in the image below, along with details such as Existing Company Name, Company Name, and Mapped Date.
Here click on Copy Settings to Copy the company mapping settings to other company mappings.
To copy the settings, select the desired company mappings and click on Update. This will copy the event set, integration profile, and ticket creation fields from the source company mapping to the selected target company mappings.
Using the Action column, you can Edit and Delete the integration mapping. Any mapping can be removed as and when necessary.
This completes the documentation of AutoTask Integration.