OK, then let's begin. I only got 30 minutes, so I'll try to be quick. I'm going to talk about one specific facet of system.ly today, which is basically containers without a container manager. I mean, there have been quite a few container talks at this conference already, so I'm basically trying to adapt the stuff that containers do and adapt them to normal system services directly. So it's kind of doing containers without actually being a container manager. What are containers again? Lots of people have lots of different definitions. Like I think the three most relevant parts of what a container is are resource bundling. You have this one tar ball or this squash-a-face image or whatever you have, and it contains all your dependencies. So you get rid of the dependencies by simply bundling everything together. There's always sandboxing involved, like namespacing and security, like SecComp and these kind of things. And there's an important component, which is delivery, so where you can actually distribute it on your cluster. For this talk, I'm just going to focus on the first two. Resource bundling and sandboxing. And I'm going to talk a little bit about how you can do these two things without actually involving a container manager at all, but just by using SystemD's own service management functionality. So let's jump right in. The first thing, resource bundling. In SystemD's inception, we had this setting root directory. It's a one-to-one wrapper around Chirute. Like Chirute is like the prototypical pseudo configuration, pseudo containerization feature that Unix always had. And yeah, it used to be semi-useful. And nowadays, it's actually pretty useful. Yeah, we'll come to that in more detail. What it ultimately does is it just invokes something with Chirute environment setup, so that basically everything that shows up as slash there is not what the host sees. Something that is much younger in SystemD is pretty closely related to this, which is root image. Where root directory, where you specify a directory that shall be the root for that one specific service, root image, you can specify a disk image, like a binary blob that contains a file system of some form. Root image is actually pretty, pretty useful. The images that you can specify there can be completely regular disk images that you could also pass to Kiimu or something like that. Everything that they need, they either need to be discoverable GPT, like GPT being the partition table logic and discoverable. By that, I mean that the partition types are properly tagged as what they're actually used for, so that you can actually have a recognized simply by looking at the partition table which one is the root directory and which one is the home directory. It also supports unambiguous GPT or MBR, which is not discoverable. By unambiguous, I just mean that if you have a partition table that contains one partition only, then it's pretty obvious that that's probably the root partition, right? So yeah, you can throw lots of different things at it. Either you avoid all the ambiguities, or you make it discoverable so that it's clear what it is. Or you can just point a raw file system to it, right? Like no partition table at all. You just generate something with Make Squash Affair, so you just create a loop device, put a file system on it. That's fine, too. One tool to create these images, of course, MKOSI, but actually can use whatever you like. You can choose that bootstrap or YAM whatever you do. MKOSI is a tool that I have been working on in the past months. It's supposed to be like a wrapper ultimately around the bootstrap and DNF, but it has a couple of bells and whistles that make it a little bit nicer to use. For example, it can do cryptography for you, which is actually pretty interesting. This root image setting and system unit files actually can do cryptography for you as well. You can actually encrypt the images that you want to run there, and system unit will handle that properly. I think encryption is not that interesting for service management, but something closely related to it actually is, I think, which is DMVariety. For those who don't know, DMVariety is a system that protects file systems from modification. It was created originally for the Chrome OS project because they wanted to make sure that offline modification of the Chromebooks is not possible, meaning that you can leave your laptop in some unsupervised area, and people cannot just take out the hard disk, modify it, put it back in, and you would not notice. But instead, that every single read access is cryptographically verified so that you detect changes. How does that all apply to service management? Basically, if you use DMVariety protected disk images, you can deploy your service on your systems and can be sure that when they run, they run in the exact version that you prepare it and that nobody has interfered offline with them, like, for example, during the downloading or while the system was already running. This is not useful for everybody, but it's certainly useful for a lot of people. Yeah, as I already mentioned, root image and root directory are just a fancy charoot. In fact, root directory is ultimately implemented with a charoot system call, at least under normal conditions, not always, but usually. Charoots are highly problematic in many ways. I mean, you can make them work if you know what you're doing, but they come with lots of problems. One of them is, of course, you first have to mount the API file systems into them, right, like slash proc slash this, otherwise, the program will not actually run from this environment because it's not there. That's something we handle a system with, yeah, whatever. It's a boolean. If you set it, then it makes sure that after charooting into this thing, you also get the proxess and def file systems there so that everything just works. So that's one thing. The other thing is how to share data. On Unix, there's bind mounts for that. Bind mounts are excellent. Traditionally, if you would use normal charoot, how people usually traditionally used it, they would establish these bind mounts on the host, so it would always show up on the mount table of the host. In system D with unit files, you can use bind path and bind read only path, which basically allows you to map anything from the host into anything into the charoot environment. And it will only show up on the mount table of the service itself, so it will not pollute your host. It's actually very easy to use, so I'm not going to go into detail with what you do there. You just specify either one path or path, and then specify a mapping. What from the host should show up where inside of the charoot environment? Pretty much related to this is a relatively new feature of system D, the set of runtime directory, state directory, cache directory, logs directory, configuration directory. Because usually, if you want to ship your service as a bundle, as an ideally a bundle that only contains the actual operating system executables, it's still interesting to actually have changeable data route that reside on the host system.  You want a state directory where your service can put stuff and it stays around. You want a cache directory where your service can put stuff and which is non-essential data, so that if it's flushed out, it's not bad. If it's there, it's optimized things. You might want to configure a logs directory, which is where your service can put logs and a configuration directory where it can put a configuration. If you use these settings and unit files together with root directory or root image, then this will a little bit work like bind pass work. It's going to be mounted from the host into the charoot environment. However, it comes with a couple of bells and whistles. These source directories automatically created in their lifetime. Because the system knows about them, it can lifecycle them together with the service itself. Like, for example, runtime directory. If you use that, it will automatically create a directory for you that has this inslash run, which is where all the runtime stuff belongs, that is automatically lifecycle together with the service itself. So you can, let's say, your engine x.  And that basically means that the run slash engine x directory is created, the instance of service is created itself, and goes away automatically when the service is shut down. The other ones are similar to this, actually. But it's basically a way how you can bundle everything in a resource bundling way in a very nice way, but you can still share specific things and have them reside on the host. Which is nice for updates, for example, because if it's on the host, it will be unaffected by updates or not as directly affected by updates, and you can update the bundles independently of that. Yeah, these things are also pretty nice because they keep bundles self-contained. Because, I mean, traditionally, if you install a Unix service on some system, they will run things like temp files or something like that, where they create additional directories in the file system hierarchy at any kind of place. But if we actually are interested in the bundling concept, then it's kind of like that we don't need to do that, at least if all we want to do is have a runtime directory, state directory, cache directory, logs directory, or configuration directory. By the way, so the runtime directory that was slash run is like a subdirectory of slash run that you configure that way. The state directory is a subdirectory of vallibs that you configure this way. The cache directory is a directory in var cache that you configure this way. Logs directory, you guessed it, probably, is vallog, and configuration directory is a subdirectory of Etsy that you configure this way. So yeah, that's that. A bigger problem, so this is how you can share data between having a bundled service like this and the host or other stuff. But the bigger problem with Truist classically is how to share the user table, right? Because on Unix, of course, the user table is usually maintained in Etsy PassWD if you have a Truit environment, and the Etsy PassWD of the Truit environment is different from the one from the host, because you still live in the same world, can become a bit of a problem. Because the idea of who user Leonard is on the host might be quite different from the idea that Truit sees there. This is only a problem if you use Truits without username spaces and PID name spaces. I mean, it's actually a problem that things like Docker have as well, except that the Docker people usually don't tell you about this problem. And it's not as visible, because if you disconnect the PID name spaces from each other, like if you can't see the process of the other users, it's not as visible that they still run as the same users. But yeah, I mean, the solution, the general solution is to actually username spaces, which we'll talk about here, which aren't yet that adopted on Linux, I figure, because they are hard to use. And if you ask me, they're kind of incomplete. But yeah, so the question is, again, what do you do if you have your bundled service and you want to use root image in a system-to-service file? And so what do you do about the user database? My suggestions to do that is not share it at all. Instead, there's this Boolean option called private users for services. If you turn it on, this basically disconnects the user tables of the service that the service sees from the one from the host. This is ultimately implemented with user NS. But instead of pretending that user NS was a solution for everything and exposing the full functionality, it will expose it in one very, very specific way. So what it does, it will basically install a mapping so that the root user of the host shows up as the root user that the container, like the services, the nobody user of the host will show up as the nobody user that the service sees. The user of the service itself will also be mapped like this and everything else is mapped to the nobody user, right? This basically means it doesn't really matter what the bundled thing actually has in ACPASSWD because we don't really care. We only care for the root user, for the nobody user and for the service user itself. And the root user and the nobody user is actually the only one where all the distributions tend to agree which user ID they actually have, right? User ID root always has UAD0 and user ID nobody, user, nobody has user ID 6553, whatever, yeah. You get the concepts. So with private users, you can disconnect that. So all the other users, like the other regular users that you might see in PS or something don't actually matter anymore. And then there's another module called NSSystemD which synthesizes user entries for root and nobody. Which basically means if you have this NSSystemD enabled which the distributions increasingly have, then you don't actually need ACPASSWD at all because these users which everybody agrees on will exist anyway regardless of ACPASSWD exists or not because NSSystemD is a module that is loaded into the user management of Linux and will make sure that they always show up. There's one piece missing in this. It's like if you have a bundle service, right? If you have a service that uses root directory or root image, how do you make sure that from inside of this environment, you actually see that the user ID you're running as has a specific name? I have some ideas about this. It's going to be very technical so I'm going to skip over this bit, but yeah. So much about the bundling, right? The essence of everything I told you really is use root directory in the root image. If you want the bundling with normal services it should just work and you can use standard images. And with the private user thing you can deal with the user database change. But yeah, the other part of containers, right? Besides the bundling is of course sandboxing and sandboxing is something we added a lot of features recently to systemD. Yeah, basically all my remaining slides are just about specific sandboxing features. We'll go quickly through them. Like one, like I blocked about this one, it's actually one of the more interesting ones. It's, you know how on classic Unix services used to be sandboxed, right? Like it's all about user IDs. It's like how we have been doing since the 90s or even before. Like the Apache user has a HTTBD or something, Apache is running as that and because it's not root that it's running as it cannot access whatever else is happening on the system. And traditionally this is how we put together our Unix systems, right? Every system service we had had its own user ID it was running as and was thus isolated to some way from everything else. It is, if you so will, the quintessential sandboxing technology that Unix always had. It kinda, I mean it's widely adopted but it's also, it's kinda frozen in time, right? It has this problem that it's very expensive to actually allocate a user because the system users that they are, most of the distributions define that you can have at most 1,000 system users.  This basically means that you cannot just allocate users traditionally just like that, use them for something and then release them because they're simply too few of them to actually do this. And even if you did, there's a general problem on Unix that there is no scheme to actually release the ownership of a system user ID again because you have the problem that user ID ownership, like the ownership of a file directory or IPC object or whatever else Linux maintains is bound to user ID, like a numeric ID. So at the time you create that object, the object becomes owned by that user ID. Now if you wanna reuse the user ID for different purposes because you only have 1,000 of them, you would have to first make sure that you have to release the original resource like the file directory IPC object and so on. But that's incredibly hard because you would have to scan the entire file system for this. And what do you do if a user owned a file on some file system that's currently not mounted so you cannot really properly solve that? So most distributions, hence, they just declare for safety reasons, we'll never actually release user IDs again. So if you install a package and you remove it, then most of the files are removed but the system users that are allocated are not. So you leave a major artifact in the system and given that there are only 1,000 of them, that's pretty nasty. In system D, in the system 235, the most recently released one, we have the dynamic user concept, which basically uses a couple of tricks to make this all more bearable, right? So it's a Boolean option. If you turn it on for a service, it basically means that the instant the service starts, a new system user is allocated and the instant the service shuts down, it's released again. How do we deal with these problems that I mentioned that the fact that user ID ownership is sticky on Unix? There are two strategies to that. One of them is we forbid creating objects in most ways. This basically, for example, means that we use a couple of other sandboxing options that I'll talk about later that basically ensure that the service has very few directories that they actually can write to. And if it can't write to anything, it of course cannot actually leave objects around owned by this user. Another strategy is to define some specific areas where the service can write to after all, but then destroy these areas the instant the service goes down, right? Specifically, that's private TMP, for example. It's a simple Boolean that is set for the service and it's actually implied if you set dynamic user for the service. And it basically means that the service, as long as run has a private directory in slash temp that appears as its own slash temp and that goes away automatically when the service goes down. So two strategies, forbid writing, and we do write, make sure that it is removed again afterwards. So that's our strategy there. Yeah, dynamic user is also pretty nice because it keeps bundles self-contained, right? Like traditionally, if you install a system user, you drop an assist users D drop in or you invoke add user or something in your RPM or something like that. But yeah, that basically means you need to distribute stuff in the whole file system. And this way you don't have to do that because the service file contains all the information about the user that needs to be allocated. And it's nicely self-contained and it leaves no artifacts in the system. So yeah, the focus is really on leaving no artifacts. One other sandboxing object concept pretty closely related to this actually is remove IPC. It basically just says that system five and POSIX IPC objects that are created by the service get automatically removed when the service goes down. You know, POSIX, like the IPC systems are usually not that visible to administrators but it's how process communicate on Linux. If it's a Boolean, it's also implied by dynamic user but you can use it for everything else as well. If you set it basically and the service goes down, we iterate through the list of currently allocated IPC objects and remove every single one that matches the user ID that your service ran as. Whereas private TMP, I already mentioned that gives you this private slash temp that is life cycle bound to your service itself. The result of this is again, no artifacts left, right?  There's another option which is private devices. I mean, you know, all these options, like they are much more fine grained than what you traditionally can do with containers, right? Like containers are by default locked down very much and very much disconnected from the host. You don't see the process table, you don't see the user table or at least you think you don't see the user table, actually do. You don't get access to devices and things like that. In system D because we're coming the other way, traditionally the services run without, like with most privileges because that's how system five when it works, we do go the other way around. We locked things down bit by bit. I wish it wasn't so, of course, because security is always better if you're coming from the lockdown version and bit by bit opens things up. But we can't for the due to the system five heritage. But still like, so yeah, so these individual bits, if you take some, use them bit by bit, you can build a very nice sandbox, but you, of course, have to turn them on all individually. Yeah, private devices basically gives you a private instance of flash dev that doesn't contain any real devices, right? What it does provide you in slash devs though is the pseudo devices like dev null, dev zero, dev random, dev view run them, which aren't real devices. Like, I mean, there's not a physical PCI card or something behind that. It's just a way how Linux likes to expose its APIs. So, and in contrast, so like, they're in contrast to let's say dev SDA, which is actually physical device, it's your hard disk, or to dev sound, whatever, which is actually your sound card. So with private devices, basically you get disconnected from that. You still get the API block character devices, but you do not get anything else. It's like, unless your service needs actual physical hardware access and almost no service does, it's the great Boolean to set. There's private network which uses network namespacing to disconnect you from the host network. For every service that doesn't need networking, it's a great thing to do. Very recently we added something more fine grade, which is a little bit like a firewall where you can basically configure for your service, which IP address it shall be able to access. You can specify that simply by IP address and the net mask and just works. There are a couple of more things like that. For example, protect kernel tunables takes away the access to process for the service. Protect kernel modules takes away the access to kernel modules for a service. It's all Booleans by the way. A protect control group takes away the right to make changes to the control group file system. Yeah, then there are system called filter, which allows to apply a specific system called filters to a service so that it can lock it down so that dangerous system calls like, for example, setting the system clock or rebooting the system are not a viable. It's pretty hard to use, or traditionally it's pretty hard to use because who actually knows all the system calls that you want to list there. It's a lot simpler now because we have system called groups which are basically named groups that make it easier to enable and disable specific facets. I got like five minutes left now. There are quite a few more, and I think it's not bad at all that we can't talk about all of them. I'll just quickly, like, with one of them, you can restrict address families like socket address families. With one, you can restrict the system call architectures, blah, blah, blah, blah. The message you should get from all of these are we have all these sandboxing options these days and you can use them like, I mean, much of this, not all of this, but much of this is applied by container manager as well to the containers as running. But the message you really should take home is that if that's what you're in for, if that's what you're looking for, then you can just do that for normal services as well. Just set these booleans on bit by bit and you can run your stuff in a very lockdown version. So, yeah, this is not supposed to be a replacement for container manager, not at all, right? But the reason why I'm doing this talk is mostly because I work for Rathad, right? And I know, like, I come in contact with lots of people who use containers for various different things, right? Like, because containers are like the big word, everybody tries to fit his specific problem into the container world. Like, for example, I met with storage people who want to ship their storage management stuff as a container. And that's certainly a great thing to do until you notice that, well, if you want to manage storage, you actually need hardware access, like, like, block device access. And as soon as you do block device access, you become really, really hard with Docker because it's not designed that way because it actually is supposed to take away the rights for you. So, and then there are lots of stories like that where people see containers as the solution for everything and then try to fit it into the problems that they have. Most of these times, they just say, okay, you're actually interested in the sandboxing or, A, you're interested in the bundling, but you're not actually so much interested in the rest of it. The message I really want to get across is that, yeah, it's a fluid thing, right? Like, maybe containers are actually not the solution for you. Maybe you can use just plain service management and turn on the sandboxing and there you go. Or maybe you can use plain service management and turn on the resource bundling and there you go and it solves your problems as well. Now, I think I got like four minutes left, so maybe we should do questions. If anybody has a question, there's a question. Based on the current state of system D, how far do you think you're along to the path of portable systems? Portable system service, you mean? Well, my last slide here was about the outlook for that. So, portable service is something I've been working on in the long run, which is supposed to be something where you really just can drop in a service, a bundle, like an image file, and then system D will deal with the rest of it. Basically, it's way how everything that I presented on my slides is just pulled together in one tool and makes it nice. At this point, we're basically there, right? Like all the individual building blocks that I want for the portable services are there. It's just a matter of writing this generator that looks at the image files you drop in, pulls out the relevant service files, makes them available on the host system, points them back so that root directory or root image is used onto the original image so that they appear as a native service. So, it's mostly there.  It's one of the things that I have on my tool list legs, basically. It was a long way to go there and to get there because I mean, adding all the sandboxing features, adding all the image handling fixes, adding, like, figuring out what we actually want to do with the user database and Sherwood environments and things like that, that was a lot of work. But nowadays, it's pretty much just actually doing the generator. Oh, by the way, what is something that's also really important to mention is like, because these bits are so fine-grained and you can pick exactly what you want, what you can also do is use this to hook random other stuff up to system D and make it run as a native system D unit. Like, for example, you could probably just use write a generator that now uses an OCI image or something like that and dynamically converts it into a unit file with the generator.  We originally created that to convert system five units, like system five in its scripts dynamically into a system D units, but it's actually way more powerful than that, you can use it for all kinds of other stuff. So what I basically wanted to say here now is that, while I think the portable services are a great way forward, none of this technology is specific to that, right? Like you can stick it together in completely different ways, write a generator from UCI to this and it will work too. Any other questions? Nobody has a question, they have a question. You said that user namespaces were kind of incomplete. Could you elaborate a bit on why you think that is? Why it is or how it is? How it is. I don't know, namespaces have been around for a while, but I don't think they, I mean, you can make them use for specific use cases. For example, flat pack is probably one of the more sensible uses where it's being used, but in general, we are lacking a shift file system, like a huge shift file system. So it basically means that whenever you actually want to use a user namespaces, the way they originally intended them to be used, you have to shift around all the UADs in your image because otherwise everything will be owned by user nobody and that's usually not how systems work, and the fact that you have to shift around, that you have to do a recursive chone is just awful, that's not solved to the end. Other than that, it's probably the major security vulnerability in the kernel in the last months or years or something, right? I don't know, I don't think, I mean, it's super complex. I don't think it's solved to the end. I think it's very hard to use. I think it's way over designed because it allows arbitrary mappings from any user table to any other user table. I also think it's a problem that suddenly systems have much smaller user tables, right? Because you always have to slice up the 32-bit you have into smaller bits. And I don't know, I mean, we make use of it like private user, the Boolean uses it, but I don't think it's solved to the end and I don't think there are any deployments, right? Maybe Docker has code for it right now, but I'm not entirely sure that they actually, people run it in the full mode, how it's intended to be. It appears to be very much like something is still in progress and has been in progress for the last five years or something and probably will continue to be in progress for the next five years or something until we get a shift Fs or something in the kernel, which doesn't look very likely at this moment as far as I know, at least. Any other questions? Okay, I think the time's over. Thank you very much for your time and Chris will probably do more announcement now, so please stay. Yeah, okay, thank you. Thanks Leonard.


