DeepSurface: Exporting

Documentation
Installation Guide
Overview
Let DeepSurface Host For You
Getting Started
System Requirements
Self Hosted Quick Start - Installing to Cloud Platforms
Self Hosted - Installation Using an OVA
Registration, Package Installation, and Initialization
First Steps After Initialization of the Console
Deployment Options
Main and Subordinate Consoles
Agent-Based Deployment
User Managed Scan Deployment
Credentialed Scanning Deployment
Mixed Environment
Deployment Tools
Active Directory Group Policy
Microsoft Endpoint Configuration Manager (part of InTune)
Tanium Deploy
HCL BigFix
Ivanti
Virtual Machines
VMWare
Virtual Box
VirtualBox Guest Additions
AWS EC2 (BYOL)
AWS EC2 (Usage Based)
Azure Cloud
Google Cloud
Additional Items to Consider
Main Console Server Certificates
LDAP
TOFU
Clock Sync
DeepSurface Commands
Multiple Vulnerability Sources
API Documentation
User Guide
Reporting
Dashboards
Exports
Risk Insight
Hosts
Patches
Vulnerabilities
Vulnerability Instances
Users
Remediation Workflow Manager
Plans
Settings
Integrations
Workflow
Exporting
Accepted Risk Plans
Accepted Risk Workflow
Explore
Model
Paths
Activity
Tasks
Configuration Alerts
Scan Logs
Notification Settings
Scanning
Status
Agents
User Managed
Credentialed Scanning Settings
Credentials
Scan Groups
General Settings
Cloud Scanning
Network Connectivity
Subordinates
Vulnerability Sources
Setup
Sensitive Assets: Polices
Sensitive Assets: Manual
Admin Settings
SMTP Settings
Certificates
Outbound Proxy
Authentication Providers
Users
Tags
Integrations Guide
Vulnerability Sources
CrowdStrike Spotlight
SentinelOne
Carbon Black Cloud
Microsoft Defender for Endpoint
Wazuh
Lansweeper Cloud
Nessus API
Tenable.io API
Security Center/Tenable.sc API
Rapid7 InsightVM API
Qualys API
Nozomi Guardian
Eclypsium
AWS Inspector
Remediation
Jira Software
Tanium (BETA)
Authentication Providers
LDAP (Active Directory)
SAML (Azure Active Directory)
SAML (Google)
SAML (Okta)
PAM
CyberArk
Delinea (Thycotic)
Microsoft LAPS
Security Guide
Firewall Configuration
Base Network Requirements
Agent Network Requirements
Credentialed Scanning Network Requirements
API Network Requirements
How DeepSurface Scans Work
Domain (LDAP) Scanning
Host Scanning Routine
Reasons for the Administrative Access Requirement
Endpoint Protection Considerations
Other Items
Scope of Data Storage and Retention
IPS/IDS Considerations
Logging
Resetting the DSADMIN password
Product Information
Changelogs
Open source Licenses
End User License Agreement (EULA)

DeepSurface will automatically track progress on and keep track of all of your remediation tasks, but we understand that users also want the ability to export tasks as tickets to their desired ticketing solution of choice. We will be regularly adding more direct API integrations with third party ticketing services, but for now we offer a few different solutions for getting tasks out of DeepSurface. In order to initiate any of the export options, first navigate to Remediation > Plans and find the remediation export menu for any active remediation plans:

You will first be given the choice of whether you would like to simply export the remediation plan as an Excel file, or if you would like to export to a ticketing integration. If you simply want to export everything as Excel, select the first option and a report will be generated for you and a notification will direct you to where you can download it from DeepSurface and no further input is necessary.

However, if you would like to export to a ticketing service and you have already configured at least one integration in our system, then DeepSurface gives you a rich interface to export each task as its own ticket, each to the same or completely completely different ticketing system. You will be able to export all or just some of the tasks, and you can even re-export a previously exported task, even to a compltely different integration. To begin, select the "Export to Ticketing" option and you will be greeted with an interface that looks something like the following:

If you have already configured export preference for your users, then tasks will already have that owner's preference pre-filled. At this point, if everything looks correct, you can simply click "Export [N] tickets" and DeepSurface will begin to export each task to its destination. It may be the case though, that some tasks do not have owners, some owners have not yet had their preferences set, or you may want to override a given preference this one time only. In that case, you have the ability to change any of those options here before completing the export. Changing an owner for a ticket will automatically apply all of that owner's exporting preferences for your convenience, but any of the pre-filled options can can be overridden. Note overridding any of the export destination or options within this interface does not persist any changes or permanently override any user preferences, it simply lets you override for this particular export. There are some restrictions and requirements when choosing different options that you should be aware of.

• If a task has no owner, the "Email Owner Directly" option in the Export Method is obviously not available considering there is no user to email.
• A task is allowed to have no owner and in that case, the ticket will be left "Unassigned" if exported to Jira, or simply be emailed to the destination email address like any other task if exported to a "Ticketing via Email" integration.
• If a task does have an owner, an email address must be present if the "Email Owner Directly" option is selected. Otherwise, much like if there is no owner, the ticket will be created as "Unassigned" for jira or simply sent to the destination email for an email integration.