---
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


---

# Reporting incidents or security incidents for multiple regulations

# Reporting incidents or security incidents for multiple regulations {#ariaid-title1}

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

You can now report incidents or security incidents for multiple regulations for various legal entities in Digital resilience incident reporting. The application streamlines operations by automating tasks, migrating data, helping to prevent duplicates, and verifying accurate reporting.

## Automated reporting workflow {#reporting-for-multiple-regulations__section_wtp_5gn_3hc}

Starting with Digital resilience incident reporting, release 21.1.1, the application uses an automated reporting workflow to generate reports within regulatory reporting timelines:

* Regulatory reporting assessment of IT incidents
* Initial Report (within 24 hours)
* Intermediate Report (every three days until resolved)
* Final Report
{#reporting-for-multiple-regulations__dri-module-in-ws_ul_mh2_kpr_12c}

You can complete these tasks and generate reports in Microsoft Word format, as required by regulatory authorities for analysis.

## Case creation by adding entities {#reporting-for-multiple-regulations__section_icd_qdn_3hc}

Digital resilience incident reporting is used for incident reporting and assessment for legal entities or other objectives according to regulations. You can now add entities to an incident, which automatically
create a Digital resilience incident reporting case.

For information on setting up the entities, see [Set up entities for the targets](https://servicenow-prod.fluidtopics.net/N8Cadu0xNLYS9tpVQ07IoQ "Set up an entity record in the instance and map it to an incident or security incident. You can map one or multiple entities to the selected incident.").

## Sequence of action tasks {#reporting-for-multiple-regulations__section_udn_1fp_3hc}

The sequence of action tasks in the Digital Resilience Incident Reporting (DIR) process, as outlined in the document "Digital resilience incident reporting for multiple regulations," is primarily driven by template configurations.
Here's an overview of how action tasks are created and sequenced:

Action task creation and sequence are explained:

1. Initial action task creation: When a DIR case is created (triggered by sources like incidents), the system automatically generates action tasks. For example, the template shown creates the 'Regulatory reporting assessment of IT incidents' action task.
2. Template configuration: Templates are configured to create specific action tasks. For example, the 'DRI Initial report' template, which runs only once, automatically creates the 'DRI Initial report' action task when the regulation's reporting status changes to 'Reportable.' Administrators can then update its name, due date, and termination conditions.
3. Closure of action tasks: When the 'DRI Initial report' is closed, the 'DRI Intermediate report' action task is created. If the 'DRI Initial report' task remains open, the system creates the 'DRI Intermediate report' action task every three days until the DIR case is closed or canceled, or the source incident is closed.
4. Closure of incident: When the source incident or security incident is closed, the "DRI Final report" action task is created, with a due date of 30 days.
5. Automated action task generation: These template configurations enable automatic creation of action tasks, as previously demonstrated. as administrators, you can create multiple action tasks and tailor their sequence to meet your organizational requirements and applicable regulations.
6. Completion of action tasks: Action tasks are completed according to the conditions defined in their templates, promoting efficient process management and required task completion.  
   Hinweis:  
   As administrators, you can customize the configurations available with the base version or add additional action tasks as needed.

{#reporting-for-multiple-regulations__ol_n4r_1fp_3hc}

For information on mapping regulations and setting up action task templates, see [Map regulations to the entities](https://servicenow-prod.fluidtopics.net/F65_By~zCyoNy8Y9~H7mEQ "Map single or multiple regulations with the entity linked to an incident or security incident.") and [Set up action task templates in Regulatory agency profile](https://servicenow-prod.fluidtopics.net/S02u9pfHtSILuFq95unT4w "Set up action task templates in the Regulatory Body Management Agency Profile [sn_reg_body_mgmt_agency_profile.list] table. Verify that the action task configurations (with Smart Assessment Smart Assessment template configurations) for the selected regulation are correctly set up.").

For information on completing action tasks, refer to [Complete action tasks and report incidents associated with regulations](https://servicenow-prod.fluidtopics.net/B25szPkV5HZtsxY9z17apA "Report incidents or security incidents associated with multiple regulations for various legal entities. The automated workflow generates regulatory reporting assessments of IT incidents, and Digital resilience incident (DRI) Initial, Intermediate, and Final reports, all within regulatory timelines. Complete the action tasks and generate reports in Microsoft Word format, as required by regulatory authorities for analysis.").