--- title: Reporting incidents from SOW and SIR Workspace in DRIR description: High-impact, high-urgency incidents created or marked as high priority in the SOW of Incident Management or SIR Workspace of Security Incident Response are classified as major incidents. These major incidents are logged and reported in the Digital resilience incident reporting application. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/governance-risk-compliance/integration-with-incident-management.html release: australia topic_type: concept last_updated: "2026-03-12" reading_time_minutes: 2 breadcrumb: [Manage, Using Digital resilience incident reporting, Manage, Operational Resilience, Governance, Risk, and Compliance] --- # Reporting incidents from SOW and SIR Workspace in DRIR High-impact, high-urgency incidents created or marked as high priority in the SOW of Incident Management or SIR Workspace of Security Incident Response are classified as major incidents. These major incidents are logged and reported in the Digital resilience incident reporting application. ## Incident reporting workflow The following example shows a sample workflow for reporting an incident in Incident Management. \[Omitted image "dri-inci-repo-wf.png"\] Alt text: Incident workflow. 1. Incident verification: Determine if the reported incident is a major ICT-related incident, a security breach, or an operational payment issue. Assess whether any critical services are impacted. 2. Incident classification: If the critical services affected criterion is not met, the incident is not classified as major. If there is any report of malicious unauthorized access to the network and information systems, the incident is automatically classified as major. 3. Incident record creation: Create an incident record. The **Details** tab includes information such as the case number, source, state, subtype, priority, requester, and other relevant details. Review actions related to the case which are documented in the Activities panel on the **Details** tab. 4. Notification: Send an email notification to the DORA analyst to update them on the progress of the case. 5. Initial report: Automatically collect initial report data. Generate an initial report no later than 24 hours once the incident is classified as major. 6. Response activation: Activate the response steps for the incident. 7. Intermediate report: Review the incident report, if the incident has been open for more than three days. Update the incident data in the intermediate report, which is generated no later than 72 hours after the incident is classified as major. 8. Response review: If the incident is still open, review the response steps. 9. Final report: Verify if the incident is closed and enrich the notes in the record. Update the final report with the revised notes, which is generated one month after the incident is classified as major. ## Incident reporting timelines To report an incident, the following timelines are considered.
| Report type | Timeline \(From the time the incident is classified as major\) |
|---|---|
| Initial report | 24 hours |
| Intermediate report | 72 hours **Note:** The intermediate report is cyclical. A new intermediate assessment is generated every 72 hours \(3 days\) from the time the incident is classified as major until the source incident is closed or the termination conditions configured on the DRI Intermediate report template are met. |
| Final report | 1 month |