CSV

The CSV adapter imports .csv files with inventory information including devices and serial numbers, users, and installed software data.

Parameters

1. File contains users information - Select this option to imports the file as a list of users instead of devices. See the below section for fields required in a Users Information File.

2. File contains installed software information - Select this option to import an installed software list instead of devices. See the below section for fields required in a Software Applications File.

3. File name (required) - Provide a unique name for the adapter connection. The value supplied here is populated in the File name field for the data supplied by a specific adapter connection.

   Note:

   The specified File Name is not required to be the actual imported file name. This field is an identifier for use in the Query Wizard.

4. Select file source - The CSV adapter supports upload of files from a variety of file sources. The parameters you need to enter change according to the file source that you select. The default is Upload File. Refer to File Sources for full details.

5. Encoding (optional) - Specify a specific file encoding or let Axonius encode it. When you enter an encoding type Axonius tries to encode the CSV file based on the specified file encoding type (for example, utf-8) for this connection. Otherwise Axonius tries to encode the CSV file based on common file encoding types for this connection.

6. Ignore illegal characters - Select this option to ignore illegal characters during the data import. An illegal character is any character that cannot be translated in the specified file encoding. If you do not select this option, and an illegal character is found, the entire data import fails.

7. Verify SSL - Select whether to verify the SSL certificate of the server against the CA database inside of Axonius. For more details, see SSL Trust & CA Settings.

8. HTTPS Proxy (optional) - Connect the adapter to a proxy instead of directly connecting it to the domain.

9. HTTPS Proxy User Name (optional) - The user name to use when connecting to the value supplied in Host Name or IP Address via the value supplied in HTTPS Proxy.

10. HTTPS Proxy Password (optional) - The password to use when connecting to the server using the HTTPS Proxy.

11. Custom prefix for dynamic fields (optional) - Specify a prefix to be added for dynamic fields. A dynamic field refers to any field that is not part of an asset default field. This can assist you in identifying such fields.

12. Multi-value fields delimiter (optional) - Specify a delimiter to separate between values within the same field in the imported CSV file. When you specify a delimiter Axonius considers fields that contain the specified delimiter as multi-value fields. For example, ';'. Otherwise Axonius considers all imported fields as single-value fields.

13. File Type - Select the type of file uploaded, either CSV, or Excel Spreadsheet. When you select "Excel Spreadsheet", the adapter supports .xls , and.xlsx files, and pulls in the entirety of the first Worksheet as if it were a CSV table. Functionality for tables uploaded from Excel is the same as for CSV files.

To learn more about common adapter connection parameters and buttons, see Adding a New Adapter Connection.

File Sources

The CSV adapter supports upload of files from a variety of file sources. The parameters you need to enter change according to the file source that you select. The default is Upload File.

Upload File

Use Upload File to import a local CSV, JSON, or XML. file.
When you select Upload File the following parameters are available:

Upload File (required) - select a local CSV file to import.

Microsoft OneDrive

Upload a file from Microsoft OneDrive.

1. Azure Cloud Environment (optional) - Select your Microsoft Azure or Microsoft Entra ID (Azure AD) cloud environment type.
2. Microsoft OneDrive Tenant ID (optional) - Microsoft Entra ID (Azure AD)​ ID. Used to authenticate Microsoft OneDrive through Microsoft Entra ID (Azure AD) and use the Graph API.
3. Microsoft OneDrive Client ID - The Application ID of the Axonius application.
4. Microsoft OneDrive Client Secret, Microsoft OneDrive OAuth Authorization Code, Microsoft OneDrive Redirect URI - Enter these parameters when multi-factor authentication is used in the Azure/Microsoft Office account. To use this option an OAuth Authorization Code must be created. The OAuth Token/Code Procedure will use the following URL

https://login.microsoftonline.com/[[TENANT_ID]]/oauth2/v2.0/authorize?client_id=[[CLIENT_ID]]&scope=https://graph.microsoft.com/.default&response_type=code&redirect_uri=[[REDIRECT_URI]]&response_mode=query
5. Path to resource (URL/Folder path) (optional)

