Information Security Governance: Lessons From the MTN Data Breach

When I started reading about MTN’s 2025 data incident, I wanted to understand where things had gone wrong. The first announcement confirmed that someone had gained unauthorized access to some customers’ personal information. But it was a detail in the company’s later explanation that made me stop: an older technology environment had been waiting to be moved when it was compromised.

Think about what that means for a moment. The business had already planned a change. Meanwhile, the existing environment was still running and receiving information from several parts of the organization.

You might recognize a smaller version of that situation in your own business. An old application stays in use while you look for a replacement. Customer records remain in a shared folder while someone prepares a new system. The move is on the list, but everyday work keeps pushing it back.

Someone still needs to protect the information during that period. Someone also needs to check what remains unfinished and decide which risks need attention. Those responsibilities are part of information security governance.

I’ll walk you through what MTN disclosed, what its later account added, and the lessons worth applying in your business. Let’s start with the story.

Key Takeaways

  • MTN Group announced a cybersecurity incident in April 2025 involving unauthorized access to some customers’ personal information.
  • The company later described a compromised server in an older technology environment awaiting migration. That server received data from several operating companies.
  • Information security governance establishes who makes decisions about protecting information, who carries responsibility, and how leaders review the results.
  • Businesses need security arrangements that suit their size, operations, and risks. Clear responsibility matters even when there is no dedicated IT department.
  • An information security management system provides an organized approach to managing information risks. ISO/IEC 27001 sets requirements for establishing and improving that system.

Information Security Governance: Overview

At the end of 2024, MTN Group reported about 291 million subscribers across 16 markets. A few months later, the company announced that someone had gained unauthorized access to some customers’ personal information. That subscriber figure describes the size of the business, rather than the number affected by the incident.

The announcement left an important part of the story unanswered: where had the access happened?

MTN said its main network and financial services infrastructure remained secure. Yet customer information had been accessed elsewhere. In a later account, the company described an older technology environment that was already scheduled for migration. Before the move was completed, a server inside that environment was compromised.

That sequence caught my attention. The system had a planned destination, but it still needed protection while the move was pending. It is a situation worth examining if your business has ever postponed a software upgrade, kept an old application running, or moved customer records between systems.

To understand the information security governance lessons, we need to follow the story from the first announcement.

What Happened in the MTN Data Breach?

On 24 April 2025, MTN Group announced that a cybersecurity incident had resulted in unauthorized access to some customers’ personal information in certain markets.

The company said an unknown third party had claimed access to data connected to parts of its systems. Its statement did not name the affected markets or give a precise number of affected customers.

MTN also drew a boundary around what it knew at that point. It reported no evidence that its critical infrastructure, core platforms, or services had been compromised. Its core network, billing systems, and financial services infrastructure remained operational. It had no information suggesting customers’ accounts or wallets had been directly compromised.

Those details matter when reading the announcement. MTN had confirmed access to personal information while reporting that the systems supporting its main services remained secure. The disclosure therefore concerned more than whether customers could still make calls or use their accounts.

The Initial Response Included Authorities and Customers

MTN said it activated its cybersecurity response processes and informed the South African Police Service and the Hawks. It also notified relevant country authorities and said it was working with authorities and law enforcement to support investigations.

At the time of the announcement, the company was notifying affected customers in line with local requirements.

Its public advice asked customers to remain alert to suspicious messages, protect their passwords and avoid sharing PINs or one-time passwords. These precautions formed part of its response to the possible misuse of exposed information.

The announcement explained the immediate response. The more detailed account of the technology involved came later.

A Later Account Identified an Older Environment Awaiting Migration

On 28 April 2026, MTN published a case study explaining that the incident involved a legacy environment. In this context, that means an older technology environment still in use.

MTN said it had scheduled that environment for migration into the Group’s fully managed domain. Before the migration was completed, it was compromised. The incident exposed a logging server receiving data from several operating companies.

