Egyptian Mao vs. Asakat. What are the differences between these two cat breeds? The Mao's most striking characteristic is his spotted coat in silver, bronze, or smoke, closely followed by his large gooseberry green eyes.  With hind legs slightly longer than the front legs, he gives the appearance of standing on tiptoe on his small, dainty feet. A medium-long tail is thick at the base, tapering slightly at the end. The medium-length coat has a silky, fine texture in the smoke coloration and a dense, resilient texture in the silver and bronze colors. The body is covered randomly with distinct spots that can be small or large, and round, oblong, or other shapes. The forehead bears an M shape, the cheeks are adorned with mascara lines, and the tail is banded, ending with a dark tip. On the pale belly are dark spots that resemble vest buttons. In addition to the silver, bronze, and smoke colors, mouse can come in solid black, blue-silver, blue-spotted, blue-smoke, and solid blue but these colors are not permitted in the show ring. These cats of a different color make fine pets, however, sharing all the other characteristics of the mouse. Ossacat stands out for his spotted coat, which gives him the look of a small wildcat. The short, smooth, satiny coat comes in 12 colors, all of which feature dark thumbprint-shaped spots on a light background. Like the Abyssinian, which was one of his ancestors, the Ossacat has what's called an agouti coat, meaning that each hair has several bands of color. The exception is the tip of the tail. The spots are formed where those bands of color meet. Rose of round spots run along the spine, and more spots are scattered across the shoulders and rear end, extending down the legs. Broken bracelets of spots encircle the legs and broken necklaces adorn the throat. Large, well-scattered spots appear on the side of the body and on the belly. The tail has what looks like horizontal brushstrokes going round it, sometimes alternating with spots. Markings around the eyes and on the cheeks make the Ossacat look as if he has been at work with a mascara tube. The forehead is marked with an M and small spots cover the lower neck and shoulders. Some Ossacats have classic, macrolintic tabby coats, which are beautiful but aren't correct for the show ring. Those cats have the same great Ossacat personality, however, and make wonderful pets. The Ossacat has a medium size to large body. He is muscular yet graceful. Large ears corner the modified wedge-shaped head. Some Ossacats have tufts of fur that extend vertically from the tips of the ears. Large almond-shaped eyes angle slightly upward and can be any color except blue. The lengthy tail has a dark tip. When the Egyptian Mao is happy, you know it. He vocalizes, called chortling, in a quiet, pleasant voice, swishes his tail rapidly, and needs with his front paws. What makes him happy is being with his family, to whom he is fiercely devoted, or showing off his hunting prowess by chasing and retrieving a toss toy or stalking and pouncing on a wriggling lure at the end of a fishing pole toy. This is a moderately to highly active cat. He likes to jump and climb and will appreciate a tall cat tree, a window perch or two, and a sturdy scratching post that allows him to stretch out to full height. The Mao also enjoys playing in the water. Don't be surprised to find him dipping a paw into your koi pond or aquarium, turning on the tap in the bathroom or kitchen, or splashing water out of your pool, or his water dish. Egyptian Mao prefers family members to anyone else.  The Mao has the distinction of being the fastest domestic house cat, as she can run at speeds of up to 30 miles per hour. The devoted and playful Asakat loves people and will trail their footsteps through the house or ride on a shoulder. Guests are welcomed by this generally social cat as new opportunities for petting or lap sitting. Oshi cats don't even mind being carried around as long as they are with you. As with any animal, they come in a range of personalities, so some are shyer than others. Favored activities include retrieving toys and learning to walk on a leash. Oshi cats are highly intelligent and learn tricks easily. Puzzle toys are a good way to keep them occupied and entertained. Carefully put away anything you don't want him to have. He is perfectly capable of figuring out how to open doors or undo latches. His Siamese ancestors bequeathed the Asakat a tendency to be vocal, but he is not as loud or as demanding. He is sensitive and will respond to nothing more than a verbal correction. Although the Asakat is adaptable, he doesn't like being left alone. Be sure he has another cat or dog as a companion if you aren't home during the day. Hello. This video is sponsored by Beemix Pets. Are you looking for high quality cat collars at an affordable cost? Check out beemixpets.com. Use coupon code KittenLife, to get 20% off. Both pedigreed cats and mixed breed cats have varying incidences of health problems that may be genetic in nature. Egyptian mouse are generally healthy, but be sure to ask a breeder about the incidence of health problems in her lines and what testing has been done for any that are genetic in nature. Oshi cats are generally healthy, but they have the potential to develop certain health problems. Progressive retinolatrophy, which leads to blindness, has been seen in a few cats in the breed, but it is not thought to be a major problem. Samoshi cats have also been diagnosed with hypertrophic cardiomyopathy, the most common form of heart disease in cats. Their Siamese and Abyssinian heritage may also predispose them to renal or liver amyloidosis and early periodontal disease. The Egyptian mouse coat is easily cared for with weakly combing to remove dead hair and distribute skin oils. A bath is rarely necessary. The Oshi cats short, smooth coat is simple to groom with weakly brushing or combing to remove dead hairs. A bath is rarely necessary. Brush the teeth to prevent periodontal disease. Daily dental hygiene is best, but weakly brushing is better than nothing. Trim the nails weakly. Wipe the corners of the eyes with a soft, damp cloth to remove any discharge. Use a separate area of the cloth for each eye so you don't run the risk of spreading any infection. Check the ears weakly. If they look dirty, wipe them out with a cotton ball or soft damp cloth moistened with a 50 to 50 mixture of cider vinegar and warm water. Avoid using cotton swabs, which can damage the interior of the ear. Keep the litter box spotlessly clean. Cats are very particular about bathroom hygiene. It's a good idea to keep an Egyptian mouse and an Oshi cat as an indoor only cat to protect them from diseases spread by other cats, attacks by dogs or coyotes, and the other dangers that face cats who go outdoors, such as being hit by a car. Mouse and Oshi cats who go outdoors also run the risk of being stolen by someone who would like to have such an unusual cat without paying for it. The active and playful Mao is a perfect choice for families with children and cat-friendly dogs. He will play fetch as well as any retriever, learns tricks easily, and loves the attention he receives from children who treat him politely and with respect.  Nothing scares him, certainly not dogs, and he will happily make friends with them if they don't give him any trouble. He is a skilled hunter, however, and pet birds or other small animals are probably not safe in his presence. The gentle and playful Oshi cat is well-suited to life with families with children and cat-friendly dogs. He can learn tricks and enjoys interactive toys and loves the attention he receives from children who treat him politely and with respect. Supervise young children and show them how to pet the cat nicely. Instead of holding or carrying the cat, have them sit on the floor and pet him. It's likely that the Oshi cat will dominate other cats in the household and may even rule the dogs. Always introduce any pets, even other cats slowly and in a controlled setting. If you enjoyed this video, kindly press the like button. Also don't forget to subscribe with notifications on so that you don't miss out on videos like this. Thank you for watching.


