---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Manage issues

# Manage issues {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

You can measure the effectiveness of your company's risk management program by how
quickly and completely it identifies and reacts to risk and compliance issues.  
Issues can be submitted using two methods, depending on the type of user involved:

* Employees and business users within your company can [self-identify
  an issue and submit it via the ServiceNow®
  Service Portal.](https://servicenow-prod.fluidtopics.net/O1~FzxK3KPHLEDSG~x0XRg "Your employees and business users within your company can self-identify an issue and submit it via the ServiceNow Service Portal. Following submission, a triage issue is automatically created.") Following submission, a triage issue is automatically created and the issue triage process begins.
* GRC users can [manually create an issue](https://servicenow-prod.fluidtopics.net/hN0Bymlo4rbJZj1qqCIQkg "As a GRC user, you can manually create issues to document policy, risk, or audit observations, or to accept any GRC problems. You can also identify the source of the issue to help analyze and classify the issues.") from within their instance to document audit observations and remediations, and compliance and risk issues.

{#manage-issues-common-core__ul_ovs_shy_b4b}  
Hinweis:  
Various types of issues can also be automatically generated under the following conditions (these types of issues are not triaged):

* Control issue: Created when a control attestation is completed, indicating that the control is not implemented, or when an indicator fails.
* Control test issue: Created when a control test is closed complete with the control effectiveness set to Ineffective.
{#manage-issues-common-core__ul_bdl_d4p_b4b}

## Goals of issue management {#manage-issues-common-core__section_z4y_v3y_b4b}

The goals of issue management include:

* Eliminating noise​.

* Consolidating duplicate issues​.

* Focusing on issues that expose the organization to the greatest risk.

* Identifying and prioritizing remediation actions​.

* Identifying new issues across the business operations​.

* Analyzing operational weakness in policies, processes, and controls​.

{#manage-issues-common-core__ul_bwk_vf3_b4b}

## Issue management workflow and life cycle {#manage-issues-common-core__section_mnf_1jy_b4b}

By remediating issues, controls can be kept compliant, and risk can be mitigated. The Issue Management workflow and life cycle are illustrated and described here.Abbildung : 1. Issue Management workflow {#manage-issues-common-core__table_exh_nm3_b4b__entry__2}

| Stage | Description |
|-|-|
| Issue intake | As described earlier, issues can be submitted using two methods, depending on the type of user involved: * Employees and business users within your company can self-identify an issue and submit it via the ServiceNow® Service Portal. Following submission, a triage issue is automatically created and the [issue triage process](https://servicenow-prod.fluidtopics.net/5lPA5gW0ZRPxH3qJhxgO3Q "After an issue has been identified and submitted by employees or business users via the Service Portal, the issue triage process begins. The actual problem is identified and assigned to the appropriate owner for prioritization and resolution.") begins. * GRC users can [manually create an issue](https://servicenow-prod.fluidtopics.net/hN0Bymlo4rbJZj1qqCIQkg "As a GRC user, you can manually create issues to document policy, risk, or audit observations, or to accept any GRC problems. You can also identify the source of the issue to help analyze and classify the issues.") from within their instance. These types of issues are not triaged. {#manage-issues-common-core__ul_ccd_hjy_b4b} |
| Investigate the issue | During the investigation phase, it is determined whether the issue requires additional study. If a triage is being performed, the triage issue is assigned to a triage team for analysis. The triage team may request more information from the issue creator. The team can also optionally send the issue to the compliance manager, risk manager, or triage manager with a triage result. |
| Remediate the issue | After the team has confirmed the issue, the necessary steps to remediate it are performed. If a triage was performed, the triage issue is converted into an actual issue or risk event. The team may also decide to track the issue as a recommendation or close it as a non-issue. |
| Review and monitor the issue | Prior to closing the issue, the policy owner reviews and approves it. The review also allows the organization to: * track past due tasks * benchmark issue timelines * identify where losses could have been mitigated * reduce gaps in the future {#manage-issues-common-core__ul_bc2_whj_b4b} |
[Tabelle : 1. Issue Management life cycle]

{#manage-issues-common-core__table_exh_nm3_b4b}
* **[Issues in the Workspace](https://servicenow-prod.fluidtopics.net/S61MWJaUyHVVkjH~Wjm1vw)**   
  You can track all your issues or one specific issue from the Workspace. Issues are listed under the Issues module in the list view of the Workspace.
* **[Group issues in the Workspace](https://servicenow-prod.fluidtopics.net/rYfM8okMoGZrYsisCNmGzg)**   
  Group issues within your workspaces to organize and manage related issues. Grouping similar issues can streamline your workflow and save time.