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 .
this post was submitted on 08 Apr 2024
112 points (100.0% liked)
Linux
1253 readers
75 users here now
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
founded 5 years ago
MODERATORS
@cyborganism@lemmy.ca 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?
Or just like... Use Ansible?
sure but it just does a small part of OP's requirements and you probably want some continuous monitoring to go along with that and a nice dashboard.
To add to your comment, there is already a native linux client for ZScalar which my workplace uses. We also use CrowdStrike for EDR, which is also Linux compatible.
$$$$$$$$$
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.
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.
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.
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 ?
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?
Well for example, I work as a DevOps specialist. I need to install certain tools on my system like Docker, kubernetes, virtual machines, etc. Those kinds of tools often require admin privileges to use in development. I may need to modify some files related to those tools in /etc but I shouldn't have access to all files. For example I would want to prevent users from modifying apt or yum repo sources.
I'm not a supporter of the approach of blocking sudo access from capable people (non tech yes), because they can still download and execute binaries as their user. Or go to rescue mode to make modifications. I had to do that myself because of a micro managing IT team. Allowed? No. Allows me to focus on my work and let me be efficient? Yes. Usually this approach also requires a backdoor tool on your device that they install, which is just ridiculous.
Just communicate setup requirements (drive encryption, firewall, AV,...) And have some tool to check the security requirements and rating and this way you can apply proper security policies in the company and respect the user's privacy
No way. You completely trust them or you do not trust them at all. In any OS. That's how security works.
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.
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.
Use NixOS if you want to use use strictly pre-installed software.
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?
I meant that if a company wants to maintain the highest levels of security, the user should never be given access to sudo. If a certain workflow requires sudo, the workflow needs to be changed, or it needs to be done in a sanitized environment, or the user needs to be highly trusted.
load more comments
(7 replies)
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.
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.
Nod32 offers a commercial antivirus for that scenario as well. The consumer variant has been discontinued.
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.
Neat! I'll check it out.
What is 'unallowed software'? A shell script the user wrote? Something they downloaded and compiled?
Limiting that seems fundamentally at odds with FOSS.
Could be things to execute. They may run a shell script (source it if they don't have exec permission), but they won't have all the previleged commands (definitely no dd)
Granted most open source free software don't have licenses that limit usage like many commercial software. You might want to keep track of the commercial software. Or look for versions that have important vulnerabilities.
First, you can run proprietary software on free software. So, running free software does not preclude license monitoring. It is also possible that certain licenses are not allowed even if they are approved by the FSF or OSI.
The goal more broadly is enforcing corporate policies around risk or whatever else needs to be enforced.
It may be that you HAVE to use certain kinds of software ( VPN was mentioned ). Perhaps you are NOT allowed to use certain software on work computers ( torrents and Steam clients come to mind ) or visit some kinds of websites.
The other risk that a company may want to monitor is ensuring software is up to date ( open source or not ). Stale software can have vulnerabilities that become attack vectors for the bad guys.
Finally there is access control, privileged access, and auditing. There may be systems or data that employees are not allowed to access or are only allowed to access under certain conditions.
I am not advocating anything here but it is totally normal for corporate IT to be tasked with limiting corporate risk and creating an auditable history of compliance. These are the kinds of tools and policies they use.
Nixos?
One thing to take a look at for central account control, sudo rules and a few other things. Is freeipa/rhel idm.
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.
All in all, i guess something like Fedora Silverblue (immutable) with some remote management software?