Good morning everybody, it's good to see you. We're going to get straight into our next session. Mikos Kaspar, he's the head of digital media over at the International Atomic Energy Agency and he's going to be talking about reading beyond core audiences. Without further much ado, Mikos, the stage is yours. Thank you and good morning. Got some slides that we'll hopefully come up in a second. So thank you for the introduction. I'm head of digital communications at the International Atomic Energy Agency which is a UN organization dealing with all things nuclear. That is ranging from ensuring that nuclear technology is not going to be converted from peaceful use to making weapons and then also promoting the peaceful use of nuclear technology around the world. Now, to many people, let's face it, nuclear is not very sexy. Some of my colleagues on the panels yesterday from the UN spoke about children, refugees, environments. These are things that actually many people care about. Nuclear, on the other hand, is a technical topic. Some people like it, some people perhaps are against it, but for the vast majority they are in the middle, they don't care. They are not aware of all the potential of nuclear. So my job as a communicator at a nuclear organization is to reach these people, reach beyond people who already care about our subject and talk to them, make them see all the potential and the contributions of nuclear to our lives. So how do we do that? That's what I talk about. So at the IA, just like in so many other organizations, digital has become the primary source, the primary method of communication. I spoke about this on a digital panel yesterday. If you were not here and are interested in this topic, please watch the recording. So we reach about 6 million people a month, which is about five times as many as we did a few years ago, by a website and then our social media channels, some of which are displayed here. So to do that, to catch, grab and keep the attention of people who are not, perhaps at the outset, are interested in your topic, you need to be innovative in terms of content creation and also distribution mechanisms. So what does that mean? Well, first of all, gone are the days when people would leisurely browse the internet and end up on your website. There are two ways to get them to your website, really. One is via search engines and the other one is via social media. So here, I'm showing you the results of something we put a lot of emphasis onto, which is search engine optimization. We make sure that our website is search engine optimized, in fact, hyper-search engine optimized, both in terms of the content, so that we repeat main words that people would be looking for, main words in the story throughout, and then also we make sure that we are compatible with the evolving algorithm of Google and other search engines. So a result we have achieved through this is displayed here. Not sure if you guys know, but PCR, which has become a household name over the last few years, is actually a nuclear derived technology. And we at the IEA have been helping countries for decades to use PCR to detect viruses. So when the pandemic started, we produced this article to explain how PCR, or actually correctly called RT-PCR works, using nuclear DR techniques. And this is a search engine optimized article that has gotten us 1.3 million new visitors over this last period. So if you search for RT-PCR in Google, we'll be the first find. If you just search for PCR, well, depending on where you are in the world, we will still be among the top five.  They also have to then engage with your content. So it's not enough to optimize for search engines. You also have to optimize for your visitors. So that's what we've done here with these articles. We've recently launched a series called Nuclear Explained, where we use simple terminology and easy to understand content creation to make stories interesting and understandable for a general public who doesn't necessarily care about technical details. So I'm showing you some examples of this. We also have infographics, videos embedded into these stories. These stories are also evergreen, meaning they don't become outdated. Therefore, if people search for them in six months or in a few years, they will still find them relevant. So how do we do that? Here's an example of a piece of content that we use both on our website and on our social media channels. This is to compare nuclear energy with other sources of energy. So you see on the left-hand side, and this is the Instagram optimized version, we show how much electricity an average person in the world needs in their life. And then we show underneath, and I've magnified that on the right-hand side below, how much fuel, various kinds of fuels you would need to generate that amount of electricity. So from uranium fuel, which is what nuclear uses, you just need one X-worth of fuel to produce the electricity each of you would need in your whole lives. Versus if you use coal, you actually need 21 elephants' weights worth of coal to produce the same amount of electricity. Similarly, another simple drawing or illustration that I'm showing you here is above the elephant, which shows you how nuclear technology can be compatible and actually complementary with renewables. So nuclear technology, which I'm not sure if you're aware, actually already today generates over a quarter of all low-carbon electricity in the world, could complement renewables, for instance, solar, so that during the day when the sun shines, the nuclear power plant would produce electricity at a lower rate, and that at night, when there's no sun, it would produce a lot more. That's what you see on a very simple graphic on the top of the slide. So oops, I jumped too many. Don't watch. Okay, now watch. So these are examples of social media-optimized content. Unfortunately, they are not displaying very well here. I'm a digital guy, so I've tried to show here some slides that move and do all kinds of things. We were not compatible with the technology here, so you don't see those wind turbines moving, and here they're supposed to have an airplane flying in at the bottom showing you how even air fuel could be made more efficient using nuclear technology. So these are examples of social media-optimized content. Yesterday, at the digital talk, we discussed how the attention span of people is shrinking and shrinking. Therefore, in order to get your message across, you also have to be shorter and shorter. So these are really sound bites and images that get across the main message very quickly. So it's an old story that people use digital-first content strategy. These days, we now use social media-first content strategy. So what does that mean? I'd like to show that to you with an example. The article you see on the left, it's an article from a website explaining how you can use nuclear technology to detect food fraud. Food fraud is like fake food, and you can do that by analyzing the isotopic composition of the food. The article here describes how Slovenian researchers have used this technology to identify fake truffle. Truffle is a kind of mushroom that's actually the most expensive food on the world by weight. It costs up to $200,000 a kilo. So I'm sure we're not going to get that for lunch today. In the middle, I'm showing you how we would have tweeted this article a few years ago. We would have taken the same image and just a variation of the lead and would have put it on Twitter. For a new story like this, we could have expected perhaps 10,000 people to then click on it and read our story. What we do these days when we have time is what you see on the right-hand side of the slide. We create a social media-optimized image. Again, in this case, it should be moving, which it's not. And a more social media-optimized text. So this is more catchy for the audience. On the next slide, which again you won't be able to enjoy because this should be moving, it's an Instagram story with GIFs. We created a quiz and other interpretation of this same article. So the same content presented in social media, in different social media-optimized ways, would now get us 10 to 20 times as many visitors as the old one would have done a year or so ago. So another example is for this article. This article is about using nuclear technology to produce improved varieties in this case of cotton in Pakistan. By the way, that cotton does not become radioactive. And so I'm showing you on the left the website article that we had and then on the right an Instagram post, sorry, in the middle an Instagram post, and further to the right an Instagram story, which again should be moving, but it's not. So same content optimized to the medium. And here is an experiment that we have run using this article on Twitter. On the left, you see this article promoted using a photo that we received from our counterparts, scientists in Pakistan, who applied this technology. It got only two retweets, so basically zero engagement. We've then looked for another photo, switched it out, and we got 47 retweets. For a niche story like this, which is very scientific, that's a very good number. Speaking of engagement, here is another type of content that I wanted to show you that we use to call for action. Social media is not just about us talking to people, but it's also people engaging with our content. So one way to do that is when we ask them a question. Here the question is, nuclear power is filling the gap energy. As I said before, nuclear power generates over a quarter of the low-carb electricity that we have in the world today. And just thanks to this very simple post, we got 150 new followers on Instagram. Another example of engagement is this post, which is a quiz. It's a quiz that we posted on the birthday of Marie Curie. Marie Curie is the only person who received Nobel Prizes in two different scientific fields in physics and chemistry. We covered many of the radioactive elements that perhaps you've all learned about in the periodic table in your school. So it's a quiz about her. It's also an example of what we call non-promotional content. We want to make sure that we don't just post content that's about the IA. You know, that would be like propaganda, it could be perceived by D-plus propaganda. So therefore, we also produce about a third of our content which what we call is non-promotional. It's still about nuclear, but it's not about the IA. So this is an example of this, this quiz on Marie Curie. You see, I've got the answers colored on the first two questions. You can try your luck or test your knowledge on the third. Just go to Instagram if you have a profile, look for IA work, and then try to answer that last question there. So far, I've talked mostly about content generation. Another pillar of the way we try to reach audiences beyond our core audience is by working with others and cross posting our posts. So really reaching other people's audiences. I'm showing you three examples of how we've done that on Twitter. Tweets we have created here run by the UN's main Twitter account, then by a social media influencer, and on the last example by UN Women. So this way, we get in front of people who may not know or perhaps not care about nuclear technology who are not aware of the many benefits that nuclear technology offers. I could have also shown you articles from our website that are picked up by others. For instance, some of our articles on agriculture are run also promoted by FAO, the Food and Agriculture Organization of the United Nations. This way, we get in front of policymakers and researchers, scientists in that domain who again, perhaps wouldn't have known that nuclear technology has so much to contribute when it comes to improving agriculture. So I've spoken about many things, there's a lot more to say, but if you're just going to remember three things from this presentation, remember to create engaging content, find cool and clever ways to distribute that content through your partners, and also don't forget that nuclear technology is cool. Thank you. Niklos, thank you so much, and really wonderful to have you here in person.