All right Let's My name is Jimmy his name is Jake and this is the weekly dumb no frogs are with us today just the The bubble thing James Everyone joining us for the weekly thumb today. All right. How was your weekend buck? All right, I guess kind of was good James There was a big one this weekend the Atlanta Braves hosted the New York Metropolitan station for the NLE East and the Mets have had the NLE East on lock for most of the years These are the new Mets buck show Walter Max Scherzer. These guys are studs The Braves big brotherdom in a way that only can happen to the New York Mets Zach I made this graphic that shows the Mets just in first place all year the Braves dip in oh Gonna catch them. Nope dip gonna catch them Nope and then at the end the Braves are in first place and they had to face to Grom Scherzer Basset who's had a good year. That's it The thing they do with the lights when the pitcher leaves to get lit up is real cool Well, the chop people have you know, but the lights you guys are cool You just got lit up lit chop and man the difference between the division and the wildcard is is pretty huge when you have to Grom and Scherzer Do you want them available for the divisional series? Well, you're gonna pitch them in the wildcard now Which I think still has a chance to flip the script because in playoffs just stuff happens So if you have Scherzer and to Grom waiting you win one of the early games, you'll be good. I love this. I Can't see that's the base. That's the sports. Well, what's this breakdown? You're telling me about oh, it's almost Vanishing no that just took an hour. I don't want to vanish. You have to It's good for the show I hear almost a breakdown. This is a classic a tale as old as time.  Well, he really added the balls Florida by itself is a Valic, yeah, it's a very phallic state one of the most phallic states It's America's penis and then he just says, you know, if you look at all these there's a lot And if you look at over here, there's a little I understand looks like Balls and a penis, but I got his back I think people that know the weekly dumb Would assume we'd and only Zach we'd shy away from this story because you can do this often You see a lot of meteorologist weiner type stuff, but this guy's kind of in the clear like he was the storm was Penal the storm was penal. I like when Zach does the little words and I'll do this The storm was penal. Mmm. You like a lot of things. I like Miz and in Maine a lot I look good. Who's Miz and in Maine looks better on them. Now. I can't really wear that one because it matches my pop Too much and we're green screen in your whole body this episode. That's true On the sideline first one of 2022 That's always there if you need it Jake we get back to the sports There's a big old story in the sports big old story in the sports that big old story too much booty in the pants Zach This one hit close to home for you. There is a cheating scandal that rocked The walleye tournament you already probably heard about this and actually you might have because this is bad And I don't like that one of the guys name is Jake, but Jake and Chase well He does go by Jacob right but when things got real they start calling them Jake in the video Yeah, that's kind of like you're a bad guy. Yeah, like Jacob's Bible and like he brings stuff He brings a loaf of bread when you have a baby Jake cheats at fishing tournaments And they're feeling fish with lead Yeah, I mean this I I caught this earlier as soon as it was four hours old And I sent it to the week the weekly dumb I said let's do this story and then it went huge over the weekend because it's wild So these guys been cheating at been cheating fishing for a while them in suspect. Yes suspect They've won they want 300 grand last year. I knew it. So they finally they weigh their fish They said those fish look old look like you caught them two tournaments ago or whatever That's that they suspect them cheating don't try to do their smack the commissioner cuts open the fish. We got weights and fish Which is electric yeah, and then that guy realizes he's kind of started a mob so later on he's like alright guys Let's take it easy Jake don't you got a goat go anywhere be cool They will have their day, but then he keeps cutting open the fish.  Like if you're gonna cheat it would be like oh, let's stuff it with more fish stuff it with more fish They put like big old muskets in there.  Yeah, I wouldn't mess with the fishing community They know places others don't in the marshes Let's get off Jake's cheating and let's talk about the not sports and Jim your boy Lil Nas X Lil Nas X he was on the microphone, but he wasn't on stage Did you hear this story Zach and then he chimes in and he says oh guys? I'm on I'm not on stage right now.   You know this looks good looks better than the employee of the week My ugly brother Luke. It's the employee of the week. Don't boom boom boom Nippetism Have the beads explode everywhere. I have to do that.  I've seen from 20 feet away Your reaction is great. I hit him Jake hit him. It's been a it's a good video from our warehouse games a game We created which I got a lot of applause So he gets employee of the week for that reason. That's me doing it Whoa do it again your your eyes are no, they were they were the same that time Same the one time they went different So you want the best damn dress shirts money can buy well check out mizzen and main Right now if you go to mizzen and main.com and use promo code dumb You'll receive $35 off any regular price order of $125 or more plus free shipping On orders $100 and more and free returns.  I was just thinking when you brought up that chart We would have been pretty good at if we had gone the law route tag team lawyers when there's time to bring out exhibits That's when we would bring the crowd down all about exhibit a except you have southern lawyers They have to like you have to get the exhibits past or well exhibit B Yeah, and then you have oh exhibit C which has the most proof But you're not allowed to show it the judge says please erase that from your memory and you know, they don't actually exhibit C is the perfect information for exhibit D and there's a photo shop of the guy Photoshopped the guy holding the gun. They're like that's photoshop.  Yes, it was yeah Yeah, this is what it would have looked like if he was holding the gun. It's a photoshop Yeah, we would be good at exhibits. We'd be good mock lawyers bringing our exhibit guys and you and I That'd be a good TV show. I'd watch that mock lawyers I think it was bash and Nash no But like not a real law show but like if there was a fake courtroom Mm-hmm where you got to do silly stuff like it was us first Nicky Cass as like fake lawyers having to figure out a situation Like that episode of always sunny whoever wins it's debate class fun debate class on YouTube exhibits only Exhibits only I don't want to hear you talk no in debate class. Oh my god. If you don't have visuals. I'm out


