okay, Another idea for a secure environment. Secure, single sign.
And this goes back to the time or, you know, really to appreciate the significance of single sign on Let's go back years and years ago toe and were prevalent in smaller networks. Have you had a network of 5 10 systems almost assuredly they were set up
in a peer of your network.
Well, if I'm connected to System A, I need a set of log in credentials to connect the system. Eh?
That I will print to a printer on computer B. I need log in credentials there. And for every system that I'm gonna access, I'm gonna need a set of credentials for that particular system. And that was the issue with a peer to peer network. And so I might have 10 other computers, 10 sets of credentials.
So I'm either going to write those username and passwords down user names
or I'm one tiu choose easy passwords, or I'm gonna use the same password for all the resource is. And ultimately, if that's the case, I'm gonna do some very unsecure things with password management.
we shifted over to the client server environment.
So I provide my log in credentials to an authentication server and in exchange for those credentials they give me are in exchange for that long and information, I get a token I'm granted to token that resides with me throughout my duration of the log in to the domain. And that's really what a domain structure
is based on. Is this idea of single sign on
and release force. That token goes that tokens simply contains a list of the groups which I'm a member.
Ah, so when I go to access printer, be my token. My memberships are compared up against the access control this on that printer. And if it says sales came on on the sales team and I have full control of the printer, Well, that's Max matched up against
the access control list on the printer,
and I'm granted access. Okay. Actually, basically, the token would say I'm on the sales team access control list on the printer would see sales team full control. Okay, so that authentication took and resides with me. I don't have to continue to provide credentials. I can simply provide my credentials one time.
Hence the name single song.
Okay, now the benefits of that much easier for end users. Obviously, um, centralized control and management of passwords so I can enforce it. Good. Robust password policy on my servers. Now again. Not foolproof, but it's a step in the right direction.
Um, single sign on environments are easier to manage. We can use those. When you look in the policy, you know, there are a lot of advantages
now, the downside, of course, to a single sign on environment is this idea of keys to the kingdom. Meaning okay, if one password were great. Me access to all the resource is in my domain.
If somebody gets that one password they have access to all the resource is so that's definitely true. But ideally, with well trained users and good password policies in place will mitigate that best.
And as a matter of fact, what we're moving towards today is this idea of super sign up. So we logged onto one authentication server and we get this authentication token that's capable of traversing trusts throughout many different domains in many different organizations. This is the idea that,
allows you to log on to numerous. Resource is with your social media accounts. Maybe your Facebook account or Twitter,
you know, like so if I'm gonna go on by
plane tickets at Southwest Airlines rather than having to create a user account there, I can simply Logan is a Facebook user, and my credentials are passed across that that trust that's been created. Sometimes we refer to those as Federated Trusts. So we have the same problems, but on a much larger scale,
you know, definitely easier for user's cuts down on user names and passwords, I've gotta remember. But ultimately, you know, keys to the kingdom, you know, exponentially increased with all these different resource is once that social media account, those potentials get compromised.
You know that the numerous domains on numerous organizations, my credentials air compromised across all across all of these
now very popular single sign on technology. So getting away from Super sign on, let's go back to the domain environment. Curb Rhodes is a very, very popular single sign on technology. Today it was developed for UNIX. Most UNIX systems still use it in a network environment.
Windows 2000 and up. So that's been quite a while ago. Windows 2000.
It was the first Microsoft system to use Purple Rose. But it's very much in use today.
It's ticket based, so users ultimately you're branded tickets to access. Resource is and those tickets provided mean evolve in a means of authentication, lots of different elements. And as a matter of fact,
ah, Kerberos is quite complex. Although you can certainly get a simplified overview of curb Rose in the C I S s P domain for access control.
There's a little commercial for the C I S S P course, but ultimately, Kerberos is about taking those credentials from a user and in exchange for those credentials, giving the user what's referred to as a ticket ranting ticket.
And that ticket granting ticket proves the usual was authenticated. So it sort of verifies the fact that, okay, they've provided the correct user name and password. Now, every time that they want to access a service, that ticket raining ticket is sent to the ticket raining server and they're granted a ticket
that says the resource so very heavily ticket
base, the key distribution center really is the heart and soul of perp arose because what makes up the key distribution center is the ticket raining server and the authentication servants and those
our first work. Which means from now on I'll stand of service standpoint. The distribution center will be great. So
Scarborough Shoes is symmetric encryption, so there's no need for certificates or public infrastructure. So, like I said today,