r/CMMC•
Inubito

Developers "requiring" local admin access

We've all been there, we have a few developers who are requesting admin access to their local machines to develop new products. I'm wondering how others handle this and remain within CMMC compliance?

A few things I was figuring:

-Verify certs/training, similar to 8570 requirements.

-Segment these machines to a separate VLAN.

-Are admin accounts REALLY required? Has anyone successfully given access simply to whatever dev environment they use? I feel like this is an old way of thinking and is for some reason considered "acceptable".

Just looking for ideas, thanks.

Posted Apr 8, 2022, 2:44 PM UTC

320
Nilram8080•

I don't see anything inherently wrong with giving developers admin access to their workstations, even if those workstations host CUI (though I'd recommend working to limiting the CUI to what is in scope for their development efforts). You'd mainly want to document who has such access and why, and make sure those users are trained appropriately for that level of trust. The NIST HB 162 "NIST MEP Cybersecurity Self-Assessment Handbook For Assessing NIST SP 800-171 Security Requirements in Response to DFARS Cybersecurity Requirements" seems to have such allowances.

If your IT department has the resources to handle any elevation needs of your development team, then by all means, work with them to lock down the systems to improve your security posture.

8
NEA42•

As in all things IT: Situation and terrain dictate.

We have some that actually need a local admin account (not going to air the laundry as to why). Thankfully, it's not as many as before, due to how tech has evolved, but there are a handful, and not just developers.

It's really not that hard to implement, control, monitor, etc. Even in scope, even with CUI, it doesn't have to cause tension, stress, or excess worry. Risk management clearly comes into play, along with policy, procedure, and technical controls. Pretty much the same as everything else.

We also worked with HR to develop a "local admin agreement" that spells out what they can/can't do, and repercussions for their actions.

As with most things, it comes down to organizational need and controls (policy and technical), like everything else.

7
el_chapo_sr•

I don’t think there’s anything wrong with providing developers with admin access if the business itself is okay with it; for compliance, just make sure that those machines are out of scope- don’t let the CUI/FCI/whatever travel to those machines

6
navyauditor•

If they are developing on behalf of a contract with the government, then their work is inherently CUI.

4
GrecoMontgomery•

This is actually a larger issue for me since it walks a line between running a tight security shop and enabling devs to do their work (and, therefore, keeping devs happy in a tight job market). I say no, no access, and instead here's a managed VDI instance that is A) all yours, B) has every IDE, npm, python, whatever - paid and open source - at your disposal, C) a promise from leadership that if they do need something else it will be obtained or configured quickly. Their laptop just becomes an endpoint with Citrix, MSFT, or horizon clients on it. Exceptions only for macOS needs and other ad-hoc reasons that need it.

The goal here is to treat dev like privileged access as it needs to be controlled BUT, while it's a pain in the ass, we sweeten the deal by giving them powerful resources with no limits to what they can use or download because it's protected (endpoint, proxy, vuln scan, etc). No worries about crap on their home or public networks, etc.

And yes, you're correct, this has never once worked out but I can dream! 😉

5
InubitoOP•

I instance that is A) all yours, B) has every IDE, npm, python, whatever - paid and open source - at your disposal, C) a promise from leadership that if they do need something else it will be obtained or configured quickly. Their laptop just becomes an endpoint with Citrix, MSFT, or horizon clients on

It's a tough problem to address for sure! I've thought about the crazy VDI solution as well, but.... You know how it is. lol

2
tekjester1•

If they do any sort of virtualization, admin rights are definitely required.

4
shady_mcgee•

What's the justification for admin access? I imagine it's a nice to have, not a need to have.

2
Darkace911•

If it is like our environment, they are consonantly reinstalling the software with the latest new version. Considering they release a build sometimes daily, we don't have to do the approvals. Plus, there side is mainly commercial.

5
shady_mcgee•

Should be able to run a local build without needing local admin. Not sure why they'd be installing mid-release builds. Maybe there's a reason for it but my guess is they're using it as an excuse to keep local admin.

1
Darkace911•

They are writing device drivers for custom hardware.

2
rt80186•