This is stock number 9263XA. We are here at Summit Automotive in Fond du Lac, Wisconsin. Your new and used SUV headquarters. Today we're checking out this super clean 2004 Chevy Tahoe Z71 LT. This vehicle has the 5.3 liter V8 motor. From this HD video you'll be able to tell that this SUV is in really nice shape considering the age and the miles on it. Summit whites the color. Factory alloy rims all the way around on this vehicle. And it has Cooper Discover 26570R17 tires with about I'd say 80-90% of the tread left. Lots of tread left on those tires. Front fender is in excellent condition. Front bumper is in really nice shape as well. No major dents or dings on it. Has factory fog lights. You can see the headlights are nice and clear. And the grille is in excellent shape. I didn't see any dents or dings on the hood. We shoot all of our videos in 1080p so if you have HD capabilities on your computer tablet or smartphone device turn them on now because it's like you're right here looking at the vehicle with me. As you can see down this side of the Tahoe very clean as well. Has some nice pin striping on the side. Vehicle runs very smooth as well and drives excellent. Has been fully safety and inspected by our service shop. And is 100% ready to go. Factory black step bars. Back rim is in excellent condition as well. And the back tires have just as much tread as the front tires. Rear bumper is in nice shape. Has a towing package which includes a receiver hitch and 7 pin wiring. And the rear gate is in nice shape as well. Take a quick peek at the back storage area. And you can see that that carpeting is in really nice shape.  As we will see in just a little bit here. But I didn't see any dents or dings down the side of the rear gate there. And the rear bumper is in nice shape as well. As we go down this side of the vehicle just as nice as the passenger side. Paints in really nice condition. Has the power folding mirrors with the built in directional signals. Inside the Z71 LT package gives you the gray leather interior. There are no rips or tears on this seat. Leathers in excellent condition. Both these seats are heated and power. Factory floor mats throughout. We have Bose sound system, power windows, power locks, power mirrors, memory driver's seat. As well as power pedals, auto headlamps. Inside you can see that this vehicle has 175,659 miles. And yes, we will be putting fuel in this Tahoe as soon as the video is over. Multifunction leather wrap steering wheel. That's in really nice shape. Has the six disc CD changer with the Bose sound dual climate control. This vehicle has never been smoked in. You can see the cigarette lighters never been used. Smells very, very clean in this vehicle. Also has your rear air controls and your homelink system up there. Power sunroof as well. Passenger seat is very clean as well. No rips or tears on that. And we got a factory floor mat on that side as well. We will take a quick look at the back seats and then we will check out under the hood. This one does have the quad seating. There are no rips or tears back here. These seats are in really nice shape. These are captain's chairs. So they have the arm rests on the side there. The seats fold up and down for extra storage and to get to the back third row. Which I told you those seats are in really nice shape and they definitely are. No rips or tears back there. And you can see the carpeting throughout is in really nice condition. And we also have rear air controls and audio controls back here. Take a quick look under the hood. 5.3 liter V8 motor. This Tahoe has been fully safety and inspected by our service shop. Has a fresh oil and filter change. All the fluids have been checked and topped off. This vehicle has been gone through 130 point state inspection per Wisconsin guidelines. And is 100% ready to go. Passed with flying colors. Has newer tires on it. Runs and drives excellent. And to see more pictures of this Tahoe or one of our other 400 new and used cars, trucks, SUVs, minivans, wranglers, you name it. We got to go to our website www.summonauto.com. Full pictures and descriptions of every single vehicle on our lot. Videos of every single used vehicle that we have all at summonauto.com. Thank you so much for checking out the video. If you like this one and want to make it yours, give us a call right now.<PHONE_NUMBER>. Ask for one of our sales associates to make this Tahoe yours today. Once again that number is<PHONE_NUMBER>. I'd hurry up because vehicles in this price point with full four-wheel drive and full-size seven passengers go quick. Once again, if you like the video and want to check out more, go to www.youtube.com. Slash Summit Auto. Remember to like, subscribe and share on those videos. In fact, in the second you see a link to subscribe to our YouTube channel on your left. A link to more SUV and used vehicle videos on your right. If you haven't been to our website on the bottom link to this vehicle on our website, click those, check us out. And we really look forward to helping you with this super clean 2004 Chevy Tahoe Z71. Thanks again.


