Skip to content
English
  • There are no suggestions because the search field is empty.

How to Create an Issue

A step-by-step guide on how to create issues, assign operational accountability, define impact metrics and evaluate risk profiles

Creating an issue records a security problem in your workspace so it can be owned, tracked, and remediated, and so its effect on your risk and Cyber Resilience is captured automatically. Creating an issue also lets you connect it to the rest of your environment: the risks it contributes to, the controls meant to address it, and the program activities doing the work. This article walks through creating an issue manually. Issues can also arrive automatically from a connected tool (see Getting Started with CyberHQ Connect).

  • From the left-hand menu, go to Catalogue > Issues and click the + button at the top of the register to open the issue form.

  • Under Identification, fill in the issue's details. These establish what the issue is, who is accountable for it, and what it touches.
    • Ref: the issue's reference. Click the regenerate icon in the field to generate an ID, or type your own to match an existing numbering scheme.
    • Source (required): where the issue came from. The list shows the sources available in your workspace, typically the names of your security tools and testing sources (for example JIRA or PenTest), so issues can be grouped and filtered by where they were found.
    • Title (required) and Description.
    • Type (required): the kind of issue, chosen from Threat, Vulnerability, Environmental, Technology, Incident or Other.
    • Owner (required): the person accountable for the issue.
    • Assignee/s (required): the users who will work the issue. Add at least one; you can add several.
    • Created Date: the date the issue was raised. Type it as DD/MM/YYYY or pick it from the calendar. If you are logging an issue that was found earlier, use the date it was actually raised. The register's Days Open column counts from this date until the issue is closed.
    • Due Date: the date by which the issue should be resolved.
    • Status is set to Open for every new issue and cannot be changed until the issue has been created.
    • Business Systems: the business systems the issue affects.

  • Under Treatment Plan, choose the issue's Treatment: Accept, Mitigate, Transfer or Avoid. Treatment is required and is set to Mitigate by default. It records how your organisation intends to handle the issue, appears in the issue's Quickview, and can be used to filter the register. Treatment does not change the issue's status; to close an issue you have decided to accept, use Risk Accepted on its Manage page. Then add treatment actions if you have them. Expand Treatment Actions (the count beside it shows how many actions the issue has), and for each action:
    • Enter a Name describing the work (required).
    • Choose the Assignees responsible for that action. These are set per action, so different people can own different parts of the remediation, separately from the issue's own assignees.
    • Set a Due Date. Since Release 2.7 you can set a due date on each action as you create it, rather than saving the issue and coming back to edit it later, so accountability is captured from the moment the issue is logged.
    • Click Add Action to add the action to the list.
    Actions are still optional, so you can save the issue now and add them later if you prefer. Once the issue is saved, you can also link it to program activities: edit the issue, open the Strategies tab and click Add Automation. This option is locked until the issue has been created.
  • Connect the issue to the rest of your environment. An issue can link to one or more Risks, to Controls from multiple frameworks, and to program activities under Strategies, all at once.

    When you link risks, the issue inherits the category ratings of the highest-rated linked risk, which keeps your numbers consistent and saves re-entering them. Since Release 2.7, controls you link here are automatically carried forward to the relevant risk category, where they are used to calculate risk reduction. Linking controls accurately therefore affects your residual risk scores directly, rather than just recording a relationship.

    Any value you set yourself is marked Manual and is preserved even if the linked risk changes.

  • Rate the issue under the Risk Assessment tab by setting its Impact Level and Likelihood Level, which together determine its severity. You can rate in Basic or Advanced mode, where Advanced gives a more granular rating and a correspondingly larger effect on your risk numbers. A source chip on each category shows whether the rating is Linked Risk, Manual, or Not Mapped, so you always know where a value came from.
  • Optionally, use Other Fields to record anything the standard form does not capture, such as an external team member involved in the issue. Start typing a Name (the box suggests names already used in your workspace), enter its Value, and click Add. Repeat for as many fields as you need. Other Fields are hidden in the register by default; turn the column on through Columns to see them in the table.
  • Click Save. Your issue is created with a status of Open and appears immediately in the Issues Register, where it begins contributing to your risk and resilience figures.

Issues can also be imported in bulk from a CSV (see How to Bulk Upload your Data via CSV) or automatically from a connected tool, rather than created one at a time.

 

With the issue created and linked, it is ready to be worked through to resolution. See How to Manage an Issue for the status workflow and day-to-day management.