# Ubient

Ubient Private Cloud Infrastructure(UPCI™)

- Site: https://ubient.dscloud.biz/

## What If Your Terminal Lived in a Chat Window?

- Link: https://ubient.dscloud.biz/blog/software/what-if-your-terminal-lived-in-a-chat-window/
- Published: 2026-10-17T12:55:53+09:00
- Author: Ubient

# Remote Linux Terminal

_Meet rtmn, a Telegram-to-Terminal gateway for Linux, and the reason its most interesting
feature is how plainly it tells you what it is._

It is late. The small Linux machine in the corner of the room, the one with no monitor
and the one you stopped thinking about months ago, has stopped doing its job. A 
service has fallen over, or a disk has filled, or something is printing logs faster
than anyone could read them.

You know the fix. It is probably one line.

But you are not at your desk. You are on a train, or in bed, or standing in a café
with nothing but a phone in your hand.

_**The fix was never the hard part. Reaching a place where you can type it was.**_

## The Distance Between You and One Line

A terminal is a place you have to go to. Usually that means a PC, a console, a keyboard,
and a few minutes of settling in. For a company with an operations team, that is
a rounding error. For one person with a spare PC quietly serving files, or a small
home lab humming in a closet, it is most of the cost of ownership, and it tends 
to arrive at the worst possible moment.

Meanwhile, one kind of app is already open on the device in your pocket: a chat 
app.

That is where rtmn begins. Its documentation describes a gateway built to ease the
inconvenience of always needing a PC or console to reach a terminal [Source 1]. 
The idea is almost embarrassingly simple. You send a message to a Telegram bot. 
The message becomes a command on your Linux server. Whatever the command prints 
comes back as another message.

    ```ubient-docs-code
    Telegram chat
      → Telegram Bot API
      → rtmn (systemd service)
      → the shell of a Linux account you chose
      → output
      → Telegram chat
    ```

That is the entire trick. There is no web console to host and no dashboard to patch.
The text you send goes to the shell itself. Type `ls -la` and a directory listing
comes back. Type `tail -f /var/log/syslog` and the log scrolls by in your chat, 
just as the documentation’s own examples suggest [Source 1].

## A Keyboard Made of Slash Commands

A chat window has no Ctrl-C, and that matters more than it sounds. A terminal you
cannot interrupt is a trap.

So rtmn adds a short list of slash commands that stand in for the keys and decisions
a chat window cannot express [Source 1]. `/sigint` sends Ctrl-C to the shell, which
makes it the panic button for output that will not stop. `/restart` replaces a wedged
shell without taking the gateway down with it. `/status` tells you the time, the
uptime, the process ID, and who is on the allowlist.

The quiet one is `/lock`. It blocks shell input while control commands still get
through, like putting the keyboard in a drawer. It is useful when the phone is about
to be set down on a café table. `/unlock` takes the keyboard back out.

Then there are `/reboot` and `/shutdown`. They run with the service account’s own
system permissions, so whether they work depends on the host’s sudoers or polkit
policy [Source 1]. rtmn does not hand out power. It borrows whatever the Linux account
already has. That detail is easy to skim past, and it comes back later.

## Two Conversations and One File

Setup starts with two chats inside Telegram. One is with `@BotFather`, where `/newbot`
produces a bot token. The other is with `@userinfobot`, which tells you your chat
ID [Source 1]. After that, the rest is a single file.

rtmn is a static Go binary with no external dependencies. It registers itself with
systemd, starts at boot, and is restarted by systemd within five seconds if it crashes[
Source 1]. You run the interactive installer as the Linux account that should execute
your commands. It asks for the bot token with terminal echo switched off, checks
the token with Telegram before committing to anything, and uses `sudo` only for 
the steps that truly need root.

Then your phone buzzes. A startup notification arrives with the hostname, process
ID, start time, shell path, and allowlist. If it shows up, the gateway is alive [
Source 1].

