Security · Leadership

Cyber risk is a board item now: five questions for Malaysian directors

Reported cyber incidents and data breaches in Malaysia keep rising, and the law now expects companies to detect and report them. What a director or owner should ask, in plain language.

Pikabyte Engineering 4 min read

5,735

cyber incidents reported to Cyber999 in the first nine months of 2025

Cyber security used to be something the IT person handled. Three things have moved it to the board table.

The volume. CyberSecurity Malaysia’s Cyber999 response centre recorded 5,735 incident reports in the first nine months of 2025. MyCERT counted 195 data breach reports in the first quarter of that year alone, up from 151 the quarter before.

The law. The Cyber Security Act 2024 came into force in August 2024, setting obligations for operators of critical national infrastructure and licensing for cyber security service providers. The amended Personal Data Protection Act requires notification of significant data breaches and the appointment of data protection officers.

The supply chain. Even if your company is not regulated directly, your customers are. Banks, insurers, hospitals and large manufacturers now ask their suppliers how they protect data, and they ask before they sign.

A director does not need to understand firewalls. A director does need to ask five questions and recognise a good answer.

1. What would hurt us most, and where is it?

Every company has a short list of things whose loss or exposure would be serious: customer personal data, pricing, designs, financial records, the ability to operate at all.

A good answer names them and says where each is kept: which system, which cloud account, which supplier.

A poor answer is “everything is in the cloud”.

2. Who can get in, and how would we know?

Most incidents at small and medium companies are not clever. Someone uses a password or key they should not have.

Ask how many people and systems have administrator access. Ask whether every person signs in with a second factor. Ask whether there are long-lived access keys stored in files or laptops, and what each one can do.

We responded to a case where one such key, with administrator rights, was exposed. The attacker used it at 11 at night to run AI services on the client’s account and to plant ways back in. Cleaning up meant sweeping every region and service, removing every access key and reviewing every role.

A good answer includes a number and a recent date: “seven people, all with multi-factor sign-in, reviewed last quarter”.

3. If something happened tonight, when would we find out?

Detection is the gap. An incident found in an hour is an inconvenience. One found at month-end, on the bill, is a crisis.

Ask what alerts exist, who receives them, and whether that person would see one at the weekend. Ask whether there is a log of activity that an intruder could not delete.

A good answer describes an alert that reaches a named person’s phone.

4. Could we recover, and have we tried?

Backups that have never been restored are a hope, not a plan.

Ask when a restore was last tested, how long it took, and how much data would be lost. Ask whether the backups are kept somewhere an attacker with access to the main system could not reach.

A good answer includes the date of the last test.

5. Who do we call, and what must we report?

In an incident, the first hours matter and nobody thinks clearly.

Ask whether there is a written list: who decides, who is called, which regulator must be told and within what time, who speaks to customers. Under the amended data protection law, published guidance describes a 72-hour window for notifying a significant breach. That is not long if the first day is spent finding out who is in charge.

A good answer is a one-page document someone can produce on request.

What it costs to get to good answers

Less than most boards expect. For a company running on a cloud provider, the essentials are a matter of setup, not spending:

  • Single sign-on with a second factor, and no stored access keys
  • Limits that apply even to administrators, including blocks on services you do not use
  • An activity log that cannot be switched off
  • Spend alerts that reach a person
  • Tested backups

We put that baseline in place in about a day. The expensive part of security is the incident you were not ready for.

How to raise it

Put the five questions on the agenda once a year. Ask for the answers in writing, one page. Compare them with last year’s.

The board does not need to be technical. It needs to notice when an answer is vague.

Sources

This article is general information and is not legal advice.

Written by

Pikabyte Engineering

Pikabyte builds custom business systems, applied AI and secure cloud infrastructure from Malaysia. Talk to us.

Start a conversation

Want this applied to your business?

Tell us what is slowing the business down. You will talk to an engineer, not a salesperson, and get a straight answer on whether software is the right fix.