Welcome to Access a Trader, the number one community for those who are committed to taking control of their trading in order to achieve success, profitability, and longevity. Thank you for joining us. Here's Dan Shapiro to help you find your edge, master your process, and own your future. Hey, guys. Good evening, everybody. Welcome to another edition of the AccessaTrader.com nightly wrap-up show. Hope everybody had a good day trading. Again, like we talked about last night, I really like beta coming into today. I thought yesterday's price action started really setting up some pretty good channels for us today. And we kind of got that move. Pretty straightforward day. I think if you look at how the market is kind of trading the last three, four days, we started talking about this a couple of days ago, the noise level in the tape is definitely lower. The COVID headlines are lower. The overall market headlines from everything, Republicans, Democrats, China, everything is lower. It almost feels like that the market is kind of in waiting mode. In a weird way, it kind of reminds me of a July or late August type of market that people are kind of going through motions that are almost ready for Labor Day and kind of going back to school. Again, all schools are closed, in the tri-state area for the rest of the year. But that's kind of how we are. And like my mom used to say all the time, no news is good news. And I think that's where the market bulls are really starting to get very, very comfortable. I think that's the best way of saying it. And if you look at today's action kind of like yesterday, pretty straightforward. You had good pivots. We talked about shop yesterday and NVIDIA and Netflix. I was a little bit disappointed in Netflix. We're still a pretty decent pivot. We'll talk about that in a second. The only thing that I didn't like about today's session was that we had a big gap. And it really did take a lot of the value from yesterday's watch list. And again, when you look at how beta trades, and I know a lot of people really like a lot of random stocks, the really big, sexy names that are up 200% one day and you never hear from them for another two years. But again, the reason why beta is so unique compared to everything else, like perfect example today, Tesla, we traded it to the long side, to the short side, literally in the same candle, in the same interval. And these are the only stocks in the entire market that you can have the luxury of missing a window in one direction and have it confirmed in the opposite direction to kind of get good value. And that's what we got today. And if you look at the headlines today after the close, you're kind of getting the same, you're kind of getting the same format that we've been seeing. So for example, Disney came out with earnings, right? And I tweeted this out and I said, look, unless Disney comes out with some really, really aggressive negative news, everybody knows the market is expecting a horrific quarter. You have 58%, right? 58% in revenue, lower revenue in the parks being closed, the cruise ships. And for a while, Disney was just sitting there. It was just sitting there. It was up a dollar, up a dollar 50, up 80 cents. And the last 40 minutes or so, they started selling off. Again, I'm not privy to what's going on in the conference call because I'm recording this video. But unless they're saying something very, very, just really, really crazy, even if the market really sells the stock off tomorrow, it's not gonna be one of those sell-offs. It's gonna be 20, 25%, 10%. It's gonna be kind of what they're saying on the conference call. And if you look at kind of the big number that jumps out at you, 1.4 billion dollars in revenue loss to COVID. And that's kind of a big deal. That might be actually why they're finally selling off the stock. But if you look at the daily chart, again, can there be a very big macro trade left in Disney, even if it starts building below this 98, 97 level? Yeah, sure it can. Of course it can. But again, I think before anybody goes into tomorrow's session and say right away, oh, the bears are in full control of Disney, for example. You know, again, you have to see how the stock opens up. You have to see how early sellers get treated and see what happens in the next round. The same way, for example, on BYND, right? BYND had this big, big move after the close. They came out with earnings. Pretty good earnings, right? Pretty good earnings. They top forecast. They're talking about rapid growth due to the closures of so many restaurants. But again, they did exactly the same thing. The smart thing with all these other companies are doing. They stopped forward guidance. Again, it's a very, very smart and savvy safety net that Apple actually started about a month ago to make lower expectations going forward. Very, very savvy as well. Airbnb, again, just to show you how devastating the effect of the COVID-19 virus is, they cut 25% of their force. Workforce, 25% gone. That's a big deal. Again, nobody's traveling. Nobody's renting out homes. This is a big deal. Again, is the economy a reflection of the stock market? Absolutely not. But again, I think the bigger headline is match.com, right? They're said in the quarter that Tinder saw a slowdown, right? Not a stop, but a slowdown, which basically means when you're sitting at home and you don't have companionship, okay, despite getting the COVID-19 virus, you might not be overly aggressive to meet a new person online, but you're still willing to do it. Match up 2% after hours. So I think going into tomorrow's session, when I looked at a lot of the charts, you could see some very, very clean takeaways from today. Very, very aggressive move up to start the day. A lot of stocks did what they had to do. Well, to get to the pivots in a second. Again, bears can make a case. Well, there was a double top here all for the 220 areas of the queues. And you can see it right here. 220 is the high here, 220 is the high here. Nice little sell-off into the close. The bulls can turn around and say, yeah, all that did happen, but look what happened as well. Not only did we reclaim the 213 area on the queues that have been over and under now for the last month, we also held the rising five-day moving average, and now we're starting to build the base here. So if you look at the charts tonight, you'll see a lot of names in between, right? You'll see a lot of names that are in between their ranges and something has to give. So tomorrow, is this gonna be one of those days that I think there's gonna be tremendous value in the overall market? Probably not, right? Cause if you look at names, for example, like in the video, right? In the middle of the range. When you look at Netflix, and it had a chance to really, really go today, we had a, you know, okay trade on it today. It could have been a lot better, right? But you can see it's right in the middle of the range still needs to confirm. If you look at Tesla, we had a two-sided pivot on this thing, one to the upside, one to the downside. It's kind of the middle of the range. So it would not shock me tomorrow if we are sitting there and waiting for two or three good pivots throughout the day. It wouldn't shock me, because again, you're getting a good sense of what's gonna happen tomorrow on the previous night's watch list, the previous night's research. And when stocks are sitting in the middle of the ranges, for example, like Amazon, right? Perfect, you know, perfect example. Amazon is the middle of the range. You know it needs for the bulls, needs to reclaim this level here and the bears need to reclaim the level here. So it's not here, not there. So a lot of names are going to reflect kind of the closing price action of the queues. Would it shock me if we rally tomorrow? No, it wouldn't. Would it shock me if we go down tomorrow, start losing the five-day moving average and get start going below the 213 air? No, again, it's kind of the same MO. It's kind of the same MO that we're talking about every single day. The market means nothing anymore, okay? The scoreboard is strictly a conversational piece. You're getting a guideline, kind of a little bit of a blueprint what you think is going to happen tomorrow, but it comes down to research, it comes down to technical analysis. And when you go through, especially, when you go through the NASDAQ 100 names, you'll see there's a couple of names that are clearly look like they're going to break down tomorrow, okay? If you do your research, it's only 100 names. It should take you 10 minutes, five minutes, five, 10 minutes to go through the NASDAQ 100 names. There are names that look like they are about to come in. There's a couple of names that look like about the rally, but ultimately, again, like I said, going into tomorrow's session, I would not be shocked if we're sitting there and sitting there and playing with our thumbs and playing with our hair, because again, we need things to confirm. Again, I hope I'm wrong, right? I hope I'm wrong, but again, when it comes down to it, it's not how many you trade, it's how many you trade properly. And when you look at today's pivot, some good stuff, some really, really good stuff here. So here's the video from last night. We talked about this, there's a lot of beta names that are setting up really well for tomorrow. That's for today, right? We discussed the technical levels on shop, on Netflix, on NVIDIA, on Roku, right? Some really, really good setups. The market gapped up today. A lot of names really gapped up a lot. Like for example, last night, I liked on the watch list for today, I liked Roku at 2450.  I liked NVIDIA at 92. It gapped up to 97, right? So we had to really pick and choose this morning from good value, but some of the names that did play out very well, they played out incredibly well. And that's the name of the game. Again, you're not trying to pick the ones that are giving the biggest move, looking for confirmation. You're looking for the ones who are sitting right on the confirmation levels and need that break of supply or demand, depending on which way you're trading, for that second entry to confirm. So let's talk about this. So there was a two-sided pivot today on Tesla. 792, 783 needs to build. I thought if this thing got going, we could have potentially saw an 809 area. So I got along this thing on the second entry and it stopped around 798, 799. If you guys remember, it just, they wouldn't get over it. And after a while, the one thing is when a stock pauses, especially when it pauses near a whole number, right? Especially, again, the whole number might not mean anything technically for that interval, but a lot of traders and a lot of investors, a lot of funds, they're going to be positioning on that whole number. So when you see, for example, a pregnant pause in the stock, it's only gonna give you a couple of minutes to really figure out who's in control of that pivot, especially near that whole number area. And if you look at Tesla, right? If you look at Tesla here, and here's what I mean, right? So here's the 793, excuse me, 792, 793. And it gave that pop right to that 799. And what I started seeing was, I started seeing the bids just got thinner and they started getting wider. So I started selling stock. I took some cash on it, it was fine. There was nothing wrong with the trade. Again, let every trade be a four, five, six point move into supply, whatever. But again, it really, all it needed to do is get one more wave of buying. We would have saw a move going into the upper Bollinger band. Again, it is what it is. So we'll talk about the downside in a second. Roku, again, I really, really liked Roku that 2450. Obviously, it opened up at 28. So here's the 2450 that I was talking about from last night, right? Here's the 2450 that I liked last night. The problem is it gapped up almost 28. So I said, listen, if it starts building above that 2780, 28, it can go obviously, Roku got nowhere near that 28 level. You can see the high of the day on Roku today was 2670. So nothing on Roku. So here, first of all, congratulations to all you guys who came in Long Shop, right? This was yesterday's pivot here, 629 and 637. There were two areas to build. I know a lot of you guys held runners overnight. And this morning, again, I said, big move, congrats to you guys who are Long Shop. I did not have anything overnight. But here was the pivot today that really took the stock, next level stuff. Shop needs 672, 673 build for more and shop exploded. Really, really big move. They do report in a couple of days. Here was shop right over here. Here's the whole, excuse me, right here, 672, right? 672, here it is. 672, that was the opening range high. It took out 672. The first move was the 690. So you had a $16, $17 candle in this thing. Then came in and came all the way back to the 700 level. So big, big move there as well. ZM, right? 145, 145.50 needs to build. Here was Zoom.  So here was the 145, 145.50 area. Went up to like 48 and change. Nice move on Zoom. Netflix, two areas of importance. 429 level needs to build. So it got long, right? I got long on that 429.50 second entry. It traded up to 431 and it took some sales, used breakeven on the balance, but it really, it came so close of really picking up a big move. 431.75 was the highs. I actually still like this level going into tomorrow's session, but you can tell here, Netflix came very, very close on a very, very big move and we were just sitting there and I go, come on, just push, just push and push and it stalled out at 431. So how to make some sales. But again, listen, again, let, again, let your worst trade be a green one. And again, this is how close it came from really busting out this channel. But again, maybe tomorrow. Again, we're still seeing, we are still seeing 450 calls pretty regularly near-term expiration. So we'll watch that again for tomorrow. NOW, monster move here. Trades thinner, okay, 361 needs to reclaim and build. Here was NOW, right? So here was NOW. Here's the 361, this whole area here, 361 just exploded. Big, big move went to 3.73, so big move there. Apple was huge today. I mean, really, really big on Apple. 296.30 needs to build. Here was Apple, right? Here was the 296.30, right? 296.30 on Apple. Big move went all the way up to into the 300, so big, big move on Apple as well. And again, that was the play. 2.90s take on the way up, right? Take on the way up. Now, I said decent flow to the upside, now we're watching both sides. 800 to the upside, 775 to the downside. So I caught a piece to the upside and we shorted Tesla to the downside. I thought there was a shot, I thought there was a shot I could get to 665. The reason why, if you look at Tesla, the five-day moving average was 665, right? Excuse me, 765, it actually traded down to 762. I like to pivot there for tomorrow. So good moves. I mean, definitely, definitely good moves to both sides. Netflix, again, here was the build, went to 431. Again, bingo, right, to 65. And then I said later in the day, there were two pivots on Tesla later in the day. I'll show you the second one that triggered 788, 789 never did, but there was actually a pivot back to the upside a little late in the day. And again, look, here's 431 to 32 needs to reclaim more. Here is the pivot towards the end of the day. This is right, I didn't take the last pivot. I know some of you guys did. This is a decent cash flow move here. 781.50, 781.50, 782 needs to build to wake up. And again, here's the last pivot of the day. So here's the 782 right over here. So 782 right here. You see that guys, 781.50, 782. And it went right to the next supply zone of 786. So if you did catch that last move, good job, congratulations. So going into tomorrow's session, you know, I kind of a mixed bag. I'm not in love with anything tomorrow. I do think there is going to be some value on some names. Again, you gotta do some research guys. Going to NASDAQ 100 on the Qs, go through your charts. There are two very, very specific charts that are sitting there right on support. And if they confirm support, they're gonna get hit. Again, it doesn't take a lot of effort, folks. Okay, you have to put in the time, you can go through the NASDAQ 100, five minutes. Okay, you'll clearly see there's two names that are sticking out like sore thumbs, and that's what's gonna be the value. So guys, have a great night everybody. God bless, and I will see you all tomorrow. Take care guys. Congratulations for putting in the time to take control of your trading. You're one step closer to owning your future and achieving the success you desire. Want daily trade ideas directly from Dan? Straight off his personal watch list? Unlock our free PS60 vault where you'll get nightly updates on pivot opportunities we're watching for the next day's session. Click the link in the description to get started today.