The requirements are modest, and they are honest about their edges. You need Linux
with systemd, root during installation, and outbound HTTPS to Telegram. The stock
binary is for x86_64, and ARM needs a custom build. Because rtmn polls Telegram 
instead of waiting for connections, the only network requirement listed on its main
documentation page is outbound HTTPS [Source 1]. If your closet machine is an ARM
board, this is not the binary for you yet.

## A Tool That Expects the Bad Night

Read rtmn’s self-defense table and one thing stands out. Nearly every row begins
with an assumption that something will go wrong [Source 1].

**The wrong chat.** On startup, rtmn greets every chat on the allowlist. If you 
mistyped an ID, or included a chat that should not be there, that chat receives 
the greeting too. The mistake announces itself the first time the service starts.
rtmn also broadcasts when it is shut down by SIGTERM, SIGINT, or a panic, so it 
says hello and goodbye.

**The runaway output.** Run `yes` or `tail -f` carelessly and a shell can produce
output forever. By default, when output passes 256 KB, rtmn sends an automatic interrupt
and tells you. It also paces itself against Telegram’s own limits, with a per-chat
limit on incoming messages, a global limit on outgoing ones, respect for `Retry-
After`, and exponential backoff, so a noisy command does not get the bot banned.

**The crash loop.** A configuration error exits with code 78, and the systemd unit
is told not to restart on that code. A service that cannot start tells you once 
instead of hammering away indefinitely.

**The leaked token.** Logs and audit records show only the first eight characters
of the token. If a token does leak, `rotate-token` validates the new one with Telegram,
rewrites the environment file atomically, and restarts the service. If the restart
fails, it rolls back to the previous token.

**The record.** Commands, lifecycle events, rejected messages, and output floods
all go into a JSONL audit log. Every rejected message is recorded with its reason:`
not_allowed`, `rate_limited`, `locked`, or `interactive_blocked`. By default the
log rotates at 10 MB and keeps up to five backups.

None of this is glamorous. These are the features you write after imagining the 
bad night in advance.

## The Part That Should Not Be Softened

A tool like this invites one comfortable misunderstanding, so it is worth saying
plainly. **An allowed Telegram chat is, in effect, a login.** The Security Guide
tells operators to treat it as shell access to the configured Linux account [Source
2]. If an allowed chat ID is compromised or allowlisted by mistake, commands run
with that account’s permissions [Source 3].

The same honesty runs through a smaller feature. Chat is message-based, and full-
screen programs expect live keystrokes and draw with escape codes that rtmn filters
out. Run `vim` or `top` through it and you would get a frozen screen. So rtmn blocks
a default list of such programs, including `nano`, `vim`, `less`, `man`, `top`, `
htop`, and `tmux`, before they run. It even looks past wrappers like `sudo`.

The documentation then calls this a convenience guardrail and not a security boundary.
It says plainly that a trick as simple as assigning the program name to a variable
is intentionally not caught [Source 1]. The real boundaries are the chat allowlist,
the Linux account’s permissions, the sudoers policy, filesystem permissions, and
network access controls [Source 2]. This is the “borrowed power” from earlier. What
rtmn can do is decided almost entirely by what you let the account do.

A few habits follow from that:

 * **Keep the allowlist short.** The installer itself pushes back at six or more
   entries unless you force it [Source 1].
 * **Never run it as root.** The Security Guide lists `User=root` as not recommended[
   Source 2].
 * **Give every server its own bot token.** Two servers polling one token race each
   other, and you cannot predict which one answers. A shared token also widens the
   damage if it leaks [Source 2].
 * **Keep the environment file root-owned with mode `0600`,** and review the audit
   log regularly [Source 2].