This added an important detail to the original disclosure. The affected environment had connections to several parts of the business, and work to move it was still pending when the compromise occurred.

The public account does not explain every internal decision or establish why the migration had not yet been completed. It does, however, identify the period during which protection mattered: the existing environment was still operating while awaiting the move.

MTN Removed the Server and Reviewed Other Environments

According to the case study, MTN identified, isolated, and permanently removed the compromised server within 48 hours. The company also said it notified relevant regulators and directly informed affected customers.

Its response extended to a review across its markets. MTN said it examined possible vulnerabilities, accelerated the migration of unmanaged environments, and strengthened interim controls where full integration was not yet possible. The review informed a two-year cybersecurity enhancement programme scheduled for completion in 2026.

This is the part of the response I would draw a business owner’s attention to. After addressing the affected server, MTN examined whether other environments needed attention too.

A business reviewing this story should follow that same line of enquiry. An issue in one application gives you a reason to check other applications with similar arrangements, especially where information moves between them.

Why This Story Matters Beyond Telecommunications

A smaller business might recognize a simpler version of this situation. An old customer database stays online while a new one is prepared. A former booking platform still holds customer details. Staff continue using a shared folder because moving its contents has been postponed.

These are examples of situations to review, rather than claims about what happened inside MTN.

The practical question is who remains responsible while the work is unfinished. Someone needs to know what information the system holds, who can access it, and what protection remains in place.

What Is Information Security Governance?

Information security governance is the way a business sets direction, assigns responsibility, and oversees decisions about protecting its information. It establishes who has authority to make those decisions and how the organization checks whether its approach supports business needs.

Let’s use a business with five employees as an example. The team keeps customer names, phone numbers, invoices and contracts in a shared online folder. Everyone uses it because it makes work easier.

The owner still needs to decide who should have access. Someone needs responsibility for removing access when an employee leaves. If a document is shared with the wrong person, the team needs to know who to tell and what to do next.

Governance gives those decisions a clear owner. It also creates a way to check that people follow through.

In a larger company, the same questions involve more departments, systems and suppliers. A manager might handle access within one department, while senior leaders approve spending and review risks affecting the wider business. Clear reporting helps information reach the people with authority to act.

The arrangements should fit the organization. The UK’s National Cyber Security Centre advises businesses to establish governance roles and decision processes suited to their circumstances, with clear responsibility for security throughout a system’s life.

For your business, a useful starting point is to identify who answers for the information you keep. That includes customer details, employee records, and supplier information and documents the business depends on.

From there, you need to understand how those decisions become everyday work. That is the relationship between information security governance and information security management.

Information Security Governance vs. Information Security Management

Information security governance sets the direction for protecting information and establishes who answers for the decisions. Information security management puts that direction into practice through the work people carry out each day. The two depend on each other.

Think back to the five-person business using a shared folder. The owner decides that employees should only access the customer information they need for their work. The owner also assigns responsibility for checking access and expects any concerns to be reported.

Someone then needs to set up those permissions, remove former employees and check whether files have been shared outside the business. That is the management work that makes the decision effective.

Business issueGovernance responsibilityManagement responsibility
Access to customer recordsApprove the access policy and assign accountability.Set permissions, review access and remove it when necessary.
An older application awaiting replacementDecide how the risk will be handled and approve the resources needed.Maintain safeguards, monitor the application and carry out the migration.
A security incidentEstablish reporting responsibilities and oversee significant decisions.Investigate, contain the incident and carry out the response.
Outstanding security problemsReview significant risks and hold people accountable for agreed actions.Complete the corrective work and report progress.

In a small business, the owner might handle responsibilities in both columns. As the company grows, more people become involved, and the handover between them needs attention.

A policy might say access must be removed when someone leaves. For that to happen, whoever manages the accounts needs to know about the departure. Someone also needs to check that the account was actually closed.

When reviewing your business, check both the decisions made and whether people follow through. Clear instructions help people understand what to do. Regular oversight helps leaders see whether it happened.

