SAMIT: Do You Really Need Active Directory
-
@scottalanmiller said in SAMIT: Do You Really Need Active Directory:
I think it is safe to assume that assuming an auditor will make up a requirement that isn't suggested and doesn't exist, and then building your infrastructure around that assumption, makes little sense. You could use that logic to do absolutely anything.
This is such a trivial thing to work around, and doctors do this every day. To assume that your auditor will make your HIPAA requirements different than the rest of the world... is a bizarre assumption unless you know you are dealing with a criminal and aren't taking the necessary legal action, but in that case, they will just find something else to extort you over.
But even if the auditor decides to require this, there is no reason to assume AD is the solution. AD doesn't do anything for AD or updates in fact. So how that helps the auditor, I have no idea.
OK OK OK - you win.. I'm clearly over thinking this. they can't require a way to get the information - so if I want them to get it by visiting every machine - that's my prerogative.
Though as you said - a PS script can do it (and well, we assume as IT we have the local admin account password so we can do this at a network level - alright... )
-
@Dashrender said in SAMIT: Do You Really Need Active Directory:
@scottalanmiller said in SAMIT: Do You Really Need Active Directory:
@Dashrender said in SAMIT: Do You Really Need Active Directory:
We'll use my office then for requirements - must be HIPAA compliant. So I have to show that AV is installed (and I assuming I have to show it's getting updates - but maybe I don't HAVE to), I'm pretty sure I have to show that updates are being applied.
AV is part of the OS. There's really nothing to show. You'd have to have removed it. And updates are automatic, again, you'd have to have disabled them. If you are audited, each machine shows you the status. That's trivial.
So you've been through an audit and the auditor allowed you to say - and to see the status of each machine's AV level - we'll be going around to every machine now - and they still passed your audit?
AD doesn't provide this... Am I missing something?
-
Thanks for the reply Scott. Some of my perceptions are based on the way things are done here but I am always trying to learn better methods. In my looking for a better position I'm trying to be as informed as possible and have a good grasp on alternative methods.
-
@scottalanmiller said in SAMIT: Do You Really Need Active Directory:
@jmoore said in SAMIT: Do You Really Need Active Directory:
> 1. What is the best way to handle accounts without Ad?
This is very broad. The best way for most shops is "do nothing". Most companies "manage accounts" because they were told this is why they needed AD, and they bought AD, so they need to do it to justify it. But generally you don't need to do this. AD doesn't provide this benefit for us as an MSP, and we don't need it, so that's a good example of just not having it. Obviously accounts DO need to be managed, but just locally on machines is really fast and easy. I do this all day, every day, and it is often faster to do it locally than to even access an AD server.
What do you use to sync accounts and passwords between the computer and services such as storage, email, and whatever other services require login?
For example:
Local computer login
Email
Git*
Intranet/company portal
etc.How do you handle 2FA centrally for all services?
What about password changes, what do you use to sync their local computer password with other services and enforce 2FA if there are these requirements?
Or, is it that you are saying to keep everything separate and let all employees manage their own accounts everywhere?
-
I think the confusion here lies with the fact that when talking about AD, there's an assumption that of all of what AD DS is and typically includes in the bucket such as Group Policy, MS DNS, etc... When you have MS AD DS, you will have Group Policy and such, so that's a part of having it.
So, if you get rid of AD, you'll also be getting rid of Group Policy and whatever else is in use with it. So, you'll not just be replacing AD and that's it, typically.
But yes, AD, by itself, is just a database that stores "objects".
-
@Obsolesce said in SAMIT: Do You Really Need Active Directory:
I think the confusion here lies with the fact that when talking about AD, there's an assumption that of all of what AD DS is and typically includes in the bucket such as Group Policy, MS DNS, etc... When you have MS AD DS, you will have Group Policy and such, so that's a part of having it.
Exactly, which is why I keep referencing what it is and isn't and saying that it doesn't do those things. We just had this discussion yesterday in the "learning AD" thread and covered how little AD does.
-
@Obsolesce said in SAMIT: Do You Really Need Active Directory:
So, if you get rid of AD, you'll also be getting rid of Group Policy and whatever else is in use with it. So, you'll not just be replacing AD and that's it, typically.
That's not correct, though. GPO exists without AD. It's part of Windows itself. You can, and still do, use it even when AD isn't there. That's part of the continuing myth that not only the part you point out that AD doesn't do what people think, but the second part is that the things that people think depend on AD, don't actually. SMB, GPO, etc. they all keep working without AD.
-
@scottalanmiller said in SAMIT: Do You Really Need Active Directory:
@Obsolesce said in SAMIT: Do You Really Need Active Directory:
So, if you get rid of AD, you'll also be getting rid of Group Policy and whatever else is in use with it. So, you'll not just be replacing AD and that's it, typically.
That's not correct, though. GPO exists without AD. It's part of Windows itself. You can, and still do, use it even when AD isn't there. That's part of the continuing myth that not only the part you point out that AD doesn't do what people think, but the second part is that the things that people think depend on AD, don't actually. SMB, GPO, etc. they all keep working without AD.
I understand what you're saying because on windows you can run
gpedit.mscand get your local computer GP system.The gotcha is no one in the world is using the local workstation settings for this, they are all using GPO Editor from an AD Server to push broad settings out.
-
@Obsolesce said in SAMIT: Do You Really Need Active Directory:
What do you use to sync accounts and passwords between the computer and services such as storage, email, and whatever other services require login?
Why do you feel a need to do this, though? There is an obvious assumption, that generally stems from AD, that we want or even need this, when in fact, it's often not even desirable let alone a requirement.
If you do need it, AD doesn't do this for me anyway, so clearly AD replacement alone isn't enough. AD doesn't provide this today (nothing does just as a blanket) so why would something else suddenly need to? If you really need single sign in everywhere, you have to address that on a unique case by case basis and see what tools work at all, let alone work well, for your specific scenario. But AD is actually quite bad at this given its LAN-assumption architecture, it's one of the worst, rather than best, approaches.
But it's going back to the basics.... we keep approaching the problem from assumptions that are derived from AD.
-
@DustinB3403 said in SAMIT: Do You Really Need Active Directory:
The gotcha is no one in the world is using the local workstation settings for this
Actually, lots are, because the local are controlled by.... Salt, Ansible, scripts, SMB (not AD)... lots of people are doing it, and not manually touching the local tools, because there are lots of ways to do it. The assumption that AD is doing something special here is not correct. Even when we say AD does it, it's not AD doing it. It's just a shared folder, and local machines just look themselves up in AD to see what they should do with the SMB share based on their group. AD is nothing more than a directory here, too.
There is no gotcha. It's just misconception. The consistent misconception is that everything is "AD vs manual individual control", which is never correct. The second consistent misconception is that "manual individual control" is never the right answer, when often it is.
-
@Obsolesce said in SAMIT: Do You Really Need Active Directory:
When you have MS AD DS, you will have Group Policy and such, so that's a part of having it.
That's mostly true, unless you aren't on a LAN. Then you potentially don't.
But also, you get this with all AD, not just MS AD. AD in no way is tied to MS, nor is any of the things people associate with it.
-
@Dashrender said in SAMIT: Do You Really Need Active Directory:
@scottalanmiller said in SAMIT: Do You Really Need Active Directory:
@Dashrender said in SAMIT: Do You Really Need Active Directory:
We'll use my office then for requirements - must be HIPAA compliant. So I have to show that AV is installed (and I assuming I have to show it's getting updates - but maybe I don't HAVE to), I'm pretty sure I have to show that updates are being applied.
AV is part of the OS. There's really nothing to show. You'd have to have removed it. And updates are automatic, again, you'd have to have disabled them. If you are audited, each machine shows you the status. That's trivial.
So you've been through an audit and the auditor allowed you to say - and to see the status of each machine's AV level - we'll be going around to every machine now - and they still passed your audit?
I have
I had to implement this with no centrally managed tool. I used wazuh to create triggers for certain events to go the SIEM.
Based just on local logs I can
- Know AV is currently running (sytemctl timer that runs a service status check every 4 mins and writes to a log file if there are any issues)
- Know when scans were last run be ingesting completed scan logs and creating a low level entry in SIEM
- Know when AV database was updated (also taken from log file)
- Know when any infections are found. It will write to the log file and in my case send a high level alert.
Dashboard shows scans every 2 mins. I was running this when testing to see a list of events over time.
-
Here is the bottom line that is making this all so hard...
Everything. Literally everything, around the term AD is a false assumption. Everything involving what it does, who provides the tools, how much it costs, what depends on it, why you want it, what you need it to do, what breaks without
it..... is generally misconception.AD is a good product, with good times to use it. The things that are often associated with AD are often good products, with good time to use them. But almost every AD implementation, whether used correctly or not, is used under a state of confusion with a belief that it does something it doesn't, that it's needed to do something it's not, that it's the only way to do something that it isn't, that something was needed that isn't, etc. AD is one of those products so incredibly simple, that everyone is convinced that it has to do more than they know it does. No matter how much we explain how simple it is, the assumption is always that there is more to the story and we are just oversimplifying. But that's not the case.
AD isn't MS only. AD isn't the only directory server. AD doesn't do anything beyond directory services. AD doesn't do security. AD doesn't enable any feature, of any OS. AD isn't necessary for any service commonly associated with it. No service commonly associated with AD is the only way to do the thing it does, either. MS is not the only maker of any service that AD is associated with. Nothing that AD does is a requirement or assumed needed functionality. Nothing done by something associated with AD is a requirement or assumed needed functionality.
The discussion is hard because we can't remove enough assumptions. AD is such a quagmire of misinformation, incorrect terms, marketing momentum that we just have to keep chipping away at a new layer of "AD isn't actually what you think that it is."
-
@IRJ said in SAMIT: Do You Really Need Active Directory:
I had to implement this with no centrally managed tool. I used wazuh to create triggers for certain events to go the SIEM.
Many RMM will do this, too.
As will MeshCentral!
Those are both central management tools, but non-Windows ones. MC is great for knowing that AV is installed and running at every machine.
-
@scottalanmiller said in SAMIT: Do You Really Need Active Directory:
@IRJ said in SAMIT: Do You Really Need Active Directory:
I had to implement this with no centrally managed tool. I used wazuh to create triggers for certain events to go the SIEM.
Many RMM will do this, too.
As will MeshCentral!
Those are both central management tools, but non-Windows ones. MC is great for knowing that AV is installed and running at every machine.
SIEM is nice to use because its one location of truth to manage.
-
Please it is much nicer for running queries
-
@IRJ said in SAMIT: Do You Really Need Active Directory:
@scottalanmiller said in SAMIT: Do You Really Need Active Directory:
@IRJ said in SAMIT: Do You Really Need Active Directory:
I had to implement this with no centrally managed tool. I used wazuh to create triggers for certain events to go the SIEM.
Many RMM will do this, too.
As will MeshCentral!
Those are both central management tools, but non-Windows ones. MC is great for knowing that AV is installed and running at every machine.
SIEM is nice to use because its one location of truth to manage.
Oh yes, we are moving to that. But for "alternatives", there are more ways to skin that cat.
-
@scottalanmiller said in SAMIT: Do You Really Need Active Directory:
@Obsolesce said in SAMIT: Do You Really Need Active Directory:
So, if you get rid of AD, you'll also be getting rid of Group Policy and whatever else is in use with it. So, you'll not just be replacing AD and that's it, typically.
That's not correct, though. GPO exists without AD. It's part of Windows itself. You can, and still do, use it even when AD isn't there. That's part of the continuing myth that not only the part you point out that AD doesn't do what people think, but the second part is that the things that people think depend on AD, don't actually. SMB, GPO, etc. they all keep working without AD.
Right, but you know I wasn't talking about Local group policy.
-
@coliver said in SAMIT: Do You Really Need Active Directory:
@Dashrender said in SAMIT: Do You Really Need Active Directory:
@scottalanmiller said in SAMIT: Do You Really Need Active Directory:
@Dashrender said in SAMIT: Do You Really Need Active Directory:
We'll use my office then for requirements - must be HIPAA compliant. So I have to show that AV is installed (and I assuming I have to show it's getting updates - but maybe I don't HAVE to), I'm pretty sure I have to show that updates are being applied.
AV is part of the OS. There's really nothing to show. You'd have to have removed it. And updates are automatic, again, you'd have to have disabled them. If you are audited, each machine shows you the status. That's trivial.
So you've been through an audit and the auditor allowed you to say - and to see the status of each machine's AV level - we'll be going around to every machine now - and they still passed your audit?
AD doesn't provide this... Am I missing something?
We were well beyond just AD at that point.
-
@scottalanmiller said in SAMIT: Do You Really Need Active Directory:
t manually touching the local tools, because there are lots of ways to do it. The assumption that AD is doing something special
I need to stop using AD and completely and wholy replace it with AD DS, because almost no one is ever talking solely about the authentication DB that MS uses - they are talking about the whole stack of services that come together.
