Importing Assets & Risks

CSV Asset Import – Field Descriptions and Guidelines

File Requirements:

• Important: When importing assets via CSV, your CSV file must include the following headers that match the field names (e.g - name, description, owner, environment_tags, compliance_tags, other_tags).

• The max file size allowed for CSV import is 500 KB.

The following fields should be provided in each row:

1. Name (Required): A short name or title for the asset.

   1. The name must be between 3 and 50 characters long

   2. Can only contain letters, numbers, underscores (_), hyphens (-), and spaces.

   3. Example: Asset Name 1

   4. Note: If the name contains commas, it must be enclosed in double quotes (" "), for example: "Asset Name, Phase 2".

2. Description (Required): A detailed description of the asset.

   1. This should be between 3 and 255 characters long

   2. Can include letters, numbers, underscores (_), hyphens (-), commas, slashes (/), periods, and spaces.

   3. Example: This is my asset description with item 1, item 2, and item 3.

   4. Note: If the description contains commas, it must be enclosed in double quotes (" "), for example: "This asset is critical, high priority".

3. Owner (Required): The full name of the person or department responsible for the asset.

   1. Must be between 3 and 50 characters long

   2. Can only contain letters, numbers, underscores (_), hyphens (-), and spaces.

   3. Example 1: John Doe

   4. Example 2: DevOps Team Lead

   5. Note: If the owner's name contains commas, it must be enclosed in double quotes (" "), for example: "John Doe, Sr".

4. Environment Tags (Optional): Tags related to the environment of the asset.

   1. Multiple tags should be separated by commas.

   2. Example: production, high-priority, external, product1

   3. Note: If a tag contains commas, it must be enclosed in double quotes (" "), for example: "environment1, environment2".

5. Compliance Tags (Optional): Tags related to compliance or regulatory frameworks.

   1. Multiple tags should be separated by commas.

   2. Example: GDPR, SOC2, mysecurityprogram

   3. Note: If a tag contains commas, it must be enclosed in double quotes (" "), for example: "GDPR, EU-Regulations".

6. Other Tags (Optional): Any other relevant tags.

   1. Multiple tags should be separated by commas.

   2. Example: urgent, needs-review

   3. Note: If a tag contains commas, it must be enclosed in double quotes (" "), for example: "critical, urgent".

Tags Handling Guidelines

1. Comma-Separated Tags:

   1. When providing multiple tags, separate each tag with a comma (e.g., production, critical, external).

   2. Note: If a tag contains a comma, the entire tag must be enclosed in double quotes (" "), for example: "production, critical".

2. Normalization:

   • Spaces in tags will be automatically replaced with hyphens (e.g., high priority becomes high-priority).

   • Blank or empty tags are ignored.

3. Validation:

   • Tags must follow a valid format: they can only contain letters, numbers, and hyphens (-).

   • Tags cannot exceed the maximum length (e.g., 50 characters).

Ensure that all fields and tags are properly formatted, with tags separated by commas, and adhere to the character limits. Wrap any field or tag that includes a comma in double quotes to avoid errors during the CSV import process.

Important: The CSV file must include headers that match the field names (e.g., name, description, owner, environment_tags, compliance_tags, other_tags).

CSV Risk Import – Field Descriptions and Guidelines

File Requirements:

• Important: When importing assets via CSV, your CSV file must include the following headers that match the field names (e.g., name, description, owner, environment_tags, compliance_tags, other_tags).

• The max file size allowed for CSV import is 500 KB.

When importing risks via CSV, the following fields should be provided in each row:

1. Type (Optional): The type of risk.

   1. If left blank, the default type will be set to compliance.

   2. Valid types include:

      1. compliance

      2. emerging

      3. financial

      4. it_security

      5. legal

      6. operational

      7. reputational

      8. strategic

      9. If you provide an invalid value, it will default to compliance.

2. Name (Required): A short name or title for the risk.

   1. The name must be between 3 and 50 characters long

   2. Can only contain letters, numbers, underscores (_), hyphens (-), and spaces.

   3. Example: Cybersecurity Risk

   4. Note: If the name contains commas, it must be enclosed in double quotes (" "), for example: "Risk Item1, Item2, Item3".

3. Description (Required): A detailed description of the risk.

   1. This should be between 3 and 255 characters long and can include letters, numbers, underscores (_), hyphens (-), commas, periods, colons, slashes (/), and spaces.

   2. Example: Potential data breach due to outdated software.

   3. Note: If the description contains commas, it must be enclosed in double quotes (" "), for example: "This risk, if unchecked, may lead to data loss".

4. Owner (Required): The full name of the person or department responsible for the risk.

   1. Must be between 3 and 50 characters long

   2. Can only contain letters, numbers, underscores (_), hyphens (-), and spaces.

   3. Example 1: John Doe

   4. Example 2: DevOps Team Lead
      Note: If the owner's name contains commas, it must be enclosed in double quotes (" "), for example: "John Doe, Sr".

5. Environment Tags (Optional): Tags related to the environment of the risk.

   1. To provide multiple tags, separate them using commas.

   2. Example: production, high-priority, external, product1

   3. Note: If a tag contains commas, it must be enclosed in double quotes (" "), for example: "tag1, tag2".

6. Compliance Tags (Optional): Tags related to compliance or regulatory frameworks.

   1. Use commas to separate multiple tags.

   2. Example: GDPR, SOC2, mysecurityprogram

   3. Note: If a tag contains commas, it must be enclosed in double quotes (" "), for example: "GDPR, EU Regulations".

7. Other Tags (Optional): Any other relevant tags.

   1. Use commas to separate multiple tags.

   2. Example: urgent, needs-review.
      Note: If a tag contains commas, it must be enclosed in double quotes (" "), for example: "critical, urgent".

Tags Handling Guidelines

1. Comma-Separated Tags:
   When providing multiple tags, separate each tag with a comma (e.g., production, critical, external).
   Note: If a tag contains a comma, the entire tag must be enclosed in double quotes (" "), for example: "production, critical".

2. Normalization:

   • Spaces in tags will be automatically replaced with hyphens (e.g., high priority becomes high-priority).

   • Blank or empty tags are ignored.

3. Validation:

   • Tags must follow a valid format: they can only contain letters, numbers, and hyphens (-).

   • Tags cannot exceed the maximum length (e.g., 50 characters).

Ensure that all fields and tags are properly formatted, with tags separated by commas, and adhere to the character limits. Wrap any field or tag that includes a comma in double quotes to avoid errors during the CSV import process.

Important: The CSV file must include headers that match the field names (e.g., name, description, owner, environment_tags, compliance_tags, other_tags).