Three Information Security Governance Lessons From MTN

MTN’s account gives us a specific situation to learn from: an older environment awaiting migration, a compromised server receiving information from several operating companies, and a subsequent review across its markets. The following lessons are practical conclusions drawn from that account.

1. Give Someone Responsibility Until the Work Is Finished

When a business approves an upgrade, attention naturally moves towards the new system. People discuss the launch date, the features and how much easier work should become. The existing system still needs an owner during that period.

That person needs to know what information it holds, which problems remain unresolved and when to raise a concern. If the replacement takes longer than expected, someone must review what that means for security.

For a smaller business, this might involve an old sales application that still contains customer addresses and order histories. For a larger company, it could involve several connected applications across different departments.

The practical step is the same: name the person responsible for the existing system and keep that responsibility clear until the system has been safely retired or transferred.

2. Follow the Information Across Your Business

MTN said the compromised logging server received data from several operating companies. That detail shows why a security review needs to consider the connections between systems.

In your business, a customer might enter information through a website form. A copy then reaches an email inbox, a spreadsheet and an application used by the sales team. A delivery provider might receive some of it too.

Each step creates another place to examine. Who has access there? What information do they receive? How long do they keep it?

Start by following one ordinary customer transaction from beginning to end. Write down where the information goes and who handles it. That gives you something concrete to review, including copies that might otherwise be overlooked.

3. Use One Incident to Check for Similar Problems Elsewhere

After addressing the compromised server, MTN said it reviewed environments across its markets. It also described stronger temporary safeguards where full integration remained pending.

There is a useful habit here for businesses of any size. When you find a problem, check whether the same arrangement exists elsewhere.

Suppose a former employee still has access to your customer database. Removing that access deals with the immediate issue. You should then review other former employees’ accounts and check how departures are communicated to whoever manages access.

The wider review helps you understand whether the problem came from one missed action or a process that needs attention. Give the corrective work an owner and a deadline, then check that it has been completed.

These lessons become easier to apply when the business has a clear framework for making decisions and following them through.

What Should an Information Security Governance Framework Include?

An information security governance framework brings together the responsibilities, decisions and review arrangements a business uses to oversee information security.

The size of that framework should reflect the business. A small company might use a short policy, a risk register and regular reviews with its service provider. A larger organisation will usually need more formal reporting and responsibilities across departments. The aim is to give the right people enough information and authority to make sound decisions.

Build your information security governance framework around these six areas.

Clear Responsibilities and Decision-Making Authority

Start by identifying who answers for information security and who handles the work. Make it clear who approves access, authorises spending and decides what happens when a significant risk remains unresolved.

If you use an external IT provider, agree on its responsibilities and the matters it must bring back to you. Your team should know when to contact the provider and when a decision needs the owner’s or management’s attention.

An Understanding of the Information That Matters

Your business needs to know what it is protecting. Customer details are one part of this. Employee records, contracts, financial information and business plans also deserve attention.

Identify where important information is kept and what would happen if it were exposed, changed without permission or unavailable when needed. Those consequences help you decide where to concentrate resources.

A Process for Reviewing and Accepting Risks

Some problems need immediate action. Others require a planned fix or further investigation. Someone with the right authority needs to make that decision.

Keep a record of the risk, the action agreed and the person responsible. Where management accepts a risk for a period, record the reason and a date to review it. This gives an outstanding issue a clear place in the business’s decisions.

Policies Supported by People and Resources

A policy should explain what the business expects in terms people understand. It might cover access to records, sharing information, using personal devices and reporting suspicious activity.

People also need the time, training and tools to follow it. If your policy requires regular access reviews, assign someone to conduct them and make the necessary records available. The instruction needs practical support.

Reporting That Helps Leaders Take Action

A security update should help you understand what needs a decision. A useful report might show overdue actions, systems awaiting replacement, important supplier concerns and the results of recent checks.

