Merge pull request #6751 from ministryofjustice/docs/update-incident-…

…process

Update incident process

runbooks/source/incident-process.html.md.erb

@@ -1,7 +1,7 @@
 ---
 title: Incident Process
 weight: 40
-last_reviewed_on: 2024-09-03
+last_reviewed_on: 2025-01-28
 review_in: 6 months
 ---
 
@@ -11,7 +11,7 @@ This document describes our incident handling process.
 
 ## 1. Confirm that the event constitutes an incident
 
-> If this is a security breach, also report it [here](https://docs.google.com/forms/d/e/1FAIpQLScjD5d4wkX1SUgxzYfh5eCfCmKfMbR1klzoyEo9gUFZdRuXxg/viewform)
+> If this is a security breach, also raise a ticket on the [Technology Portal](https://mojprod.service-now.com/moj_sp). This can be done by telephone or online chat.
 
 We define an incident as an event which:
 
@@ -158,6 +158,7 @@ After the incident is resolved:
 * An incident report **must** be published in the [Incident Log](https://runbooks.cloud-platform.service.justice.gov.uk/incident-log.html#incident-log) section of the Runbook site.
 * A blameless post mortem meeting **may** be scheduled
 * A [runbook] for how to fix this issue **should** be published
+* If a security incident was raised on the Technology Portal, ensure the incident is updated there and resolved
 
 [runbook]: https://runbooks.cloud-platform.service.justice.gov.uk
 [raise a ticket]: https://github.com/ministryofjustice/cloud-platform/issues/new?template=cloud-platform-support-request.md&labels=support+team