CSV - Send to Share

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

• Enforcement Set name (required) - The name of the Enforcement Set. A default value is added by Axonius. You can change the name according to your needs.
• Add description - Click to add a description of the Enforcement Set. It is recommended to describe what the Enforcement Set does.
• Run action on assets matching following query (required) - Select an asset category and a query. The Enforcement Action will be run on the assets that match the query parameters.
  • A query only returns results for the asset type it was created for.
  • Not all asset categories are supported for all Enforcement Actions.
    • See Actions supported for Activity Logs, Adapter Fetch History and Asset Investigation Modules
    • See Actions supported for Vulnerabilities.
    • See Actions supported for Software.
• Action name (required) - The name of the Main action. A default value is added by Axonius. You can change the name according to your needs.
• Configure Dynamic Values - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

Additional CSV Settings

1. Split by asset entities - Select to create a CSV file where each asset on a device is shown as a separate row. This separates each asset as the 'expand' option in the application. It separates each asset by its entity. For example, you will be able to know which values were fetched from each adapter connection.
   a. If supplied, each value on a device or user is shown as a separate row.
   b. If not supplied all values on a device are in the same cell on the CSV file.
2. Split by field values - Choose field value - For complex fields and lists you can create a CSV file where the values of complex fields and lists are represented as separate rows in the file. From the drop-down box select the value that you want to display in the file, 'Tags' for instance. Only fields that have been discovered are available. For example, if you export by Installed Software, you will be able to see each installed Software name and its version.
3. Don't split complex objects into columns - When selected, complex objects appear in a single column in JSON format. By default, each field in a complex object is split into a separate column in the CSV file.
4. Export CSV delimiter to use for multi-value fields (default: Export CSV delimiter to use for multi-value fields field under the System Settings section in the GUI Settings) - Specify a delimiter to separate between values within the same field of an exported CSV file, otherwise the delimiter defined in Export CSV delimiter to use for multi-value fields is used.
5. Maximum rows (default: 1048500) - Specify the maximum number of rows to be included in the CSV file. When you set a value here the generated CSV file will include the top x rows, based on the specified values. Otherwise, the generated CSV file will include the default maximum rows, set as 1048500.
6. Include associated devices (only for Vulnerabilities and Software) - For Software and Vulnerabilities queries. Select this option to include the associated devices with the preferred hostname as a predefined field for each software or vulnerability. When you create a CSV file with associated devices (for Vulnerabilities or Software), if the exported query results are larger than the value set under Maximum rows (or the default value of 1048500), an appropriate notice is displayed at the end of the CSV file.

For more details about other Enforcement Actions available, see Action Library.