Caesar's entertainment has put out MLB's 2019 season win totals, so we're not gonna do everybody We'll do the Mets in the end. So these are over under? Over unders. They never go high with them. Mets 83 and a half. Really? Mm-hmm. I say over So you're gonna think do you think they're a winning team? Yeah, I do. So you go over 83 then Yeah, I think so bless you Peter. Thank you. I think I would go over Yankees 96 and a half That's that's a lot number As much as I love their team, and I think they're a playoff team the money tells you to go under right 97 wins Then you're flirting with back-to-back hundred win season. That's tough to do. What's what's the Red Sox number Red Sox number? It that's a good question 95 and a half So their numbers lower than the Yankees. Well, so they got the Yankees the favorite And is that the highest number 96 and a half? Gotta be right Astros are 97 and a half see I bet the under on all the Dodgers are 95 Indians are 91 and a half. Why would the Dodgers be three over what they won last year Red Sox 95 and a half? 96 and a half so the Astros have the highest now. You got to realize something here. This is complete Tonka truck Complete Tonka truck. We don't know what the team is. So if they get Machado's there's a good one or three and where Harper goes Harper goes to the Dodgers does the same you can bet it now though I mean you can make you can you get gamble on whether or not they're gonna get them. It's baseball Let's break it down. It's bait with breaking down baseball breaking down baseball You know what for all the big numbers Red Sox 95 and a half Yankees 96 and a half Astros 97 and a half. I bet under on all I think that's where the money is really let's look at the National League East Braves 84 they won the division last year 84 even 84 in the Mets are 83 and a half. Yeah Marlin 65 and a half Nationals 88 and a half Harper right and Who else we have so they've got the Nationals four more than the division champion from last year and the Phillies 83 Wow This is all Tonka so but right now the time to bet the odds tell you though that Harper's not going back to Washington And I and I get no, I think the odds now tell you you think so. Yeah at 88 God But they don't know that Harper is going back. No, so they're giving you 88 with Harper not there So Corbin makes them better than they were last year that much in possibly losing Harper They're still the favorites to win the division They also sign on Corbin and Robertson That's enough to make them win the division And the Braves they went and got down on the nationals winning the division the Braves four back Well, Philly's got Robertson. So you're saying Corbin. There's somebody else at the Nationals at it I don't know I Think it was this Corbin. No, there was one other player a significant player No, who the Phillies. Yeah, no Wait, didn't they sign a catcher? Hmm. Was it Kurt Suzuki? That wasn't significant. Well, no, no, there's not that's that's interesting man. Oh Annabelle Sanchez. That's not that's significant But so you think the Nationals are the best team in the division. I wrote a Brody Van Wagon is gonna be very upset I do. I think the national by four over the Braves Would the Braves had Braves at 84 Braves out of Donaldson And he figured the young kids will play you could play better. Oh, I like the Braves isn't over and You know, you like the Mets isn't over at 83 and a half You got like the Braves so they got the Mets third they have the Mets third I would I would take it over with the Braves and I would take it over with the Mets The Yankees I would leave that alone at 96 and a half again on the team. Yes But things have to go right when that's why people like whipping on Aaron Boone for them winning on your game Another team in your division at an otherworldly you know, so Vegas has the Astros is the best team in baseball. Yep Significantly so no one game better than the X. That's pretty significant when the Dodgers are at 95 Well, I don't get that Dodgers are a great team, but they won 92 games last year. What what makes you think they're gonna win three more What do they do? Well, because because they're gonna get some people saying Harper they can get Harper But that can't be factored into their over under because they're getting see her back Well, they think they lost Machado


