Stage 3 of 3 · Act

The 90-day plan: what leaders do, ask and decide

Everything in this report comes down to four habits: close the common doors, limit what any one account or agent can do, notice quickly, and recover fast. Here is how to put them in place in 90 days, with an owner for each step.

  • 9 min read
  • For CEOs, boards and executive teams
  • Includes a 10-question self-check

Board questions this part answers

  • Which risks have we accepted, and who owns them?

Four layers of defense, built around the business

Pick a layer to see where it stops an attack, what it involves, and who owns it. No single layer is enough; together they turn a breach into an incident.

Tap a layer to see where it stops the attack

  • Strong, phishing-resistant sign-in on email, admin accounts and remote access, with no exceptions for executives.
  • A complete list of internet-facing systems, each with an owner, and critical flaws fixed in days.
  • Help-desk resets only after verifying the caller on a channel they do not control.

Owned by CISO or Head of IT

Go deeperWho owns what

An agent can carry out a task. It cannot carry accountability. Neither can a security vendor. These are the owners in most companies; titles differ, the jobs do not.

Who owns what
RoleOwnsMust be able to show
Board and CEOHow much risk the company accepts, and which services matter mostDecisions on trade-offs, and funding for the gaps
CIO or CTOSystems, architecture and AI deploymentsThe agent and system inventories, release checks, restore results
CISO or Head of IT SecurityThreats, controls and the response teamCoverage figures, detection and containment test results
CFOPayment controls and the cost of disruptionFraud test results, cash runway with systems down, insurance terms
COO and business ownersEach critical service, and what an agent in it may doTolerable outage times, manual fallbacks, approved agent scopes
General Counsel and DPOLegal duties and contractsThe notification matrix and supplier obligations
HR and ProcurementPeople and suppliers joining and leavingAccess removed on exit; supplier access reviewed and cut off on demand

The 90-day plan

Four stages with owners and a proof of done for each task. Tick tasks off as you go. Urgent active threats always take priority over the calendar.

Tap a stage, then tick tasks off as you go

Tasks done: 0 / 16

Know what matters, who can reach it, and where the obvious gaps are.

  • Rank the 5 to 10 services the business cannot run without, with a tolerable outage time for each.

    Owner: CEO, COO and business owners · Done when: A one-page list signed by each owner.

  • List every AI agent, assistant and connected app, including those bought by departments.

    Owner: CIO · Done when: A register with an owner for every entry.

  • Review who holds admin rights and remove any that are not needed.

    Owner: Head of IT · Done when: Before-and-after counts of admin accounts.

  • Fix or isolate internet-facing systems with critical flaws.

    Owner: CISO and COO · Done when: Each one fixed, isolated or formally accepted by a named executive.

The first 24 hours of an attack

What the leadership team does, in order. Keep a printed copy: the systems holding your plan may be the ones that are down.

  1. Name one incident lead

    One person runs the response and reports to the CEO. Everyone else knows who that is.

  2. Contain first, investigate second

    Isolate affected systems, revoke stolen access and pause risky integrations and agents. Stopping the visible agent may not stop the work it started; check queued jobs and connected services.

  3. Preserve evidence and start the log

    Record what was seen, when, and every decision. Do not wipe and rebuild before evidence is kept; you will need it for insurers, regulators and the police.

  4. Call counsel and the insurer

    Their breach lines exist for this. In Indonesia, if personal data is involved, the 3 × 24-hour clock may already be running.

  5. Decide how the business keeps running

    Manual processes, which channels stay open, and how staff, suppliers and customers are told.

  6. Say only what you know

    Confirmed facts, what you are doing, and when you will update next. Do not blame AI, or anyone, before the evidence supports it.

  7. Restart on evidence, not on hope

    Bring systems back when they are clean, access is restored to the right people, and transactions reconcile, not just because the screen works again.

The board self-check: ten questions

Answer honestly; 'don't know' is a useful answer. Your result shows where to start and whom to ask. Nothing you enter leaves this page.

