Study guide

13.2 DSS Deliver, Service, and Support

ISACA COBIT 2019 Foundation Certificate Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Certificate Rules, Retakes, and How to Study

2 Chapter 2: Framework Introduction

2.1 Purpose of COBIT and EGIT 2.2 I&T Versus the IT Function 2.3 COBIT 2019 Product Family 2.4 Stakeholders, Audience, and Benefits

3 Chapter 3: Framework Positioning

3.1 Umbrella Framework and Related Standards 3.2 Evolution from COBIT 5 to COBIT 2019

4 Chapter 4: Governance System Principles I

4.1 Provide Stakeholder Value 4.2 Holistic Approach 4.3 Dynamic Governance System

5 Chapter 5: Governance System Principles II and Framework Principles

5.1 Governance Distinct from Management 5.2 Tailored to Enterprise Needs 5.3 End-to-End Coverage 5.4 Three Governance Framework Principles

6 Chapter 6: Governance System Components Overview

6.1 Seven Governance System Components 6.2 Generic Versus Variant Components 6.3 Focus Areas

7 Chapter 7: Process and Structure Components

7.1 Processes Component 7.2 Practices, Activities, and Metrics 7.3 Organizational Structures 7.4 Principles, Policies, and Frameworks

8 Chapter 8: Information and People Components

8.1 Information Component 8.2 Culture, Ethics, and Behavior 8.3 People, Skills, and Competencies 8.4 Services, Infrastructure, and Applications

9 Chapter 9: Integrating Governance System Components

9.1 How Components Work Together 9.2 RACI Charts and Key Roles 9.3 Components Supporting Objectives

10 Chapter 10: The Goals Cascade

10.1 The Goals Cascade 10.2 Enterprise Goals and Alignment Goals

11 Chapter 11: Core Model and EDM Governance Objectives

11.1 The 40-Objective Core Model 11.2 EDM Governance Objectives 11.3 Governance Versus Management Objectives

12 Chapter 12: APO Align, Plan, and Organize

12.1 APO Strategy, Architecture, and Innovation 12.2 APO Portfolio, Resources, and Relationships 12.3 APO Risk, Security, Data, and Quality

13 Chapter 13: BAI, DSS, and MEA Management Objectives

13.1 BAI Build, Acquire, and Implement 13.2 DSS Deliver, Service, and Support 13.3 MEA Monitor, Evaluate, and Assess

14 Chapter 14: Performance Management

14.1 Performance Management Principles 14.2 Capability Levels 0–5 and Maturity

15 Chapter 15: Designing a Tailored Governance System

15.1 Why Tailor: Design Factors 15.2 The Eleven Design Factors 15.3 Design Workflow and Toolkit

16 Chapter 16: Business Case

16.1 Business Case for EGIT 16.2 Benefits, Costs, Risk, and Tracking

17 Chapter 17: Implementation Lifecycle

17.1 Implementation Lifecycle Overview 17.2 Seven Implementation Phases 17.3 Roles, Pain Points, and Challenges 17.4 Design Guide and Implementation Guide Together

13.2 DSS Deliver, Service, and Support

Key Takeaways Explain This Topic AI

DSS is the 6-objective Deliver, Service and Support management domain — the run layer after BAI hands a solution to operations.

DSS02 Managed Service Requests and Incidents restores service and fulfills requests; DSS03 Managed Problems finds and removes root causes so incidents do not keep returning.

APO13 Managed Security defines and monitors the information security management system; DSS05 Managed Security Services runs day-to-day security operations.

DSS06 Managed Business Process Controls maintains controls inside in-house or outsourced business processes; MEA02 Managed System of Internal Control evaluates the overall control system.

DSS01 Managed Operations executes standard operating procedures; DSS04 Managed Continuity keeps critical business processes and required I&T services available through disruption.

Last updated: August 2026

Quick Answer: Deliver, Service and Support (DSS) is the 6-objective management domain that runs I&T after BAI transitions a change. DSS01 Managed Operations executes operational procedures for internal and outsourced services. DSS02 Managed Service Requests and Incidents restores service and fulfills user requests. DSS03 Managed Problems finds root causes so incidents do not recur. DSS04 Managed Continuity keeps critical business processes and required I&T services available through disruption. DSS05 Managed Security Services is day-to-day security operations — not APO13 Managed Security , which owns the information security management system (ISMS) . DSS06 Managed Business Process Controls maintains controls inside business processes; MEA02 Managed System of Internal Control evaluates the system of internal control. Do not call a restored incident a solved problem.

