Lesson 24 of 33
In Progress

Service Desk Management Process

1                  Introduction

The Service Desk will operate within the KPMG Global Security Operations Centre (GSOC) to serve as a single point of contact for all requests coming into the GSOC and provide an interface to other processes that service these requests.

1.1              Purpose

The GSOC will utilise the ITS Global Service Desk Tool (now known as the Service Desk Tool) and associated processes to handle requests coming into the GSOC. This document describes the activities that the GSOC will perform to use these tools and ensure that all relevant information about requests coming into the GSOC is collected and all requests are managed throughout their lifecycles.

1.2              Scope

This document covers the activities that are performed within the GSOC to manage requests within the Service Desk Tool for new or changes to existing GSOC services and requests for help from member firms in relation to security incidents. 

1.3              Ownership

The responsibility of ownership and ongoing management of this document, including the processes contained therein, rests primarily with the Head of GSOC.

1.4              Audience

The intended audience for this document is the GSOC Team.

1.5              Exceptions

Exceptions will be in line with ITS Global Service Desk Management and must be validated by the GSOC Operations Manager.

1.6              Reporting Violations

Any violations to this policy should be reported directly to the following email address:


1.7              Key Definitions

Service desk: a service for managing help desk incidents, problem tickets, change records and service requests.

2.1          Responsibilities

The following roles have responsibilities for respective components of the service desk management process. This list is not intended to provide an extensive list of the responsibilities of each of the roles:

1.7.1          GSOC Operations Manager

The GSOC Operations Manager is manages the overall service desk activities and acts as a further escalation point for issues that cannot be resolved by senior members of the GSOC.

1.7.2          Escalation Group

An Escalation Group will be assigned within the Service Desk Tool to receive tickets raised for the attention of the GSOC. The Escalation Group will comprise of one or more members of the GSOC and will monitor the Service Desk Tool queue, review incoming voicemails, log tickets as necessary and determine the appropriate escalation paths for requests.

1.7.3          Requestor

A requestor is an individual or group of individuals that may request for a service, report an incident or request for support from the GSOC. Requests may come from within the GSOC, Member Firms, ITS Global or other entities external to the GSOC.

2.2          Upstream (Dependent) Processes

2.3          Downstream (Affected) Processes

2                  Process Overview

The workflow below describes how the GSOC interacts with ITS Global Service Desk to manage all requests and incidents sent into the GSOC throughout their lifecycles.

2.1              Process Description

The following sections describe the workflow shown in the diagram above.

2.1.1          Raising tickets (1.0)

The requestor will raise a ticket through the Service Desk Tool in accordance with the ITS Global Service Desk requirements. Requests sent directly to the GSOC through the GSOC Communication Process must be logged as tickets by members of the GSOC on behalf of the requestor.

2.1.2          Triggering ITS Global Change Management Process

If an incoming request concerns a Change, then the ITS Global Change Management Process will be invoked.

2.1.3          Receiving tickets (2.0)

The Escalation Group assigned for the selected service or request type will receive the ticket and determine whether it is sufficiently documented.

2.1.4          Information gathering (3.0)

The Escalation Group will gather as much information as possible on the request reported. Any incomplete or suspected inaccuracies will be verified with the requestor to make sure that a complete and reliable description of the request is obtained.

If the requestor cannot provide the information requested then a reminder will be sent to the requestor and the ticket updated in line with the ITS Global Service Desk Management Process.

2.1.5          Triggering processes to resolve the issue

The ticket should be assessed to determine which GSOC process to service the request and the identified GSOC processes will then be invoked as follows:

Request TypeProcessExamples
Service requestITS Global Service Management ProcessMember firm requesting for detailed report not available on the list of reports
Security incidentITS Global Security Incident Management ProcessMember firm seeking support to resolve a security incident
IT IncidentITS Global IT Incident Management ProcessMember firm unable to access a service provided by the GSOC
ChangeITS Global Change Management ProcessTooling engineer determines a change to one or more services within the GSOC is needed in order to resolve the issue reported in the request

The tickets will be reassigned as necessary, depending on the escalations specified in the respective GSOC process.

2.1.6          Verify ticket and close

When a solution has been provided/found, the ticket should be updated to indicate that the issue has been resolved and the end-user will be notified in order to verify if the proposed solution is acceptable for the problem raised. Once the issue is resolved, documented and verified by the user, the ticket should be closed.

However, if the problem remains the issue will be raised as a problem and handled through the ITS Global Problem Management Process. The original ticket should be updated to indicate that the issue has been pushed to problem management and closed.

2.2              Periodic reviews and updates of tickets

When new information is uncovered in the investigation of an issue, the incident should be updated accordingly. The assignee should log all phone conversations, e-mail, file attachments, status changes, reassignments, and create relationships whenever they occur in order to keep the investigation information and status relevant and up to date.

The Escalation Group should review Incident tickets in their queue to provide updates on the progress towards a solution. Any reminders received about pending tickets should be acted upon in accordance with the priorities and any agreed SLAs.