• If a folder path is supplied:
  • The remaining necessary parameters for Microsoft OneDrive must be provided.
  • The path must be separated by forward slashes.
  • For personal files on Microsoft OneDrive, use the path relative to 'My files'. For example, the folder path for "My files > Documents > Axonius > file.csv" should be Documents/Axonius/file.csv).
  • Use the URL of the file when opened in the browser (recommended). Alternatively, use the Copy Link from the file (this method will work, but, the link will expire and will need to be regularly updated).

6. Username for remote resource and Password for remote resource - Username and password for the remote resource. You cannot use these parameters when multi-factor authentication is used in the Azure/Microsoft Office account.

When uploading files from Microsoft OneDrive, and using OAuth authentication the value supplied in Microsoft OneDrive Client ID must have Files.Read.All delegated permissions in the Azure application in order to to fetch files.

When uploading files from Microsoft OneDrive, the value supplied in Username for remote resource (Share/URL) must have Files.Read.All permissions to fetch files.

Microsoft Azure

Upload a file from a container on Azure.

1. Azure Storage Container Name (required) - The name of the container on Azure where the CSV file is located.
2. Azure Connection String (required) - The connection string that includes the authorization information required to access data in the Azure Storage account. You can find the connection string in the Azure portal under Storage Accounts -> [Account Name] -> Access Keys, where [Account Name] is the specific storage account that contains the CSV files to be ingested into Axonius. Copy the entire connection string and paste it into this field.
3. Azure Blob Name (required) - The Azure Blob Name.

Amazon S3 Bucket

Upload a file from an Amazon S3 Bucket.

1. Amazon S3 bucket name (required) - The name of the S3 bucket from which to fetch the file.
2. Amazon S3 object location (key) (required) - The location within the S3 bucket from where the file can be fetched.
3. Amazon S3 Use EC2 Attached Instance Profile
   • If enabled, Axonius uses the EC2 instance (Axonius installed on) attached IAM role / instance profile.
   • If disabled, Axonius uses the supplied account details in the AWS Access Key ID and AWS Access Key Secret.
4. Amazon S3 Access Key ID and Amazon S3 Secret Access Key (optional) - The credentials used to access the S3 object.
5. Amazon S3 Region - The Amazon region on which the S3 bucket is located.
6. Amazon S3 Interface VPC Endpoint - Custom VPC endpoint.
7. Amazon S3 directory (default: false). - Select this option to show that the object specified in object loction is a directory.

Box Platform

Upload a file from Box Platform.

1. Box Platform private key configuration file (required) - The private key configuration file that provides the Required Permissions to fetch assets. This JSON authentication file must have permission to read/download the specified File ID. In order to fetch files from Box Platform both of these settings must be configured.
2. Box File ID (required) - The ID of the Box file. The ID for any file can be determined by visiting a file in the web application and copying the ID from the URL. For example, for the URL https://*.app.box.com/files/123 the file_id is 123. Refer to Box Platform documentation for more information

URL/FTP

Supply a URL or FTP from which to fetch the file.

1. Path to resource (URL) (required) - Specify an HTTP(S) URL or FTP URLwhere a file can be fetched for this connection.

• For HTTP(S) URL
  • The endpoint must support the HTTP GET method.
  • All URLs must start with HTTP:// or with HTTPS://
• For FTP URL
  • All URLs must start with FTP:// or with SFTP:// or with FTPS://
  • The default port for each method is as follows:
    • FTP: 21
    • SFTP: 22
    • FTPS: 990
    • A custom port can be specified in the supplied path, for example: ftps://my.host.in.axonius.com:21/path/to/file.ext

2. Username for remote resource and Password for remote resource - Username and password for the URL. These settings may be required if the "ubuntu" user on the Axonius system does not have access to the URL. The username and password are used for BASIC authentication of this connection.

3. Additional HTTP headers (optional) - Specify additional information to pass with the HTTP request (for example {"Accept": "text/csv"}).

SMB Share

Upload a file from an SMB share path.