There is also something the architecture diagram makes plain, even though the documentation
does not dwell on it. Every command you send and every line of output you receive
crosses Telegram’s Bot API. The shell stays on your machine, but the channel does
not belong to you. A fair rule of thumb is that if you would not say it aloud in
a corridor, you should not `cat` it into the chat. It is the same instinct as the
argument in [our earlier post on personal data](https://ubient.dscloud.biz/upci/your-private-local-network-with-ubient/),
that the best security is the kind you practice yourself.

## One Server, Several Doors

Some servers need more than one gateway, for example separate ones for operations,
applications, and administration. The documentation’s answer is separate instances,
each with its own Linux account, bot token, environment file, audit log path, and
systemd service name [Source 4]. Its example instances are named `ops`, `app`, and`
admin`.

The logic is the same as before. Each door opens only onto what its own account 
is allowed to do, and a leaked key opens only one of them.

## What It Is Not For

rtmn is not a text editor in your pocket. If you need a long session of careful 
editing, a real terminal at a real keyboard still wins. It is not for systems without
systemd, and it is not for ARM boards without a custom build. It is also not for
any environment where you cannot vouch for every chat on the allowlist. The documentation
itself recommends using it only where the environment is guaranteed safe [Source
1].

What it is for is smaller. It is the quick look, the restart, the interrupt, and
the answer to “is it still running?”, delivered by a tool that has thought about
being wrong.

## Small Tools for a Private Network

Back to the late-night scene, then. The phone is in your hand. You send one line,
watch the answer arrive, and put the phone away.

_**A terminal in a chat window is exactly as safe as the habits around it.**_ That
is not a flaw to hide. It is the first thing worth knowing, and rtmn says so on 
its very first page.

## Primary Sources

 * **[Source 1]** Ubient Documentation, “Remote terminal(rtmn)” (documentation for
   version 1.1.2)
    - [https://ubient.dscloud.biz/docs/ubient-software/rtmn/](https://ubient.dscloud.biz/docs/ubient-software/rtmn/)
 * **[Source 2]** Ubient Documentation, “Remote terminal(rtmn): Security Guide”
    - [https://ubient.dscloud.biz/docs/ubient-software/rtmn/security-guide/](https://ubient.dscloud.biz/docs/ubient-software/rtmn/security-guide/)
 * **[Source 3]** Ubient Documentation, “Remote terminal(rtmn): Overview”
    - [https://ubient.dscloud.biz/docs/ubient-software/rtmn/overview/](https://ubient.dscloud.biz/docs/ubient-software/rtmn/overview/)
 * **[Source 4]** Ubient Documentation, “Remote terminal(rtmn): Account-Isolated
   Installation”
    - [https://ubient.dscloud.biz/docs/ubient-software/rtmn/account-isolated-installation/](https://ubient.dscloud.biz/docs/ubient-software/rtmn/account-isolated-installation/)

## What If Your Next Device Is One You Already Own?

- Link: https://ubient.dscloud.biz/blog/software/what-if-your-next-device-is-one-you-already-own/
- Published: 2026-10-11T07:24:51+09:00
- Author: Ubient

# Has software support for your legacy device ended?

Many functional electronic devices are discarded prematurely when software support
ends, creating a false impression of hardware failure. This software obsolescence
drives global electronic waste and consumes environmental resources by prompting
unnecessary replacements long before physical components actually stop working.

Extending hardware lifespans through device repurposing, lightweight software, and
initiatives like INISS can reduce technological waste. Combining extended software
support, efficient system design, and accessible open-source operating systems allows
existing computing resources to remain useful for significantly longer periods.

## The Illusion of Hardware Failure

Every year, many physically intact smartphones, tablets, and laptops are left unused
or discarded despite retaining much of their original functionality. Their screens
may remain undamaged, their processors may still perform computational tasks, and
their batteries may continue to hold a usable charge. Yet, these devices can become
increasingly difficult to use as software requirements evolve and support for older
platforms comes to an end.

Consumers may mistake sluggish animations, freezing browsers, and application incompatibilities
for signs that their hardware has reached the end of its life. Although physical
wear and hardware failures are genuine causes of device retirement, they are not
the only reasons a computer becomes unusable. In many cases, the problem lies in
the relationship between the hardware and the software it is expected to run.

Software obsolescence describes a situation in which changes in software requirements,
discontinued maintenance, or compatibility limitations reduce the practical usefulness
of otherwise functional hardware. Operating system updates, increasingly demanding
applications, and the discontinuation of platform support can all contribute to 
this problem.

A processor does not necessarily lose its ability to perform useful work simply 
because its manufacturer or software ecosystem no longer supports it. Older hardware
may still be capable of handling everyday computing tasks, even when it can no longer
accommodate every modern application or operating system. Recognizing this distinction
allows us to reconsider how we evaluate the useful life of technology.

The objective is not to deny genuine hardware limitations, but to identify opportunities
to extend the usefulness of machines that remain capable of performing meaningful
work.

## The Growing Crisis of Electronic Waste

The premature disposal of electronic devices contributes to the growing global problem
of electronic waste, commonly known as e-waste. Large quantities of discarded electronics
contain components that may still be functional, including circuit boards, displays,
processors, and storage devices. When these products are discarded solely because
their software has become unsupported or incompatible with modern applications, 
potentially useful hardware resources are lost before their physical capabilities
have been fully exhausted.

The environmental impact extends beyond the waste itself. Manufacturing replacement
devices requires raw materials, energy, water, and complex industrial processes.
Extracting and processing materials such as copper, aluminum, lithium, and cobalt
can create substantial environmental burdens. The production of a new electronic
device also involves transportation, component manufacturing, and assembly, all 
of which contribute to its overall environmental footprint.

Extending the useful life of existing electronics can reduce the need for premature
replacement and help preserve the resources already invested in manufacturing them.
The potential benefits depend on the condition of the device, its energy consumption,
its intended use, and the environmental costs associated with maintaining it.

Recycling remains an important part of responsible electronic waste management, 
but it does not eliminate every environmental cost. Recovery processes cannot always
reclaim all the materials contained in a device, and some products are difficult
to dismantle because of their construction or the use of adhesives. Recycling also
cannot recover all the energy and resources consumed during the original manufacturing
process.

For this reason, extending the useful life of a functional device deserves consideration
alongside repair and recycling. Before treating an electronic product as waste, 
it is worth examining whether alternative software, a different operating environment,
or a new purpose could allow it to remain useful.

## When the Updates Stop: The End of Software Support

When a manufacturer announces the end of software support for a device, the hardware
does not necessarily stop functioning. The display may continue to work, the battery
may still charge, and the processor may remain capable of performing everyday computing
tasks. What changes is the software environment in which the device operates.

Without continued operating system maintenance, security vulnerabilities may remain
unpatched. Over time, this can increase exposure to security risks, particularly
when a device continues to access the internet or handle sensitive information. 
The degree of risk depends on the vulnerability, the device’s configuration, the
applications in use, and the security measures available.

Compatibility can also deteriorate. Application developers may discontinue support
for older operating system versions, web browsers may no longer receive necessary
updates, and services may introduce requirements that an unsupported device cannot
satisfy. As a result, some applications may stop working even though the underlying
hardware remains operational.

The causes of these limitations vary. They may involve hardware architecture, security
requirements, maintenance resources, software dependencies, or product-support policies.
In other cases, a manufacturer’s commercial priorities may influence how long a 
product receives updates.

Regardless of the underlying reason, the practical consequences can be similar: 
a device that once met its owner’s needs becomes progressively less useful within
the software ecosystem on which it depends.

This creates an important distinction between physical failure and the loss of software
compatibility. The end of official support does not automatically mean that a device
is unsafe for every purpose or incapable of performing useful work. However, continued
use requires an appropriate assessment of security, compatibility, and functionality.

Addressing software obsolescence therefore requires more than keeping hardware physically
intact. It also requires ways to maintain, replace, or adapt the software environments
that make the hardware useful.

## Rethinking Hardware Longevity and Traditional Reuse

Prioritizing hardware longevity can reduce unnecessary replacement costs for consumers
while helping to limit the environmental impact associated with manufacturing new
electronics. Extending a device’s useful life from a few years to a substantially
longer period can preserve the value of the materials and energy invested in its
production.

Practical hardware reuse already takes many forms. Older laptops and desktop computers
can serve as local file servers, backup systems, media centers, or dedicated machines
for specific tasks. Depending on their hardware capabilities and software requirements,
some devices can continue to perform these roles long after their original operating
system has stopped receiving support.

Lightweight Linux distributions may provide another way to extend the usefulness
of aging computers. By choosing a system that places fewer demands on available 
processing power and memory, users may be able to restore acceptable performance
on hardware that struggles with more resource-intensive environments.

However, the practical accessibility of these solutions remains an important consideration.
Installing an alternative operating system, identifying compatible drivers, configuring
network services, and maintaining security can require technical knowledge. Compatibility
also varies between devices, and changing operating systems does not guarantee that
every application or peripheral will continue to work.

These limitations create an opportunity for solutions that make existing open-source
technologies more accessible to ordinary users. Extending hardware longevity is 
not just a matter of proving that an older computer can still perform a technical
task. It is also a matter of making that capability practical, maintainable, and
useful in everyday environments.

The challenge is to reduce the gap between the hardware that people already own 
and the software capabilities they need.

## A Second Life Through INISS and Next-Generation Operating Systems

Extending the useful life of aging hardware requires new approaches to the relationship
between operating systems, software support, and existing computing resources. One
project addressing this challenge is INISS (Interconnected Network Infrastructure
Standardization System), an operating system and network infrastructure standardization
system currently under development by Ubient.

According to Ubient’s official documentation, INISS originated from a specific problem:
computer systems that remain functional are often left unused or discarded simply
because their software has reached the end of its support period. The project aims
to provide these legacy computer systems with a new life cycle rather than treating
the end of their original software support as the end of their usefulness.

INISS is built upon Debian Linux, an established open-source Linux distribution.
This provides the project’s development with an existing open-source foundation,
while Ubient’s broader approach focuses on making such technologies more accessible
and practical for a wider range of users.

The project’s name emphasizes interconnected network infrastructure and standardization.
This direction is relevant to the wider challenge of extending the useful life of
computing devices: existing hardware should be evaluated not only in terms of its
ability to run the latest standalone applications, but also in terms of the useful
roles it may serve within a broader computing environment.

Ubient’s wider UPCI™ concept also emphasizes intelligence integrated into infrastructure,
standardized private networks, and lightweight architecture. These principles establish
a broader context for understanding the company’s interest in interconnected systems
and efficient use of computing resources.

However, INISS is still under development. Its specific hardware compatibility, 
networking behavior, supported workloads, resource-management mechanisms, and security
characteristics should be evaluated against the project’s technical documentation
and actual releases as they become available. The precise ways in which devices 
will communicate or cooperate should not be assumed solely from the system’s name
or overall objectives.

The significance of INISS at this stage lies in its stated development purpose: 
exploring a new life cycle for legacy computer systems through an operating system
built upon the open-source Linux ecosystem. It represents an approach to the problem
of software obsolescence that places the continued usefulness of existing hardware
at the center of the discussion.

## Building a Sustainable Future for Personal Tech

Achieving a more sustainable future for personal technology requires changes in 
engineering practices, product-support policies, regulation, and consumer expectations.

Right-to-repair legislation and other durability initiatives can help consumers 
maintain their devices and encourage manufacturers to provide longer periods of 
software support. The specific measures required will vary by jurisdiction, but 
a central objective is to reduce situations in which repairable and functional devices
become unusable because essential software maintenance or compatibility has been
discontinued.

Software developers can contribute by designing efficient applications, maintaining
compatibility where practical, and considering the capabilities of existing hardware.
Modular software architectures and lightweight computing environments may also provide
additional options for extending the usefulness of older systems.

At the same time, users and organizations can reconsider whether replacing a device
is always necessary when its original software environment becomes unsuitable. Depending
on the device’s condition, security requirements, and intended purpose, repair, 
alternative software, or a change of role may provide a practical path forward.

Ubient’s development of INISS addresses this broader challenge by exploring how 
a new operating system can give legacy computer systems another useful life cycle.
Its eventual contribution will depend on the capabilities delivered through development
and how effectively those capabilities address the needs of real users.

Tackling software obsolescence does not require technological progress to stop. 
Instead, it requires progress to account for the useful life of the hardware that
already exists.

By combining longer software support, efficient system design, responsible reuse,
and new approaches to operating systems, the technology ecosystem can reduce unnecessary
replacement and make better use of existing computing resources. The objective is
to ensure that hardware remains useful for as long as it can safely and effectively
serve a purpose, rather than allowing the end of one software environment to determine
the end of the entire device’s useful life.

## Your Private Local Network, with Ubient

- Link: https://ubient.dscloud.biz/blog/upci/your-private-local-network-with-ubient/
- Published: 2026-10-03T06:02:06+09:00
- Author: Ubient

# A poem

## Blooms ━

> _**Universe blooms in every newborn twilight.
> Petals rain in veils across the 
> ether.Cosmos laces outward, unveiling dreams.Its nascent forces resonate across
> space, through realms unseen, calling to us, revealing everything.

Have you seen this passage before? Could it be the very first thing you saw on the
opening screen? Perhaps most people found its unexpected content puzzling, or simply
moved on to the next screen. This passage is an acrostic poem spelling out **_‘UBIENT
PRIVATE CLOUD INFRASTRUCTURE’_** not ‘UPCI’, while also expressing Ubient’s ideals.
There is nothing difficult about it. It is simply meant to give your mind a moment
to breathe. Now, having taken that moment, shall we give some thought to something
important?

# How do you protect your sensitive information?

## Even in the Age of AI, Personal Privacy Still Matters

Even in the age of AI, personal privacy remains extremely important. One might even
say it has become more important. Cloud frontier AI models sometimes offer people
ease and convenience, but they also often collect a great deal of information, and
may use users’ data for service improvement and model training. Some AI companies
even directly ask users to be careful, noting that some conversations may be seen
by reviewers and telling them not to enter confidential information. [Source 5]

## The Gap Between the Convenience of AI and Awareness of Personal Data Security

As AI advances, we have entered an era in which people have begun to rely on AI 
for a wide range of their own tasks, including tasks that used to take a great deal
of time. But while enjoying this convenience and the benefits of advanced technology,
how far has people’s awareness of protecting their privacy and personal information
actually kept pace?

## How Much Are Real Personal Data Breaches Increasing?

Rather than data measuring users’ security awareness itself, the sections below 
review the backdrop to that question: the current state of personal data breaches
and infringements, using official statistics and overseas reports.

### Case 1

**_Real data shows that the risk to personal information is not merely hypothetical._**
According to “2025 Personal Data Breach Report Trends and Investigation/Disposition
Cases” (Original text: 「2025년 개인정보 유출 신고 동향 및 조사·처분 사례」), released
on May 15, 2026 by the Personal Information Protection Commission (PIPC) and the
Korea Internet & Security Agency (KISA), **_personal data breach reports in 2025
totaled 447, up 45.6% from 307 in 2024._** Among the causes of breaches, **_hacking
accounted for the largest share at 62% (276 cases)_**, a sharp rise from 171 cases
the year before. The PIPC cited malware such as ransomware and web shells, exploitation
of web vulnerabilities such as SQL injection, and abnormal access to administrator
pages as the main hacking patterns.

**_Source: Personal Information Protection Commission and Korea Internet & Security
Agency, “2025 Personal Data Breach Report Trends and Investigation/Disposition Cases,”
May 15, 2026. [Source 1]_**

### Case 2

What is more noteworthy is that this upward trend did not end with 2025. According
to a press release the PIPC published on _**October 2, 2026**, **breach reports 
received in the first half of 2026 alone totaled 432**_, already close to the full-
year 2025 total of 447. The PIPC explained that as AI technology spreads, attacks
targeting personal information are becoming more sophisticated and intelligent, 
and personal data breaches and infringements are increasing rapidly. It also stated
that incidents continue to occur at businesses holding large volumes of personal
data, such as telecommunications, platform, and retail companies, affecting millions
to tens of millions of data subjects.

**_Source: Personal Information Protection Commission, press release “Investigating
Personal Data Breaches and Infringements Faster, Fairer, and More Transparently”(
on the “Plan for Rapid Investigation of Personal Data Breach and Infringement Cases
and Strengthening Investigative Capacity”), October 2, 2026. [Source 2]_**

### Case 3

This problem is not limited to Korea’s domestic breach-report statistics. Verizon’s“
2026 Data Breach Investigations Report,” published in 2026, covers events from late
2024 to late 2025 and analyzed **_more than 31,000 real-world security incidents,
of which more than 22,000 were confirmed data breaches, involving organizations 
in 145 countries._** Verizon stated that this is the largest number of breaches 
it has examined in a single report, but because this reflects the size of the analyzed
sample, it is difficult to read it as a measure of the global volume of breaches.
Among breaches with an identified entry point, **_exploitation of software vulnerabilities
accounted for 31%_**, overtaking credential abuse (13%) as the most common initial
access vector, and **_ransomware was involved in 48% of all breaches._** In addition,
the median threat actor **_researched or used AI assistance in 15 different documented
attack techniques_**, and most AI-assisted development of malware and tooling was
associated with already well-known attack techniques.

**_Source: Verizon, “2026 Data Breach Investigations Report” and Executive Summary,
2026. [Source 3]_**

### Case 4

The European Union Agency for Cybersecurity (ENISA)’s “ENISA Threat Landscape 2026”
analyzed **_8,257 incidents_** recorded between January and December 2025 affecting
EU Member States and EU-based organizations. **_DDoS attacks, which are low in impact,
made up 51.3% of recorded incidents_**, but ENISA assessed that the threat causing
the greatest damage in the short term is financially motivated activity, led by 
ransomware. Financially motivated activity accounted for about **_29%_** of all 
recorded incidents, and among the recorded claims within it, **_ransomware deployments
made up 47.3% and data breaches 36%._** However, the data breach figure is based
on sale claims posted on cybercriminal forums, and ENISA stated that it could not
verify their authenticity. In addition, in 2025 **_more than 48,000 new vulnerabilities(
CVEs)_** were published, a 22% increase over the previous year. ENISA observed that
attackers mainly use AI as a tool to augment their existing capabilities, while 
also analyzing that the adoption of AI systems in enterprise environments is creating
a new attack surface, and that attacks targeting digital supply chains and third-
party dependencies continue.

**_Source: European Union Agency for Cybersecurity (ENISA), “ENISA Threat Landscape
2026,” September 22, 2026. [Source 4]_**

### Case 5

These sources differ in scope (Korea, worldwide, the EU), period, and methodology,
so they cannot be added together into a single figure or compared directly. Even
so, both Korea’s official report statistics and the overseas reports show that **
_breaches targeting digital assets, including personal information, are a real and
significant threat._** Their diagnoses of AI differ in emphasis. The PIPC pointed
to the growing sophistication of attacks as AI spreads; Verizon noted that AI is
increasing the speed and scale of already known attack techniques; and ENISA noted
that AI serves as an aid for attackers while the AI systems being adopted can themselves
become a new attack surface. In particular, in the PIPC’s domestic statistics, personal
data breach reports were 167 in 2022, 318 in 2023, 307 in 2024, and 447 in 2025.
They dipped slightly in 2024 and then rose sharply in 2025, and 432 were received
in the first half of 2026 alone. This makes it hard to view the protection of personal
data as solely the responsibility of service providers.

According to recently published data, personal data breach reports, as shown above,
have on the whole risen sharply over the past several years. It is nothing short
of a serious problem. If such news keeps repeating, more people may come to feel
fatigued about security. The best form of security can be said to be protecting 
oneself.

## A Local Network You Can Control

Ubient researches easy and systematic management tools for the privacy and security
issues that have become more important in modern times, together with personal network
users as well as various local network users. Infrastructure, as it is generally
called, has mostly been introduced and maintained by companies. Or, only those with
extensive IT knowledge or strong interest manage to set up even a small local infrastructure.

## A Personal Privacy Infrastructure Anyone Can Build

However, ordinary users inevitably have relatively little such knowledge and interest.
Ubient aims to find ways for such users, too, to easily build a personal privacy
network infrastructure, as long as they take an interest and make up their minds.

## A Local Network Brand for Individual Users, Not a Company

Ubient is not a company. Ubient is a local network infrastructure brand for individual
users. Unlike projects in which many people gather to form a team and carry out 
research and development, progress will inevitably be slower. Even so, Ubient plans
to carry out many ideas and projects in order to work together with people who share
various commonalities and have been left in the blind spots of their time and society.

## Primary Sources

 * **[Source 1]** Personal Information Protection Commission and Korea Internet &
   Security Agency, “2025 Personal Data Breach Report Trends and Investigation/Disposition
   Cases” (원문: 「2025년 개인정보 유출 신고 동향 및 조사·처분 사례」), May 15, 
   2026 (press release: 「개인정보위, 2025년 개인정보 유출 신고 및 조사·처분 사례
   분석결과 발표」)
    - [https://pipc.go.kr/np/cop/bbs/selectBoardArticle.do?bbsId=BS074&mCode=C020010000&nttId=12078](https://pipc.go.kr/np/cop/bbs/selectBoardArticle.do?bbsId=BS074&mCode=C020010000&nttId=12078)
 * **[Source 2]** Personal Information Protection Commission, press release “Investigating
   Personal Data Breaches and Infringements Faster, Fairer, and More Transparently”(
   원문: 「개인정보 유출·침해사고, 더 빠르게 더 공정하게 더 투명하게 조사」), October
   2, 2026
    - [https://pipc.go.kr/np/cop/bbs/selectBoardArticle.do?bbsId=BS074&mCode=D010030000&nttId=12555](https://pipc.go.kr/np/cop/bbs/selectBoardArticle.do?bbsId=BS074&mCode=D010030000&nttId=12555)
 * **[Source 3]** Verizon, “2026 Data Breach Investigations Report” and Executive
   Summary, 2026
    - [https://www.verizon.com/business/resources/reports/2026-dbir-data-breach-investigations-report.pdf](https://www.verizon.com/business/resources/reports/2026-dbir-data-breach-investigations-report.pdf)
    - [https://www.verizon.com/business/resources/executivebriefs/2026-dbir-executive-summary.pdf](https://www.verizon.com/business/resources/executivebriefs/2026-dbir-executive-summary.pdf)
 * **[Source 4]** ENISA, “ENISA Threat Landscape 2026,” September 22, 2026 (analysis
   period: January 1 to December 31, 2025)
    - [https://www.enisa.europa.eu/sites/default/files/2026-09/ENISA%20Threat%20Landscape%202026_Final.pdf](https://www.enisa.europa.eu/sites/default/files/2026-09/ENISA%20Threat%20Landscape%202026_Final.pdf)
    - [https://www.enisa.europa.eu/news/exploring-the-evolution-of-the-cyber-threat-landscape-how-dependencies-weaken-our-digital-resilience](https://www.enisa.europa.eu/news/exploring-the-evolution-of-the-cyber-threat-landscape-how-dependencies-weaken-our-digital-resilience)
 * **[Source 5]** Google, Gemini Apps Privacy Hub
    - [https://support.google.com/gemini/answer/13594961](https://support.google.com/gemini/answer/13594961)