Hello everyone, welcome back to the iPhone video slash iOS 17 video. I'm in the final beta. I want to show you how to work with the mental health and mood functionality now built into the health app. Here we go. So I'm on my home screen. I'm going to click on the health app right here. And when I do that, you'll see stuff that you've seen before, but watch this. If I go down here to the bottom and click on browse, you're going to see a few things. And one of them is mental well-being. I'm going to click on that. And now you're going to see here up at the top that I had a neutral moment earlier. So I logged a moment a little while ago. But if I want to go ahead and let's say add my current mood or emotion, I can click on state of mind here. And now look at this, I can go ahead and click on this log button. And now I can explain, I can tell the iOS or I can tell my phone, so to speak, or Apple, however you want to look at it, how I feel right now, which is my current emotion. And I can also say how I felt overall today. So my last check-in was, I guess a little while ago, they're not too long ago about how I feel right now, but watch this.  And I'm going to go ahead and use this slider. And today I've had an okay day, but I'll show you the different styles. So if you can go from very pleasant all the way down to very unpleasant. And yes, hopefully it doesn't alert the authorities either way, but I'm going to go with something like this. I'm going to go with pleasant. So I've had a pleasant mood today. I'll click on next. And then I can go ahead and, well, oops, I hit the button there. I've been confident today. You can just go ahead and play around with this, but this is how you track your moods and your emotions. I'm going to go self-care, something like that. Click on done and presto. I've logged my mood. So you can go ahead and log your moods and emotions over time. I can click on that again. I can also click on how I feel right now, click on next. And now this is how I'm feeling in this exact moment. So right now I'm going to go with very pleasant. Why not? Click on next. And I feel surprised. Why not? I'm just showing you the examples. And you'll see here I am logging my mental health and I can check this through charts over time. So I just started doing it now, but over time these charts would work. So there you go. That's how you use it inside iOS 17. Thanks for watching.