Ask for enough explanation to understand the business impact. If an application is no longer receiving security updates, you need to know what it holds, how it is protected and what options are available.

Regular Review and Follow-Through

Set a review schedule that suits the business and arrange additional reviews when significant changes occur. A new supplier, a system migration or a security incident might require earlier attention.

Use the review to check progress, reconsider unresolved risks and decide what needs to change. Record those decisions so they lead to work someone owns. Clear responsibilities, risk oversight and meaningful reporting are central themes in established governance guidance.

Once these arrangements are in place, the next task is to make them part of everyday operations. An information security management system helps organise that work, from assessing risks to checking whether the safeguards are effective.

How an Information Security Management System Supports Governance

Once you have assigned responsibilities and agreed on priorities, the work needs a structure people can follow. An information security management system, usually shortened to ISMS, brings together the policies, processes, people and safeguards used to manage information security risks. ISO/IEC 27001 sets requirements for building and continually improving that system.

Think about a business that wants to protect its customer records. Management has already decided who should have access and who answers for security. The next step is to turn those decisions into everyday arrangements.

Someone documents how access is approved. New employees receive instructions before using the system. Access changes are recorded, and reviews check whether people still need the permissions they hold. If a review finds a problem, someone takes responsibility for correcting it.

Those activities belong together. Each one helps the business carry out its decisions and check the results.

Protecting Confidentiality, Integrity and Availability

An ISMS addresses three qualities of information: confidentiality, integrity and availability. In plain language, information should reach authorised people, remain accurate and complete, and be accessible when needed.

For a small clinic, confidentiality means keeping patient records accessible only to authorised people. Integrity means protecting those records from improper changes. Availability means the clinician can retrieve them when treating a patient.

A business needs to consider all three. A file might be well protected against unauthorised access but impossible to recover after a computer fails. Another might remain available while employees accidentally overwrite important details.

This is why the work starts with understanding the information and the risks around it. The safeguards should respond to what could realistically go wrong.

Giving Leaders Evidence to Review

An ISMS gives leaders records they can use to assess performance. These might include incident reports, audit findings, staff training records and the results of security checks.

The value comes from what those records reveal. Repeated access errors might point to unclear instructions. Unfinished corrective actions might show that a team needs more time or resources. Management reviews help turn those findings into decisions.

ISO 27001 in Nigeria: Leadership, Scope and Certification

For a Nigerian business looking to formalise these arrangements, ISO/IEC 27001:2022 provides an internationally recognised set of ISMS requirements. Organisations can implement the standard and decide whether to pursue certification. Certification itself is carried out by an external certification body. ISO develops standards but does not issue those certificates.

Before discussing certification, though, let’s look at two things: who will lead the work and what the system will cover.

Leadership Has Responsibilities Throughout the Process

ISO 27001 places responsibilities on top management. These include establishing the security policy and objectives, providing resources, assigning responsibilities and supporting continual improvement.

In a small company, that involvement might come directly from the owner. In a larger organisation, several senior managers will have responsibilities within the system’s scope.

Either way, someone needs authority to resolve issues that the implementation team cannot settle alone. An employee reviewing access might identify a problem, but management might need to approve spending, change a supplier arrangement or decide how an outstanding risk will be handled.

That involvement should continue after certification. The business will keep changing, and its security arrangements need regular review.

Read What the Certificate Actually Covers

A certificate has a stated scope. That wording matters because it identifies the activities covered by the certified management system.

MTN Nigeria’s published certificate provides a useful example. Its scope includes commercial data centre services and the design, development and support of three named applications: EWP, MADAPI and NPG, located in Lagos. The certificate lists an original registration date of 25 June 2018.

This tells us something specific about the certified activities. It does not establish the certification status of every MTN Group operation or explain whether the environment involved in the incident fell within that scope.

The same care applies when reviewing your own certificate or a supplier’s. Read the scope and check whether it covers the service you are relying on. Look at the named organisation, locations and activities, then verify the certificate’s status with the issuer.

