{"id":33378,"date":"2026-08-25T13:17:54","date_gmt":"2026-08-25T10:17:54","guid":{"rendered":"https:\/\/quriiri.fi\/?p=33378"},"modified":"2026-08-25T13:42:53","modified_gmt":"2026-08-25T10:42:53","slug":"turvallinen-sms-rcs-viestinta","status":"publish","type":"post","link":"https:\/\/quriiri.fi\/en\/turvallinen-sms-rcs-viestinta\/","title":{"rendered":"Secure SMS and RCS messaging: CTO Thomas Wahlberg's tips"},"content":{"rendered":"
Text messages and RCS messages are effective tools for business communication. However, their security doesn\u2019t happen on its own. Thomas Wahlberg, CTO of Quriiri, points out that even small oversights can open the door to misuse. With the right choices, however, it\u2019s possible to make communication extremely secure.<\/h5>\n\n\n\n
We asked Thomas what things companies should consider when messages are sent via an API or a browser-based user interface.<\/p>\n\n\n\n
<\/p>\n\n\n\n
1. Web forms: the most common attack vector<\/h2>\n\n\n\n
Abuse often starts in a simple place: a web form where a user enters a phone number.<\/p>\n\n\n\n
A typical attack proceeds like this: a hacker finds a form that sends an SMS to the entered number, for example, for phone number verification. Thousands of foreign numbers are automatically entered into the form, and the messaging costs start to rise.<\/p>\n\n\n\n
Thomaksen's advice for securing forms:<\/p>\n\n\n\n
\n
Restrict the acceptable countries only to those that are actually needed.<\/li>\n\n\n\n
Add validations and usage restrictions to the forms.<\/li>\n\n\n\n
Consider CAPTCHA protection.<\/li>\n\n\n\n
Take advantage of Quriiri's land and communication rate limiters.<\/li>\n<\/ul>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n<\/figure>\n\n\n\n
<\/p>\n\n\n\n
2. Strong passwords and two-factor authentication<\/h2>\n\n\n\n
If a criminal manages to send messages in your company's name, the consequences will be visible in both costs and reputation. A strong password and two-factor authentication remain the most effective protection.<\/p>\n\n\n\n
\u201dThe recommendation is a password of at least 16 characters. Two-factor authentication, preferably using an authenticator app, is the best way to protect against password leaks and cracking.<\/em>,\u201d, Thomas says.<\/p>\n\n\n\n
In addition to passwords, you should ensure that old user accounts are deleted and access rights are kept up to date.<\/p>\n\n\n\n
<\/p>\n\n\n\n
3. API keys: keep them strictly under control<\/h2>\n\n\n\n
API keys determine who can send messages on behalf of your organization. Protecting them is at least as important as protecting user credentials.<\/p>\n\n\n\n
Thomak's practical instructions:<\/p>\n\n\n\n
\n
Do not share API keys in chat applications, email, or during screen sharing.<\/li>\n\n\n\n
Name the keys descriptively so they are easy to identify and revoke if necessary.<\/li>\n\n\n\n
Remove unused keys regularly.<\/li>\n\n\n\n
Restrict key visibility to those with a genuine need.<\/li>\n<\/ul>\n\n\n\n
<\/p>\n\n\n\n
\u201dA leaking API key is difficult to detect. It can be exploited systematically, for example, for mass mailings conducted at night, where the damage can quickly grow to be significant.,<\/em>\u201dThomas says.<\/p>\n\n\n\n
<\/p>\n\n\n\n
4. IP address restrictions: allow calls only from known sources<\/h2>\n\n\n\n
One of the most effective ways to secure an API integration is to restrict the IP addresses from which API calls are accepted. In Quriiri, you can specify the allowed IP addresses directly in the settings.<\/p>\n\n\n\n
In practice, this means that even if the API key ends up in the wrong hands, the request will be rejected if it comes from an unknown address.<\/p>\n\n\n\n
If the field is left empty, calls are allowed from all IP addresses. Limiting should be done whenever possible.<\/p>\n\n\n\n
Quriiri supports both IPv4 and IPv6 addresses, as well as CIDR notation for specifying subnets. Multiple addresses can be separated by commas or line breaks.<\/p>\n\n\n\n
<\/p>\n\n\n\n
5. Boundaries and Limiters: Prevent Damage Before It Happens<\/h2>\n\n\n\n
Quriiri offers several tools that can be used to prevent misconduct before it occurs.<\/p>\n\n\n\n
Ground-level borders<\/strong><\/p>\n\n\n\n
If your company sends messages only within Finland, it\u2019s a good idea to block numbers from other countries entirely. In Quriiri, international numbers are blocked by default. The most common cases of abuse involve mass text messages sent to expensive international numbers, where the cost of a single message can be tens of cents.<\/p>\n\n\n\n
Message budget limits<\/strong><\/p>\n\n\n\n
Daily, weekly, and monthly limits are one of the most effective ways to limit damage in a situation where messages are sent without authorization.<\/p>\n\n\n\n
\u201dThe greatest damage usually arises from malicious traffic continuing for a long time. By setting the limits to match the normal message volume, potential damage can be minimized. Criminals operate systematically and often time their sabotage for weekends or nighttime. The limits also protect against human errors and programming mistakes.<\/em>,\u201d says Thomas.<\/p>\n\n\n\n
<\/p>\n\n\n\n
6. Sender ID: luvita and protect if necessary<\/h2>\n\n\n\n
The reliability of text messages is based on the recipient's ability to identify the sender. Falsifying sender information has been a common method in scams, which is why the rules of the game have changed.<\/p>\n\n\n\n
Traficom Regulation 28 L\/2025 M entered into force on May 4, 2026. It applies to SMS, MMS, and RCS messages and requires companies to ensure they have the right to use the Finnish phone number or alphanumeric sender ID they use. If sender information cannot be verified, the ID will be changed or message delivery will be blocked entirely.<\/p>\n\n\n\n
Additionally, a company can protect its alphanumeric sender ID by registering it with Traficom. Registration grants exclusive rights to the ID and prevents others from using the same name.<\/p>\n\n\n\n
Authentication and protection are not just about compliance. They directly affect whether the message appears trustworthy to the recipient and whether it actually gets delivered.<\/p>\n\n\n\n
<\/p>\n\n\n\n
7. Be prepared: what to do if something happens?<\/h2>\n\n\n\n
Even if everything has been done correctly, risks cannot be completely eliminated. That is why it is a good idea to think in advance about how to act in a problem situation.<\/p>\n\n\n\n
Practical questions that are worth answering in advance:<\/p>\n\n\n\n
\n
What should be done if an API key leaks?<\/li>\n\n\n\n
Who is cutting off the connection?<\/li>\n\n\n\n
Who is notified of the situation and how?<\/li>\n<\/ul>\n\n\n\n
<\/p>\n\n\n\n
\u201dA quick response is often the factor that separates a minor annoyance from a real crisis<\/em>,\u201d Thomas summarizes.<\/p>\n\n\n\n
<\/p>\n\n\n\n
8. Unicode or GSM: don't let character encoding surprise you<\/h2>\n\n\n\n
If a message contains even a single Unicode character, the entire message is treated as a Unicode message. In this case, fewer characters fit into a single message, and the same content may require multiple messages. This is reflected in the costs.<\/p>\n\n\n\n
A Unicode character can slip into a message unnoticed, for example in copy-paste text from documents or AI tools, a dash, or the wrong form of a space character.<\/p>\n\n\n\n
The Quriirin user interface displays a warning about this when writing a message. When sending via the API, it's a good idea to check this separately.<\/p>\n\n\n\n
<\/p>\n\n\n\n
RCS is a safer channel<\/h2>\n\n\n\n
RCS is not only a visually richer messaging channel. It is also harder to abuse.<\/p>\n\n\n\n
\u201dRCS agents always undergo a strong background check by the operator. Therefore, abusing them is considerably more difficult than regular SMS<\/em>,\u201d, Thomas says.<\/p>\n\n\n\n
When using RCS with SMS fallback, messages reach all users and the security level remains high.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Summary<\/h2>\n\n\n\n
Secure communication is built on small, concrete actions:<\/p>\n\n\n\n
\n
limitations, limiters and validations<\/strong><\/li>\n\n\n\n
strong passwords and two-factor authentication<\/li>\n\n\n\n
Managed use of API keys<\/li>\n\n\n\n
IP address restrictions: allow calls only from known sources<\/li>\n\n\n\n
approved and, if necessary, registered sender IDs<\/li>\n\n\n\n
contingency plan for emergency situations<\/li>\n<\/ul>\n\n\n\n
<\/p>\n\n\n\n
When these things are in order, corporate communication is considerably more difficult to misuse and customer trust is maintained.<\/p>\n\n\n\n
![\"\"](\"https:\/\/quriiri.fi\/wp-content\/uploads\/2026\/08\/SMS-viestinnan-turvallisuus-Thomas.webp\")
<\/figure>\n\n\n\n