IT Service Delivery and Support Spring2014 WeekOne
IT Service Delivery and Support Spring2014 WeekOne
Overview
IT Auditing and Cyber Security
Spring 2014
Instructor: Liang Yao (MBA, MS, CIA, CISA, CISSP)
1
IT Service Delivery and Support
Introduction
Goals and Objectives
Expectations
IT Service and Delivery Overview
2
Goals and Objectives
3
Expectations
4
IT Service Delivery and Support
Course Syllabus
5
Related ISACA Curriculum Topics
6
Fundamentals of IT Audit
IT Audit Objectives
IT Audit Requirements
IT responsibilities within the Organization
Manage Risks in an Automated Environment
Mitigate Security Risks
Addressing Risks via Internal Controls
Definition of Internal Control
Audit Risk
7
IT Audit Objectives
8
Requirements
11
Risks Examples
12
Mitigate Security Risks
13
Internal Control Definition
14
Internal Control Definition
15
IT Service Delivery and Support
Frameworks
CoBit: an IT governance and control framework that focus on what should be addressed to
ensure good governance of all IT-related processes
(*CoBit 5 is available on ISACA’s website.)
16
COSO Components of Internal
Control
17
IT Service Delivery and Support
Elements – By ITIL
Service support : Service support describes the day-to-day operation and
support of IT services. It includes the service desk function as well as the
following five processes:
Service desk – The service desk function is the single point of contact
between users and IT service management. Tasks include handling
incidents and requests, and providing an interface for other ITSM
processes.
Incident management – Incident management's goal is to restore service
operation as quickly as possible with minimal disruption to users.
Problem management – Problem management is a process designed to
minimize the adverse effects of incidents and problems caused by
infrastructure errors. It also seeks to proactively prevent the recurrence
of these incidents and problems.
18
IT Service Delivery and Support
Elements – By ITIL
Configuration management – Configuration management is a
process of identifying and defining configuration items within a
system. It also involves monitoring the status of these items,
processing requests for change, and verifying the completeness
and correctness of configuration items.
Change management – Change management is a process of
controlling changes within IT services or systems, with proper
approval and minimal disruptions.
Release management – Release management is the process of
introducing new or changed configuration items to the
infrastructure. These configuration items have been approved by
change management, tested, and determined to be ready for
implementation.
19
IT Service Delivery and Support
Elements – By ITIL
Service delivery: Service delivery describes the long-term planning
and improvement of IT service provision. It addresses the following
five processes:
20
IT Service Delivery and Support
Elements – By ITIL
Capacity management – ensures the projected business
needs will be met in a cost-effective and timely manner. It
also ensures the infrastructure can handle new technology.
Capacity entails storage, facilities, networking capabilities,
and people.
IT service continuity management – ensures that the proper
and required IT technical and service facilities can be
recovered in the agreed upon and required time frame
following a disruption to the business.
Availability management – ensures services are available
when and at the level the customer requires them, as
defined by the service level agreement.
21
CoBit Framework
22
CoBit Framework (continued)
23
Delivery and Support Domain
25
CoBit 5 New and Modified Process
There are several new and modified processes that reflect current
thinking, in particular:
26
Audit Risk
Audit risk “refers to the risk that an auditor may issue unqualified report due to auditors
failure to detect material misstatement either due to error or fraud.” (source: wikipedia)
When the controls are adequate and reliable, there may be less need to look at the
details of transactions
Therefore, the auditor can take an approach that allows some reviews or test of
controls, also called compliance or functional tests, reducing the need for detailed
(substantive) tests. This decision is based on risk analysis; control of high-risk
transactions or events need to be reviewed first. Controls of low-risk transactions or
events can be evaluated as time permit.
27
Audit Risk (continued)
28
Auditing IT Infrastructure and Operations
Risks Types
Inherent Risk
Mitigate Risk/Residual Risk
Controls Types
Preventive Controls
Detective Controls
Deterrent Controls
System Controls vs. Application Controls
Manual Controls vs. Automated Controls
29
Risk Types
30
Risk Assessment – Likelihood and Impact
Likelihood
Impact Likelihood
Impact
31
IS Operations Review
32
Review and Discussion
33