1. Path to resource (SMB) (required) - Specify an SMB share path where a file can be fetched. This path must include the file name and must start with double-backslashes ("\\").

2. Username for remote resource and Password for remote resource (optional) - Username and password for the SMB share. These settings may be required if the "ubuntu" user on the Axonius system does not have access to the SMB share. The username and password are used for authentication of this connection.

3. Suppress NetBIOS name lookup - Select this option so that Axonius does not verify the server's name via NetBios. This option must be enabled in order to use wildcards in SMB file names. When this setting is enabled, the path must include the server's full NetBIOS name in the following format:
   \\<full_server_NetBIOS_name>\path\to\file.ext

• Wildcards are supported in file names as follows:
  • Suppress NetBIOS name lookup must be enabled.
  • The asterisk * wildcard matches any sequence of characters (0 or more, including NULL characters).
  • The ? wildcard matches a single character (or a NULL at the end of a file name).
  • The matching file names are sorted by file creation time.
  • If multiple files match the wildcard search, the most recently created file is selected.

Google Sheets

You can upload a file that was previously fetched by the Google Sheets adapter.

1. Service account JSON credentials (required) - A JSON Key Pair associated with a service account that has the Required Permissions to fetch assets. Click Upload to upload a file containing the binary contents of the keypair file (JSON) generated for the service account credentials.
2. Spreadsheet ID (required) - The Spreadsheet ID (gathered from the link to the spreadsheet)
3. Data range (A1 or R1C1 notation) (required) - A1 or R1C1 notation of the data range to read. Example: 'My Worksheet'!A1:Z99 to pull cells A1 to Z99 from the worksheet “My Worksheet”. Always use single-quotes when specifying a worksheet that contains spaces in the name. A data range and a worksheet range must be specified as an absolute path.

Advanced Settings

1. Set Time Zone - Set the time zone of date fields fetched with this adapter. Default is UTC.
2. Use fetch time for Last Seen - Select this option to set that all entities (devices and users) fetched by this adapter have their Last Seen set to the time the entity was fetched (fetch_time).
3. Additional primary keys for software files - Enter additional primary keys to use when correlating installed software CSV files. By default, only "hostname" is used as a primary key. Contact Axonius support before you use this option.
4. Do not add filename to entity IDs - By default Axonius adds the filename to the ID of the entities created by the CSV file (device ID etc). Select this option to not add the filename to the entity ID.

APIs

When uploading files from Microsoft OneDrive, Axonius uses the List FIles Shared With Me - OneDrive API - OneDrive dev center.

If multiple file options are added to a 'file-based' adapter, what file is imported?

If multiple import file import types are provided in the CSV adapter (or for other file-based adapter), they are imported in the following order:

1. Path to resource (SMB/URL/Folder path)
2. Amazon S3 Bucket
3. Uploaded file

The file content is determined based on the following order:

1. User assets - If File contains users information is selected
2. Installed software list - If File contains installed software information field is enabled.
3. Device assets - If none of the options above is selected, the CSV is assumed to be a device CSV. If a device exists more than once in a CSV file, only the first device found is used.

Which fields are required for each Import Type?

For single value fields the following delimiters are supported:s , , ; and \t .

Which fields are imported with a devices file?

The following data is imported as common data fields while any other data in the CSV/JSON/XML is exclusively be Adapter Specific data.

Which fields are imported with a users file?

The following data is imported as common data fields while any other data in the CSV/JSON is exclusively Adapter Specific data.

Which fields are imported with a software applications file?

The following data is imported as common data fields while any other data in the CSV/JSON is exclusively Adapter Specific data.
In order for vulnerabilities to be parsed from the CSV adapter, the MINIMUM requirements are:

• The adapter is configured with "File contains installed software"
• The file has at least the following headers:
  • Hostname (or any of the headers supported as hostname)
  • Software Name (header must be present, though may be empty on a row)
  • CVE ID

The other headers (or data in a row for those headers) are optional for the purposes of parsing vulnerabilities

Example CSV File

For an example of a CSV file, download the following zipped csv:

CSVExamples.zip