If you want to deploy Linux in an enterprise scenario properly, the only real option is using RHEL. Red Hat has a product called Satellite which allows for centralized managing of RHEL installs. This includes patch management, security policy monitoring and provisioning. You can also use something like Red Hat IdM to do user management like in AD. It is also basically your only choice if you have to comply with something like HIPAA. For AV you can use something like Sophos if you absolutely need it https://support.sophos.com/support/s/article/KB-000038296?language=en_US .
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
@[email protected] this is RHEL's business. Probably take a look at their documentation how they do it. Probably Fedora and OpenSuse are kind of downstream from that so they might know how to do so without getting paid service involved, but if you're looking to do this for your company: Redhat is where to look.
Anti Commercial AI thingy
CC BY-NC-SA 4.0
Yeah that's what I was thinking also. And what about SUSE? Could they have something similar?
Have a look at manage engine software
Well that's exactly the kind of thing I was looking for!
There's Zscaler for Linux. We're using it in our corpo.
You have to run your software mirror no matter what. Even if it's a proxy mirror where you don't actually store most of the packages.
SELinux/AppArmor for more granular access policies.
SSSD connects local auth with AD.
You should look into what your vendor has on offer, e.g. Landscape if you're on Ubuntu.
As others have said config-as-code would probably be part of the equation too.
Zscaler is corporate spyware. As far as I know, it can log all connections, even ones that don't go through the Zscaler nodes. It can also act as MITM proxy.
I'm doubtful about whether it's (or at least many configurations of it) are legal in EU.
I hate zscaler. At my company it's set up so that it proxies all traffic through it and comes with its own CA certificates, which breaks a lot of things - I can't install pip packages for python, I can't clone/work with git repos if they're on https only. We are used to temporarily disable it to do these things because corporate won't change the policies.
Sounds like it's used as a MITM proxy and logs all website URLs you visit. If you live in EU that's probably illegal.
There's a lot of universities using Linux on their pc labs, I guess you can look up how they admin their systems to compare. When I was in college, I had a programming class (R language for actuarial sciences) and the computer had some restrictions, like we couldn't save anything locally so we had to plug a pendrive to save our scripts and we couldn't install any library not installed by default.
Unis tend to be a mess because professors and department heads can just say "I don't want any sysadmin telling me what to do with my machines" and that's that.
If you want to control users, don't give them admin privileges.
Most of things you enumerated solve windows specific problems and therefore have no analogs in other OSes.
That's the thing. They need some admin access. Especially if they're working in IT and need to do certain tasks that require that privilege.
Allow only those tasks in policykit, make a link with pkexec <tool>
?
The simplest solution is to set up the sudoers file to allow only specific commands your users need. I assume you need more than that, but what kinds of use cases does that solution fail to handle?
Takes a bit more than that to really lock down a Linux install. At the very least you'd have to also limit their ability to mount extra storage, mount their /home with noexec, and centrally manage their browser.
That list makes me wanna get a job on a small company of up to 10-20 people, where none of these things are usually needed...
I hear you. But if we want Linux to seriously become the next desktop OS, I think it's important to find something that gives large organisation some kind of way to manage their large IT inventory and users securely.
~~FreeIPA~~
Fleet comander seems to be great for this task. It runs FreeIPA among a few other things to allow for active directory like control.
https://fedoramagazine.org/join-fedora-linux-enterprise-domain/
I'd say most of those are needed; they're just not used.
In no particular order;
- Detecting "installed" software is iffy. Linux can have all kinds of things running on it that aren't "installed" as-such (same as Windows with portable EXEs, Linux has AppImage/etc). Excepting things like that, you can detect installed apps through the package managers (apt/pkg/yum/snap/etc).
- OS updates in Debian-likes and Redhat-likes are controllable out of the box, but I'm not familiar with a way to prevent a user from doing them (other than denying them root access, which might make it hard for them to use the system, depending on what they need to do).
- I've had a lot of good results with OpenVPN.
- lol antivirus. Not saying Linux doesn't get viruses, or that there arent antiviruses for Linux, but the best way to avoid getting them is still to just avoiding stupid shit. Best thing I can offer is that if you have some kind of centralized storage, check that for compromised files frequently, and keep excellent backups. And make sure your firewalls and ACLs don't suck.
but the best way to avoid getting them is still to just avoiding stupid shit.
This is fine and dandy on a personal pc, but in a work environment you are now being actively targeted by malicious actors if your company is a good target.
Constantly.
So once you are in that zone you do need some fast acting reactive tools that keep watch for viruses.
Didn't say it was the only way, just the best way. Most effective attacks are still against humans, not computers.
other than denying them root access, which might make it hard for them to use the system
If the user is even slightly knowledgeable, they can't all protection systems using sudo
. That's a big no-no if you want top-notch security.
Source - I have broken my corporate's Linux-specific protection mechanisms.
If the user is even slightly knowledgeable, they can’t all protection systems using sudo. That’s a big no-no if you want top-notch security. Source - I have broken my corporate’s Linux-specific protection mechanisms.
I'm not 100% sure I'm getting what you were trying to say in that first sentence, but you realize that not all users have sudo privileges, and if your company left you with sudo that was a mistake, correct?
Linux noob here... But aren't there user types? Like admin with install permissions and user type without ? Doesn't that take care of most of your questions?
Not really. I want users with some admin privileges. As someone pointed out, a properly configured sudoers file can allow that with sudo.
Most of this would probably be handled by the regular unix permissions and things like sudo access for commands that are needed. You can specify exactly what commands people can run using sudo. You can also make groups so that you can have people that can run certain commands in those groups. As far as default permissions to run files, that would be handled by your path and execute permissions. Same with umask settings. I worked at a large company and to my delight and a lot of windows users dismay, they forced us to have linux laptops for our particular jobs. I loved it, but a lot of people just weren't happy. I found that I could do everything much easier when I had native tools for working with other unix based machines right there on my desktop.
FreeIPA?
Edit: You can use Fleet comander https://fedoramagazine.org/join-fedora-linux-enterprise-domain/
Antivirus would probably be clamav.
As for policy, selinux would be my first Google.
Software allow lists I’m only going to mention system wide since stopping user space installs or chroots would be your software detection tool that I would be clueless on. System wide I’d look at sudo where you can control exactly what root level commands different users/groups can run.
If you don't want the user to install software, you can mount any user writable partitions noexec. That will not stop them from running scripts though.
policy control
It's not exactly the same, but you could use puppet to enforce configuration
Software Center with software allow lists
You can setup a custom repository with only approved software and then set that as the only one that the system is configured to retrieve packages from. This can also be controlled via puppet.
controlled OS updates
Same as the previous point. Upgrades are installed from the repos.
zscaler
I don't know what that is/does, and their website isn't helping.
software detection tool to detect what's been installed and determine if any unallowed software is present
I'm pretty sure carbon black app control has a linux version.
antivirus
There are a number of different antivirus solutions for linux. A quick search will give you a bunch of lists. I'm not personally familiar with any of the options, but I don't imagine it will be difficult to find one that will work for your use case.
BlueBuild and deploy your customized image to the devices
I can highly recommend this. This is the modern way of creating corporate environments. It's very easy to create, update and maintain, switch, go back.
A lot of points you mention can be achieved with Univention (a debian based central management environment) and a few extra steps. Should be possible, imho.
One thing to take a look at for central account control, sudo rules and a few other things. Is freeipa/rhel idm.
All in all, i guess something like Fedora Silverblue (immutable) with some remote management software?
I was looking for what you said a few years ago out of curiosity before and remember looking into something called Shibboleth. I didn't looked into it in details but it seems to cover identity and policy management. Not sure about the rest of the features you need though.