Question 1. Define IT governance.
Model answer: The leadership, organisational structures and processes that direct and monitor IT so it supports enterprise objectives, creates value and manages risk.
CBE NEXUS · UNDERGRADUATE TEXTBOOK SERIES
Information Systems
Comprehensive undergraduate notes, governance diagrams, applied case studies and university assessment.
Undergraduate level · Chapter 13 of 16 · Directing, assuring and improving enterprise technology services
Learning outcomes: Explain IT governance; distinguish governance and management; apply risk and control concepts; describe IT audit methods; evaluate ITSM practices; and assess service continuity, supplier and compliance governance.
IT governance is the system of leadership, organisational structures and processes that ensure information technology supports enterprise objectives, creates value and manages risk. It clarifies who makes technology decisions, who is accountable for outcomes and how performance is monitored. Governance is not simply an IT department responsibility: boards, executives, business owners, technology leaders, risk specialists and users all have roles.
Governance connects business strategy with technology investment and operational delivery. It establishes decision rights for architecture, data, cybersecurity, sourcing, applications and digital transformation. Effective governance prevents isolated projects from creating incompatible systems, uncontrolled expenditure or unacceptable exposure. It also recognises that technology decisions affect customers, employees, suppliers and the public.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Governance evaluates stakeholder needs, sets direction and monitors performance. Management plans, builds, runs and monitors activities in accordance with that direction. Administration performs operational tasks such as account provisioning, system configuration, records maintenance and routine reporting. These functions interact but should not be confused.
A board may approve risk appetite and strategic priorities; an executive committee may allocate investment; an IT service manager may coordinate delivery; and administrators may implement access controls. Clear separation supports accountability and reduces conflicts of interest. In small organisations, one person may perform several roles, but review and approval controls should still be designed.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
IT-business alignment means that technology capabilities, investments and services support organisational strategy and measurable outcomes. Alignment is continuous because markets, regulation, user expectations and technology change. A project can meet its technical specification yet fail to create value if it does not solve the business problem or achieve adoption.
Value realisation begins with a defined business case, baseline measures, expected benefits, owners and a review schedule. Benefits may include improved service quality, lower operating cost, faster processing, better decisions, resilience or new revenue. Track both financial and non-financial outcomes and distinguish outputs delivered from benefits actually achieved.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Frameworks provide structured guidance for governance, risk, control, service management and security. COBIT is commonly used to govern and manage enterprise information and technology; ITIL provides practices for IT service management; ISO/IEC 38500 addresses governance of IT; ISO/IEC 20000 concerns service management systems; and ISO/IEC 27001 specifies requirements for an information security management system.
A framework is not a substitute for judgement. Organisations should select practices according to size, complexity, legal duties, threat exposure and service criticality. A useful implementation adapts the framework to actual processes, assigns accountable owners and measures whether controls work. Copying a large organisation's documentation into a small organisation can create bureaucracy without improving outcomes.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
COBIT provides a framework for enterprise governance and management of information and technology. It helps organisations connect stakeholder needs, enterprise goals, alignment goals, processes, organisational structures, information flows, people, services and infrastructure. It distinguishes governance objectives from management objectives and supports performance assessment.
COBIT implementation should begin with enterprise context and priority issues. A governance design considers decision structures, policies, information, culture, skills and technology. Capability assessments can identify gaps and guide improvement, but a maturity score alone does not demonstrate effectiveness. Evidence should show that activities achieve intended outcomes and risks are controlled.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
IT strategy defines how technology capabilities will support the organisation over time. Enterprise architecture describes the relationships among business capabilities, processes, information, applications, technology platforms and standards. Architecture governance helps ensure that projects fit the target direction while allowing justified exceptions.
Architecture principles might require interoperability, reuse, data ownership, security by design and approved integration patterns. An architecture review board evaluates significant designs, dependencies, technical debt and exceptions. The review should be timely and proportionate: excessive approval delays can encourage teams to bypass governance rather than improve design quality.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Decision rights specify who may propose, approve, execute, review or challenge a decision. Common governance bodies include board risk committees, executive technology committees, architecture boards, data governance councils and change advisory groups. Each body needs a defined mandate, membership, quorum, escalation route and record of decisions.
A RACI matrix can clarify who is Responsible, Accountable, Consulted and Informed for an activity. It should normally identify one accountable role for each decision. Committees should not diffuse accountability: the named executive or service owner remains responsible for ensuring that decisions are implemented and outcomes reviewed.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Policies express management intent and mandatory rules, such as acceptable use, access control, data classification, incident reporting and supplier security. Standards define specific requirements; procedures explain repeatable steps; guidelines recommend good practice. These documents should be consistent, accessible and approved by appropriate authorities.
Policy governance includes ownership, version control, communication, staff acknowledgement, exception handling and periodic review. Requirements should be testable. A statement such as 'systems must be secure' is too vague; a control should specify the expected behaviour, responsible role, evidence and review frequency.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
IT risk is the possibility that technology-related events affect objectives. Risks include cyberattack, service outage, data loss, privacy breach, project failure, supplier disruption, skills shortages, poor data quality and technology obsolescence. Risk management identifies, analyses, evaluates, treats and monitors risks within the organisation's appetite and tolerance.
A risk register records a clear cause-event-effect statement, likelihood, impact, inherent risk, existing controls, residual risk, owner, treatment and due date. Risk scoring supports prioritisation but should not create false precision. Critical risks require escalation and active monitoring, especially where consequences could affect safety, legal compliance or essential services.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Internal controls are policies, procedures and activities designed to provide reasonable assurance that objectives are achieved, reporting is reliable, operations are effective and obligations are met. Preventive controls aim to stop unwanted events; detective controls identify them; corrective controls restore or remediate after an event.
Control design should address a defined risk and be proportionate to its impact. Examples include segregation of duties, approval limits, access restrictions, reconciliations, backups, logging, change approvals and independent review. A control that exists only on paper is not effective; organisations need evidence that it is performed consistently and exceptions are resolved.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
IT audit is an independent and systematic examination of technology-related controls, systems, processes and evidence. It assesses whether controls are suitably designed and operating effectively, whether information is reliable, and whether systems comply with relevant requirements. Audits may be internal, external, regulatory, financial, operational or specialised security reviews.
Audit independence is supported through objective reporting lines, freedom from operational responsibility for the area being audited and disclosure of conflicts. Auditors should define objectives, scope, criteria, period, locations, systems and limitations. Management remains responsible for controls and remediation; auditors provide assurance and recommendations rather than owning the process.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Risk-based audit planning directs effort toward areas with the greatest significance to organisational objectives. Inputs include enterprise risk assessments, prior audit findings, major changes, incidents, regulatory obligations, outsourced services and management concerns. Audit plans should consider both likelihood and consequence, as well as control maturity and the reliability of previous evidence.
A risk-based plan is flexible. A major cloud migration, acquisition, ransomware incident or new payment platform may require an audit outside the original annual schedule. Audit committees should understand coverage gaps and resource constraints. Lower-risk areas may receive periodic review, while critical systems and high-impact controls may require more frequent assurance.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
An audit typically moves through planning, understanding the process, risk and control assessment, testing, evaluation, reporting and follow-up. Evidence may include system configurations, access listings, logs, tickets, contracts, policies, interviews, observations, reconciliations and reperformance. Evidence should be relevant, reliable, sufficient and traceable to the audit objective.
Auditors document procedures, samples, results, exceptions and conclusions. Inquiry alone is usually weaker than corroborated evidence. For example, a manager's statement that access is reviewed quarterly should be supported by dated review records, evidence of challenge and proof that inappropriate access was removed. Protect audit evidence because it may contain confidential or personal information.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
IT general controls support the reliable operation of systems and include access management, change management, operations, backup and recovery, system development and security administration. Application controls operate within specific applications and may include input validation, processing checks, authorisation, calculations, interface controls and output review.
Weak general controls can undermine reliance on application controls. If unauthorised users can change application code or database records, otherwise well-designed transaction checks may be bypassed. Auditors assess the relationship between general and application controls and tailor substantive testing where control reliance is not justified.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Access governance ensures that users receive appropriate permissions for legitimate duties and that access is reviewed, changed and removed when circumstances change. Core principles include least privilege, need to know, unique identities, strong authentication, segregation of duties and periodic recertification.
Privileged accounts require additional safeguards because they can alter systems, data and security settings. Use controlled elevation, separate administrator accounts, multi-factor authentication, session logging, emergency access procedures and independent review. Joiner-mover-leaver processes should connect HR events to timely account changes and retain evidence of approvals.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Change management controls modifications to applications, infrastructure, configurations and data. It assesses business need, risk, testing, approval, scheduling, communication, rollback and post-implementation review. Emergency changes need a rapid but documented path and retrospective review to ensure that urgency does not become a permanent bypass.
Configuration management maintains reliable information about components, versions, relationships and dependencies. A configuration management database or equivalent inventory can support incident diagnosis, impact assessment, asset lifecycle planning and audit. Data quality matters: an inaccurate inventory may create a false sense of control.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
IT operations include routine monitoring, job scheduling, event management, capacity, availability, backup, patching, endpoint management and operational support. Governance defines service objectives, responsibilities, escalation thresholds and evidence requirements. Monitoring should identify meaningful exceptions rather than overwhelm teams with alerts.
Operational procedures should be documented, tested and maintained. Runbooks need clear ownership and current contact details. Service continuity planning considers people, facilities, suppliers, data, applications and infrastructure. Critical operations should not depend on undocumented knowledge held by one individual.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
IT Service Management (ITSM) organises people, processes, partners and technology to deliver and support services that create value. Service management considers the complete lifecycle from demand and design through transition, operation, improvement and retirement. A service is more than a technical component: it enables an outcome for a customer or user.
Service definitions should identify customers, users, outcomes, service hours, dependencies, support routes, service levels and responsibilities. Service catalogues help users understand what is available and how to request it. Good service management balances reliability, cost, speed, security and experience rather than optimising one measure in isolation.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
ITIL describes a service value system that connects guiding principles, governance, service value chain activities, practices and continual improvement. The guiding principles encourage focus on value, start where you are, progress iteratively with feedback, collaborate, think holistically, keep processes simple and optimise before automating.
ITIL practices include incident management, problem management, service desk, change enablement, service request management, service level management, monitoring and event management, release management and configuration management. Practices should be adapted to organisational context and integrated across teams rather than treated as isolated departments.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
An incident is an unplanned interruption or reduction in service quality. Incident management aims to restore normal service quickly and minimise impact. A problem is a cause or potential cause of one or more incidents; problem management investigates causes and reduces recurrence. A service request is a predefined user request such as access, information or standard equipment.
Incident prioritisation commonly considers impact and urgency. Communication should tell affected users what is known, what work is underway and when the next update will arrive. Major incidents require coordinated leadership, technical response, stakeholder communication and a post-incident review focused on learning rather than blame.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Change enablement seeks to maximise successful changes by assessing risk, authorising appropriate changes and managing schedules. Standard changes are low-risk and pre-authorised when criteria are met; normal changes receive assessment and approval; emergency changes use an expedited route with appropriate controls.
Release management makes new or changed services and features available for use, while deployment moves components into target environments. Use version control, automated testing, separation of duties, release notes, rollback planning and post-deployment verification. Measure change success through failure rate, rework, incidents and time to restore service.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
A Service Level Agreement (SLA) documents agreed service expectations between a provider and customer. It may define availability, response time, restoration targets, support hours, capacity, security responsibilities, reporting and escalation. Operational Level Agreements and underpinning supplier contracts help coordinate internal and external dependencies.
Service measures should reflect user outcomes. An availability target can conceal frequent short interruptions or poor performance during peak periods. Define measurement windows, exclusions, data sources and calculation methods. Review service performance with customers and agree corrective actions where targets are missed.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Availability management seeks to ensure services meet agreed availability needs. Capacity management balances current and future demand with resources, while performance management monitors response time, throughput, latency, utilisation and user experience. These practices require forecasts, baselines, thresholds and plans for growth or seasonal peaks.
Availability calculations must define the measurement period and what counts as downtime. Capacity plans should consider workload patterns, dependencies, resilience and cost. Performance problems may arise from network latency, inefficient queries, overloaded services or poor client-side design. Monitoring should trace the user journey across components.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Business continuity management prepares an organisation to maintain or restore priority activities during disruption. Disaster recovery focuses on restoring technology services, infrastructure and data after a disruptive event. Both require business impact analysis, risk assessment, recovery strategies, plans, assigned roles, communication and exercises.
Recovery Time Objective (RTO) is the target time within which a service should be restored. Recovery Point Objective (RPO) is the maximum targeted data-loss interval measured in time. A service with a short RTO and RPO may require replication and resilient architecture, while a less critical service may use less costly recovery arrangements.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Outsourcing and cloud services can provide specialist capability, scalability and speed, but they do not remove the customer's accountability for appropriate governance. Supplier risk includes service concentration, subcontractors, data location, security, resilience, financial stability, exit barriers and contractual ambiguity.
Due diligence should examine security assurance, privacy, continuity, service performance, incident notification, audit rights, data portability and deletion. Contracts should specify responsibilities and evidence. Cloud shared-responsibility models must be understood for each service type; the customer remains responsible for controls assigned to its role.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Data governance establishes decision rights and accountability for data quality, definitions, ownership, classification, lineage, access, retention and disposal. Privacy governance addresses lawful and fair processing, transparency, purpose limitation, data minimisation, security and rights of individuals under applicable law.
A data inventory and classification scheme help determine where information is stored, who may access it and how it should be protected. Retention schedules should reflect legal, operational and archival needs. Deletion must account for replicas, backups, exports and supplier copies. Governance should be supported by evidence and periodic review.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Compliance management identifies applicable laws, regulations, contractual commitments, industry standards and internal policies. Requirements may concern privacy, cybersecurity, financial reporting, records, accessibility, consumer protection, intellectual property or sector-specific obligations. Legal applicability depends on jurisdiction, sector, data and organisational role.
Maintain a compliance obligations register with accountable owners, control mappings, evidence sources, review dates and escalation routes. Avoid assuming that certification automatically proves compliance with every law. Legal and regulatory specialists should interpret obligations, while technology and business teams implement controls and retain evidence.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Cybersecurity governance sets strategy, risk appetite, roles, policies, investment priorities and oversight for protecting information and services. It connects security operations with enterprise risk, business continuity, supplier management and legal obligations. Senior leaders should receive concise reporting about material exposure, incidents, control effectiveness and remediation.
Incident response should define detection, triage, containment, eradication, recovery, communication and lessons learned. Preserve evidence and coordinate with legal, privacy, communications, regulators and affected parties as required. Governance should ensure that findings lead to funded improvements, not merely a post-incident report.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
An audit finding describes a condition, the expected criterion, the cause, the consequence or risk and a recommended corrective action. A strong finding is evidence-based, specific and proportionate. Management should identify an action owner, milestones, resources and target completion date.
Follow-up verifies that remediation is implemented and effective. Closing a ticket or receiving a policy document is not sufficient if the underlying risk remains. High-risk overdue findings should be escalated to accountable executives and the audit committee. Trend analysis can reveal recurring weaknesses across business units.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
Governance metrics help leaders understand whether technology supports objectives, controls work and services meet expectations. Indicators may include critical service availability, unresolved high risks, overdue audit actions, change failure rate, incident restoration time, privileged access review completion and supplier assurance status.
Use a balanced set of leading and lagging indicators. A leading indicator may show that access reviews are completed on time; a lagging indicator may show confirmed unauthorised access incidents. Metrics need owners, definitions, thresholds, reliable sources and an agreed response when performance is outside tolerance.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
AI, robotic process automation, low-code platforms and connected devices introduce governance questions about accountability, data quality, security, explainability, bias, intellectual property, human oversight and vendor dependency. Uncontrolled experimentation can create shadow IT, duplicated spending and data leakage.
Establish proportionate review for use cases, classify impact, assess data and model risks, define human oversight, monitor performance and provide routes to challenge outcomes. Governance should enable responsible innovation rather than prohibit experimentation. Pilot projects need exit criteria and a plan for production support, security and lifecycle management.
Governance evidence should be retained in a form that allows an independent reviewer to understand what was required, who performed the activity, when it occurred, what exceptions arose and how they were resolved. Evidence may include approvals, system-generated logs, reconciliations, test results, meeting decisions, supplier reports and signed attestations. Apply access controls and retention rules to audit records because they can expose vulnerabilities or confidential business information.
Implementation should start with a clear owner, a defined scope and a baseline of current performance. Map the relevant process from request to outcome, identify dependencies and specify the control points. Select measures that demonstrate whether the activity achieves its purpose. Where a control fails, distinguish a one-off execution error from a structural design weakness, insufficient resources or unclear accountability.
Review the arrangement after significant organisational, technical or regulatory change. A process that was proportionate for a small on-premises system may be inadequate after migration to a multi-cloud service or introduction of sensitive data processing. Engage affected teams, test procedures and update documentation. Continual improvement is effective when findings lead to practical changes and subsequent evidence confirms that risk has reduced.
A university plans to move its learning platform, student records and collaboration tools to cloud services. Departments have purchased separate subscriptions, data ownership is unclear and the institution has no consistent supplier exit plan.
The university establishes an executive sponsor, architecture review, data governance council and cloud service owner. It inventories systems and data, maps shared responsibilities, classifies workloads, assesses supplier resilience and privacy, defines identity controls and approves a phased migration plan. Contracts specify incident notification, audit evidence, availability, data portability and secure deletion.
The institution pilots a low-risk workload, tests identity integration and recovery, measures service quality and user experience, then reviews lessons before migrating critical records. It maintains an exit strategy and periodically tests restoration and export of data.
Prepare an assurance file containing the business objective, stakeholder responsibilities, risk assessment, control design, test evidence, exception analysis and agreed remediation. Explain which decisions require executive oversight and which can be handled operationally. Evaluate whether the proposed changes are sustainable, measurable and proportionate to the service's criticality.
An internal audit discovers that several former employees retain active accounts and multiple administrators share a generic privileged login. Management believes the risk is low because the network is protected by a firewall.
Auditors define access governance criteria, obtain user and privileged-account listings directly from systems, compare them with HR records, inspect approval and review evidence, test selected accounts and examine administrator logs. They assess whether shared credentials prevent attribution and whether access is removed promptly after role changes.
Management assigns individual administrator identities, introduces controlled elevation and multi-factor authentication, automates joiner-mover-leaver triggers and establishes periodic recertification. Follow-up testing verifies actual removal and traceable activity rather than accepting a policy update alone.
Prepare an assurance file containing the business objective, stakeholder responsibilities, risk assessment, control design, test evidence, exception analysis and agreed remediation. Explain which decisions require executive oversight and which can be handled operationally. Evaluate whether the proposed changes are sustainable, measurable and proportionate to the service's criticality.
A payment service becomes unavailable during peak activity. The service desk receives repeated reports, technical teams investigate separately and customers receive inconsistent updates. The cause is eventually traced to a capacity bottleneck introduced by a recent release.
The organisation invokes major incident management, assigns an incident commander, coordinates technical investigation and customer communication, and restores service using a tested rollback. A post-incident review examines monitoring gaps, release testing, capacity forecasts, escalation and decision-making.
Improvements include load testing, clearer service ownership, alert thresholds, a release readiness checklist, customer status updates and a problem record to address the root cause. Measures include restoration time, repeat incidents and change-related failure.
Prepare an assurance file containing the business objective, stakeholder responsibilities, risk assessment, control design, test evidence, exception analysis and agreed remediation. Explain which decisions require executive oversight and which can be handled operationally. Evaluate whether the proposed changes are sustainable, measurable and proportionate to the service's criticality.
A security audit reports overdue patching, incomplete supplier assessments and inconsistent backup tests. The technology team submits a dashboard showing many tasks as completed, but the board cannot determine whether critical risks have been reduced.
The audit committee requests risk-ranked findings, named owners, target dates, evidence of implementation and independent retesting. Management distinguishes administrative closure from verified effectiveness and escalates high-risk exceptions where funding or supplier action is required.
A revised dashboard reports residual risk, overdue high-priority actions, evidence quality and trend. The board receives concise decisions required, rather than a large list of technical activities without business context.
Prepare an assurance file containing the business objective, stakeholder responsibilities, risk assessment, control design, test evidence, exception analysis and agreed remediation. Explain which decisions require executive oversight and which can be handled operationally. Evaluate whether the proposed changes are sustainable, measurable and proportionate to the service's criticality.
Answer using precise definitions, relevant frameworks, evidence-based examples and clear calculations where required.
Model answer: The leadership, organisational structures and processes that direct and monitor IT so it supports enterprise objectives, creates value and manages risk.
Model answer: Governance evaluates needs, sets direction and monitors; management plans, builds, runs and monitors activities within that direction.
Model answer: Ensuring technology capabilities and investments support organisational strategy and measurable business outcomes.
Model answer: COBIT, ITIL, ISO/IEC 38500, ISO/IEC 20000 and ISO/IEC 27001.
Model answer: A responsibility assignment tool identifying who is Responsible, Accountable, Consulted and Informed.
Model answer: The amount and type of risk an organisation is willing to pursue or retain while achieving its objectives.
Model answer: Preventive controls stop events; detective controls identify them; corrective controls restore or remediate after occurrence.
Model answer: An independent examination of IT-related controls, systems, processes and evidence against defined criteria.
Model answer: It supports objective conclusions and reduces conflicts that could impair assurance.
Model answer: Planning, understanding, risk assessment, control testing, evaluation, reporting and follow-up.
Model answer: Controls over access, change, operations, security, backup and development that support reliable IT environments.
Model answer: Input validation, transaction authorisation, processing checks, interface reconciliation and output review.
Model answer: Users receive only the minimum access needed for their authorised duties.
Model answer: A controlled process for assessing, approving, testing, scheduling and reviewing modifications to services and systems.
Model answer: The organisational capabilities and practices used to deliver, support and improve IT-enabled services.
Model answer: An incident is an interruption or reduction in service quality; a problem is a cause or potential cause of incidents.
Model answer: A predefined user request such as information, access or a standard service action.
Model answer: An agreement documenting service expectations, measures, responsibilities and escalation arrangements.
Model answer: A process for identifying critical activities and assessing the consequences of disruption over time.
Model answer: RTO is the target time to restore a service; RPO is the maximum targeted data-loss interval.
Model answer: The customer retains responsibility for controls and obligations assigned to its role under the service and shared-responsibility model.
Model answer: Decision rights and accountability for data quality, ownership, access, classification, lineage, retention and use.
Model answer: The condition, criterion, cause, consequence or risk, evidence and recommended corrective action.
Model answer: It verifies that remediation is implemented and actually reduces the identified risk.
Model answer: Leading: timely access reviews and completed recovery tests. Lagging: confirmed security incidents and service outages.
Model answer: Availability = 7,182 ÷ 7,200 × 100 = 99.75%.
Model answer: The service should be restored within four hours, and recovered data should be no more than 30 minutes behind the disruption point.
Model answer: 6 ÷ 80 × 100 = 7.5%. The auditor should investigate the nature and risk of the exceptions.
Model answer: Ownership establishes accountability for action, resources, milestones and escalation.
Model answer: Regularly use performance data, feedback, incidents and reviews to identify, prioritise, implement and verify service improvements.
Use these official organisations for curriculum guidance, examinations and further learning information.