Understand What Certification Demonstrates

Certification provides independent assurance that the management system meets the relevant requirements within its scope. An accredited certification body adds another level of assurance because its competence has been independently assessed.

Your business still needs to operate the system, respond to changes and address weaknesses. A certificate should therefore sit alongside evidence of ongoing work: reviews completed, staff trained, risks assessed and problems corrected.

For businesses considering ISO 27001 in Nigeria, the useful starting point is understanding the gaps in current practice. That gives the implementation effort a clear purpose and helps management decide what support it needs.

What Nigerian Businesses Should Know About Data Protection Obligations

The MTN story also brings us to the responsibilities Nigerian businesses have when handling people’s information. The main legal framework is the Nigeria Data Protection Act 2023, supported by the NDPC’s General Application and Implementation Directive 2025, commonly called the GAID. The Commission reports that the GAID came into force on 19 September 2025.

For this discussion, the important connection is between legal responsibilities and the everyday decisions your business makes about information.

Know Why You Collect Information and How You Use It

The Act requires lawful, fair and transparent processing. It also requires attention to the purpose of collection, the amount of information collected and how long it is retained.

Take a customer enquiry form as an example. Before adding another field, consider why the business needs it. The person completing the form should receive clear information about how their details will be used.

The same thinking applies after collection. Customer information should have an agreed purpose and retention arrangement. Otherwise, old records tend to remain scattered across inboxes, spreadsheets and applications long after anyone has reviewed them.

Put Appropriate Safeguards in Place

Section 39 requires appropriate technical and organisational measures to protect personal data. The factors to consider include its sensitivity, possible harm, retention period and the availability and cost of safeguards relative to the organisation’s size.

For your business, that means making deliberate choices about access, storage, staff responsibilities and recovery arrangements. The appropriate level of protection depends on what you hold and the consequences of something going wrong.

A clinic handling medical records and a retailer holding delivery details will have different circumstances to assess. Both need to understand their information and make sensible provision for protecting it.

Prepare for Breach Reporting Before an Incident

Section 40 requires a controller to notify the NDPC within 72 hours of becoming aware of a breach likely to risk individuals’ rights and freedoms. Where a breach is likely to create a high risk, affected individuals must be informed immediately. The Act also requires breach records.

Those requirements make internal reporting important. An employee who notices unusual access needs to know whom to contact. The person receiving the report needs a process for arranging investigation and assessing notification duties.

Waiting until an incident occurs to assign those responsibilities makes the response harder.

Check the Requirements That Apply to Your Business

The GAID provides further requirements covering matters such as compliance audits, training and data security reviews. Registration and certain filing obligations depend on the applicable classification of the controller or processor. Your business should assess its position against the current rules.

ISO 27001 implementation can support the security work involved, but legal compliance needs its own review. You still need to identify the obligations attached to how your business collects, uses and shares personal information.

With those responsibilities understood, the next step is to examine what your business already does and decide where improvement should begin.

How to Improve Information Security Governance in Your Business

Once you understand the responsibilities involved, the next step is to decide what needs attention first. Trying to change everything at once makes it harder to judge whether the work is helping.

Approach this in stages, starting with how your business currently operates.

Establish Your Starting Point

Bring together the policies, supplier agreements, incident records and security reports you already have. Then compare those documents with what people actually do.

You might discover that a written procedure has fallen out of use, or that employees have developed a useful practice nobody has documented. Both findings matter. They help you build an accurate picture before deciding what to change.

If your goal is ISO 27001 implementation, use a gap analysis to compare those arrangements with the standard’s requirements.

The Information Security Governance Checklist at the end of this article provides a starting point for that conversation. Use it to identify areas requiring a closer look.

Prioritise the Gaps by Their Likely Impact

Some findings deserve attention sooner than others. Consider the sensitivity of the information, the likelihood of something going wrong and the effect it would have on people and operations.

