# : Secure by Design

DigiNepal Magazine · No. 2 · November 2026

> What Black October 2026 taught the world — and the discipline Nepal cannot skip.

URL: https://diginpl.com/magazine/2026-11-secure-by-design

Cover photo: A padlock and circuit-trace motif on a dark field (Illustration · DigiNepal Magazine)

## On the cover

- WE UPGRADED THE TECHNOLOGY.
- DID WE UPGRADE THE SECURITY?

## From the editor

October 2026 delivered one of the most alarming stretches in recent cybersecurity memory — from critical PHP and Node.js flaws to supply-chain compromises, cloud breaches and a certificate-authority crisis. Our founder reflects on what it means for everyone building the digital future, and why Nepal cannot skip the discipline of building secure by design.

## In this issue

- [We Upgraded the Technology. Did We Upgrade the Security?](https://diginpl.com/magazine/2026-11-secure-by-design/we-upgraded-the-technology-did-we-upgrade-the-security) — Feature: What Black October 2026 taught the world about building — and the discipline Nepal cannot skip.
- [SecInv: You Cannot Protect What You Cannot See](https://diginpl.com/magazine/2026-11-secure-by-design/secinv-you-cannot-protect-what-you-cannot-see) — Feature: Inside SecInv — the agent-based security and management console built to give an organisation real-time, verifiable control of every device on its network.
- [The hospital is moving home](https://diginpl.com/magazine/2026-11-secure-by-design/the-hospital-is-moving-home) — Feature: AI that assists instead of replaces, care that starts before you are sick, and health data that patients actually own — Padam Sundar Kafle on where digital health goes next, and why it only works when it is built on trust.

---

# We Upgraded the Technology. Did We Upgrade the Security?

*Feature* · DigiNepal Magazine, No. 2 · November 2026

> What Black October 2026 taught the world about building — and the discipline Nepal cannot skip.

By Padam Sundar Kafle · 10 min read · https://diginpl.com/magazine/2026-11-secure-by-design/we-upgraded-the-technology-did-we-upgrade-the-security

## Key takeaways

- Security by design, not as an afterthought — build it into architecture, code, deployment and operations from day one.
- Modernise before old systems become liabilities: stay supported, patch promptly, know your dependencies.
- Adopt Zero Trust — verify identities, enforce least privilege, limit the blast radius of any compromised credential.
- Secure the software supply chain: review third-party components, protect CI/CD, verify releases, manage secrets.
- Build resilience, not just defences — monitoring, tested backups, rehearsed incident response and recovery.
- Make cybersecurity a leadership responsibility, with budget, accountability, policy and a security-aware culture.

## The month the internet flinched

Every so often, the digital world stops pretending it is invincible.

October 2026 was one of those months — a stretch so bad that security researchers have started calling it **"Black October."** Across a single busy week, the people who keep the internet running watched failure after failure roll across the systems we all quietly depend on.

It started with the runtimes and servers the web is built on. Researchers disclosed two critical flaws in **PHP** — **CVE-2026-109618** and **CVE-2026-109619**, each rated a severe **9.2** — that let an attacker run their own code on a web server *without logging in at all*. The details leaked a day before the patch was ready, and within hours real-world attacks began. **Node.js** shipped urgent fixes for ten vulnerabilities, including one that could execute code through compressed data and others that weakened TLS and DNS checks. **Java** patched fifty-five flaws, forty-nine of them remotely exploitable. Even the plumbing of anonymity was not spared: hijacked **Tor relays** were caught intercepting SSH traffic.

Then it reached the layer of *trust itself*. The AI gateway **LiteLLM** had a malicious version pushed to the world's package registries. **OVHcloud's** official command-line tool was found shipping backdoored binaries. The cloud platforms **Railway** and **Zeabur** disclosed breaches that exposed customer credentials, API keys and database passwords — Zeabur citing more than 321,000 affected accounts. And most unsettling of all, the certificate authority **eMudhra** was found to have eight intermediate signing keys so weak that researchers cracked them almost instantly — forcing Mozilla, Google and Apple to block the certificates worldwide (**CVE-2026-111943**).

Online, someone summed up the mood in five words: *"one-third of the internet is broken."* An exaggeration — but not by as much as we would like.

```stats
9.2 | CVSS severity | PHP, unauthenticated RCE | crit
321,810 | accounts exposed | Zeabur breach | high
8 | weak CA keys | eMudhra, blocked worldwide | high
55 / 49 | Java flaws / remotely exploitable | October patch set | warn
```

Laid out day by day, the week looks less like bad luck and more like a system under sustained strain.

```timeline
Oct 17 | Weak keys found | A researcher finds eMudhra's eight weak CA intermediate signing keys.
Oct 20 | A flaw leaks early | Details of the critical PHP flaw leak a day before the patch is ready.
Oct 21 | "Black October" peak | PHP CVE-2026-109618/109619 (CVSS 9.2) is patched; Node.js ships ten fixes; LiteLLM 1.107.0 is pushed as a malicious release; Railway and Zeabur disclose breaches.
Oct 22 | The fallout | Mozilla, Google and Apple block the eMudhra certificates worldwide.
```

> [!warning] The PHP flaws needed no login and were being exploited within hours of the details leaking. For an exposed server the safe choices narrow to two: patch in a hurry, or pull it offline until you can.

## What these threats actually are

Behind the logos and the jargon, almost all of October's failures fall into four plain-language categories. Understanding them is the first step to not fearing them.

**Remote Code Execution (the PHP and Node flaws).** This is the nightmare scenario. "RCE" means an outsider can make *your* server run *their* instructions — install malware, read your database, take over the machine — often without any password. A single unpatched web server with an RCE flaw is an unlocked front door. That is why the PHP flaws, scoring 9.2 out of 10 and needing no login, set off alarms everywhere.

**Supply-chain attacks (LiteLLM, OVHcloud's CLI, the poisoned packages).** Modern software is assembled, not written from scratch — every app pulls in hundreds of ready-made components. A supply-chain attack poisons one trusted ingredient at the source, so *everyone* who installs it is compromised at once, through the front door they opened themselves. You did everything right and still got hit, because you trusted a tool that was quietly turned against you.

**Certificate-authority compromise (eMudhra).** When your browser shows a padlock, it is trusting a "certificate authority" to vouch that a website really is who it claims to be. That trust is the foundation of every secure connection online. When a CA's secret keys leak — as eMudhra's did — an attacker can forge that proof and impersonate banks, governments, anyone. It is not one broken lock; it is a broken locksmith, and every door he ever made is now suspect.

**Credential and secrets exposure (Railway, Zeabur, SBI).** The keys, passwords and tokens that systems use to talk to each other are the crown jewels. Leak them, and an attacker does not need to break in — they simply log in as you. Worse, rotating a leaked key usually requires a redeployment, and at Railway deployments were frozen during the incident. The lock was fine; someone copied the key.

None of these are exotic. They are the ordinary consequences of an extraordinary pace.

| Threat type | What it is | October example | Why it's dangerous |
|---|---|---|---|
| Remote code execution | An outsider makes your server run their code, often with no login | PHP and Node.js flaws | One unpatched server is an unlocked front door |
| Supply-chain attack | A trusted component is poisoned at its source | LiteLLM, OVHcloud CLI, poisoned packages | You did everything right and are still compromised |
| Certificate-authority compromise | A CA's signing keys leak, so trust itself can be forged | eMudhra | A broken locksmith — every door he made is now suspect |
| Secrets / credential exposure | The keys and passwords systems use to talk to each other leak | Railway, Zeabur, SBI | An attacker logs in as you instead of breaking in |

The specific flaws behind the week show how little room there was to react.

| Issue | Severity | Impact | Fixed in |
|---|---|---|---|
| PHP — CVE-2026-109618 & -109619 | CVSS 9.2 | Unauthenticated remote code execution | 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35 |
| Node.js — 21 Oct release | 10 vulnerabilities | Includes a Brotli RCE | 22.23.4 / 24.22.1 / 26.12.1 |
| eMudhra — CVE-2026-111943 | 8 weak CA keys | Forgeable certificates | Go 1.26.10 / 1.27.3 denylist |
| Java | 55 flaws (49 remote) | Remotely exploitable | October critical-patch update |

## When the locksmith closes shop

October's most consequential failure did not end with a patch. It ended with a business decision.

The security community's account is stark: researchers found **eight** eMudhra intermediate CA signing keys weak enough to crack almost instantly, and Mozilla, Google and Apple blocked the affected certificates worldwide (**CVE-2026-111943**). eMudhra's own account, published on 22 October, is narrower. The company says it revoked the affected authorities *within fourteen hours of discovery*, that no end-entity certificates were ever issued from them, and that its infrastructure was not compromised and no data was breached. Affected customers, it says, receive free certificate replacement, and a full root-cause report is going to the browser root programmes.

Both accounts can be true — and the ending is the same. That same day, eMudhra's board chose to **withdraw from the global SSL/TLS certificate business** altogether — a line it puts at roughly **one percent** of its revenue — while keeping its India signing, PKI and identity services. *"For many certifying authorities, SSL/TLS is the whole business,"* said chairman V. Srinivasan, a reminder of how narrowly some firms sit atop public trust.

```stats
14 hrs | to revoke, per eMudhra | the company's stated response | ok
Blocked | by Mozilla, Google and Apple | the certificates, worldwide | high
~1% | of revenue, exited | the global SSL/TLS line it left
```

That is the real weight of a certificate authority. The padlock in your browser is a promise vouched for by someone you will never meet; when that promise cracks, the cost is not measured in downtime but in trust — and trust, broken at the root, can take an entire line of business down with it. Which is exactly why eMudhra belongs in a story about building for trust. The root of trust is so consequential that a single failure at it can end a business. Build it right, or do not build on it at all.

## Why a wave like this reaches every government

Here is the part that should concern every public institution, including ours.

Governments do not run on a separate, special, safer internet. They run on the *same* PHP, the same Node.js, the same web servers, the same cloud platforms and the same certificate authorities that failed in October. A flaw in a shared ingredient is not one vulnerability — it is the *same* vulnerability sitting inside thousands of government systems at once, from tax portals to land records to health databases.

That is why a single bad week can ripple into public life around the world. When a certificate authority is compromised, every service that trusted it — including government ones — may have to be treated as impersonable until certificates are replaced. When a critical RCE is disclosed with active exploitation, the safe response is often to *take public-facing systems offline* to patch them before an attacker gets in — a precautionary shutdown, chosen as the lesser harm. It is not that every government "fell." It is that a wave like this forces hard choices everywhere at once: patch in a panic, or pull the plug to stay safe.

And the stakes are not abstract. Think about it:

- **Government** — what happens when citizens' identities, public records, or essential digital services are compromised, or must be taken offline to protect them?
- **Healthcare** — what happens when a hospital loses access to critical systems, or to sensitive patient information?
- **Banking and finance** — what happens when financial data, credentials or transactions are exposed?
- **Businesses and startups** — what happens when one poisoned dependency or leaked cloud credential undermines an entire platform?
- **AI and emerging technology** — what happens when we accelerate innovation without securing the systems and supply chains behind it?

These are not IT questions. They are questions about human trust, human safety, and human lives.

## Why this matters more for a country like ours

It would be easy for Nepal to read a list of foreign breaches and feel like a bystander. That would be a mistake.

We are digitising fast — government services, health records, payments, identity. Every one of those systems inherits the same software, the same clouds, the same open-source dependencies, the same certificate authorities that failed in October. We do not get a separate, safer internet. We get the same one, and we carry the same risks — often with thinner margins and fewer specialists to absorb the blow. A backdoored tool, a poisoned package, a leaked key: none of them check your passport at the border.

The lesson is not *"slow down."* Nepal cannot afford to slow down. The lesson is **build it right the first time**, because retrofitting security onto a live national system after a breach is the most expensive and painful way to learn it.

## What must actually change

At DigiNepal, we did not arrive at this view after October. We built the platform around it — government to health, payments to AI, on infrastructure we can stand behind. These are the principles I believe every serious digital effort, public or private, now has to adopt:

> [!key|Secure by design: six principles]
> - **Security by design**, not as an afterthought
> - **Modernise** before old systems become liabilities
> - **Adopt Zero Trust** — verify everything, enforce least privilege
> - **Secure the software supply chain** — even the "official" releases
> - **Build resilience**, not just defences — assume something gets through
> - **Make cybersecurity a leadership responsibility**, not just IT's

**1. Security by design, not as an afterthought.** Security belongs in the architecture, the code, the deployment and the daily operation — from day one, not after the first incident.

**2. Modernise before old systems become liabilities.** Stay on supported technologies. Patch promptly. Continuously assess what your dependencies actually are — you cannot defend what you have forgotten you are running.

**3. Adopt Zero Trust.** Never assume access is safe. Verify identities, enforce least privilege, and design so one compromised credential cannot bring the whole house down.

**4. Secure the software supply chain.** Review third-party components. Protect your CI/CD pipelines. Verify releases — yes, even the "official" ones. Treat secrets management as a first-class discipline. October was, above all, a supply-chain month.

**5. Build resilience, not just defences.** Assume something will eventually get through. Continuous monitoring, tested backups, rehearsed incident response and real recovery plans are what turn a catastrophe into an inconvenience — and what let you patch *without* pulling the plug.

**6. Make cybersecurity a leadership responsibility.** Security is not the IT team's problem to carry alone. It needs budget, accountability, policy, and a security-aware culture that starts at the top.

## The real measure of transformation

I keep coming back to one line, because I think it is the whole argument in a sentence: **digital transformation without digital trust is incomplete.**

True transformation is not measured only by how quickly we ship new technology. It is measured by how safely, how reliably, and how responsibly we deliver it. The platforms — and the governments — that will still be standing a decade from now are not the ones that moved fastest. They are the ones that earned, and kept, the trust of the people who depend on them.

Black October was a wake-up call the world did not ask for but badly needed. For those of us building Nepal's digital future, the right response is not fear. It is resolve.

Let us evolve with technology. Let us modernise with purpose. And above all, let us build systems that are **secure by design, and resilient by default.**

The future belongs not to those who innovate the fastest — but to those who innovate responsibly.

## Sources

1. [eMudhra to exit global SSL/TLS certificate business — eMudhra press release (22 Oct 2026)](https://emudhra.com/en/press-release/emudhra-to-exit-global-ssl-tls-certificate-business)
2. [Mozilla, Google, Apple block compromised eMudhra CA certificates — BleepingComputer](https://www.bleepingcomputer.com/news/security/mozilla-google-apple-block-compromised-emudhra-ca-certificates/)
3. [eMudhra signing keys exposed — Help Net Security](https://www.helpnetsecurity.com/2026/10/21/emudhra-certificates-private-keys-compromised/)
4. [CVE-2026-109618 & CVE-2026-109619: critical unauthenticated RCE in PHP — Rapid7](https://www.rapid7.com/blog/post/etr-cve-2026-109618-and-cve-2026-109619-critical-unauthenticated-remote-code-execution-in-php/)
5. [October 21 cybersecurity roundup — Cyber Security News](https://cybersecuritynews.com/october-21-cybersecurity-nightmare/)

Cite: Padam Sundar Kafle. “We Upgraded the Technology. Did We Upgrade the Security?.” DigiNepal Magazine, no. 2, November 2026. https://diginpl.com/magazine/2026-11-secure-by-design/we-upgraded-the-technology-did-we-upgrade-the-security

---

# SecInv: You Cannot Protect What You Cannot See

*Feature* · DigiNepal Magazine, No. 2 · November 2026

> Inside SecInv — the agent-based security and management console built to give an organisation real-time, verifiable control of every device on its network.

By Padam Sundar Kafle · 4 min read · https://diginpl.com/magazine/2026-11-secure-by-design/secinv-you-cannot-protect-what-you-cannot-see

## Key takeaways

- Agent-based endpoint management: each device enrolls with a client certificate and talks to the console only over mutual TLS.
- Continuous inventory of hardware, OS, network and installed software — so “which machines are affected?” is a query, not a week of phone calls.
- Security posture / compliance checks per device, surfaced live.
- Signed commands (inventory refresh, reboot, scripts, remote session, screen view) that an agent can cryptographically verify came from the console.
- Multi-tenant by entity with role-based access — viewers see, admins act; each facility sees only its own fleet.
- Secure by design: identity proven, commands signed, access scoped, inventory continuous — not bolted on after a breach.

## You cannot protect what you cannot see

Read back the roll-call of October 2026 and a quiet pattern emerges. A backdoored command-line tool. A poisoned package pulled onto thousands of machines. A certificate key compromised at the root. Almost none of it began with a dramatic break-in. It began on an *endpoint* — a laptop, a server, a workstation — running something nobody was watching closely enough.

That is the uncomfortable gap in most organisations. They know their mission, their people and their data. They do not always know, at any given moment, exactly which machines are on their network, what software those machines are running, whether they are patched, or whether one of them is quietly doing something it should not. And you cannot protect what you cannot see.

**SecInv** — the Security and Management Console we built inside the NIHIS health-information programme — exists to close that gap. It is an agent-based endpoint management and security tool: not a dashboard of guesses, but a live, verifiable picture of a real fleet of devices, and the controls to act on it.

## How it actually works

Every managed device runs a small **agent**. On first contact it enrolls using a **client certificate**, and from then on every conversation between the device and the console happens over **mutual TLS** — both sides prove who they are, every time. There is no shared password to leak, no anonymous device quietly checking in.

Once enrolled, the agent periodically reports what the machine actually is: hostname and platform, operating system name, version and build, CPU and cores, memory, disk capacity and free space, network addresses, manufacturer, model and serial — and the full list of installed **software**, by name, version and publisher. That inventory is the foundation everything else stands on, because the first question in any incident is always the same: *which machines are affected, and what are they running?* With SecInv, that is a query, not a week of frantic phone calls.

On top of the inventory sits **security posture** — the compliance checks that tell you whether a device is in the state it is supposed to be in. And when something needs to change, the console does not send a polite request. It issues a **signed command** — inventory refresh, reboot, run a script, open a remote session, view the screen — cryptographically signed so the agent can verify it came from the console and nothing else. A compromised network cannot forge an order to a machine.

| What the console surfaces | The question it answers |
|---|---|
| Inventory | Which machines exist, and exactly what each one is running right now |
| Security posture | Is each device in the state it is supposed to be in? |
| Signed commands | Refresh, reboot, run a script, open a remote session — verifiably from the console, nothing else |
| Multi-tenant, role-based | Each entity sees only its own fleet; viewers see, administrators act |

## Built for how real organisations are shaped

Few institutions are a single flat fleet. A health-information exchange is dozens of facilities, each with its own devices, its own staff, its own responsibilities. SecInv is **multi-tenant by design**: every device, user and policy belongs to an **entity**, and the console scopes what each person can see to the entity they are responsible for. Access is **role-based** — a viewer sees; an administrator acts — so the power to reboot a machine or push a script is never handed out by accident.

The console itself is deliberately plain: **Dashboard, Devices, Agents, Entities, Policies, Users.** No theatre. Just the few things a security team actually needs to answer at 2 a.m. — *what do we have, what state is it in, and what can we do about it right now.*

## Why this belongs in a story about October

The breaches of last month were not, mostly, failures of firewalls. They were failures of *visibility and control* — of not knowing what was running, not verifying what was trusted, not being able to move fast when it mattered. Every principle in the companion piece to this article — know your inventory, verify your supply chain, adopt zero trust, build to recover — lands on the same hard surface: the endpoint.

> [!key|Secure by design, in four moves] How SecInv answers October's failures of visibility and control — with no feature it does not actually ship.
> - **Identity proven, not assumed** — client certificates and mutual TLS on every exchange
> - **Continuous inventory** — hardware and installed software, so "which machines are affected?" is a query
> - **Verifiable control** — every command cryptographically signed; a compromised network cannot forge one
> - **Scoped by entity and role** — viewers see, administrators act, each only within their own fleet

SecInv is one answer to that, and it is the kind of answer I believe in — not bolted on after a breach, but **secure by design**: identity proven with certificates, commands signed, access scoped, inventory continuous. It will not make an organisation invincible. Nothing will. But it replaces the dangerous comfort of *"we think we're fine"* with something far more useful on the day it matters: **we know.**

That is the whole point. In a month that reminded the world how little it sometimes sees of its own systems, the quiet advantage goes to those who can answer, honestly and instantly, a single question — *what is actually running on our machines?*

Cite: Padam Sundar Kafle. “SecInv: You Cannot Protect What You Cannot See.” DigiNepal Magazine, no. 2, November 2026. https://diginpl.com/magazine/2026-11-secure-by-design/secinv-you-cannot-protect-what-you-cannot-see

---

# The hospital is moving home

*Feature* · DigiNepal Magazine, No. 2 · November 2026

> AI that assists instead of replaces, care that starts before you are sick, and health data that patients actually own — Padam Sundar Kafle on where digital health goes next, and why it only works when it is built on trust.

By Padam Sundar Kafle · 4 min read · https://diginpl.com/magazine/2026-11-secure-by-design/the-hospital-is-moving-home

## Key takeaways

- Healthcare is a closed-loop care journey — booking, consult, diagnostics, prescription, delivery, follow-up, monitoring — not a single add-to-cart transaction.
- Care is moving home: remote monitoring, Bluetooth tools and smart sensors make it preventive rather than reactive.
- AI is decision support, not decision-making — it predicts risk and explains reports, but the final medical call stays with a clinician.
- AI + BI = CI: pairing AI with business intelligence turns hospital data into clinical intelligence.
- Patient data is more sensitive than financial data; patients should own and control who sees it.
- Build for security, privacy and, above all, trust by design — adopt technology only where it genuinely solves a problem.

Healthcare is quietly changing shape. For most people it still means one of two things — book an appointment, or get medicine delivered to the door. Useful, but small. What is actually arriving is bigger: a continuous loop of care that begins before you are sick and follows you long after a visit ends.

```video
J7UXR-9Famc | The full discussion — the future of digital health, AI, and care that starts at home.
```

## Healthcare is not add-to-cart

It is tempting to treat health services like any other online shop: add to cart, check out, done. Healthcare does not work that way. It is **need-based**, and it is a journey, not a transaction — an appointment leads to a consultation, which leads to diagnostics and lab tests, a prescription, medication delivery, follow-up, and then long-term monitoring. Each step depends on the one before it.

The right way to think about it is a **closed-loop care system**: every interaction feeds the next, and the record travels with the patient. The checkout button is the least interesting part.

## The hospital is moving home

The sharper shift is where care happens. More and more of it is moving into the home — remote monitoring devices, Bluetooth-enabled medical tools, smart beds with embedded sensors, continuous monitoring that never needs a hospital corridor. The point is not convenience. It is that care can begin to be **preventive rather than reactive**: catching the drift before it becomes a diagnosis.

> [!key|What "preventive" looks like in practice]
> - A personal screening and vaccine timeline that tells you what to check, at what age, and how often — each row cited to USPSTF, CDC, WHO and Nepal's MoHP.
> - The ZettaBand ring and band as preventive sensors: your own vitals flag the moment a clinician visit is worth your time. The device never diagnoses.
> - Upload any lab report and get it read back in plain words with a next step — decision support, never a diagnosis.
> This is the "hospital at home" idea made real, and free, in ZettaHealth.

```stats
57 | conditions | checked at once, across 7 areas
109 | signed rules | USPSTF · CDC · WHO · Nepal MoHP
17M | indexed entries | bilingual, cited
128/128 | calculators | verified correct | ok
```

## AI should assist, not replace

The most important sentence about AI in medicine is the quietest one: its role is **decision support, not decision-making**. AI can do a great deal of real good — predict future health risks, read a patient's history, explain a lab report in language a person actually understands, watch recovery progress, and surface treatment options for a clinician to weigh. What it must not do is make the final call. That stays with a qualified clinician, every time.

And a caution worth repeating: today's models, ChatGPT included, can be **confidently wrong**. They are useful assistants, not autonomous medical experts. Human oversight is not a nice-to-have; it is the design.

## AI + BI = CI

AI's value is not only at the bedside. It can make the hospital itself work better — predicting appointment no-shows, improving staffing, analysing patient flow, reducing insurance-claim friction, sharpening clinical documentation. The useful shorthand is simple: **AI + BI = CI** — artificial intelligence plus business intelligence becomes *clinical intelligence*. Insight and operations, pointed at the same goal: better care, delivered more reliably.

## Data sovereignty, and trust

None of this works without trust, and trust in healthcare rests on one fact: **patient data is more sensitive than financial data.** You can reissue a card. You cannot reissue a diagnosis.

That is why the regulations matter — in the GCC and the UAE, innovation has to respect strong patient consent and data-residency rules, and it should. The direction I believe in goes further: patients should **own and control** who sees their health records — a Web3-style approach where the data belongs to the person, not the platform.

## The next three to five years

Expect more AI-powered services, virtual health companions, a real tilt toward prevention, fewer routine hospital visits, and more treatment delivered at home — with human-in-the-loop AI becoming the standard, not the exception. Healthcare becomes more proactive, more personal, and more technology-driven, without ever handing the final decision to a machine.

## Trust by design

If there is one piece of advice to carry out of all this, it is this: **adopt technology only where it genuinely solves a problem.** Build for security by design, privacy by design, and above all **trust by design**. Innovation should solve problems, not create them.

Digital transformation without digital trust is incomplete — and nowhere is that truer than in the place we go when we are most vulnerable.

## Sources

1. [Watch the full discussion — the future of digital health (YouTube)](https://www.youtube.com/watch?v=J7UXR-9Famc)
2. [ZettaHealth — prevention, answered (free)](https://zettahealth.axz.si)
3. [ZettaHealth preventive care — try it](https://demo.axz.si/preventive)

Cite: Padam Sundar Kafle. “The hospital is moving home.” DigiNepal Magazine, no. 2, November 2026. https://diginpl.com/magazine/2026-11-secure-by-design/the-hospital-is-moving-home

---

Cite: “: Secure by Design.” DigiNepal Magazine, no. 2, November 2026. https://diginpl.com/magazine/2026-11-secure-by-design
