Any user with access to a sheet can upload a CSV of assets to that sheet. There are a lot of fields for hosts, and none of the fields is specifically required when you manually enter host data. However, using the CSV upload feature does require some of the host attributes. For optional fields, you should not put a space in the blank field, but leave it completely empty. Extraneous spaces can cause errors on certain fields.
Unlike the other CSV uploads, the host CSV upload does not support comments in the CSV file.
All fields are optional unless otherwise stated.
| Field Name | Details |
|---|---|
| names | Required |
| description | A description of the host |
| ips | Required |
| macs | Required |
| aco | AMP Communications Outlet; you can use this to track a physical port where a host is connected to your network. If you’re not using ACOs, you can specify any string here that’s meaningful to you. |
| site | Site where this host is located |
| building | Building where the host is located |
| floor | Floor where the host is located |
| room | Room where the host is located |
| location_notes | Sometimes Required |
| off_premises | Is the location of the host outside of organization premises? “true” or “false” (Defaults to false) |
| inventory_tag | String with additional information about the host |
| serial | String representing the host’s serial number |
| system | Deprecated field representing system type |
| classification | Numeric value representing classification. Using the default configuration, “1” (Confidential), “2” (Protected), “3” (Published), “s” (Surplus), and “u” (Unknown). |
| categories | List of categories within the parent classification. Using the default configuration, the options include health, financial, ferpa, ssn, research, critical_to_unit and critical_to_organization. If the list contains more than one entry, enclose in quotes. |
| priority | Field indicating the importance of the host. Using the default configuration, the options are “c” (critical), “i” (important/non-critical), “n” (normal), and “u” (unknown). |
| system_type | High level description of the host. Default possible values include “ca” (Classroom A/V), “dt” (Desktop), “in” (Infrastructure), “lt” (Laptop), “pd” (Personal Device), “ph” (Phone), “pr” (Printer), “se” (Server), “ot” (Unknown/ Other), and “vs” (Video Security). |
| encrypted | Is the device encrypted? “true” or “false” |
| free_fields | A comma-separated list of valid |
| owners | List of owning users or org units |
| it_contacts | List of users or org units that are considered IT contacts for this host |
| users | List of people or org units that use the host |
If any location element is specified, then the entire location must resolve to a pre-existing location already in Isora GRC’s database. Otherwise all location fields should be left blank.
If off-premises is set to true, then you also must include location_notes.
This field contains configurable picklist label values. Depending on your configuration, the options present may differ from the default configuration. For more information, see Customizable Picklist Label Values
Free fields can be used to specify additional attributes that are not found in the default host attributes. These can be anything you care about. One benefit of using free fields is that you can key in on those values when searching hosts, so you can easily find hosts that match your given attribute, just like you can search on built-in attribute values. All of the values in free fields are considered to be strings. Here is an example free_fields entry (note the use of quotation marks to encase the entire field; in CSV files commas are used to separate fields, so if you have a field that includes commas, the whole string must be quoted):
"purchasinggroup:depA,osType:Unix,refreshcycle:3"If the list contains more than one item, then the entire field should be quoted. Individuals should be specified by username, prefaced with a “u:” and org units specified by code and prefaced with “o:” For example, to list user Bob Kovack with username bobkov and org unit Accounting with code ACC, the field should contain:
"u:bobkov, o:ACC"All individuals specified must have existing user accounts in Isora GRC and all org units specified must already exist in Isora GRC’s list of org units.