DSS is the smallest build-or-run domain and one of the highest-yield ones, because Foundation stems love incident versus problem and security planning versus security operations . Six official titles. Zero governance titles. The service desk does not become the board because it is busy.

Where DSS sits

Management’s verb set is plan, build, run, and monitor . DSS is the run domain. APO planned. BAI built, acquired, and transitioned. DSS keeps the lights on, restores what breaks, removes what keeps breaking, survives a site-down event, operates security services, and keeps business-process controls alive while work is actually happening.

If a stem is still defining requirements or running a pilot, you are in BAI. If the engine is live and Monday’s queue is on fire, you are in DSS. If someone is later assessing whether the control system is adequate, you have stepped into MEA — the next section — not back into DSS06.

The six official objectives

ID Official title One-sentence purpose

DSS01 Managed Operations Coordinate and execute the operational procedures that deliver internal and outsourced I&T services, including monitoring of those procedures.

DSS02 Managed Service Requests and Incidents Provide timely response to user requests and restore normal service for all types of incidents.

DSS03 Managed Problems Identify and classify problems, find root causes, resolve them, and recommend improvements so incidents do not keep returning.

DSS04 Managed Continuity Establish and maintain the ability to continue critical business processes and required I&T services through incidents and disruptions.

DSS05 Managed Security Services Protect enterprise information in line with security policy through operational security roles, access privileges, and security monitoring.

DSS06 Managed Business Process Controls Define and maintain controls so information processed by in-house or outsourced business processes meets control requirements.

DSS01 Managed Operations

DSS01 Managed Operations is the shift that actually runs. Coordinate and execute the activities and standard operating procedures required to deliver internal and outsourced I&T services, and monitor those activities. Scheduling, job execution, backup execution, facilities procedures, and the outsourced runbook all sit here when they are operations , not projects.

DSS01 is easy to skip on a flashcard because it looks like “just operations.” The exam uses it as the home for run-the-engine work that is not an incident, not a problem, not a continuity event, and not a security service. Northline’s nightly claims batch, the vendor’s contracted operating hours, and the monitoring that those procedures actually ran are DSS01. A failed batch that users feel becomes a DSS02 incident. A batch that fails every Monday for the same reason becomes a DSS03 problem. The procedure of running the batch is still DSS01.

High-yield pair 1: DSS02 versus DSS03

Memorize this pair until it is automatic.

Lens DSS02 Managed Service Requests and Incidents DSS03 Managed Problems

Object A user request, or an unplanned interruption / reduction of service The underlying cause of one or more incidents

Job Record and fulfill requests; record, investigate, diagnose, escalate, and restore incidents Identify, classify, find root cause , resolve, and recommend improvement

Success Service is back, or the request is done The failure mode is removed or mitigated so it does not keep returning

Time sense Now — restore and fulfill Next — stop the recurrence

Northline picture Mobile app is down for 400 users; the desk restores service in 20 minutes The same crash has happened four Mondays; a team traces a capacity leak and removes it

DSS02 has two official objects in one title: service requests and incidents . A password reset is a request. A severity-1 outage is an incident. Both are DSS02. Neither is a problem until someone treats the cause as the object of work.

DSS03 Managed Problems is not a slow incident. It is a different objective. Restore first (DSS02), then decide whether the pattern deserves root-cause work (DSS03). An enterprise that only restores, and never hunts causes, has DSS02 without DSS03. An enterprise that refuses to restore until the permanent fix is designed has inverted the pair — users stay down while someone writes a five-why.

ITIL language will appear as flavor in stems. Use it as a hint, not as a license to invent COBIT titles. The official COBIT 2019 names remain Managed Service Requests and Incidents and Managed Problems .

DSS04 Managed Continuity

DSS04 Managed Continuity establishes and maintains a plan so the business and IT can respond to incidents and disruptions, continue critical business processes and required I&T services , and keep information available at a level the enterprise accepts.

Continuity is not “the incident lasted a long time.” A DSS02 incident restores a service that is supposed to be up now . DSS04 is the capability to keep or recover critical work when the normal environment is not available — site loss, regional outage, ransomware that takes the claims engine offline for days. Northline’s regional failover, the paper-claims fallback that is actually rehearsed, and the recovery time the business will accept are DSS04.

