Services
Linux servers
VYN IT runs Linux where an application, an appliance or a service requires it: web, database, file, VPN or a vendor stack. We install, harden and patch those systems and connect them to backup and monitoring.
VYN IT runs Linux where an application, an appliance or a service requires it: web, database, file, VPN or a vendor stack. We install, harden and patch those systems and connect them to backup and monitoring.
Linux is not a reason to leave admin keys in a private home directory. Two people can reach the system, updates have a window, and the backup is not on the same disk. If the business software requires Windows, it stays on Windows.
What we do
Running a service
The server does what the application needs, with updates, user accounts and a known admin path.
Hardening
Only the services that must run. SSH with keys, not with a password that sits in a ticket. The host firewall matches the network firewall.
Patches
In a window, with a way back if an update stops the application.
Backup
Data and, where needed, the configuration, on another target. A restore is tried.
Handover
When a vendor delivers an appliance, we write down who patches and who holds root. Otherwise nobody is responsible in a fault.
Technologies and solutions
Current distributions
The one the vendor supports and that still receives updates. Not an expired version because it was installed once.
SSH and accounts
Keys, named users, sudo instead of a shared root for daily work.
Services
Web, database, file or the package the application brings with it.
Backup
Files and dumps on a target outside the machine.
Monitoring
Free space, the service and the backup job. Read Monday to Friday.
What you gain
The service has an owner
Someone knows which application runs on the machine and who may patch it.
No shared root
Two people can get in, and not only through a private key with no copy kept.
Updates are not an ambush
The window is set before the package is applied.
The data is copied
A dump or the files sit elsewhere and have been restored once.
Typical problems
An appliance with no owner
The vendor left it there, nobody patches, and only the installer knows root.
A distribution without updates
The version is old, and the application still requires it. That is named, not ignored.
SSH from the internet with a password
The server is reachable from anywhere with a short password.
A cron that writes nowhere
The target is full or gone, and nobody reads mail to root.
How we work
- 1
Advice
We clarify which application needs the Linux server and who has root today.
- 2
Planning
Distribution, accounts, backup target and the window for updates.
- 3
Implementation
Build or take over, harden, first restore test.
- 4
Optimization
Open services, old keys and full disks are cleaned up.
- 5
Ongoing care
Patches and jobs stay in care on business days.
Frequently asked questions
Do you move everything to Linux?
No. Only what the application or the service requires. Windows business software is not forced onto Linux.
Which distribution?
The one the vendor names and that still receives security updates. A preference is not an argument against that support statement.
Can you take over an existing appliance?
Yes, when access and the update path are clear. Without root and without a contract with the vendor, we cannot honestly look after the device.
Is SSH from the internet acceptable?
Not with a password and not without a restriction. Keys, a limit on sources, or VPN. We set that up instead of leaving it.
Who reads the errors?
A role address, Monday to Friday. Mail to root on the server itself is not an alert path.
Contact and advice
Call us or send an inquiry. We reply on business days and say whether and how we can help.
+43 1 996 96 33