Good morning, cyber traders, happy Wednesday. Good to see you, Mark. How's everybody doing? Excellent to see everybody this morning. Good to see you, Bob. Everybody at YouTube, Facebook, welcome back. Sorry about the little camera, hopefully that didn't hurt anybody. Good to see you, Lori. So anyway, Mark, it's dead. Mark, it is so dead. I know this is like the last Fed meeting until the end of the year.  It just shows you how powerful the Fed is and see how everything works out.  I told you, going into December, thinking of trying to do some type of swing trading is going to be quite difficult, trying to catch some of these, you know, opportunities. Maybe there's the rally, maybe it comes back, whatever it is, but just be very careful on your swing trades unless you got a really, really good deal on a stock that you like, that you always want to buy, whatever. But I don't really kind of do anything other than, you know, there's a couple of stocks that I have and just look at them into, you know, January. So, but day trading, obviously we had a couple of good stocks that made some big moves yesterday. Want to kind of talk, we'll talk a little about those and then we'll touch base and show you what's moving this morning. First of all, I'd like to start off at AMC. So, we talked a lot about AMC yesterday. AMC has been taking a very, very big hit. If you could watch at it, watch it, you know, listen, it was getting crushed in pre-market, and let me bring this up a little bit higher so you guys could see it. It came down and, you know, and then all of a sudden, look at the volume on the bottom, these volume bars. I mean, all of a sudden things just really took off, went from that $20 in, what is that, 50 cents, all the way up to 2440, and then you could see it right around that time when we kind of like don't really want to do too much around that time that stock started dying out. What time was that? That was around 10 o'clock, okay, and 1030, then pretty much it was kind of teetotottering. So, that one worked out pretty good for a lot of us, trading that AMC, and I know some of us chased it.  And good thing he covered it because he would have got really hit pretty hard. And, you know, it's very easy to take a small loss, it's very difficult to take a big loss. And remember, our biggest thing we teach you here, like I mentioned to you during the market hours, we don't teach you how to make money, we teach you how to stop losing it. Once you know how to learn to stop making, take care of those losers, the winners always take care of themselves. That's everyone's biggest issue. And he proved it yesterday, you know, with discipline, how to trade that one. Couple of stocks that are rolling in from yesterday, they're coming in again, they're gonna be in today's watch list. GRTX, so GRTX, if you look at that stock right there, stock had some pretty good volatility. You could see the stock got really beat up here on the long-term chart. Stock was literally down to $1.30, gapped up pretty big, up to the $2, had a little bit of a move, you know, not super, but you had to trade a lot of shares of it. You could see stock trade, 16 million shares. It right, as of right now, it is a gap fill, all right? So, and when we talked about this yesterday, resistance levels are right at six. Now, three to six are very big difference, but you know what happens, it's an uncharted territory, no one really owns at these prices, and that's what causes those big little run-ups. So that one's going back on the watch list. Another one, ALZN, is another one that is going back on the watch list too.  It wasn't nothing crazy, I mean like, but what was nice about this one was the last 30 minutes of the close. You could see volume really kicked up, and it had a nice little move from 290 all the way up to about $3, did a little bit of shake right here, right around that 316, and then obviously made its big run. But you could see these volume bars down at the bottom, I mean, you could see, look at this, this is pretty cool. So you could see this stock at what, it traded 153 million shares. Really didn't do that much of a dent though, you know, went from like 230 to about 330, and then did an, and yesterday did what, about 57 million. So it takes a lot to move that stock, and even like today, you know, in pre-market it would trade 660,000 shares. So regarding about other stocks that we're looking at, so the one that a lot of us have been focusing on this morning, happened to be this GMTX. Now GMTX also took a very big hit from 17, all the way down to about 250, one of the first days that are up, you got some nice resistance levels right around here, around 340, I'm seeing a 55,000 share seller and a 46,000 share seller in the level four. So they just kind of showed up right around 830. Meaning it's gonna be pretty much of a big resistance, think on my level four is working again. Not really seeing any big buyers up until about three bucks. So, you know, it's got good volume, it's good level one, if you're an advanced trader, you could trade several thousand shares of it, you don't have a problem getting out of it. We know about the GRTX, that was from yesterday and SCAC is another one that had some really nice movers the last couple of days, we traded the stock, was at 75 cents, ran to $1.70, and no, this is not a penny stock, we don't trade penny stocks here, just happen to be the, you know, people think anything under a dollar is a penny. I don't trade anything under a dollar, but once it broke a dollar, you could see a thing had some really good movement. She's moving again this morning, pretty damn volatile stock, honestly, you could see what it did yesterday, ran from $1.80, you could see these candlesticks, boom, thing drops about 20 cents. But just be very careful with it, it was more of a nickels and dimes yesterday, and that's what we got. Now, there's a couple of stocks I put on the B and the C list, you had ECC, SSC, there's another stock that moved pretty nicely yesterday, you could see here in the long-term chart, the stock went from $10 to 27, stock had a really good push at 11 o'clock, ran from about $10, I mean $18 all the way to 26, and then all of a sudden she was a phenomenal short, I don't know if she was on your short, I mean once it broke this $17, you know, I mean in the middle of the day it was a great, I was basically all we had, but that one did pretty well. It's holding here pretty strong, let's see how it works out, but you could see the tier size is very, very small, and remember it's not about buying the stock, it's getting it, okay? And getting it is, if no one's selling any shares, you gotta remember, you gotta focus on that spread, so that one's moving, not that we're gonna trade it, but Roblox is obviously taking a big hit, it's got a really nice short going on, you know what, I was a fan of Roblox when it was in the 70s, it went to the 80s, and then I got out of it, and then I'm like, how does this thing go to 137? I mean, if you really know what this company does, it's like, wow, that's a lot of money for that stock, but obviously, if it breaks this $100, the stock can drop only down to 87. So once again, a little bit more advanced stock, so if you're an advanced trader here at Cyber Trading, that might be up your alley. Another stock that did pretty good in the after hours was this CFVI, big push right here, right at the close. She's kinda holding here, been pretty volatile, we trade the last couple of days, we're from 10 to 15, very, very volatile stock, very small tier sizes, automatically category three, so if you know what level you're at, that's what that's gonna show up. And then obviously through the ALZN back on the watch list. So you can see, it's not really a big good day, I mean, the market's at 13, 13, are you kidding me? That's it, I mean, it shows you there's nothing going on right now, but does not mean that a day's over, we always find some things that move. So my goal is just focus on the day's pay, and that's it, that's what you have to look at. You can look at the DWAC also I wanna throw on there, she had a nice pop, I don't know what happened after hours, but this stock has just been a hell of a roller coaster, just be very careful on the swing trade. I made money on the swing and then I got out of it, but she's been pretty damn volatile the last week. So we'll keep an eye on that. Alex, as I agree on the day's pay otherwise, one can throw away gains, I know I have done it. Well, Alan, we've all been there, we all've done it, okay? You just gotta be very, just don't think like, oh, this is the big one. I mean, we saw what happened at AMC yesterday. Just be happy you got what you got out of it. You know, being here for so long, our list is always like 10, 15 deep going into pre-market. Now we're talking two, three deep. This is perfectly normal. It's a great time to learn.  All right, guys? One last stock, that rich, one of the instructors here just posted a stock was QNR, was it X? Yeah, it's got a little bit of a movement right now, 57%. It looks like it just made a pop just now, bottom just picked up as of right now, doesn't look too tradable. It went all the way to seven, didn't only drop down to five, but we'll throw it to this on the B list too. And we all know that some of these things out of nowhere just pop out of the blue. So we'll throw it out, thanks a lot for that, Rich. Everybody else, we'll be back here at 2.30, if you're watching YouTube Facebook live and don't forget, if you haven't got the email, Friday is going to be one of the biggest events of the month and the year on trade with the pros. You're gonna be meeting some of the best masterminds, best gurus in the industry. So if you haven't registered yet for that, be happy to. And if you're new here to Cybertrain University and you are doing a trial, please make sure you talk to your education advisor, let them do a walkthrough with you so you can explain to you what, so you can have the best experience to see if trading is for you because it might not be and that's not a bad thing. But if it is, best job you'll probably ever find. So what you gotta learn before you can earn. Good luck, everybody. We'll start commentating in the Cybert Room and the market opens up. If you're watching YouTube Facebook live, we'll be back here at 2.30.