Engineer here, reasons why my teams needs admin access: custom BIOS, modified kernel, custom device drivers, applications making extensive use of privileged OS calls, so on and so forth, plus the need to configure the product OS to the customers security profile which is frequently higher than our internal requirements.

I am frustrated by the automatic condescending "you don't really need local admin access". It comes off as non-collaborative and leads to engineering actively circumventing controls because it is easier than doing things the "correct way". The process needs to be collaborative and well communicated so that both sides understand the risks, the needs, and why and when controls are absolutely required.

4
shady_mcgee•

reasons why my teams needs admin access: custom BIOS, modified kernel, custom device drivers, applications making extensive use of privileged OS calls

All of this screams "Segregated network with no access to production". If you want to have this access on a device which is air-gapped from the prod network then go ahead, but if you want this on your standard workstation it's a risk, and with the current threat landscape you'll be really hard-pressed to convince anyone that it's an acceptable one.

the need to configure the product OS to the customers security profile which is frequently higher than our internal requirements

I feel like you're contradicting yourself here. Does the team need elevated access, or does the team need their builds to work in a more restricted environment? It can't be both. If you need to simulate a client network which has different controls than yours then it needs to be, again, in a dedicated network air-gapped away from your production network.

The process needs to be collaborative and well communicated so that both sides understand the risks

I'm 100% in agreement here which is exactly why devs (or anyone else) should not have local admin. Give them admin and they will make changes, install updates, and install random software from the internet with zero oversight.

Removing admin access forces them to make a request for the software: This introduces oversight since a different individual will need to look at and approve the request. The dev needs to communicate the request, why it is needed, and the impact of not allowing it. This request is then analyzed, other options are presented which the dev may not have thought about, and a decision is made. Maybe the request is approved, maybe an acceptable workaround is devised, maybe the request is denied because it introduces too much risk, but the end result is it's not just the dev making that decision on the fly.

That's is a good thing. No single person should be able to make a change to a production component without a second individual validating it

1
rt80186•

First point, engineering is air gaped from the end user environment with a rigorous process with input and oversight from multiple stake holders to take an engineering first article into production. These processes processes predate security engineering but have been expanded to incorporate it

From there on, do you understand that modifying the operating system kernel inherently requires bare metal access? This isn't a negotiable point, and it is organizations jobs is to figure out how to balance this with access to the outside world in coordination with product engineering, safety engineering, readability engineering, human factors engineering, security engineering, quality, contracts, and who ever is paying the bills. The conflict between security and safety is a particularly interesting case. Both require the ability to demonstrate the providence of COTS elements while on the other hand, safety emphasizes baseline stability whereas security emphasizes continuous baseline updates

3
SuddenlyDonkey•

Would setting them up with LAPS meet CMMC compliance?

2
NEXTitManger•

We use a product called autoelevate to control this.

2
TXWayne•

We have a policy against having local admin on your system but then we also have an eWaiver process for policy exceptions like this. For an admin account, local or on any server, you have to take specific training, submit a waiver spelling out why you need it and on what specific assets, have it approved by your boss, and someone in your Corporate or BU cyber organization and it is renewed annually. Plus there is monitoring to make sure that that account is not used for anything other than admin duties. It is pretty simple to set up a Splunk script to look for people’s admin accounts out cruising the internet and then warn them that is unacceptable.

2

MFA Admin amounts vs standard user as admin. Give them admin accounts like you’d give IT. Tell them it can only be used for authorized purposes. Standard acct for standard day to day.

1
navyauditor•

Great answers here. You are authorized to designate who needs admin access in your org. You can do this in a compliant fashion. Use of those creds to do things like download software they should not is something you have to watch out for. I recommend strong policy supported by leadership. Developers are good at finding their way around technical controls although you should have those too. I think the segemented LAN is a great approach (DevNet) and still maintaining that their regular log in creds are not admin. They are user like everyone else, but they have admin creds or access to admin creds when needed.

1
InubitoOP•

Hey everyone I appreciate all your inputs! Some good discussions going on here. It does seem like there is a genuine need for devs to have admin access to systems, obviously not full network/domain, but the local makes sense.

1