Securing third-party access to your corporate network
-
This is one of those really big, but never mentioned, benefits to fully open source systems. Working in a primarily UNIX environment, we have no per user costs. Adding users doesn't require compromises based on cost. This may sound trivial or petty, but at the end of the day, many of these concerns are around money. On a Linux system you could add each user for free, audit each one individually and enable two factor authentication for free because it is per user. Easier, safer, more effective.... for free.
These little things add up to big benefits when they are all taken together. This one is minor enough that no one ever mentions it. But you run into these constantly.
-
Are LMI accounts still free? Regardless, money isn't an issue, either for LMI or AD. It's convenience mainly. Partly mine, partly the third-party. I don't actually know the names of some of the people who connect to our servers. Often times I'll just know them as "Bob from the Helpdesk", and I might not even find that out until after they have closed the call. I'm also guessing that their systems for storing client credentials might not work well with individual accounts.
-
@Carnival-Boy said:
Are LMI accounts still free? Regardless, money isn't an issue, either for LMI or AD. It's convenience mainly. Partly mine, partly the third-party. I don't actually know the names of some of the people who connect to our servers. Often times I'll just know them as "Bob from the Helpdesk", and I might not even find that out until after they have closed the call. I'm also guessing that their systems for storing client credentials might not work well with individual accounts.
You don't know their names? Anyone I've ever had allowed to remote in has to had to have paper work on file and we did background checks on them ourselves before they were allowed in ours systems. When it comes to any issues that may occur this information is really needed.
-
-
@Carnival-Boy said:
I'm also guessing that their systems for storing client credentials might not work well with individual accounts.
That's potentially a problem. Although each person can store there own in that case, no need for a centralized system.
-
@scottalanmiller said:
@Carnival-Boy said:
I'm also guessing that their systems for storing client credentials might not work well with individual accounts.
That's potentially a problem. Although each person can store there own in that case, no need for a centralized system.
They can always use keepass or lastpass etc.
-
@thecreativeone91 said:
You don't know their names? Anyone I've ever had allowed to remote in has to had to have paper work on file and we did background checks on them ourselves before they were allowed in ours systems. When it comes to any issues that may occur this information is really needed.
When you are dealing with helpdesk outsourcing that can be tough as you are dealing with a pool of people, not a named engineer.
-
@scottalanmiller said:
@thecreativeone91 said:
You don't know their names? Anyone I've ever had allowed to remote in has to had to have paper work on file and we did background checks on them ourselves before they were allowed in ours systems. When it comes to any issues that may occur this information is really needed.
When you are dealing with helpdesk outsourcing that can be tough as you are dealing with a pool of people, not a named engineer.
I've always done if for the people that were on vendor support contracts. Not a big deal just meant every time there was a new employee there was a day or two delay til they could do anything with their software on our network. Much of it was required by regulations anyway.