YouTube team keep it clean. What's going on? It's engraving here with another video and in this video the speculation is finally over and Because there was there was that question that sort of awkward moment Where when the Raven signed Earl Thomas? Everybody was all cool like okay. We got our Thomas now nice. Hope he stays healthy nice cool nice He's a good player nice. Hope his legs are okay nice, but One thing that everybody wasn't so sure about that. Hold on. What number is he gonna wear? What numbers Earl Thomas gonna be because Marlon Humphrey currently wears number 29? But now we finally got the answer to that question Because Marlon said he was gonna give up 29 at Earl Thomas. He said he got respect for his game respect for what he's done in the league And he gave it up to him So Marlon Humphrey has now chosen his number, but really quick before we get into that the flag football game I put the fly out. It's official It's official June 1st If y'all want to see where it's set the times and all that y'all check my Instagram check my Instagram check my Twitter I will be doing a separate video on it just to give all the specifics But just come through if you want to come through. Let me know that you're coming through You can hit me up on Instagram send me a DM on Twitter. However, but everything is dead now Everything is dead now. If anything changes, y'all know, I will let you know, but everything is dead now We should be good to go. We should be great to go and again, I think this Whoo, I'm still gonna try to look up some places to try to keep them up Go sort of on the back burner because I feel like this thing may just be a lot more people than I even expected man So I look forward to seeing y'all there. I look forward to um Playing against y'all playing whoever will whoever gonna be rocking with with team keep it clean like my team And we'll figure out that all that out when we get there. Maybe we could do some little one-on-ones too Of course have the the flag football the games where it's whether seven on seven or eight or whatever we do We're just gonna have a good time. Everybody just I want everybody to come with a good vibe a good mind frame And again, like I said, even if you're not playing that's fine. That's fine It's for everybody even if you don't play you could just come chill and relax just vibe. That's it Even if you don't play it's fine so if you do play and I'm covering you just be prepared to be bored because you're not gonna do anything Be prepared to be bored. You're gonna feel like it was more than hungry covering you or something Just be prepared to not have any action come your way to not have any passes thrown your way And if you do have any passes thrown your way, don't expect to catch them I'm just trying to let y'all know. I'm trying to I'm trying to prepare y'all so anybody who's in front of me Who I'm lined up against Just be prepared to have a boring Saturday Or half along. I'm lined up against you for Because for some of y'all I'm a traveler.  I'm gonna just stay on this side. Let him go somewhere else. I ain't traveling.   But anyway, the flag football game is set Game set match and it is the location. Like I said, check my instagram check twitter all that good stuff I put it all on there. Um, so appreciate y'all and I love y'all I look forward to just having a real good time a real good time And like I said, just come with a good vibe Friend bring your friends your family whoever because we just coming out there to chill and just just have fun That's it If you mad that day leave all your anger where you left it at leave it at home If you upset that day don't bring that energy Just come with good energy and a good vibe because that's what we that's what we here to do Well, that's what we're gonna be there to do So anyway, um Team keep it clean Marlon Humphrey he He made a decision on his number And just to show you what kind of offseason that's this has been because this is a big offseason of change This has been a huge offseason of change this Throwback throwback this throwback this throwback this throwback this throwback this throwback this throwback and now this throwback Marlon Humphrey decided that he is going to wear the number 44 He's gonna wear the number 44 and That is such an ugly number four cornerback I know some of y'all don't want to say it and I respect that I believe that's the number that his father wore So that's cool. You honor your dad and whatnot. That's cool.  It's not any disrespect to him. The number's just very ugly Let's be real about it.  It looks like he's supposed to be blocking for syrus jones Now again, let me say that again with the number 44. It looks like Marlon Humphrey supposed to be blocking for syrus jones Shout out to the people who understand where we coming from. Remember our old fullback who wore 44 And he blocked for number 27 Shout out to those two legends um for the ravens anyway um That's that The number's so ugly. Um, but hopefully his number Because you know those things where they say you if you feel good you look good and you play good That number does not look good at all So hopefully it doesn't mess Marlon Humphrey up on the field. Um, because I know even even though like some of y'all might be like Um, no, it's just it's just a number engraving and can't mess his play ups.  Um, but if you got a haircut It could make you feel a certain way It can make you feel a lot better about different stuff that you're doing It could give you a little boost of confidence If you got on a nice shirt some nice pants some nice shoes or whatever It can make you feel like okay, whatever you're doing. It could give you a little extra boost And I feel like it could be that same way with a number But hopefully with this case would it be in his daddy's old number? It can give him that extra boost like I'm trying to make my daddy proud even though he already has He already has he and he's made a lot of us proud. Um, because Marlon Humphrey again, he has um He's been he's been really good man. He has been really good and once jimmy smith isn't here next year Um, he's gonna make life after jimmy smith. He's gonna make us be able to still breathe Uh, because man, he's he's been really really good Um, but I I expect our secondary to go through some major changes next season Like major I think jimmy smith would be out. I think brandon call be out. Um and Avery could be his time next year. We'll see but um, we still got to get through this year first And I really did think that jimmy smith could have been a goner this year Um, especially after he got to spend it for the first four games Um Yeah, I just thought and then when when eric the cost was started shaping this team I really thought that hey, he could be on the outs But again, like eric the costa said he didn't want to make a strength of the team He didn't he said he found no reason to make the strength of a team a weakness Just okay cool. I understand that I get that so Do you think? um, but anyway With this with this number change. I'm just oh man We gotta get them all in Humphrey jersey.  It's so ugly But again, we we we understand and realize the story behind it um And shout out to malin humphrey because I was watching his interview where I don't know if y'all caught that too I saw it on twitter, but i'm sure they probably put it on ravens.com or something like that But his interview that he did with the nfl network with is it andrew sissillianos sissillianos or whatever The little the the short the short guy from nfl network.  That's that's what's up, man. He went to the mcdonald's just so he can get some wi-fi um, and he talked about the whole early time. I mean, yeah early timers thing again where um He said early timers, uh, he was going to give up early timers his number and at first he was like, um He was gonna ask him for money, but he said, uh, well, you can give me something if you want to But what I want you to do is just uh, give it to my mom's um her track team, uh in alabama So I thought that was cool. Isn't it in alabama? I think it's in alabama. Whoever said he said early times to give it Give it to donate the money to his mom's track team. All right, he said he did say that he said if early timers want to give me something That's cool, too So he threw that in there. I like that He made sure that he put it out there like hey, it all just got this big deal If you want to slide me something, let me know So That's that so now we're gonna have a 29 a 23 a 22 a 24 a 28 a 26 a 27 and a 44 in the secondary Oh and 36 for chuck clark Oh and and 21 for john elliott We got all these nice numbers except chuck clark's and marlon humphries. We got all these nice numbers We stacked and of course nobody could use 20, but we got all these nice numbers Nice numbers then he and he went and chose that But it's all good man because we know his play Is going to Look much better than his jersey Appreciate y'all team keeping clean again. Make sure y'all check my instagram. Oh, I put it on instagram and facebook And twitter So y'all check all the those for the flag football game I look forward to seeing you guys there and again, like I said, we will be doing us Video just about that period. So we're gonna have a video just about the flag football Period. So just in case anybody got in. I mean, you shouldn't really have any questions um The address that I put The address that's on there. That's the address of a clubhouse to a community Obviously not gonna have the flag football at the clubhouse, but the park is like Right down not even I can't even say down the street because down the street is too far It's Right like I can't even say around the corner because around the corner is too far But the the the field is going to be like right there Close to that clubhouse because the field don't have an actual address But the clubhouse does um, but again, we'll do the video on the specifics on all of that. Um, appreciate y'all Love y'all. Thank you all and Just like malin Humphrey in his old jersey I'm out


The Navy is full of buzzwords and acronyms. Interoperability, ORM, and Saved Round are all words and concepts that are part of our day-to-day lives, but the outsiders make no sense. Military families are no exception to that. Maintaining communication between service members and their families is a key part of resiliency, or overcoming challenges related to military service. This can encompass everything from communicating with your spouse and family, surviving deployments, to reintegration when your service member comes home. A great place to learn about what it takes to be resilient is the Focus Project. Focus Family Resiliency Training is an eight-session course designed to teach adults, children, and eventually the family unit as a whole to communicate. Details about the project can be found at focusproject.org. The most important thing to remember is that you are not alone. There are people and organizations standing by to help you.