Do not steal this job with BAI04 Managed Availability and Capacity . BAI04 designs availability and capacity into the change. DSS04 is the run-domain continuity capability after disruption. Do not steal it with EDM03 Ensured Risk Optimization either. The board sets appetite. Management runs continuity.

High-yield pair 2: APO13 versus DSS05

Chapter 12 already stacked risk and security. Repeat the operational half until you cannot miss it.

Altitude Official objective Job

Governance EDM03 Ensured Risk Optimization Board appetite and tolerance; I&T-related risk identified and managed at board altitude

Management planning APO12 Managed Risk Continual identification, assessment, and treatment of I&T risk within tolerance

Management planning APO13 Managed Security Define, operate, and monitor an ISMS

Management run DSS05 Managed Security Services Day-to-day security services : access privileges, vulnerability handling, security monitoring, operational protection

DSS05 Managed Security Services protects enterprise information so operational security risk stays acceptable in accordance with the security policy . It establishes and maintains information-security roles and access privileges and performs security monitoring . That is the SOC shift, the access-granting desk, the vulnerability scan that actually runs, the SIEM that someone watches.

APO13 Managed Security is the ISMS — the management system that defines how security is governed as a system of policies, roles, control objectives, and ISMS monitoring. Northline can buy a SIEM (DSS05-flavored) and still fail APO13 if nobody owns the ISMS. It can write a beautiful ISMS and still fail DSS05 if nobody grants access correctly or watches the alerts. Neighbors, not twins. Neither title is Ensured . Neither is a project in BAI.

High-yield pair 3: DSS06 versus MEA02

DSS06 Managed Business Process Controls defines and maintains appropriate business process controls so information related to and processed by in-house or outsourced business processes satisfies information-control requirements. Application input edits, segregation of duties inside the claims workflow, maker-checker on a payment, and the control that still applies when a vendor runs the process all sit here.

MEA02 Managed System of Internal Control — taught fully in the next section — continuously monitors and evaluates the control environment as a system . DSS06 puts and keeps controls in the process . MEA02 assesses whether the system of internal control is adequate . A stem about embedding an edit in the claims payment process is DSS06. A stem about management evaluating whether the internal-control system as a whole still works is MEA02.

Do not call DSS06 “audit.” Do not call it “the ISMS.” Do not promote it to EDM. It is a run-domain management objective about business process and application controls where the work happens, including when that work is outsourced.

Scenario: Monday on the Northline service floor

The digital-claims engine is live. Watch the IDs.

DSS01 runs the overnight batch and the vendor operating procedures. Monitoring shows the batch completed.

At 8:10 the mobile app fails for 400 users. DSS02 records the incident, diagnoses, escalates, and restores service in twenty minutes. A separate queue fulfills access requests from new adjusters — also DSS02, because requests live in the same official title.

The same crash has now happened four Mondays. DSS03 opens a problem, classifies it, finds a capacity leak BAI04 should have caught, and recommends a permanent fix so Monday does not keep repeating.

A regional fiber cut later that week takes the primary site offline. DSS04 invokes continuity: failover, the accepted information-availability level, continuation of critical claims intake. This is not “a long incident.” It is continuity.

While the site is degraded, DSS05 watches access and security monitoring so the failover path does not become an open door. The ISMS that says this must happen is still APO13 ; the service that does it on the shift is DSS05.

Through all of it, DSS06 keeps maker-checker on claim payments — including the outsourced overflow team — so a continuity event is not an excuse to skip process controls. Next quarter, MEA02 will evaluate whether that control system, as a system, is still adequate. That later evaluation is not DSS06.

Exam traps

Incident = problem. DSS02 restores and fulfills. DSS03 removes root causes.

DSS02 as incidents only. The official title is Managed Service Requests and Incidents .

APO13 = DSS05. ISMS versus security services.

DSS06 = MEA02. Process/application controls versus the system of internal control.

DSS04 as a long DSS02 ticket. Continuity is a planned capability for disruption, not a slow restore.

DSS01 as the whole run domain. Operations is one of six official titles.

Calling DSS governance because operations feels “in charge.” Only EDM is governance.

Prefer the answer that keeps all six official titles, keeps restore separate from root cause, keeps the ISMS above security services, and keeps process controls below the MEA02 control-system evaluation.

Loading diagram... DSS run domain: operations, incident versus problem, continuity, security services, process controls