this post was submitted on 15 Dec 2024
140 points (98.6% liked)
Technology
59974 readers
3693 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Remediation after an attack happens is part of the security posture. How does the company recover and continue to operate is a vital part of security incident planning. The CYA aspect of it comes from the legal side of that planning. You can take every best practice ever, but if something happens. Then what does the company do if it doesn't have insurance fallback or other protections? Even a minor data breach can cause all sorts of legal troubles to crop up, even ignoring a litigious user-base. Having the policies satisfied keeps those protections in place. Keeps the company operating, even when an honest mistake causes a significant problem. Unfortunately it's a required evil.
On a company computer? That's presumably on a company network? Able to talk and communicate with all the company infrastructure? You seem to be specifically narrowing the scope to just your machine, when a compromised machine talks to way more than just the shit on the local machine. With a root jump-host on a network, I can get a lot more than just what's cached on your system.
We don't use google at all if it's at all possible to get away with it... We do have disposable docker images that can be spun up in the VDI interface to do things like test the web side of the program in a chrome browser (and Brave, chromium, edge, vivaldi, etc...). We do use MS for email (and by extension other office suite stuff cause it's in the license, teams... as much as I fucking hate what they do to the GUI/app every other fucking month... is useful to communicate with other companies... as we often have to get on calls with API teams from other companies), but that's it and nextcloud/libreoffice is the actual company storage for "cloud"-like functions... and there's backup local mail host infrastructure laying in wait for the day that MS inevitably fucks up their product more than I'm willing to deal with their shenanigans as far as O365 mail goes.
I'm pushing for a rewrite out of an archaic 80's language (probably why compile times suck for us in general) into Rust and running it on alpine to get rid of the need for windows server all together from our infrastructure... and for the low maintenance value of a tiny linux distro. I'm not particularly on the SUSE boat... just because it's never come up. I float more on the arch side of linux personally, and debian for production stuff typically. Most of our standalone products/infrastructure are already on debian/alpine containers. Every year I've been here I've pushed hard to get rid of more and more, and it's been huge as far as stability and security goes for the company overall.
No, it's "even devs meet SCA". Not necessarily a standard image. I pointed it out, but only in passing. I can spawn an SCA for many different linux os's that enforce/prove a minimum security posture for the company overall. I honestly wouldn't care what you did with the system outside of not having root and meeting the SCA personally. Most of our policy is effectively that but in nicer terms for auditing people. The root restriction is simply so that you can't disable the tools that prove the audit, and by extension that I know as the guy ultimately in charge of the security posture, that we've done everything reasonable to keep security above industry standard.
The SCA checks for configuration hardening in most cases. That same Debian example I posted above, here's a snippet of the checks
No, we have hard limits on what people can access. I can't access prod infra, full stop. I can't even do a prod deployment w/o OPs spinning up the deploy environment (our Sr. Support Eng. can do it as well if OPs aren't available).
We have three (main) VPNs:
I can't be on two at the same time, and each requires MFA. The IT-supported machines auto-connect to the corporate VPN, whereas as a dev, I only need the corporate VPN like once/year, if that, so I'm almost never connected. Joe over in accounting can't see our test infra, and I can't see theirs. If I were in charge of IT, I would have more segmentation like this across the org so a compromise at accounting can't compromise R&D, for example.
None of this has anything to do with root on my machine though. Worst case scenario, I guess I infect everyone that happens to be on the VPN at the time and has a similar, unpatched vulnerability, which means a few days of everyone reinstalling stuff. That's annoying, but we're talking a week or so of productivity loss, and that's about it. Having IT handle updates may reduce the chances of a successful attack, but it won't do much to contain a successful attack.
If one machine is compromised, you have to assume all devices that machine can talk to are also compromised, so the best course of action is to reduce interaction between devices. Instead of IT spending their time validating and rolling out updates, I'd rather they spend time reducing the potential impact of a single point of failure. Our VPN currently isn't a proper DMZ (I can access ports my coworkers open if I know their internal IP), and I'd rather they fix that than care about whether I have root access. There's almost no reason I'd ever need to connect directly to a peer's machine, so that should be a special, time-limited request, but I may need to grab a switch and bridge my machine's network if I needed to test some IOT crap on a separate net (and I need root for that).
Nice, we use Google Drive (dev test data) and whatever MS calls their drive (Teams recordings, most shared docs, etc). The first is managed by our internal IT group and is mostly used w/ external teams (we have two groups), and the second is managed by our corporate IT group. I hate both, but it works I guess. We use Slack for internal team communication, and Teams for corporate stuff.
That's not going to help the compile times. :)
I don't use Rust at work (wish I did), but I do use it for personal projects (I'm building a P2P Lemmy alternative), and I've been able to keep build times reasonable. We'll see what happens when SLOC increases, but I'm keeping an eye on projects like Cranelift.
That's fair. I used Arch for a few years, but got tired of manually intervening when updates go sideways, especially Nvidia driver updates. openSUSE Tumbleweed's openQA seemed to cut that down a bit, which is why I switched, and
snappermade rollbacks painless when the odd Nvidia update borked stuff. I'm now on AMD GPUs, so update breakage has been pretty much non-existent. With some orchestration, Arch can be a solid server distro, I just personally want my desktop and servers to run the same family, and openSUSE was the only option that had rolling desktop and stable servers.For servers, I used to use Debian, and all our infra uses either Debian or Ubuntu. If I was in charge, I'd probably migrate Ubuntu to MicroOS since we only need a container host anyway. I'm comfortable w/ apt, pacman, and zypper, and I've done my share of dpkg shenanigans as well (we did unattended Debian upgrades for an IOT project).
SCA is for payment services, no? I'm in the US, and this seems to be an EU thing I'm not very familiar with, but regardless, we don't touch ecommerce at all, we're B2B and all payments go through invoices.
If you're worried someone will disable your tools, why would you hire them in the first place? Also, that should be painfully obvious because you wouldn't get reporting updates, no?
We do auditing, and our devOPs team gets a weekly report from IT about any devices that aren't updated yet or aren't reporting. They also do a manual check every quarter or so to verify serials and version numbers and whatnot. I've gotten one notice from our local devOPs person, and very few of my team show up as well. The ones that do show up tend to be our UX and Product teams, and honestly, they have more access to interesting info than we devs do (i.e. they have planned features for the next 6 months, we just have the next month or so). And they need far fewer exceptions to the rules, since UX mostly just needs their design software and Product just needs office stuff and a browser.
I obviously can't speak for all devs, but in general, devs tend to be more interested in applying updates in a timely manner and keeping things secure. In fact, I think all of my devs already used a password manager and MFA before starting, which absolutely isn't the case for other positions.
But it does. If your machine is compromised, and they have root permissions to run whatever they want, it doesn't matter how segmented everything is, you said yourself you jump between them (though rare).
No, it's just a term for a defined check that configurations meet a standard. An SCA can be configured to check on any particular configuration change.
Not necessarily? Hard to tell if something is disabled vs just off.
I don't hire people... especially people in other departments.
But while I found this discussion fun, I have to get back to work at this point. Shit just came up with a vendor we used for our old archaic code that might accelerate a rust-rewrite... and logically related to the conversation I might be in the market for some rust devs.
Sure, but I need MFA to do so. So both my phone and my laptop would need to be compromised to jump between networks, unless we're talking about a long-lived, opportunistic trojan or something, which smells a lot like a targeted attack.
Sounds fun, and stressful. Good luck!