For our next talk, we have Wes McGrew. He's going to talk to us about post exploitation of Docker containers. Thank you. So the target audience for this talk is unapologetically red team members, people who are doing red teaming engagements, other offense-oriented services, such as penetration testing, application security testing. And the title of the talk, I always have long titles for my talks. There's the clever bit, and then there's the actual part of it. And so it's a look at multi-container applications. So building, nowadays with containerization technology in Docker, which I'll cover in a little more detail, you can build an application basically out of these LEGO blocks of Docker images or other containers that you find on the internet. And so portions of your application can be made up of these immutable containers. And what that means is that you're working at a higher level of abstraction, and all of your vulnerabilities come from these lower levels of abstraction, where these Docker images have vulnerabilities. And the way they talk to each other in a non-authenticated way on the back end can cause issues. And so the goal of this talk is to give a penetration testing practitioner who's not already familiar with Docker or is facing multi-container applications, a little bit of tactics and tools to use to examine these systems. And so my title at Horn Cyber Solutions is Director of Cyber Operations. And so what that means is that I oversee all offense-oriented services. I run teams that do multiple teams that are simultaneously doing pin tests, red teaming engagements, and application security testing for a number of different clients. And so I try to get hands on with it as much as I can, but really I'm more interested in the management of all of these sorts of things and making sure that all the teams are up to date on the latest tools and techniques. In a previous life, I was a professor at Mississippi State University. I still adjunct there. I teach class every semester. And there I worked on industrial control systems, developed a reverse engineering program there for getting the NSA, CAE, and research education, cyber operations. And so basically most of my research, most of my work has been on the offense side of things. And so if you're a blue team in here, you might find things a little bit lean, but you can learn how to break these things and so that you can then look out for these tactics and techniques. The intention for this deck really is to make a strong point about the relationship between an attacker's skill level, your skill set, the set of things that you know as an attacker and your development as an attacker over time versus developer trends. And so this talk isn't just about attacking Docker containers specifically or even multi-container applications specifically. It's really about how do you develop your skills over time as an attacker, whether malicious or not. And so how do we leverage what you already know and how to look at learning new technologies moving forward and the sort of attitude to approach it with. We wanna provide a hacker that's experienced in exploitation and post-exploitation of networks of systems.  How do you move and take your, most of your training as a penetration test or a red teamer has been in that mode? Looking at that attack surface, looking at protocols between services, looking at vulnerabilities on the outside edge of each of those individual systems. How do you move and take that skill set and apply it to an application? And so historically applications have been monolithic. And so a monolithic application is something that's, it's made up of primarily a single binary or a single service running on a single system or a single virtual machine. And so with a monolithic application, if you're wanting to inspect the state of internal things to the application, how functions call each other, how data is stored in memory, you're looking at attaching as a debugger, you're looking at setting breakpoints, you're looking at exploitation in terms of memory corruption or other sort of remote code execution to get to the point that you can examine these things and then you're in this sort of environment of a debugger or something where you're limited in how you move. With multi-container applications where you're building your application out of these immutable images, talking to each other, a lot of times your variable storage and your function calls wind up taking the place of TCP IP connections, wind up taking the place of things like Redis databases that actually store what would normally be a local variable. And so it allows you to explore the internals of an application in the same way that you penetration test a network. So I'm going to demonstrate this with some concrete docker example, with a concrete docker example. The white paper for this talk has a set of different things to sort of step up to this, but I'm going to show you the cool one first. And the inspiration for this approach in this talk is what I consider a classic talk by H.D. More and Valsmith from DEF CON 15, Tactical Exploitation, it's quite an old talk I guess now, but it's actually, it's well worth going back and looking at if you're a pentester and you never saw it. All of the work in any kind of field is built on the shoulders of giants, built on the shoulders of people who have come before you and doing this sort of work. There's been a number of talks on docker and containers, overall there's entire, there's docker con and general purpose docker talks out there in research, but specifically in security and in previous DEF CONs and black hats, we have here a list of good references, good material to read to prepare yourself for this sort of thing. You've got Mortman, Greta Fiori, Bettini, Czerny, Dolce, and the, and these are all great works, but they all focus on different things than what we're focusing on here. They either, and focus on the underlying implementation or architecture of docker, the way it's implemented at a kernel level, which for the purpose of this talk isn't exactly the most important thing, and having some advice for that low level security sort of sorts of things. And then there's vulnerabilities in the platform itself, in your docker run times and your docker infrastructure and the way that developers use docker and how you can target docker developers. The thing is, if I get on stage here and I present a docker talk that has docker zero day, well, in a couple weeks everybody will have updated, well, most everybody, except for that one client, right? They'll have updated their docker instances and those vulnerabilities don't work anymore. So really, you want something more timeless, and so what you're looking at really here is post-exploitation as being something more useful to learn in the long term, because you're always gonna find a way into one of these applications through vulnerability in its outer attack surface. And so the focus of all those other talks has been on defense as well, or at least on specific attacks, and so this is more of a general tactics for red teamers type thing. So when we're looking at containerization in docker, if you haven't fooled around with it a lot, and I don't think a lot of penetration testers have, it's getting more and more popular, but as a means of developing an application, what you're looking at here is essentially an operating system level virtualization. That's versus VMware, where it's simulating the hardware of a system. We're talking about simulating the user space and file systems and libraries and networks for this container that's running, but everything, all the containers are sharing a single kernel. And so that means that it's a lot more lightweight. If you wanna spin up a new docker container from an image, it just takes a matter of seconds to do that, and it's very quick to do this because it's a very lightweight type system. And so due to it being lightweight and due to it being dynamic, and if you tag on something like Kubernetes or docker swarm onto this to have these things scale dynamically with load or size of data, what you wind up with is a really easy way of developing applications out of these pre-built containers. And it eases deployment and development. So if I develop, and the reason why I'm doing this talk is I started developing an intelligence collection platform that used this to scale for large sets of data. And the useful thing for me for it was that when I developed it on my laptop, I could push that image out to the server and it worked exactly the same as it did on my laptop. And then that's a very solid guaranteed thing as far as docker's concerned. So development and deployment of these things winds up being relatively easy. When we look at vulnerabilities in these systems, it's important to look, and I think this is one of the most important overall themes for this talk, is to look at the concept of vulnerabilities and layers of abstraction. I've talked about this in some of my previous talks when I talk about security of penetration testing, basically Opset for pen testers. That's my previous few years of talks. I see vulnerabilities, the lifecycle, it doesn't begin with discovery. So you see these vulnerabilities lifecycle diagrams and they begin with the discovery of the vulnerability and then notification and then patching and on and so forth and the cycle of life begins again. It really begins with a mistake. Developer made a mistake in the development of an application. They either didn't design security in, they made a typo in their programming. They have some, they committed some error that becomes exploitable in Sergey Brotis's weird machines terminology. Essentially it's an unexpected execution.  And to me, I think that these vulnerabilities are mostly the result of not understanding the layer of abstraction directly beneath you. And so if you're a web application developer or not understanding the HTTP protocol that's underneath you as you're working in JavaScript and APIs and frameworks and things like that, if you don't understand how cookies work but you're relying on your framework to do that for you, there can be an issue there. Textbook example of this is with C programmers. If you're a C program and you learned in a college course that didn't really dive into the implementation of C, you might think that these buffers are just gonna be, I said I had 20 bytes for this buffer. Why's it even let me put any more in there, right? Well, C will happily let you do that, obviously. We all know this. And even if you know that and you know your program's gonna crash, you don't really understand the implications of it. You write a C program and it crashes when the input's wrong.  But what you don't understand is what's really happening is you're going past that buffer and you're running over things on the program stack. If you don't understand that there's a program stack that's holding your local variables then you didn't understand what's happening in that segmentation fault. Base pointers, return pointers, all that sort of thing that you can manipulate. And so all that's the sort of thing that if you go a level lower than C and you're looking at assembly and machine code and stepping through things with a debug, you learn to understand those sorts of things, but that's not at the layer of abstractions that you're developing.  But underneath it, at some point it becomes a magic box. You have an understanding of how that computer works at a basic level, but it may not be the case. And even for myself, I think sometimes, well maybe I should have done a degree in computer engineering instead of computer science because when it gets down to like the transistors and the physical properties of silicon, I don't know, right? You know, there's probably something to that that I don't understand that will bite me one day. And so for a hacker to keep up with these sorts of things, you've got two different directions to look in. One is in your layer of abstraction, higher, lower, and as a hacker, you tend to want to start learning lower and lower and lower so that you can get further underneath that developer's understanding of things. But horizontally, you've got different technologies like this and this diagram. You've got languages on the left-hand side and protocols on the medium on the right-hand side. And so there's lots of different things and it's hard to keep up with this. And so you have things that you specialize in for our pen testing teams. We have folks that are very good at web applications. We have folks that are very good at network-based attacks. We have folks that are very good at looking at embedded control systems and things like that. And so you have your specializations but you always want to be broadening this. If you're a developer, you usually move upwards in the stack, though. So we're moving downwards as penetration testers, red teamers, and things like that. But a developer is typically moving upwards. And so if you were a web developer in the late 90s, you might have been writing your code in C. I've written some web applications in C++, CGI.  But, and it's not something that I would deploy on anything internet-facing nowadays. If I found the code, I need to find that code. You could compile a program that outputted HTTP headers and HTML and stick it in a CGI bin directory and then wait to get owned, right? And then, you know, well, that's not so smart. So we start putting scripts out there. And so that's a higher level of abstraction. And then we have web-specific languages. Okay, things like, regrettably, PHP and things like that that are designed for the web, right? And then on top of that, we have frameworks. Think of things like Django that do a lot of things for you. So like Django, you've got your object model that handles all your database stuff. You've got all these connectors and everything. So where you don't have to understand HTTP, you just write the code that backends your website and you have some templates for the front end and it's all, it's kind of hiding things from you, but it's making it easier for you to develop apps. As you go up this, these layers of abstraction, it becomes easier for you to develop applications. And then nowadays it seems that most web applications are strictly running in JavaScript in your browser than hitting web APIs on the back end. And so that's another way of developing another way of hiding some of this complexity. When we look at containerization, it's as if we can take any specific web application that's been developed almost, and you can look on the Docker Hub out there and pull down an image of it and have them talk to each other. And you can build a serviceable app out of these things with just some connecting code and some configuration files and some scripts to spin up the containers for them and to have them talk to each other. And so essentially this is the next sort of meta level of developing an application. And so your mindset as an attacker versus a developer, after you learn Hello World for something, you learn these things by looking at their tutorials. You learn them by reading the most basic introductory book that you can find on the topic. You learn them from trainings and tutorials and videos and things like that. Nobody sits down with like, nobody sits down with KNRC and learns C anymore, right? They're gonna go through some tutorials first. So if there's a developer, which you're gonna learn after you learn Hello World is, what can I build with these language constructs?  I'm gonna use the same approaches and the same practices. And the problem with security for that is that most of the time, tutorials sort of hand wave security for things in favor of getting something up and running in like a couple of screens worth of text on a website. If you're an attacker, the first thing that you do, like first thing I did after I started looking at doing Hello World in Docker so I could build a multi-container application is like, well, how does this work? How does this Hello World work? And so you start digging into, well, how to do these Docker containers look at each other? And so if you're an attacker or a developer, this abstraction allows for more efficient development. That's basically what we're talking about here. These layers of abstraction, essentially the idea of having these building block containers, you can have mixed technology in them. It doesn't matter if this one application is written in .NET, doesn't matter if this one's written in Python, we'll actually look at an example in the video of an application like this. And the way they talk to each other, they have to, at that point, speak over common protocols like TCPIP. They can't rely on them being PHP talking to PHP or C talking to C. These are technologies that have to communicate over the same sorts of networks that organizations operate on. And an interesting example of this is if you look at a lot of multi-container applications use Redis, and I might not be pronouncing it correctly, but it's essentially, when I saw it in an application, I was like, what is this thing? And it's essentially, it's a key value store. So it's essentially a variable storage container or a service, you can run it outside of a container. But you connect to it and you say, this variable name, assign it to this value. And you have some complex data structures in there too. You can have some cues and stacks and things like that in there. And so instead of storing things in local variables in your container applications, since your containers are immutable, they can't maintain state if they go away and then come back, they'll store state inside of these Redis containers where other applications can come in and look at that data and use it. And so we'll look at some examples of that. But so instead of having a program stack in C, for example, where you'd have storage memory that pointers are pointing to locally, you now have them on this network-based service. And so what this means is the developers are moving up the stack in an abstraction and as attackers are moving down, there's a few things happening. One, there's things higher on the stack that attackers need to learn to work with, things like containerization and modern web development technologies and things like that that we might not be very interested in. The good news, however, is that our existing techniques for penetration testing networks of systems apply directly to penetration testing inside of a multi-container app. And so you're existing, now, you might be a penetration tester today, but once you start looking at web applications, now congratulations, you're an application security expert. And so your current toolset, your current skillset becomes more lucrative over time because you're going relatively lower in the stack to the developers. So think of somebody in the 70s or 80s who was writing assembly language code and that's what they had to do just to write an application for a computer back then. Well, now, they're very good, that person would be very well suited towards embedded systems development or other lower level things. And so when we're looking at these sort of, these multi-container applications and application internals, we want to have things like control over execution, opportunity to turn code against itself, things like ROP and web APIs and CSERF and things like that. All these sorts of things, especially in case of malware analysis and return-oriented programming and CSERF, these things require very specialized tools and sometimes you might even be internal to an application, right? To exploit a monolithic binary application, you're looking at having to attach this thing to a debugger just to get an understanding of how to develop an exploit for it. The skill set for this, you know, it's different. So an internal application security expert, somebody who analyzes applications for vulnerabilities needs to have a very strong understanding of the language that they're targeting and methods of exploitation and some of those can get quite arcane. But a penetration tester generally works on the outside attack surface. They're using known vulnerabilities or relatively easy to find vulnerabilities because they're targeting the attack surface of an entire organization at once. And so you might have been trained in doing some very simple buffer overflow exploits as a penetration tester, but if you're writing them every day in your daily work as a penetration tester, I'm going to be very surprised, right? If you're connecting to a remote service on a client and you're throwing the A's in until it crashes type of thing and you're able to develop that exploit sort of blindly without seeing the other side of it, you know, that's a, I mean, kudos to you, but that's just not the norm in pen testing. It's more of an application security thing. And so there's a training gap there, but the nice news is with this containerization is that your existing skills of system to system pen testing apply much easier. So containerization allows for the design of applications that are composed of many of these things, and so we're democratizing post exploitation manipulation. So essentially after you gain access to one of these multi-container applications, and so there's lots of vulnerabilities in these things. So if you look on the Docker Hub, there'll be official Docker images for different web applications, but there'll also be a lot of Docker images that people made one off for web applications that at some point may not have had official Docker images. And so somebody will take it upon themselves to create an image for their own use, push it to their Docker Hub so that they can use it, and by default it's available for anybody else to go and grab and use in theirs. But they didn't sign up to be a package maintainer, right, they didn't sign up to maintain this thing over long periods of time, and so there's use of it may have been over, or they may not care about the vulnerabilities in it, and so you'll see in the demo there's a Joomla image out there that you can grab and it's an old version of Joomla. There's an official Joomla image out there, but there's also a lot of, it isn't vulnerable, but there's also a lot of backdoor images and there was a news article a while back on somebody who had crypto miners embedded in these images. And so there's lots of things, and that's smart, I wish I'd have thought of that. So there's lots of vulnerability in the images themselves that can give you that entrance into the backend network for these things. And so you essentially have this Docker network underneath the horizontal line there where your containers all work and can talk to each other, and then there's an outside attack surface of ports that are forwarded to the outside world from the host. And those ports are, and you specify those ports, but once you're on the inside of this network, it's kind of free for all, they can all kind of talk to each other, no matter what they've specified. And so essentially a test of an application becomes a microcosm of an organization-wide test. Your actual post exploitation of this sort of thing is gonna involve identifying that you're on a Docker network, which will be pretty simple because you're gonna find yourself on a system that doesn't have a lot of tools. It's purpose built for that one application, and so you might be getting a busy box shell or something and in the video we'll actually show you another technique that you can look at very quickly to see that you're on a Docker container network. And so your idea is, once I gained access to one of these things, let's enumerate the rest of them, let's find out what's on the rest of them, let's figure out how they talk to each other and see if we can move around. And this is all analogous to, on a monolithic application, function hooking and break points and inspection of memory, but it's at a network scale. And so the implementation of this is so you have access through conventional exploits. It's familiar territory for attackers with system or network level of experience. The limitations of this is you're living off the land. You're gonna have to transfer your own tools in and just kinda statically compile them and hope for the best that they'll work once they're on there.  You're gonna be doing a lot of port forwarding in order to get your tools on your system to reach in there and look at those other hosts. And so the demonstration video for this is demonstration of exploitation and post-exploitation of a multi-container application. This is a Docker multi-container application that's used frequently in public Docker trainings. It's out there on GitHub. The links are all in the white paper for the talk. This is used to teach people about Docker. And it's a voting application. It's meant for cats versus dogs. But I've changed it to blue team versus red team so we can have some fun. We're gonna attack this thing. We're gonna look at how different aspects of it, like the voting interface is written in one language. The backend takes the votes as another language. The database is a Postgres database and then there's a Redis queue that the votes get stuffed into and popped out of. It's like a stack or a queue, actually, in this case. You have a data structure list in Redis where the votes are being pushed onto the left-hand side and then popped off the right-hand side as a queue. And so we'll bump over to our video here. Get my controls. Okay, my controls were hidden under the bar there. All right. Okay, so this is a tour through the application itself. The voting app at the top there is written in Python. Bumped out a full screen on me. The result server is written with Node and JavaScript. There's a Joomla image. In the tutorial of this, there's not really much external attack surface. Drop that vulnerable Joomla image in there just for the purposes of demonstration. You see in the networks there that it's showing Front Tier, Back Tier for some of these. Some of them are only Back Tier containers. Those are two separate Docker networks. And it's essentially like a DMZ and then the internal network that we're talking on. There's a worker node that depends on Redis and it's simply popping votes off of the Redis queue and then pushing them into a database. There's the Redis queue itself on the back end and then a database that the votes actually wind up in. And it's good that this is a video because there's a lot of moving parts to this that can go wrong. It took a few takes for this. And so we can start this thing up using Docker Swarm as instrumentation. And the details of all this are in the white paper. And so I'm moving through this quickly but it's all there. So there's your voting interface. There's the results off of another port and there's that juicy Joomla image there waiting to get popped. We can punch in votes and see the results. And we can even change our vote. We get a cookie that our vote is associated with and so it can flip and flop as time changes. So we wanna break it, right? And luckily this particular Joomla image there's a module in Metaspoit that can take care of hitting this thing. That's just making note of the local IP address of the attacker. You can see at the bottom of the screen the attacker target designation there. The asterisk designates which screen we're looking at at any moment. Right now we're looking at target. We're loading up that particular attack module. We're setting our target up which we identified from the web interface. You know, boring Metaspoit stuff. Type faster old Wesley. Setting our local hose because that PHP interpreter is gonna phone back to us. And it's a quick exploit. It just goes ahead and works. You're sitting in a PHP interpreter right now. You get some information about the system that you're on. It's the, and it'll be the same kernel version for every container because they're all sharing in the kernel. We can drop to a shell and this is showing you in the proc file system in the C groups you can actually, without going into what all that means you see a lot of references to Docker. And so that's first indication that we're on such a system. Now we're doing IP information for this Docker container that we're inside of and there's an internal and an external network there. There's the 172.19 and 172.18 that are both that that are those frontier and back tier networks. We can background that interpreter session and so we have that session sitting there. We have that persistence on that Joomla server. We're grabbing a statically compiled version of Nmap off of GitHub in order to be able to scan that internal network. Statically compiled because we wanna upload that which is what we're doing right now into a temp folder onto that compromise container so that we can start working from there. We have to have it statically compiled because we don't have a lot of library support on that target and certainly Nmap's not already there unless you've broken into a Cali image container, right? They're fantastic, I like working with them. I think the actual attacker pane on this interface is running in a Cali container. And so here we're Nmapping the 172.18 network which is the external network, the frontier network. All ports on the first 10 hosts. By these default configurations of Docker they're sort of incrementally assigned IP address numbers. And so you see and there's actually good naming for most of them except for that Joomla server that I didn't really give a good name for. And also the Docker host is the first one up there. So that gives you an idea of those three HTTP services that we're looking at, the front end voting interface, the results application in the Joomla. Now the scan is going across the back tier because now we have access to one of these containers. Now we can start scanning the back tier network and seeing what's there. It's gonna be a lot more interesting stuff. It's gonna be stuff that we can play around with. And so you've got the Reddit server down at the bottom. The next one up is the Joomla instance, the Postgres database there. We've got, and again, the Docker host up there at the top at dot one. And so now we've got a database and a Reddit server we can mess with. Now so now we can start manipulating local variables. So we're back into our interpreter console all running on our Joomla instance. And we're gonna set up some port forwarding so that we can interact with those services directly. Basically we're creating a tunnel from our external attacker image or container or virtual machine or your local instance of Cali Metasploit. And so we set a port forward here to where we can get at that database. And we can just use the regular old Postgres command line to interact with it. And the thing is, is by default with all of these Docker images, is they're meant to get up and running very quickly. So many of them are configured to just have default or no credentials, no authentication, nothing because they're all sitting on those back-tier networks where nobody can get at them directly. And so once you are in there, you're usually good to talk to each other unless somebody's done a lot of special configuration, which is not in the tutorials. And so here we're looking at the tables and looking at the votes that are in there. The votes take the form of an ID associated with that voter. And also which one they voted. A is red and B is blue I guess. I don't quite remember. But then we've also done some inserts to see more votes being put in for blue. So blue team members can celebrate for now. Now as past Wesley just pauls their brain farting I guess. All right, now we're back into a shell and we're going to, since we're just doing NetCat for the Redis, we don't really need to set up a port for it. We can NetCat from, we can NetCat from that host. A lot of times you'll have Busybox which we'll have NetCat built in. Here we've gone into monitor mode on Redis. So once you tell Net into a Redis instance, all the commands are plain text and monitor allows you to see what's going on and live feed of interactions. And so all those pops are that worker or container continuously looking is there a new vote? Is there a new vote? Is there a new vote? Because when it finds a new vote, it'll pop it and throw it into the database. And so it's continuously doing that. And as I hit the votes here, you'll see things change and I'll move the window out of the way there so you can see it. And so you see votes being pushed onto the right-hand side and popped off the left-hand side. And so now that we know how this works, we kind of got in a feel for that. It's almost like watching an instrument and a debugger to see how does this part of the program talk to this other part of the program? We can now start playing with it directly.  And it's just as good as pushing them from the web interface. And so I've posted in a ton of votes there with unique IDs of just alphabetic letters. It doesn't verify that they're valid or associated with any cookie or anything. It's just sort of there. It's a toy application. And so now the red team's winning, of course. And there I am rubbing it in about highlighting it. And so the takeaway from this is that your existing offense-oriented skills, none of that was very difficult. Like this is not zero-day. This is just regular old tactical post-exploitation stuff that you'll learn as a pen tester if you haven't already learned it, if you're getting started. These are things that'll be in classes and stuff. But these existing offense skills become useful at a lower relative position in the stack of abstraction from developers as they're using higher and higher abstracted technologies. And so developers are moving up and so the new low level moves up. And so it's important that you update yourself. And so for us, we don't want the first, we don't want the first multi-container application we encounter to be on a client gig. We don't wanna have to learn it on the spot then. We wanna have some familiarization with things like Docker and Kubernetes and other technologies for newer development methodologies so that we are familiar with these things when we see them. We'll freak out when we break into a Joomla instance and see that there are no tools in place and don't even think to look to see if there's another back end network that this thing can talk to. And so it's important to update yourself and not only move down the stack in terms of getting lower and lower level of skills for exploitation but work up the stack as well. If something seems cool and trendy like cloud or containerization or blockchain or anything like that, it's really easy to turn your nose up at it, right? Because it's trendy and you don't wanna be trendy but ultimately, your clients are gonna wind up using these technologies and you need to understand them. And so it represents a good entrance into application security testing for existing penetration testers. There's a white paper available in the conference materials. It has all the information about the demo and a couple other demos. There's a lot of discussion in that that's not in this talk and a lot of links to resources that I used when I was learning about this stuff, previous work that's being done in security of these things and also some pointers to some information on how to secure these applications, if that's your thing. I appreciate your time and I'll be down here ready for questions and to hand out cards and trade contact information. Thank you.