Answer each question for your company

  1. 1Which outage would hurt us most, and how long could we survive it?

    Evidence that answers it: A ranked list of critical services with tolerable outage times.

  2. 2What can each of our AI agents actually do, and can we stop it?

    Evidence that answers it: An agent register showing access, actions and limits, and a tested way to stop each agent.

  3. 3Who owns each supplier and app connection into our systems?

    Evidence that answers it: A register of connections with owners and a way to revoke each one.

  4. 4Can one person both request and approve a payment?

    Evidence that answers it: A separation-of-duties test.

  5. 5Could an email or document trigger an action in our systems?

    Evidence that answers it: Results of tests with hidden instructions in documents and emails.

  6. 6Who must we tell after a breach, and how fast?

    Evidence that answers it: A notification matrix approved by counsel, with owners and deadlines.

  7. 7Have we proven we can restore our critical systems?

    Evidence that answers it: A dated result of restoring a critical system from backup into a clean environment.

  8. 8Would our finance team stop a convincing fake request from the CEO?

    Evidence that answers it: An unannounced payment-fraud exercise.

  9. 9What happens if a critical supplier goes down?

    Evidence that answers it: A tested fallback for each critical supplier.

  10. 10Which risks have we accepted, and who owns them?

    Evidence that answers it: A list of exceptions with owners and end dates.

Go deeperHow the score works

How the score works: 'Yes, with evidence' counts 2 points, 'Partly' 1, and 'No' or 'Don't know' 0, out of 20. Below 40% is Exposed, 40 to 69% Partly prepared, 70% and above Well prepared. A useful answer has a date and a result: 'We restored this service on this date and met the target' is evidence; 'We have backups' is not.

Go deeperWhat the board should see every quarter

Measures with an owner and a trigger for action. Show the worst items next to the averages; one untested recovery plan can matter more than excellent coverage elsewhere.

What the board should see every quarter
MeasureHow it is calculatedWhat to watch
Agents with an ownerProduction agents with a named owner ÷ agents discoveredAgents found that nobody approved
Risky actions under controlHigh-impact actions with tested approval ÷ all high-impact actionsInclude tools and delegated tasks in the count
Strong sign-in coverageProtected privileged accounts ÷ all privileged accountsSeparate people, service accounts and agents
Age of critical exposuresDays open for each critical weakness facing the internetThe oldest items, and any accepted exceptions
Time to containDetection to confirmed removal of harmful accessInclude nights, weekends and supplier delays
Recovery provenCritical services restored within target ÷ critical servicesWhich services have never been tested
Supplier readinessCritical suppliers with a tested escalation route ÷ critical suppliersA certificate alone is not a test

If you want help

Within Red Asia Group, SALT runs security operations around the clock and AI-assisted security testing for enterprises. If you would like a second opinion on your 90 days, we are glad to talk.

Questions leaders ask

What should a board ask about cyber security?

Which outage would hurt us most and how long could we survive it; what each AI agent can do; who owns each supplier connection; whether one person can request and approve a payment; when we last restored from backup; whether finance would stop a fake CEO request; and which risks we have accepted and who owns them.

What should we do in the first 24 hours of a cyber attack?

Name one incident lead, contain affected systems and stolen access, preserve evidence and log every decision, call legal counsel and your insurer, decide how the business keeps running, and communicate only confirmed facts. In Indonesia, start the 3 × 24-hour UU PDP clock if personal data is involved.

Who is responsible for cyber security in a company?

The board owns the risk, the CEO owns the response, and a named executive, usually the CISO, CIO or Head of IT, runs security day to day. Business owners decide what their services and AI agents may do.

Where do we start if we have done nothing yet?

Turn on strong multi-factor sign-in for email, admin and remote access; make offline backups and test restoring them; add a callback and second approver for payment changes; and write a one-page incident plan with names and phone numbers.

How do we measure our readiness?

Use the ten-question self-check on this page. 'Yes, with evidence' scores 2, 'Partly' 1, and 'No' or 'Don't know' 0; below 40% is Exposed, 40 to 69% Partly prepared, and 70% or more Well prepared.

Board questions this part answers

  • Which risks have we accepted, and who owns them?

Want a second pair of eyes on your 90 days?

Red Asia Group's technology companies run security operations and testing for enterprises in Indonesia. If you want help turning this report into your own plan, start with a conversation.

Sources for this part4 sources
  1. [14]

    CISA, FBI and partners · Scattered Spider joint advisory (AA23-320A)

    Revised 29 July 2025. Describes criminals calling IT help desks to have passwords reset and sign-in devices moved.

    Open the original
  2. [37]

    CISA, NSA and partners · Careful adoption of agentic AI services

    1 May 2026. Joint guidance from US, Australian, Canadian, New Zealand and UK agencies.

    Open the original
  3. [43]

    Republic of Indonesia · Law No. 27 of 2022 on Personal Data Protection (UU PDP)

    17 October 2022. Article 46 (3 × 24-hour notice), Article 34 (impact assessment), Article 56 (transfers abroad), Article 57 (administrative sanctions).

    Open the original
  4. [58]

    CISA · Implementing phishing-resistant MFA

    Fact sheet. Sign-in methods that a fake login page cannot capture.

    Open the original