Hey, hello everybody and welcome back to the Think Tech Hawaii studio for another episode of security matters. I have four amazing guests with me today. Aaron man is with us from a lead John she'll be talking on behalf of the Security Industry Association's rise organization. Linda said from GSA schedules is with me she will be talking from see a board of directors as well as our women's committee. Malcolm Reed is with us from Bryson LLC. He brings the perspective from the board of directors of as is, and Dave Corbin is with us from the Broad Institute at MIT and Harvard, and he will be bringing us as his connects perspective and some of the other work from the as is diversity equity and inclusivity committee. Please go to their LinkedIn. I'm not going to give them the time today to go sort of introduce and give their history like I normally do since we've got a major discussion with us and not a lot of time. With that, we're going to get it started and Aaron I'll let you start off with, let's talk about rise. Let's look talk about diversity and sort of what role do you believe rise can play in helping the industry focus and become one of the more diverse industry so we can attract new talent. I am really excited to be here representing rise today and just to kind of talk about some of our initiatives we are really excited just about the trajectory that our group has had in the last five six years since it's been around. I've been involved for the past year and a half, and I've seen the group grow astronomically so in the last year we actually expanded our user base by 200% so we have over 800 young professionals who are in the security industry globally who are part of our rise community. And so knowing that we have such a broad reach we are actively working on a lot of initiatives to help empower these individuals build their network full of cheerleaders and dynamic other leaders in the industry to really promote the security industry as a place where young talent can go to not only grow their careers but be developed foster their careers up skill and kind of grow on that really awesome trajectory that the security industry has. And so we've got some really awesome initiatives happening right now. We have a scholarship that we're actually will be announcing winners in the next couple weeks or so. In 2018 for that scholarship we had six applicants in 2019 for the scholarship we had 19 this year we had 46 applicants from six countries. And so we're seeing a lot more representation from the global security industry really kind of getting interested in how young professionals can play into what the industry is going to look like a year from now five years from now and 10 years from now. And so we are actively kind of promoting different webinars and content. We have a diversity and inclusion subcommittee that's about to announce a really amazing opportunity for industry professionals at every level. And we're just looking at the ways that we can bring young talents into the industry faster than make them feel like they belong they have the experience and learning and the right to be at the table that they're at. And give them the tools to build their network and really kind of empower them to take on these issues as we continue because diversity and inclusion is an ongoing initiative not going to be solved in a year. And so the work that we're starting today is hopefully going to be some of the work that we're capitalizing capitalizing on when we're leaders tomorrow. That's awesome. Thanks. Thanks for the leadership and thanks for you know promoting this within rise I mean we're going to need all of these voices from every angle come at it so it's awesome that rises so engaged and I think I think when they've outgrown our WISF group if they've got 800 already but what do you what's the perspective of the sea aboard I know that they put together this joint effort along with as is it's going to happen on Thursday December 10. But you know from an industry perspective you know what do you think see as role can be and you know what can our women's security form do to help promote diversity and inclusivity through the industry. Well you know obviously diversity equity and inclusivity is a big issue and I'm really proud of the collaboration that she is doing with as is and all of our groups. You know within the organizations you see that you know we spread out it's touching the various groups within our organizations that focus on this. I'm really proud of see a different from most industry you know we have 40% females on our board of directors. And so that's you know that's like six of 15 voting members and even our executive committee is two thirds female. So you know we're really reaching out there to make that effort and again with our committee groups you know and this is something for other organizations to think of our committee chairs are many women committee chairs you know in our organization. So you know within the various committees course rise Aaron has just explained that to you but you know the women and security forum has been very active. And one of the initiatives that we put out there you know to include you know our young people we've created an adopt a college program where members and other see a staff will reach out to colleges and participate. In virtual days where you know for educational opportunities and job opportunities and we've already begun engaging even though we just launched it with Penn State UVA local community colleges. Historically black colleges including Bowie State which is near Annapolis where where I am. And in addition to that we launched a scholarship program this year which you know about Andrew this was very successful. It was amazing the way industry contributed and supported this. We were able to provide scholarships to 12 individuals from various backgrounds in work. So that that was absolutely amazing that we got that together this year. And then of course one of the more recent things that the women in security form announced was the formation of a see a speakers bureau. And so you know the women in security form have put this forward we're looking for people to sign up to help cultivate women in industry and in the role of leadership of course and and you know many other aspects of diversity and inclusivity. That we are reaching out to do with our organizations. It's awesome. Yeah I I was an early proponent of I was talking to the event organizers about these mammals you know every every conference I would go to every speakers a guy I'm like really can we just make it mandatory you have to have you know equal numbers of men and women are or you know let's let's create like if people see it different it'll become different right anyway. Welcome from the from the board chair at as is I mean this is a major initiative I know you're very active with the diversity inclusive initiative there. Let's talk about diversity from as his perspective you know they've got such a global influence in the industry you know what what do they look into competition how can we how can we support it. But first of all Andrew thank you very much for having me on your on your program. It's a pleasure to be here as well to contribute to the other professionals as well from the ASIS perspective. ASIS is a global organization. So we have just what 34,000 plus members across the globe. And by that very definition is very diverse. You have people from different countries, male, female different nationalities as well. ASIS is looking to expand that diversity. There's an opportunity right now in this space to expand the whole thought process behind what what is the ENI what is diversity equity and inclusion and what it means to the industry, the security industry is something that is continually growing as more as the world gets involved with more risk is more risk involved in technology is more risk involved in natural and man made disasters. The security professionals role is much more important as we move forward in today's world. And that's why we need different perspectives. From from our perspective at that ASIS, we have a woman in security council, we have a young professional council, but we wanted to to tap into that and grow further into embracing the ENI which is even a bigger conversation and just those two groups only was incorporating those two groups and reaching much more underrepresented communities. I always tell people, if you had someone on your board of directors who grew up in a single parent home and or who had less resources than the average person, and they were able to get to sit next to you in a board room. You want that person on your team, because that person can work with less resources and accomplish much, much more. So the ENI is it's a no brainer, you know, it's a no brainer to the many organizations but for us at ASIS, it's an opportunity to reach more members to incorporate their views and to keep the world. We want to keep the world a safer place, essentially. Yeah, and I think I do agree, you know, more voices is is how we do that right we don't want to exclude a voice that could have a solution to save the life I've been a been a proponent of that sort of idea. So, David, you're you're heading the DNI committee I suppose for for as is as well as I think running the connects program or contributing to the content there. What from your perspective, you know what's what's the role as this can play and what what sort of sort of leadership are we looking to accomplish, you know, with with the DNI program you know what can we, how do we engage our industry partners to help us you know the manufacturers and integrators. To clarify I'm not leading the DNI group that's being led at the very top levels of ASIS with the president ASIS and the and also the CEO of ASIS and one thing I will say is that ASIS has done a great job in backing up their, you know, initial statement that they made around diversity equity inclusion and their commitment to that. And, you know, shortly after that statement came out in support of the community in support of diversity equity inclusion within the organization. They did form the diversity equity inclusion task force which I mentioned is is headed by the top levels of ASIS and includes people from both ASIS headquarters and you know the membership in the board. Welcome and I have both on that task force. So, it's going to be a long term strategy. And I know that there is a long term commitment from ASIS to the diversity equity inclusion work, but it's not something that's going to, you know, get resolved in the next year it's something that has to be an ongoing conversation and ongoing work. And I think that the program coming up on Thursday is really a big first step in that in engaging the community the security community in this, this discussion around diversity equity inclusion and getting the different perspectives and hearing about people's challenges. And that takes me to that to the connects platform which is ASIS connects and that is you know anybody who's a member has access to that community and there is a new diversity equity inclusion community. You can go into the connects link which is right at the top of the membership screen, and you search out that community and right now there's about 105 people signed up from 21 different nations so it's not just you know if you're in the US. It's not just talking to people from the US if you're in, you know, wherever you are you're getting the perspective of people from 21 different nations which is very unique and, you know, Malcolm and I were talking yesterday about if you went on LinkedIn, and you had that conversation you might not have that level of diversity and I would say that level of safety around knowing that your, your conversation is is probably going to be more supportive and less likely to have, you know, some issues with the people who you're interacting with It's a safe space to talk about this, this topic, and to start getting as I like to say getting comfortable with having uncomfortable conversations, but if you go on there right now people are posting different resources asking questions. Everybody is struggling with the same issue so it's a great place to get on there and speak with your fellow colleagues about this issue and to get ideas and into exchange ideas and start conversations. And my understanding is that's open to everyone in our community it's not limited to current as his membership. Oh, you're right. You're correct. Yeah. Okay. That's awesome. So, so definitely check that out as is what connects website and you know join that community and get engaged with the conversation. So let's get into this. This one's a little interesting to me this discussion of equity, you know, equity equity to me obviously means that the opportunities are there for the same sort of earnings the opportunity there for the same types of appointments within an organization. And there's obviously a massive lack of equity across not just the security industry but globally and a lot of companies right there they're working on this. So I know you've talked a bit about some of these metrics and some some experiences that you've actually had yourself. You want to kick us off with a little bit of little understanding of the, maybe the inequity that's out there that we're going to try to mount an effort against. Thank you Andrew. And there's so much data on this information and it's, it's a tremendous amount of information to support what we're seeing here. So what we've seen from like the Department of Labor statistics from the government. We've seen that the inequity in terms of gender and and for race as well. So, for example, and that leads into the topics such as intersectionality, where someone can, can be both female and a person of color. And we've seen that they that person would make much less significantly less and then someone from a majority. And that's where organizations such as, you know, McKinsey and company and they're looking at ways in which diversity can really help companies become more profitable. And that's, that's the connection there. So now it's not just looking at, you know, salary ranges and that there is great inequity there, but how can, how can we tap into that rich diverse workforce that's out there. I'll say this because this in the public domain. A lot of a major company recently said, hey, I can't find talent from a particular group to get into the management. And there was a blowback on what he said, a big company here in the huge company. And I can't find any, but, but that's incorrect. There's so many talented people, but somehow that there's inequity in that recruitment and selection system as well. Because people are not being able to, to capture these opportunities, these opportunities are set cause you know people seem to communicate they feel comfortable with people who are like them. And that's in the turns that implicit, implicit bias and all these other things in the, and I, these things really affect person earning potential.  And you can do the research yourself how many CEOs on the 14500 are people of color. How many CEOs are women? Not many. And there's a reason for that. It's because we need to start shifting our mindset and start embracing our differences and realizing that as, as the, the team for 2020 for ASIS against what we are stronger together. And I think that team goes into our, the ENI team as well, but there is salary, there's a huge difference and you can go across, goes across race and gender and when I run race and gender intersects the effect and the effect on that is much greater on the individuals that would make, for example, I believe a black female makes 58 cents on the dollar for, you know, against a white male. So that, that's a significant, it affects their earning potentials affects what they can do for their families as well. Yeah, so hopefully we'll be able to teach our companies Lynn, you work with a lot of companies from our industry are what's your perspective on that, you know, the folks that you tend to deal with at the tops of these organizations are they open to promote in are they are they comfortable sitting and doing the things they've always done.  It's rare and when I started, you know, I was among very few women in a totally male dominated industry, but I think awareness is crucial.  Okay. And I was working for different companies that were struggling during a time, you know, where there was some economic issues. I kept getting laid off so I started my own company. And fortunately for me I started it in the security industry, where my male allies lifted me up and supported me recognizing that I was a good multitasker and I could get it done. And so, you know, in my role on the sea of board of directors and in working with women in security form. I have found so many people who are really willing to embrace this and encourage it. And I'm amazed at the growth. We've had in this area just in the last year. You know, it's, it's, it's really, gosh, I wish it would have happened 30 years ago, but still really thrilled to be part of it and very encouraged by the young professionals in the ASIS group, and as well as rise and see it because it's we have to do it. I think we're really taking a leadership role here with the security industry, and it's got to go beyond this.   There you go. That's, that's what we're doing today. This is our ask out there people if you're watching, we want your help. Hey Aaron in the rise community. What's the feeling, you know, equity? Is it, is there an equitable opportunity for young professionals to move in our industry? Do they feel, you know, motivated? Do they feel that they'll be rewarded? Is there work to do there? I think, so based on my experience, I think it's gotten better in the four and a half years that I've been part of the industry. I think that young professionals are consistently proving themselves to be mature leaders who actually can be trusted with business responsibilities and they're being hired and trusted and being able to economically do their job. What I don't see yet is a ton of young people in major leadership positions within their organization, but I think that there's the trajectory in place for that to happen. And I think that's why groups like RISE or the ASIS Young Professionals Group are so important and impactful because there's a lot of learning and growth to happen as you're going through your career. And we want to earn that feat at the table. We want to diminish the fears of a young person who might have the merit to move into that position, but doesn't necessarily have the tenure or the experience. And I think that's where talent development and professional development really comes into play because we have this unique opportunity to connect people with industry professionals who have been in the industry for 30 plus years. And in some cases, that's longer than some of us have been alive, which is such a unique opportunity because, you know, why would you stay in an industry for that long if it didn't offer you incredible opportunities? It didn't give you a network. It didn't give you a job that was fulfilling and rewarding. And so to be able to help kind of foster that sense of community, give young professionals a place to kind of forge their own path, connect them with individuals who have done that, who have built the industry, who are the foundation of the industry, and then really empower ourselves to go and push the industry into the next few years is really crucial to diversity and inclusion. And especially, I think the status something like 55% of millennials are always looking for a new job. And if their companies or their organizations or their industry doesn't offer them professional development opportunities it doesn't offer them growth and and kind of networking opportunities. That's a pillar of what they look for in their ideal organization. So we're going to start having a talent problem. If we don't tackle these issues, if we don't give everyone trust in autonomy, if we don't have diversity and inclusion strategies, we're going to start losing candidates who have skills that we need. And it's really, really fascinating because suddenly the security industry isn't sourcing talent just from security vocational kind of programs. We're sourcing talent from a plethora of different pawns where that talent can easily go to a different industry. We're sourcing cyber security and tech and innovation and design and storytelling and marketing, and these skills are so applicable elsewhere as well. So if we don't have kind of a really amazing trajectory for young talent, if we don't have the right programs in place, if we're not empowering people if we're giving them that the table that they're at is where they deserve to be. They have the right and the experience and the knowledge to be there and giving them decision making power and giving them the opportunity to mentor other individuals and giving them the opportunity to be mentored by individuals. The security industry is going to face them hard times, but that's why it's so fun to be part of a group like rise and kind of participate in some of these broader industry initiatives. We really are being given a voice and kind of like what Lynn said, the security industry is a leader in that. And we're just really excited to have a seat at the table and play a role and really kind of help promote this as a pillar of the foundation of the industry. That's awesome. Yeah, I 100% agree. You know that we're going to have to have it coming from all angles. Dave, is there a perspective out of the task force to build a playbook or to get some instruction for companies that are maybe struggling with doing this type of work internally? Are there some models out there that people can sort of look at? Or is there thoughts of building some models? I mean, as this has been a great trainer of industry for probably since its inception, you know, is there that kind of speaking there? Or are there questions like that that maybe come up in Connect like from owners who's like, I don't know how to build this program. I don't know what to do. How do we help those folks get engaged? Well, there's certainly in Connects I've seen a lot of conversations, people asking for help building the diversity equity inclusion programs, but also giving some examples of what they've done so there's some resources in that regard. So conversations in the task force, it's certainly one of the products I think that the task force would like to deliver some point. I don't know when or what that would look like, but I think ultimately the goal, one of the goals is to provide resources to the membership in order to really tackle this issue. So I can't say that there'll be a guide coming out in the next six months, but I think that certainly that'll be one of the things that comes out at some point down the line in some form. The task force is in its infancy still and we're really gathering, we're in the information gathering process and trying to understand how we can best serve membership in this regard. So like I said, we're playing the long game and but I think you'll see some great resources coming out many different types of resources coming out of the task force and in the months and years to come. Yeah, I love it that we have a global community to draw from that should give us ideas that can appeal to everyone you know at whatever level they're at. We're, we've got a couple of minutes left so I want to get to inclusivity our good industry friend who left our industry actually Chelsea render told me once that you know diversity was getting invited to the dance hall but inclusivity was getting invited out onto the floor to dance right and that always sort of stuck with me. So maybe we'll go around again and then we'll start with you. Just your perspective on on inclusivity and how can we open ourselves 360 degrees to be as inclusive as possible. Well, one thing that I wanted to mention was an initiative that she has related to addressing technical papers. Okay, and rewriting some of the language in there that refers to gender, you know, etc. And this is initiative that Joe Gittens from see is working on but obviously this, you know, other companies have done this I think this is something that we should encourage in the industry from our leadership from our manufacturers etc. You know as we put together these things we need to rethink this a little bit and change our language. So that's something that we could do. We have to get the bias out of the language. Malcolm your thoughts. So, yeah, for me. Essentially, the research has shown like for example Harvard Business Review. They did a study and it said that essentially that diversity by itself does not increase organizational effectiveness. Right, but it's how organizations harness that diversity, and by harnessing that diversity, we're listening to the voices and bringing the differences of people together to the table. And that's where you're making it inclusive. And by and when that happens, you get leadership. You don't have, you don't have inclusivity unless there is leadership, you know, from different groups and stuff like that. So if you have people in your company is diverse. That's not that you have to have leaders in your company at your board level at your executive level management level, who are diverse. And that's when you start bringing that voice to make a decision, a decision making voice, then you're being inclusive. I'm listening to you. You're not just standing in the room. I'm actually listening to you. When I listen to you and your voice is heard, you know, so that's so important. And I think moving forward in our industry, that's what we need to tap into bringing those voices young people, women, people of color, other groups as well. When they're represented, represented groups, bring them to the table, listen to their voice and get them to affect strategic decision in a company or organization. Perfect Dave final thoughts, inclusivity. Yeah, I'll echo it Malcolm said to a point in that you know you can have diversity without inclusion, and it's important that you know you have the right people have have a seat at the table. And also, you know, having a way to not only mentor people but to sponsor them and sponsorship is different than mentorship sponsorship is helping open doors for people sponsorship is is more than just hey this is how I did it it's it's, I'm going to open doors for you I'm going to introduce you to the right people.  Right. So, you know organizations have to look from the top down. This is not a flash in the pan issue this is a long term issue. And it's not new.  And people are having those difficult conversations but I think that having the conversations is a huge first step, even when they're really uncomfortable which they are. But having those conversations is was one of the first steps in, in, in, you know, looking under the surface and identifying the issues that that are in the way of diversity and inclusion. Awesome Aaron I'll let you close this out with your thoughts are the young professionals included. Are you getting enough time on the podium and at the table. We're pretty fortunate at least from the rise perspective and a lot of my peers who are young professionals in the industry share the fact that we are being given a seat at the table and it's, it's really wonderful to be invited, and, and kind of acknowledged as a voice and a perspective that that is important to building this strategy. And I think that that that is kind of what inclusivity and really is when it comes down to it it's, you know, every person has unique experiences has unique perspective. They were brought up in different environments and those perspectives and experiences shape the way that they see the world and security is one of those universal experiences that we hope everyone has, but we don't have all those experiences to know what's needed to shape their spaces to deliver technology that can be used by every person. And so to be able to be part of the conversation, have our, have our kind of our perspectives heard.  The presentation really matters when people are considering what they want to do long term. And in some cases breaking glass ceiling is really phenomenal, but it would be even better and even safer if there weren't any more glass ceilings to break. And so I think that we are being given a seat at the table. But we'd like the table to expand and we'd like to pull up a couple more people and we'd like to have sit down and have a meal together because I think that I think that's what's next and I think the event on Thursday is a really awesome step in that direction. Awesome. Thank you. Aaron Dave Malcolm and thank you all very much for joining me today. The big event we're talking about as is here co sponsoring a diversity equity inclusivity event on Thursday just Google that up, sign up, be a part of the conversation. This is our ask. If you're listening today, we need your voice and we appreciate it. Thanks everybody. I appreciate you again for being here today. Aloha and take care.