For example, a publicly accessible folder containing customer records would deserve more urgent attention than an outdated heading in an internal policy.

This helps you explain why a particular action should receive time or funding. It also keeps the improvement plan connected to the risks the business actually faces.

Put the Changes Into Everyday Work

Once you agree on an improvement, explain it to the people affected and build it into the process they already use.

If you change how employees request access, include the new steps in onboarding. If you introduce a way to report security concerns, make sure staff know where to send a report and what information to include.

Walk through the process with the team. A procedure that seems clear to its author might raise questions when someone tries to follow it.

Check Whether the Improvement Works

Choose evidence that matches the change. After improving employee onboarding, review a sample of new accounts. After updating the incident-reporting process, run a short exercise and see whether the report reaches the right person.

Use what you find to adjust the process. That gives you a practical way to improve without waiting for a serious incident.

Astute Business Consult supports management system implementation. Bringing your findings and priorities into that discussion helps focus the support on the areas your business needs to address.

What MTN’s Experience Means for Cybersecurity in Africa

MTN’s account shows how a shared technology environment can connect information from several operating companies. That connection is relevant to businesses expanding across African markets, particularly where branches rely on common applications and service providers.

Expansion creates decisions about where information will be processed, which teams will use it and which suppliers will support the work. Those decisions should form part of planning a new operation.

Consider a Nigerian business opening an office in another country. Its existing customer system might be convenient for both teams. Before extending access, the business needs to understand what information will become available, where it will be stored and which legal requirements apply.

For transfers of personal data from Nigeria, the Nigeria Data Protection Act sets conditions for transferring information abroad and requires the basis for the transfer to be recorded. The applicable route needs to be assessed for the particular arrangement.

There is also a practical reporting issue. If a shared service has a security problem, the people responsible in each affected operation need reliable information quickly. Agreeing those communication arrangements in advance helps teams understand their responsibilities.

Resolve these questions as you plan your business’s expansion. Adding a new market should include reviewing how its information will fit into the wider organisation’s security arrangements.

Frequently Asked Questions About Information Security Governance

Does Information Security Governance Cover Paper Records?

Yes. Information security also concerns printed records and information handled outside digital systems. ISO 27001’s scope includes protecting information in different forms.

For a business keeping printed contracts or employee files, this includes deciding who can retrieve them, where they are stored and how they are disposed of.

Can We Outsource Information Security Governance to Our IT Provider?

An IT provider can carry out agreed security work and advise management. Your leadership still needs to set priorities, approve significant decisions and oversee the arrangement. Clear responsibilities and escalation routes are central to effective governance.

Ask the provider to explain what its service includes, what it expects your team to handle and which issues require your approval.

How Often Should Leaders Review Information Security?

Set a schedule that reflects the business’s risks and rate of change. Significant incidents, new services and major operational changes should also prompt a review.

ISO 27001 requires management reviews at planned intervals. A quarterly review is one possible arrangement, but the appropriate schedule needs to suit the organisation.

What Should an Information Security Report Show?

A useful report should explain significant risks, incidents, overdue actions and decisions requiring management attention. Include enough context for the reader to understand the effect on the business.

For example, a report about a failed recovery test should explain which information could not be restored, the likely operational impact and the proposed corrective action. The purpose is to support a decision.

Check How Your Business Protects Customer Information

MTN’s account began with unauthorised access to customer information and later explained the older environment involved. For your business, the useful next step is to examine the arrangements you have today.

You do not need to settle every question in one meeting. Start with an honest review and use the findings to decide what deserves attention first.

Download the Information Security Governance Checklist

The checklist will help you review leadership responsibilities, information handling, supplier oversight and outstanding security risks.

Work through it with the people responsible for your records and systems. Use the findings to identify gaps and agree on the next actions.

Related Articles

Facebook
Twitter
Email
Print

Leave a Reply

Your email address will not be published. Required fields are marked *