Okay, so what I would like to do is tell you a little bit of an application story. And that is using the tools and the virtualization that is provided through OpenStack and Open Daylight. Redware took those tools and used it to create a cyber control plan or a cyber defense network. And I'll explain a little bit further what that means and we can have a conversation about that. So the first reason is why? Well, if you look at what's happening in the security industry right now, what we're seeing is we're seeing more and more continuous attacks. So as opposed to a few years ago, where it was relatively rare, we're now seeing in 2014, 19% or about one in five attacks are being called constant. And so in this environment, we're seeing about half of all respondents and this is the respondents of our enterprise customer base, saying that they could only fight the campaign for one day or less. And so we've seen more recently, we are seeing customers that are under attack from a cybersecurity standpoint for days or weeks or even months, particularly when it comes to banks and foreign governments. And so there's a need for a more comprehensive type of solution. The second piece is especially when we get into carrier networks, which is driving a lot of the NFV and SDN development. The service provider networks are being affected in two realms. One, they're being affected themselves. We're seeing them as targets of attack. And you can see some of the logos of some of the different companies that have been affected by these attacks. And the second piece is the enterprise customers themselves are turning to them as their connectivity provider to provide them the kind of security that they require through their network. And so what we're seeing is in the case of BT, BT is seeing about 60% of their customers saying that these attacks are becoming harder and harder to stop. The second piece is we're seeing a rise in multi-vector attacks. And what we mean by multi-vector attacks is the first generation of DDoS security attacks was around volumetric attacks. So this was sending 10 gig of traffic down a one gig pipe and try to knock over your router. And now what we're seeing is we're seeing multi-vector attacks where I'm not only going after the physical pipe with a volumetric attack, but I'm also using the protocols that you're using, whether that's web or SIP or whatever applications you're running to actually attack those application servers and try to take those application servers down as well. And so the shift from volumetric to application again requires a much more comprehensive look at the network. The third piece of this then is mobility. And as carriers are now moving from 3G to 4G networks, 4G is an LTE-based network, very flat, all IP-based. And now all of my smartphone devices are IP-addressable devices. And that creates two things. Number one, that means all of those can be addressed and therefore attacked. And number two, it also means that I can have a handset that roams onto my network and now can be a rogue handset that is used then to launch attacks either at a carrier's infrastructure or again at the carrier's enterprise customers. So all of these then are combining for a need for much more comprehensive, much more holistic approach. So if you look at this then, this is some of the research from some of the most recent studies that we've done looking at what are the different elements in the chain that are being attacked. And what you can see is there's no longer any single element that's taking the brunt of most of these attacks. You can see a third of them are going after the internet pipe but also a third of them are going after the server and the applications that are being used. And so what we see here is this starts to get into this notion from an SDN and an Open Daylight controller standpoint of wanting to use the entire network and all of the telemetry and all of the different elements to look at different attack telemetry and determine what's the best place to fight the attack because there is no single device and therefore no single box that's gonna be able to combat the attack. So if you look at this in general you can see several key themes that are coming up. One is that the security threats are becoming much, much more aggressive and much, much more sophisticated. You've got these multi-vector attacks going after layer four through seven. The networks themselves are getting more complicated as enterprise customers not only have on-premise devices but now they have cloud devices that they wanna protect as well. The second piece of that is we're also seeing a rise in encrypted attacks where carriers and enterprise customers are seeing now the need to go after, are seeing the need to not only look at clear channel or unencrypted attacks, unencrypted traffic but also encrypted traffic as well. And so the countermeasures are getting much more complicated. So there's a need to not only do challenges on certain requests to see if those requests are legitimate or those bots but also then to decrypt traffic and look inside and determine is there an a various act that's trying to be committed within this encrypted tunnel. And then the third piece of it is if I look at SDN and if you look at Open Daylight one of the things that provides is this network wide view and this is extremely important when it comes to carriers because from a carrier perspective the macro level problem that they're seeing is although the revenues are rising their profits are flat. And the reason for that is because of their huge operational costs. So as the revenues rise so much of their different operations and procedures basically manually scale with revenue and therefore they aren't seeing any growth in profits. And so one of the big opportunities here around NFV and SDN is to really change that dynamic and change that equation and show them some significant savings from an operational standpoint. So the need then is to come up with a network wide security control plane and that's really what Radware has been working on to provide that to get a much more end to end holistic view to act and mitigate these cybersecurity threats. So if you look at what we did we basically leverage three different elements. One is NFV. So we took our different security elements and we virtualized those and we virtualized those either in an NFV environment or in an OpenStack environment. And so we created both physical hardware as well as virtual instances of these different security elements. The second piece is SDN and that was leveraged using an open daylight controller and what we did is we built our software on that SDN open daylight controller to basically take telemetry from multiple different points in the network. So be able to look at everything from the network feeds that were coming directly off the router from layer two and layer three and layer four as well as looking at application level feeds coming from the servers, looking at DPI, DPEC and inspection data that would come off the DPI appliances. So what you get is you get a much richer set of data from which to correlate and then look at make a decisions. And then the last piece is wrapped that completely in the orchestration and cloud nature of OpenStack and orchestration. And so this is really the tool set that we use to build the application that we're gonna talk about. So one of the things that we did is we built it on an open daylight controller. So the reason we did that is because when we look at carrier networks, carrier networks today are really leveraged around building these islands of SDN. And so in these islands of SDN they've got a virtualized software defined data center at layer two and layer three and maybe they're multiple geographically dispersed. And then also a layer three WAN that they're using and this could be virtualized using Cisco, using Juniper, using Octelucent, whatever the router vendor may be. And what we were able to do then is by taking the flexibility of open daylight in being able to take multiple different types of telemetry and multiple different network feeds, we were able to then combine and correlate all of the different information coming not only from the software defined data center and the elements there, but also from the WAN elements itself. And then by collecting that data we were able to use our behavioral engine which sits over the top and basically create an overall baseline for normality within the network. So what we do is we look at multiple different parameters within the network, establish that baseline and then look for anomalies against that profile. And then when we see anomalies against that profile, we can then determine and again using some of the flexibility in the open daylight controller determine where is the best place in the path to actually provide the mitigation to stop the threat. So let's walk through an example. So let's say we have an attack going through one of our carrier customers to an enterprise data center. So in this case, the attack is detected and telemetry is sent then from a virtual instance and this could be an instance running OpenStack, this could be an NFE instance at the enterprise data center. And basically at that point then the attack is characterized using about 34 different parameters that look at the different aspects of the attack, the vectors that are being used, et cetera. And this runs in real time in about 18 seconds. So over that 18 second time period it collects all the telemetry, determines the different vectors in the attack and sends that then to the open daylight controller where our application which is called defense flow sits over the top. So our application on top of open daylight then looks at those 18 parameters, determines what's the best place in the network then to block that attack. Let's say in this case, it's at a scrubbing center that a carrier is using that's somewhere in a different geographical location. So what it would do then is it would take that telemetry and that information and specifically the signature that is required to block that attack. And it takes that signature and that signature that is pushed down to that scrubbing center and then the open flow routers are used then to redirect the attack. And so that redirected flow is then sent through the scrubbing center, it's cleaned there and then sent on to the enterprise data customer. And that's just one example but obviously the rules could be whatever the carrier or enterprise customer decides they want to use as their policy rules. So if they wanted to block the attack using a particular ACL, they could do it that way. If it needed to be redirected, let's say not to a scrubbing center but it was more of a web application type of attack and wanted to go to a web application firewall, that could be done as well or if it needed to be decrypted because it was an SSL attack, multiple different ways to mitigate the attack but it would go to the proper network element either hardware or virtual. And so what you have here is you have here now a cyber control plane basically that's built on top of the open daylight controller that's taking telemetry from the entire network correlating it and providing a much richer set of information then to make decisions and then based on the policy that's put in place on the application and on the controller then determine where in the network to provide the best mitigation and providing this multiple layers of network defense. So we think this really becomes kind of a killer application for SDN and the reason for this is because there's kind of this virtuous cycle that can happen here and this is where if I start the circle over on the left side, I program the network, I collect the telemetry, I get flow visibility from the open flow open daylight controller APIs and I get all of the information then around of the network. That then flows up to my SDN application that I built on top of open daylight and as we talked about a little bit previously I then take that information, I build all my baselines and determine what is normal traffic within this network and then against that I can look at any type of anomaly and determine what degree of membership does that have with normal behavior and basically then either pass it as normal behavior and allow this traffic to go through, say that this is suspect behavior in which case then I can provide either automated or manual challenges from a security operation center to challenge that flow and see if it's legitimate traffic or not or if it's clearly out of membership with the norm I can determine that it is definitely nefarious behavior and then go through whatever policy rules to block. So I do that real-time attack characterization and again that's done looking at all the different factors and parameters in about 18 seconds and then I move into the war room which is really the policy-based room of the application where based on the policy rules that are set within the application it determines again what is the right element and what is the right place within the network to block the attack and basically sets all the policies in place so that it can be fully automated and in a carrier environment could be done completely without the interference or the mediation of the security operation center. So let's look at a specific example. So here's an example of a carrier that's running an NFV-based orchestration system and wants to offer a DDoS-based security service. So the customer says I want to have the service and so how do I deploy? Well first of all I use the virtual infrastructure manager and I set up all of the virtual instances on-prem and this can be done again using OpenStack and I set up all my virtual instances and now I want to deploy then the service configuration. So in our case then what we do is we have VDirect which is a plugin which basically then programs the VM sitting on the customer-prem that sets up the virtual instance for the security element and then the DDoS policy is set. So again the rules based on when it sees an anomaly what should be done, those rules then are pushed down into that virtual element running OpenStack for example. Now once that's done the ongoing maintenance basically it's a provision once and run forever type of service so there is no ongoing maintenance once that initial policy is set unless there's some type of real-time update to rules or policy or something like that that needs to be done. So once that is done then if I do that I can now leverage that and I can do that as well in an SDN type of environment so I can have that same type of functionality but now instead of using that plugin to provide the policy I can use this OpenDay like controller that can see network-wide and use that then to push down information to the virtual instance. So now let's take an example where I see an attack coming in through to the enterprise the attack gets characterized by that enterprise device that telemetry is then pushed up to the defense flow application that's running on the OpenDay like controller based on the policies that are then set the application sitting on the OpenDay like controller then makes the determination where to redirect the traffic and basically based on that then it can determine whether there are other instances in the network that would be the best to divert to or should have put an ACL in place from some perimeter based router in the Layer 3 WAN or whatever the policy rules of that carrier basically would determine. So what we're left with then is we're left with this cross-domain anti-DOS that focuses on the entire network so it gives the ability using OpenDaylight and using OpenStack to basically provision instances of our security algorithm anywhere around the network collect telemetry from it and other applications and then determine where is the right position of the network to mitigate that attack. So basically in conclusion what this application allows us to do is it allows us to basically take what today is a federally manual procedure where a security operation system would basically see an attack coming in assign a security engineer a security engineer would then troubleshoot the attack use BGP or some other equivalent routing protocol then to manually divert the traffic clean it and then use BGP again to send it back on its way to the enterprise to take that very manual carrier process and use OpenStack and OpenDaylight to basically completely automate it and offer virtual detection where I can take telemetry from OpenFlow from OpenFlow enabled elements from NetFlow enabled elements from third party elements as well feed that into my analytics engine then have my war room where I've set up all of my dynamic policies basically replacing a lot of the functionality and the manual troubleshooting that a security engineer would do and basically set up rules in place by which depending on what type of application or what type of attack I see what are the rules to deal with that automatically push those rules or ACLs down into the network and then program it to act so that when it sees it it's automatically rerouted sent to the proper device scrubbed or cleaned and then sent on its merry way and with that I'll be happy to take any questions all the communications from telemetry to analytics engine to war room and then on to the mitigation points where in all those communication points are they restful and or restful APIs that you might plan on opening up where are they proprietary? So they are done through open restful APIs all of those interfaces any other questions? Yes sir well first of all the flexibility of Open Daylight and the fact that by the way the interfaces are defined that I can take multiple different types of telemetry I can take snippy I can take inputs from snippy from net flow from open flow so the first piece is the flexibility upon which that was built is probably the primary reason and then the second piece is just from a market acceptance standpoint we're seeing more and more specifically speaking from a carrier or a large cloud enterprise customers we're seeing more and more more and more of our customer base that want to see these types of applications built on an open source open daylight controller the enterprise device as opposed to the carrier device so the answer there is it really depends on how the carrier wants to deploy so let's say that first of all a typical carrier deployment today will be an out of path deployment where they're using some type of a scrubbing center and so in this case they're not seeing all of the traffic because the traffic is not always flowing through the scrubbing center at any one time and what they're using is they're using some type of either open flow or net flow statistic collection from the perimeter routers to signal for an attack okay and basically that's a typical carrier that's a typical carrier deployment model and what you get there is you're able to detect all sorts of volumetric attacks as well as layer 4 attacks and things but because you're not in the path you're not always going to see let's say an HTTP web-based attack and so the on-prem device which is an always-on 100% of the traffic is going through that is going to see that type of an attack where unless the carrier is running an always-on type of service themselves which more and more carriers are moving to if they're not running that type of deployment model then the value of the CPE device is to look for those type of application attacks that the scrubbing center wouldn't see could we use the mic at the back of the room for questions and answers or you could just repeat the question any other questions okay if not thank you all very much I appreciate your time


Marines and sailors with the Scout Sniper Platoon and personal security attachment of the 31st Marine Expeditionary Unit met at a campaign and shooting range to test and improve their skills in combat marksmanship. Pitting Marine against Marine takes the training to another level. Anytime you add competition to training, it's gonna make it more realistic, make it more effective. Three man teams with 20 rounds per Marine engage 59 pop-up targets in a time limit of 60 seconds. Each Marine was also required to fire a minimum of five rounds from each shooting position. Prone, kneeling, and standing. And that's always good for the Marines because you're not always going to be able to take that well-anked shot from the prone. You sometimes have to get up out of the prone, shoot off of a barricade. Today the Scout Snipers won the competition, but every Marine took away a higher state of expeditionary readiness. Marine Sergeant Paul Robbins, Jr. Camp Hanson, Okinawa.


Hey, this is Brett and this 2021 Ram 2500 Megacab Short Box Bighorn Level B Sport Appearance Group is stock number 13600Z. I am here at Summit Automotive in Fond du Lac, Wisconsin. You're new and used Ram and heavy-duty truck headquarters. This 2021 Ram 2500 has the 6.7 liter Cummins diesel engine. It's paired up with these 68 RFE 6-speed automatic transmission. This truck has been fully safety and inspected by our service shop per the state of Wisconsin inspection process. It has a fresh oil and filter change. All the fluids have been checked and topped off and it is 100% ready to go. I'm going to go all the way around in this video inside underneath. Start it up and take a look under the hood to give you the most accurate representation that I can. Diamond black pro coat is the color and I shoot all my videos in 4K, so if you have HD capabilities, turn them on now because it is your best way to check out the quality condition options and cleanliness of the truck before seeing it in person. Very clean down this side of the vehicle. Didn't see any dents or dings. It looks really good. Front fender, no dents or dings in there. If you like the video, you can subscribe to my YouTube channel, which is youtube.com. Click the bell notifications and you'll get updates every time I do videos of amazing vehicles like this one. Each and every day here at Summit Automotive. This one comes with Cali off-road painted and polished aluminum wheels and it has Milestar Patagonia XT tires. These are 35x12.5 R20LTs. And I would say they have close to 80 to 90% of the tread left on them. Very new tires on here. This one does have a front end leveling kit on there. I'd say it's probably about a three inch leveling kit, maybe two and a half. Frame and underbody, it looks really good. Front fender once again, no dents or dings. Headlight lenses are nice and clear and it does come with the factory fog lights. The sport appearance package gives you the painted front and rear bumpers. You also get the front bumper parking sensors. And the gloss black grille. The hood is in fantastic condition, no dents or dings on there. And the passenger side front fender looks really good as well. Passenger side front wheel, no scuffs or scrapes. And diamond black pearl coat, one of my favorite blacks that there is. It's got a lot of gold flake in it, which is really cool. A little bit of purple and greens as well. As you go down this side of this 2021 Ram 2500 mega cab, take note of how clean that body is, how reflective and mirror-like that paint is. I take these HD videos, so if you are far away or even if you're close by and you just cannot make the trip down but you're still interested in purchasing the vehicle, you can see the truck, hear the truck, and have confidence in what you're looking at before you even get here. So when you do get here, there's absolutely no surprises. And you can make a smart and informed buying decision from wherever you're at. If this video helps you make that buying decision, let your salesman know that you saw the video that it was helpful and that brought sense to you. Back wheels in excellent shape as well, and the back tires have just as much tread as those front tires. Frame and underbody back here is in excellent shape, and it's like that all the way underneath. It has all the remaining factory exhausts, so it hasn't been altered with. Altern, lower rockers and cab cores look great, and it comes with a nice set of amp research step bars. They work great. Coming around to the back, rear bumper is in excellent condition. It does have the full towing package, backup parking sensors, receiver hitch, 4-pin and 7-pin wiring. Tailgate is in very nice condition as well, and it comes with a revolver 4x roll-up tonneau cover. Comes with a very nice spring and bed liner, and it also has a gooseneck hitch back here. Also a plug-in 115 volt, 400 watt, and then some side box tie-downs. That spring and bed liner goes onto the tailgate, which is a really nice feature as well. And the tailgate shuts nice and solidly. You also get the LED tail lamps, back wheel, excellent condition as well. And on the rest of this side looks really good. It does have the heated fold-up tow mirrors, built-in directional signals. They fold up like so, and in like that.  No rips or tears on those seats there, and fantastic condition. Smells perfect inside this truck. Don't think it's ever been smoked in. You get a power driver seat, factory all-weather floor mats, auto headlamps, and power pedals. Power windows, locks, and mirrors, and these mirrors do power fold in. I always like showing both sides, so you know that both sides are working properly. Wood grain trim, cloth bolster on the door there. Back seats are just as clean as the front seats. No rips or tears back here. It does have the latch child safety system for any child car seats you may have. Power sliding rear window with the built-in rear defrost. Seats are in excellent shape, all-weather floor mats. You get two USBs, two USB-Cs, and a 115 volt, 400 watt plug-in. These seats fold down two different ways. So the first way, the whole backrest goes down, which is great, because it goes all the way to the back of the cab. And if you needed a flat place to lay, put both sides down. You get almost a full-size bed there. Also, if you got pets, put both sides down. They get a nice flat place to lay as well. And then you get a storage bin back here, which is pretty sweet. And then you can put just the backrest down. Now that gives you a little bit higher load floor here, but it also gives you an enclosed area for stuff that maybe that could roll around or whatever. So that's nice as well. And yeah, very, very clean back here. Child safety locks in the back doors and the inside of the doors all look fantastic. We'll hop inside, check out the miles, the radio, and everything that this truck has to offer on the interior. You can see that this one has 14,804 miles. You do get these 7-inch LCD display on there. Digital speedometer, compass display. You can change those corners to read whatever you want. Very nice and clean. Comes with the heated leather wrap steering wheel, cruise controls, and gear selector on the right, Bluetooth and information center controls on the left. This one does come with the 6-speed, 68 RFE automatic transmission. You get the Uconnect 4C radio. This one has the factory navigation system. There's Highway 41. So that is working nicely. You also get AMFM and Sirius XM radio capabilities. Heated seats, heated steering wheel. Any of your backup cameras right here. So you get your normal backup camera, and then you have your cargo cam, which is pretty sweet. You can see what's going on in the bed if the tonneau cover was up. And then you can zoom in on your receiver hitch to get hooked up to your boat camper trailer the first time, every time. You can also do your climate controls here, and you have all your different apps, including off-road pages, projection manager where you can project your cell phone to the screen, via Android Auto or Apple CarPlay. We actually did a demo on Android Auto on an 8.4 if you want to check that out. That's in the upper right-hand part of the screen.  They take a second to load. So while they're loading, I will show you that you get your manual volume and tune controls and climate controls down there, as well as heated steering wheel and seat buttons. You also have a factory brake controller, factory exhaust brake, tow haul mode, front and rear parking sensors, and two USBs, two USB C's, and an aux jack. You get your push button four-wheel drive and your push button start. You get your off-road pages. They do take a second to load. But once they're loaded, you can see that I can change that steering angle, and it changes up there as I turn the steering wheel. So that's kind of cool. You also have latitude, longitude, and altitude there. You have your accessory gauges and pitch and roll if you're doing some off-roading. You also have, if your transfer case is in four-wheel drive or too high or too low. Down here is your 115-volt 400-watt plug-in. You get your sliding cup holders right here and your keyless entry with remote start. Passengers side, floor mat, and seat are in fantastic condition. No rips or tears. Once again, I don't think this truck's ever been smoked in, smells brand new inside. Headliner is absolutely perfect, and you do get map lights up there. Power sliding rear window button, assistant SOS buttons, and home link buttons for your garage door security systems and lighting systems. You also get an auto-dimming mirror. We'll start it up and take a look under the hood. Starts right up. No check engine lights or anything like that. I did want to show you the tire and loading information sticker, as well as the VIN sticker. I would personally like to thank you for checking out the video, and hopefully from this HD video you have been able to verify the quality, condition options, and of course, cleanliness of this truck all the way around inside and out. Under the hood, we have the 6.7 liter Cummins diesel engine. Engine-based, very clean, runs very smooth. Once again, this truck has been fully-safetyed and inspected by our service shop. Per the state of Wisconsin inspection process, it has a fresh oil and filter change. All the fluids have been checked and topped up, and it is 100% ready to go. There is the emission sticker. And I would highly recommend this truck from a quality and condition standpoint. I don't think you'd be disappointed in this one. I'd ship it to California, Florida, New York, wherever. Whoever is going to get it is going to love it. Super good looking. And to see more pictures of this truck, or one of our other 550 new-news cars, trucks, SUVs, minivans, Wranglers, halftones, three-quarter-tons, one-tons, you name it, we got to go to that website right there, summitauto.com. Full pictures and descriptions of every single vehicle from two locations, all at summitauto.com. And if you'd like to check out more HD videos, you can go to youtube.com.com. Remember to like, subscribe, and share on this video. In all the videos that you see there, click the bell notifications. You'll get updates on the videos I do each and every day here at Summit Automotive. In fact, in a second you'll see a link to subscribe to my YouTube channel in the upper left. Link to more Ram 2500 truck videos I've done in the upper right. A link to this vehicle on our website in the lower left. And a link to one of our latest YouTube videos in the lower right. Click those, check us out. And we're super excited to help you with this Ultra Clean. Really good looking 2021 Ram 2500 Mega Cab Short Box Big Horn Level 2 Sport Appearance Package in Diamond Black Crystal Pearl. Thanks again for checking out the video. Remember to like, subscribe, and share on the YouTube channel. I really appreciate it. Thanks again.


Hello there, my beautiful, lovely, talented, and delightful internet friends. Welcome back to my channel. Thank you so much for joining me here today on Footless Show where I am still Joe and I am still missing a foot. And today we're gonna talk about pregnancy as an amputee. Right off the bat, no, I am not pregnant. Thank goodness, let's clear the air on that. But as I logged on to YouTube to just, you know, mindlessly binge watch some videos this afternoon, I saw that Mama Dr. Jones, which is a channel that I follow, she seems absolutely delightful. I really like her videos. Check her out. Just posted an interview with Rebecca Gregory, who is a Boston Marathon bombing survivor and was pregnant as an amputee. Now I have not watched this video, but I'm very excited too because I've never really talked to anyone about pregnancy as an amputee. Like I was already terrified of pregnancy. Like I don't want kids, but being pregnant while also dealing with a prosthetic and all of that. Oh God, I have a lot of questions and a lot of curiosities. And so I'm so excited to go through this with you today. But first, a quick word from our delightful, lovely sponsor who I love working with. I am absolutely thrilled to be able to introduce you to our sponsor today, you guessed it, Ana Luisa Jewelry. I absolutely love being able to tell you about Ana Luisa, especially as we are in the midst of the holiday season and everyone's looking for gifts for people. Their exceptional quality is something I can personally attest to because I got this over a year ago. I've worn it quite a bit. It is just as lovely and sparkly and comfortable as it was the day I got it. They honestly have fair prices with no luxury markup with prices starting around $39. And one of my favorite things about them is that they are all about sustainability. All of their jewelry is carbon neutral, meaning that they offset 100% of their carbon emissions, starting with sourcing of their raw materials all the way to the disposal of the pieces. For me personally, one of my favorite things about Ana Luisa Jewelry is that it helps me feel like pretty and feminine and lovely, even if I'm just hanging at home in a sweatshirt. Their pieces aren't too gaudy and they also aren't too simple.  Clearly random side note, I also really like the clasps that they use for their necklaces in particular. I have a hard time with tiny motor movements sometimes and opening up necklace clasps is something I think everyone struggles with, but theirs are ridiculously easy and I can actually do it on my own and it doesn't hurt my fingers. If you yourself are a jewelry person or you know someone in your life who you're looking for a lovely gift for, please check out the link linked down below. Ana Luisa is an absolutely fantastic company. I love being able to work with them and I love being able to tell you about them. I'll let you in a secret. If you look at many of my recent videos or my live streams, you pretty much always see me wearing either their earrings or necklace or something like that. So I honestly wear them just about every day right now at home. Check them out, link down below and please let me know what you think. Without further ado, let's get to it. I call this look chic comfort. I got up and got dressed this morning with just like this turtleneck and my pretty jewelry and I was like, yeah, I look good. And then I got tired of that and wanted to be cozy so I stole my husband's sweatshirt. Don't tell him. But a few of the things that I'm curious about are the weight gain that comes with carrying another human inside of you and wearing prosthetics, gaining any kind of weight, even a few pounds, honestly, can make prosthetics change how they fit you, can become uncomfortable or it can no longer fit anymore. So that's something I've always been freaked out about. Balance on a prosthetic leg when your center of balance is totally different. Also, probably on a pretty inconsequential side note, I've often wondered if women who are giving birth as amputees wear their prosthesis during giving birth. I'm assuming the answer is no, but I'm kind of curious. Full disclosure, like I said, I have never been pregnant. That's something I currently plan on ever being. Who knows? And thus, pregnancy is something I only know about through stories of my friends and walking alongside them and things of that nature. So I am a really no expert and I'm looking forward to learning. Let's jump into a little bit about your pregnancies. I know you have Noah who was there with you that day and then now you have another daughter as well. I do, Riley. They're so cute. So tell me what were some of the differences before and after the bombing and as well as losing your leg about the differences in your pregnancies? Well, the big thing was that doctors told me after the bombing, I spent 56 days in the hospital initially. And one of the things they said is, Rebecca, I'm so sorry based on your internal injuries. We don't believe that you will ever be able to have another baby again. In 2015, I was doing pretty well. I had just gotten married and to my college sweetheart. We really, really wanted a baby and it came as kind of a surprise because I didn't think that I would be able to have one. And so we went to the doctor and sure enough, she said, you're pregnant. It was just a really amazing time because I thought to myself, in 2013, I was three feet from a bomb that should have killed both my son and I. And here I am in this new beautiful life and I get to have another baby. So I'm just like a little bit teared up. That's absolutely beautiful and a miracle. Did the pregnancy end up being more complicated or what would you highlight as some of the things that made it different than being pregnant before all of this? So the whole one leg thing makes it interesting. And I have to be really careful. I think one of the things as far as gaining weight. Okay, so that's always been one of my biggest fears too is that as an amputee, if you gain weight, your legs don't fit the same way anymore. And beyond that, specifically with your center of balance being changed and your body constantly changing, from my understanding, using the kind of prosthetics become really difficult. Even a couple of pounds, my leg fits differently. And because of pregnancy and swelling and other issues that I already have, time to think about that a lot.   I know that I was probably out of my leg more oftentimes than I was in it. It was tough. There were a lot of things that were easy too. I mean, my pregnancy in general for the first couple of months went by really seamlessly. Even though I was high risk, I was having more doctor's appointment. All in all, it was really, really good. With regards to the prosthetic leg, I haven't had a lot of patients who have been pregnant with that, but I've had a few. I would say the biggest problem that we would run into is difficulties with fitting. Even if you gain a normal amount of weight, there's some swelling in pregnancy that's very common. Did you have any problems with mobility towards the end because of problems with the prosthetic or were you able to tackle that? I was able to tackle that, and I owe a lot of that to my doctors, my prosthetists because they were really, really mindful of the fact that they wanted me to be as comfortable as possible. So I would encourage anyone who's an amputee and has a prosthetic leg or two to really just go into your prosthetist as often as you can if you have any sort of issue because a minor tweak is a really, really big thing when you're an amputee. So that makes a lot of sense. Sometimes it's the tiniest little things.  They'll put a little pad in there and it looks like it wouldn't make any difference because it's so minuscule, but it makes walking actually bearable or comfortable. A caveat that I've wondered about is these appointments aren't free generally speaking. And so if you're someone who's copay for those appointments or is paying out of pocket, it would make it really difficult to be able to have a leg that fits during pregnancy. Thankfully, currently I and the amputees I immediately know have medical coverage, but not everybody does. So I'm really glad this was something she was able to do because it sounds like that was a huge turning factor and being able to actually stay active and stay moving during pregnancy. Also this comfortable chic thing sounded like a good idea because I was cold, but now I'm really warm. So outfit change. At the seven month mark, I started to develop a really just small backing and it wasn't even painful. It was just this feeling that something might not be right. I told my husband, I said, I'm getting a little bit of pain in my back. I think we might need to go get this checked out. My doctor, we called her immediately. She said, absolutely, go to the hospital right now. I'll meet you. And it ended up being me going into preterm labor. And we would have had no idea, but my doctor was very, very good about making sure we go to the hospital and getting checked out. So any mothers out there, please let me know if you feel like sharing, but something that I've always thought would be so disorienting about pregnancy and giving birth is obviously the fact you don't know when it's gonna happen, right? But especially when you're not expecting it for weeks to go into the hospital with some back pain and then come out with a baby. That seems like it would be so jarring. I don't know, maybe I'm thinking about that the wrong way. But that's crazy that her doctor caught that and was like, yes, go to the hospital and then she was actually in labor. Did they think that because of your presentation? I'm wondering if maybe the amputation itself had anything to do with our concern with that because we do get a little bit worried about venous stasis and circulation issues in some of our amputee patients, but is that ended up being what it was or was it something different?  I mean, I have all of this shrapnel in my body. Of course, when I fill out my medical form since I got blown up by her bomb in 2013. And so they kind of chalked it up to my injuries from that. I think it's really interesting that she brings that up because there are some heightened concerns with things like circulation as an amputee. They're just health issues. Your doctor needs to be aware of like your doctor needs to know that you're an amputee and you should be aware of as well. There was this one particular doctor who had absolutely no bedside manner in a bed and they're telling me the worst possible thing.  It was just the way it was presented to me. I appreciate upfront honesty.  I said something I don't understand about bedside manner or not. I've had really good doctors and I've had not awesome doctors. And I also appreciate when people are blunt and upfront with me about like, here's what you're facing here, your choices.  You know, that's just what it is. That's no way for someone to be able to get through something. Like obviously that's the most disheartening or discouraging thing that you can hear. Rebecca, I'm really sorry that that was said to you. Bedside manner really does matter and it's not about lying to people or lying to patients or trying to make them feel better. I think it's about how you present often really difficult information. It was crazy because I ended up getting her out in 14 and a half minute. Wow, did you push a lot longer than that This was pretty quick. I can't remember exactly how long. It was a lot more than 14 and a half minutes. Not that fast. Was there any difference between delivery, you know, before your agitation and after or was it pretty much the same? It was pretty much the same except my husband is so funny because during all of this, I mean it was very stressful and everyone was sad. We had nurses crying and giving me hugs and it was so funny because I'll never forget this. One moment where I couldn't feel when they gave me my epidural, I couldn't feel my leg at all, obviously. And so, but I was so uncomfortable because of the phantom pain that I was experiencing too. And so it was a really weird dynamic between the two. Oh, that's so weird. So I was trying to get up in the bed to be able to kind of like move a little to try to get more comfortable.  Humor is the best way of coping with a lot of things. Was your recovery any different after the birth than you remembered it being with Noah or was it about the same? It was about the same. I mean, the biggest thing is that not having a leg, I couldn't put my leg on right away after giving birth because of the swelling. So it took a little bit of time to do that. So just the inconveniences of getting in the wheelchair. That's a really interesting point. I didn't really fully think about that once you have the kid, your body is still changed. Like you're dealing with swelling or dealing with some weight gain still. And not being able to use a leg when you're used to generally being able to use a leg as you have a newborn. That's gotta be a real challenge that sounds really difficult. Like I get frustrated if I can't wear my leg for half the day because of swelling or pain. But the idea of not having a leg that's either comfortable or reliable or you just can't get on as you're going through this, like that's really, that's difficult. The everyday things that I think if you tease have to deal with that are not necessarily normal, but they're normal to us now. Yeah. So it was just that. But really, I mean, all in all, it was pretty easy. So for starters, as I said, Rebecca's story is incredible. I followed her on social media for quite some time. We've exchanged like one set of messages back and forth. So I don't think I can call us friends, but I mean like Rebecca, if you're watching this and you wanna be friends, I mean, it'd be cool. I think you're pretty awesome. Be cool, Joe, be cool. But what struck me from the amputee perspective watching this is it sounds like, yes, there were some things that are different. There are some complications, but that's kind of just life as an amputee. Things, they're always gonna be like small difficulties or adjustments or things that are just different, right? Things you have to figure out an adjustment for. And it sounds like pregnancy is very much the same way. I'll be honest, after watching this, I almost feel, like I said, I never want to have kids, especially biological ones, but if for whatever reason that ever happened, I do feel a little bit more reassured that maybe it wouldn't be the end of the world. Can you tell that I'm fairly terrified of pregnancy and children? Yes, not children, childbirth. I'm not generally terrified of kids, but some are frightening for sure. So I've linked mom and Dr. Jones' channel down below. I've also linked Rebecca's TikTok. That's where I know her from. She is delightful. Her videos are absolutely hilarious. I aspire to one day be as funny as her and her husband, their skits are amazing. Thank you so much for joining me here today. Go watch the original video. You can hear way more of Rebecca's story. Highly recommend. And while you're here, if you wanna hit that subscribe button, maybe that like button, maybe ring that notification bell if you're feeling extra generous. That'd be fantastic and I'd appreciate it. A huge thank you again to our sponsor, all the information is linked down below. I would highly recommend them. Huge thank you to my patrons for continuing to support this channel and enabling me to do what I do here. Thank you. And you, watching this video right now, thank you so much for spending a few minutes out of your day here with me today. It could be anywhere in the world, doing literally anything else. And you chose to spend a few minutes with me and that means a lot to me. Thank you. I love you guys. I'm thinking about you and I will see you in the next video. Bye guys. Have her from the sky.


Good evening. Can I thank you for your attendance. Are you all now, I'm sure, Detective Deputy Commissioner Ross Barnett, who has led this investigation for some time. Deputy Commissioner Barnett will make a statement and then I will add to that and then we'll conclude. Can I let you know at the outset though that regrettably we're not going to be able to answer questions but we do hope that in the information we provide you that that will be more than sufficient this evening. Ross. Thank you Commissioner. We wish to advise that a short time ago a 41 year old man was charged with a number of offences relating to the disappearance of Daniel Morkham at Wombi on the 7th of December 2003. The charges preferred murder, deprivation of liberty, child stealing, indecent treatment of a child under 16, and interfering with the corpse. The man will remain in custody and appear in the Brisbane Magistrates Court on Monday. This is obviously a very significant milestone in what has been a complex and protracted investigation. However as the matter is now before the court it would be inappropriate to discuss any aspect of the circumstances of the investigation and the arrest and the investigation leading to it. Today's arrest is underpinned by the dedication, tenacity and professionalism of every officer who has worked relentlessly on this investigation for nearly eight years. We have repeatedly affirmed our commitment to solving this disappearance and have never wavered in that resolve. Commissioner. Thanks Deputy. I'd just like to add to that by thanking and mentioning a number of people. Firstly and most importantly on behalf of the entire Queensland Police Service we extend our thanks and appreciation to Bruce and Denise and the entire Morkham family for their courage, their patience and their resolve over the last eight-year period. We also want to thank all of their supporters, the supporters of the Morkham family and the volunteers and particularly those who established and maintain the Daniel Morkham Foundation. We want to thank of course the public and in particular the public of the community of the Sunshine Coast for their outstanding support for us throughout this investigation and in particular in regards to that the regular and constant flow of information that they provided to us. We want to thank the media for their ongoing support and contribution to keeping this in the public eye which has been enormously important throughout. We want to thank crime stoppers and other similar community organisations for their assistance and support throughout. We also want to thank all of the police agencies across Australia and overseas who provided assistance to us in what is without question the largest missing person investigation in the history of the Queensland Police Service. And finally but by no means of least importance of course I want to thank all of the detectives and all of the members of the Queensland Police Service who have worked with commitment, determination and continuous resolve in the investigation of this matter. Despite this breakthrough today a significant significant amount of work remains to be done and that includes the search of an area of bushland on the Sunshine Coast. And again as Deputy Commissioner Barnett mentioned because this matter is now on the criminal justice system and before the courts it's not appropriate that at this time we discuss it any further and regrettably neither is it appropriate for us to take any questions. But I thank you again for your support and I thank you for being here this evening. Thank you very much. Yes, Assistant Commissioner Mike Conlon who is in charge of State Crime Operations Command has met with the Morkums and I have talked with Bruce and Denise as well. At this point in time though it's not appropriate I think to go beyond that. Thank you.


You might have seen this picture of that bridge already in press, maybe it's already some months back. You might know the Swiss Alps, they have very famous mountains. One of the most famous ones is the Mount Toblerone or Matterhorn. And just in front of that mountain, there is now the longest pedestrian suspension bridge in the world, which ranges about a bit more than 1,600 feet. So it's quite a challenge for everybody to pass that bridge. So you watch down, you see 300 feet below, there is nothing. It goes side by side. Very interesting challenge. So if you have some time left after the summit, I can encourage you to go there for a hike. It's a beautiful area and take up that challenge. Also at Swisscom, we took a challenge. We tried to bridge things. We tried to bring people together. We tried to bring cultures together. And we tried to make our environment a better place. And in the next minutes, we want to present you a little bit, something out of our journey that we had, trying to bridge our beautiful cloud-native world with the classic enterprise environment. I'm going to start with a small story. So there is Hans. Hans is a developer at Swisscom. Hans knows the cloud-native ecosystem very, very well. So already for a couple of years, he has done some projects, pushed his code, consumed services, and he's a happy customer, mainly because everything is API-driven. That's not new for most of you. It's standardized interface and everything is self-service. So for him, he gets immediate feedback if he does something, if he issues something, it takes minutes to be ready. And the best thing in a large enterprise, you get built-in compliance. So it's very hard to do things wrong and break the rules. Now Hans got tasked to do a bit bigger project where he cannot solve each of his problems within this cloud-native ecosystem. So for that, he might need a very special database. Let's call that database Oracle for now, which is by design not that easy to run in that cloud-native space. So there is a classic enterprise environment where such services are built since decades and they're engineered very well with very skilled people who operate them. Hans also has an experience with these people from earlier. So there's also standard interface. It's called mail with a standard protocol, SMTP, and it's very fancy. On the other end, you get their people and they do natural language processing and try to figure out what you really want. The experience that Hans gets is, hey, you get feedback based on the human motivation on the other side. Things usually take days, weeks, maybe even months, and you experience the full bandwidth of these heavyweight manual processes. Now Hans came to us and said, hey, I really like the cloud-native stuff. Why can't we just do the same with our classic ecosystem? And of course we were thinking about that. And while we were having discussions, we came to a very important conclusion. We have two silos here. Nobody likes the word silos, but essentially there are two silos. And there is one thing missing. So at some point when you do a project, they need to interact somehow. And based on our experience, this thing in between is a black hole. Like today we had this teaser with the cloud boundary or cloud-native galaxy with all these planets and spaceships. And as you know in the universe, they're also black holes. And sometimes connectivity is kind of a black hole especially when you come from a development point of view. Based on experiments though, we found out or we could prove that there are at least... Can you press one? There are at least N plus two firewalls involved. So N is the amount of things that the people around us know about and there are for sure two additional ones that no one knows about. And with that, we continued these discussions and asked, hey, how can we improve this situation? How can we make the user experience better when it comes to these kind of services that our users want to consume? And there were people having very great ideas. They said... Can you switch? Stopped working. They said, use APIs. That will solve all of your issues and you can do everything by machines and you don't have to care anymore. Now, this is true. So it's a best practice decoupling teams using APIs that works well. We see that at very large scale with Amazon, Google and all these folks. That's kind of proven. But there is always a bot. And the bot started when a small story that we had with our connectivity engineers, they're brilliant people and they really understand this black hole where we kind of stop and say, oh, we cannot see how that works. So we're a bit afraid, maybe. They really understand it.  And we got a lot of documentation on how we can use their APIs which would make our lives easier. Everything started with a book full of sequence diagrams. They were complex back and forth communication and so on. Then we had an appendix full of network topologies that we had to understand and in the detailed specification of the API, there were tons of parameters that we understood. And our conclusion after that one was, hey, so now we need to learn, we still need to learn how network topologies really work and we need to learn and understand how BGP is working in order to use their API. And with that question, we had an interesting discussion, Matthias and I, and we were really thinking, hey, is there a way that we, how we can simplify that process, how we can force people to think, start to think in simple patterns and I think Matthias has a great answer for that. Yeah, so at least we tried with one approach and that was basically not our idea, so we spent the last three years to build up this cloud-native ecosystem and as you might know, there is actually already a well-established contract between applications and services which is called OSB API. And I'm not knowing what this is about, this is basically a very simple API that allows you to provision services to your users and also bind these services then to your app so that they can use the services. So this OSB API was well-proven in our cloud-native ecosystems. We have built probably one or two years to bring up these services which we're working fine so we basically thought, can we just break down these more complex services also in this API? So what we then tried is we went to the classic enterprise ecosystems, we went to each service teams which might be databases, Oracle ones, or a site-based one, but also all the services, for example the connectivity one or the internet team and also stuff like email service or messaging services and we tried to make them and to implement the OSB API and the idea would be that each team owns this OSB API so to say as a contract to the outside world and so to allow basic interactions to the cloud world. We tried this approach and we even went a step ahead because within Swisscoms there are a lot of different services so there's legacy services and there's new services and we have a huge zoo of services and we went ahead with this guideline which says we should produce each service where it makes most sense, for example which means the NetApp stays in its place we don't virtualize it or try to migrate it to Kubernetes but it's there where it is but we should abstract it away using the OSB API so that we can consume it everywhere. So there are a lot of these service producers as we call them which range from the cloud native stuff to classic stuff and Kubernetes could also be produced as a service if you want to consume that just as a fun fact and within Swisscoms we have a lot of different consumers so we don't only have platform as a service and that's also the container as a service but we also have an infrastructure as a service and the people there would also profit from having access to these services and also we have some customers that would like to access these services from their own prem since they're just migrating to the cloud or having some hybrid story and in between to allow this we came up with thank you Swisscom we came up with this OSB API as basic contract between all service producers and all the clouds on the top level would have to implement these clients and of course this is a little bit OSB API is very basic so we had to implement some extensions when it comes to events metering and logging we will get to that later and of course we also had to automate the black hole and so there was some connectivity automation involved and the plot twist about this is that the connectivity automation itself is also an OSB API so we have tried that now probably for the last year we tried all various sorts and forms of services to put into this OSB API and we have learned quite some stuff about it so let's share our experiences when it comes to strengths yeah, it's a standard so what do I mean with standard and what do you get out of it so when I say OSB API is a standard it means basically all the consumers when they have it planted at once they can use all services which is a nice thing so you save a lot of effort and for Cloud Foundry Kubernetes you get the client implementations right away since they're supported out of the box so that means it also goes the other way around so if you have your clients once working then you can basically also use the hybrid cloud provider service brokers for example Pivotal has recently released the AWS service brokers and also Google has the service brokers so if we are slowly moving to the hyper cloud then we might just plug the services in try to work this well and also you could use that across companies so if your partner company has a nice service you could just hook it up to your cloud portfolio it has a very simple pattern so what does it mean it actually forces you to design your services very simple so it means you only have these two operations so you better make your service interaction work with these two actions and this also means it also means some limits so we will come to that afterwards but what something that was nice was it was very easy to understand it forced you you could not have the sequence diagram with bi-directional communication it forced you to really be simple and it was very easy to understand so we could sit together with the connectivity engineers or with the database engineers and they would get the service broker API specification like in 30 minutes when we explained them it was very easy to implement so we had this one after this one whiteboard session they could just go off and implement it basically because they have also good libraries so it was very easy to really implement it then in the end and the last thing which might sound like a limit so open service broker API currently is based on polling so if you want to know about the state of your service then you have to actually poll it sounds like a limit but it actually also really constraints you to use basic rest and not being able to talk the other way around which then ends up in communication nightmares so we actually had a lot of service that really worked well benefiting from these these strengths but there were also a lot of limits so we had to figure out that we cannot just press every service into this API yes so I have the honor to talk about things that didn't work so well during our journey I'm going to start with a couple of technical things that we experienced trying to really build more at once services first thing is relations once you pass the level of my service is I want to consume API or I want to create the DB schema somewhere once it gets bigger and more complex you hit limits quite early in your process and and we checked out in the community and we follow proposal from others for example in that area we kind of followed how the Azure folks solve that issue with parent references but it doesn't feel like very native then another issue which also had to do a lot with more complex services or maybe not cloud native or cloud ready services is the binding concept so binding as we know is A built for apps and B is ephemeral and the ephemeral part is quite hard for some services because they usually assign credentials or users with ownership within your service and once you want to unbind or in other words a bit of that user it's quite hard because that user owns some objects and you don't really know what to do with these objects then another thing we already heard that this morning in the keynote from SAP by default the catalog is static so you cannot really dynamically change things without notifying the consumer platforms I think it's very interesting talk this afternoon as a follow up from SAP when they show more about their service manager I can really recommend to join that session I'm too far away probably No it's actually Swisscom trying to lock me in so next point that's not on the list here is day 2 actions or advanced tasks a very good example is backup restore that's not part of the OSB specification provisioning and binding and that's it whatever you want to do after you have created your service or one week later two weeks later that's out of concept which again has some limitations then on the cultural side we also experienced some limits so we found that not everyone especially when it comes to these highly engineered teams they know a technology very well but usually they're not the software engineers and they cannot become software engineers within a month or two so it takes some time to understand the complexity how to build software which serves all the needs that we expect as a consumer of an open service broker API then another thing that I like to name is the GUID problem I think a lot of you remember these times where we had naming conventions for everything and naming conventions were usually made in a way that you can read out the customer and the stage if it's production or not you could read like say the whole history of an application or a system just based on the name and with introducing OSB API as kind of the broker to create new instances you have to deal with GUIDs which from an operator point of view doesn't feel that nice so you kind of have to get rid of your pet thinking model where you everyday say hi to all of your pets and look how they are you just trust in the system and the last point and we had interesting discussion about the deprovisioning use case if that is really a valid use case so we really allow our customers to by themselves with just one call without a safety net a multi step process to be able to delete their data these were kind of the discussions that we had and I don't want to answer if this is right or wrong but just to give you an overview of also on a cultural level what things we hit after we've learned about all these limits to continue the journey with OSB API and all these services since it worked out pretty well for most of the cases so we thought about how can we mitigate these limits and we came up with a model that helped us pretty good which is basically the first step is to try can you do it within the OSB API even if it means you probably have to cut off some corners maybe don't do this requirement if it doesn't fit in do we really need this requirement try to really use the standard because it means if it's in the standard you don't have to do any more efforts on your other platform so it's best if you can do it within this API and for example one of the limits we had was this relation thingy and when we reached out to the community through the Azure guys they were like yeah with this parent reference you could do it just fine within the OSB API you can model relations that way and you can actually even use it very nicely from the CFC Li so that was something let's try to model it in the standard because this is where 90% or 80% of your services should go and it means less effort in maintaining them and if you cannot do this if you cannot cover it with the basic thing you can take a look at the extensions that are out there in the community for example for backup restores there are proposes out there and that's what we did when we really needed backup restores so there are these extensions out there and we hope they get merged at some point so that the Cloud Foundries and Kubernetes clients they support this kind of stuff so that we can do more advanced stuff but yeah try to keep it simple don't try to rely on too much extension because that's going to hurt you with maintaining and last but not least if you really really need to do something that's not possible within the OSB API and especially that goes for the binding problem so if you have to model oracle databases with schema owners you're going to delete all your data if these are binding so you have to use something different so what OSB API offers you there is actually you can delegate the whole management of your service instance to a third party endpoint which can be a dashboard which can be an API so you basically can say when I order I can still order my oracle database and I can still maybe bind it for an API user but then all the further management goes over this API which also has a nice side effect that the teams themselves can maintain this API completely autonomous so but this means the most effort and the least profit from standardization so we try to keep these numbers of services very low. So that's basically how we cope with this limits and maybe some different interesting stuff that you're going to notice if you're going to build a lot of OSBs is that if you have all these different teams and they choose the technology they want it's going to be a lot of different OSB technologies and for example the database team they use to WebLogic since 10 years and they want to use Java so they write the Java OSB and another team they are scripting guys coming from CIS admin background they want to have a Python OSB and the messaging guys they have all this fancy process engines that they use to configure their router so their OSB API is just a layer on top of this process engine or the mail guys they have everything API they have an OSB API on top of that so we've all seen all different kind of OSB APIs but as marketplace guys we somehow need to make sure that they don't have to reinvent the wheel and they don't have to solve the same challenges again so they all have the same challenges when it comes to security for example to state if you use OSB need state you have to solve that it needs probably as in canding if it as in processes and the security officer knocks at your door and says hey this OSB they are so important because it's basically at the heart of your business so if you don't have security there you can basically sell your business or you can just close down your business and so he comes to me with a nice order credential safely make sure that they're placed somewhere where it's secure and that you have stuff like audit and login since we need to know what happened if the critical operations go over this API so we thought about this what should we do about this and still keep the autonomy of the teams so what we came up with was basically this idea we shouldn't try to force everyone to use Java because that would just prevent the DB team from doing anything anymore we should instead provide guidelines and try to underline these guidelines with some tools and platforms that are really nice to use and get the job done so that the teams prefer to use our technologies and platforms than to build it themselves so for example to show you some guidelines we've come up with we have some guidelines regarding placement and connectivity we have created a VPN where everybody can hook his service broker in so that they can communicate with the client platforms very easily or we have created a guideline regarding audit, login monitoring what's required for you if you want to bring your own OSB and also how to secure your credentials safely you might know for example Cretab or revolt offers this kind of stuff and then we also have these tools and platforms that should make this easy so we have an open service broker that's publicly available on Github and this thing for example adds Cretab support to solve this it adds white box monitoring for the middle pillar and it also runs fine as an app on cloud foundry which is the second point so we try to push very hard to push these OSBs internally on the cloud foundry because these offers you managed services for example for logging or for monitoring so they can really cover the stuff on top so that's how we try to get some governance over all the OSBs that we have so after having spent probably two years with OSBs and OSB APIs what we do it again so probably what have we learned so these limits really hurt you in some use cases so we had discussions with some service producers who tell me why do you try to fit my service in this very basic APIs and we had trouble finding the right balance between standardization so these limits really hurt you so it's good to know them one thing that was funny was that actually we had some guys with the first OSBs and worked out within the cloud foundry and then some guys came up with hey can't we solve this problem also with OSB API and it was completely unrelated so don't try to force too much in the API just because you can model it somehow to fit in the OSB API it's especially important to know the limits it's not a silver bullet it does not solve the job it's just one specific form of an API that allows you within the cloud space to use services don't try too much to use it outside so our recommendation is also know your use case know what you want to do will it be limited to really service provisioning can be done with these two operations and especially have no the strengths and limits that we just highlighted before so with that being said if you have any questions you can ask us find us at the Swisscom booth anytime thanks a lot for your time and have a good meal


The first 3D printed items from space were unboxed this week and a group of students are aiming to fly the first rocket with a fully 3D printed engine. This is your space pod for April 15, 2015. 3D printing, also known as additive manufacturing, is the process by which an object is created by depositing material, which can be plastic or metal alloys, layer by layer until the entire 3D structure is created. The International Space Station currently has a 3D printer on orbit and is being used to test the quality of items printed in space. The 3D printer is a collaboration between NASA and the company made in space. So far, over 20 items have been printed in space, including the very first tool to be printed in space, which was a wrench. These items have been returned to Earth aboard the Dragon capsule as part of SpaceX's fifth commercial resupply mission. If 3D printed items from space have comparable quality to 3D printed items on Earth, then they may reduce our reliance on resupply missions to both the International Space Station and future space stations and space colonies. Imagine if you're performing crucial maintenance when a tool breaks. Usually, you'd have to wait for the item to be built on Earth and then are assigned to a resupply mission and then actually flown up to you. But with 3D printing, you could just print it yourself. However, 3D printing can do more than just build spare parts. 3D printing allows manufacturing time to be shortened and reduces production costs, especially of complex designs and especially in the case of rocket engines. Instead of having to manufacture multiple complex pieces and then join them together, such as in the case of fuel injectors, 3D printing allows the entire piece to be built layer upon layer in as little as one or two parts. This can result in less variation between rocket engines and thus increased performance. The Super Draco engines for SpaceX's Dragon V2 capsule will be fully 3D printed and they will be used for both the launch escape system and the propulsive landing systems. As yet, these rockets have not flown in space but have undergone numerous test firings. They will be used for the Dragon V2 pad abort test. However, the date for this test is not very clear and won't be happening until at least May because of SpaceX's numerous launches in the meantime, including the launch of the 6th ISS resupply mission and the launch of a commercial satellite as well. In the meantime, a group of students from the University of California, San Diego, are aiming to fly the first rocket with a fully 3D printed engine. The students are part of an organization called Students for the Exploration and Development of Space, which uses education and hands-on projects in space-related activities to encourage student interest in space. Right now, the team is working on the Vulcan 1, a fully 3D printed engine which they hope will evolve into the first stage of a three-stage nanosight launcher in the future. The engine will undergo its first flight this June at the Experimental Sounding Rocket Association's Rocket Competition. Originally a team of just 9, over 60 students now contribute to the project, working both evenings and weekends, with some students contributing over 40 hours per week to the project. This is not the first time this group of students have built a rocket engine. Back in 2013, the team successfully built and test fired the Tri-D engine, basically a smaller version of the Vulcan 1. This was an invaluable learning experience for the team. All their hard work and knowledge gained through this Tri-D engine project was put into refining their design for the Vulcan 1 engine. The Vulcan 1 is 50% bigger and delivers 500 pounds more thrust. The Vulcan 1 has been built and the team are looking for community support to help raise funds for the construction of the remainder of their rocket, transportation costs and the testing of two new injector plate designs. They will be launching a Kickstarter campaign next week and aim to raise $15,000. Visit 3D-Rocket.com for more information about this project and for updates on their Kickstarter campaign. I had the opportunity to talk with some of the students from this project this week and the one thing that struck me most was how passionate and motivated they were about their work and the potential of their work to help bring down the cost of rocket manufacturing, making space more accessible for everyone. Thank you for watching and I hope you enjoyed this video. If you would like to watch more Spacepods, head over to our YouTube channel at youtube.com. And while you're there, why not subscribe? I'd love to give a huge shout out to all the patrons of tomorrow that helped contribute to crowdfunding this Spacepod. Thank you so much for your contribution. If you would like more information about how you can become a patron of these Spacepods, head over to Patreon.com slash Spacepod. And remember, you can set a monthly limit to your contributions so you don't bust your budget. My name is Lisa Sozynowski and I'd like to wish the team of the Vulcan one the very best of luck in their endeavor to show the world just how much a group of students can achieve.


From Miami Beach, Florida, it's theCUBE, covering Acronis Global Cyber Summit 2019. Brought to you by Acronis. Hey, welcome back, everyone. This is theCUBE's two-day coverage of Acronis's Global Cyber Summit 2019. Here in Miami Beach at the Fontainebleau Hotel, I'm John Furrier, your host of theCUBE. We are at Coptia Fisher Partner, Chief and Chief Privacy Officer at Greens Food Martyr. Legal advice is right here on theCUBE. Ask her anything. We're going to do a session here. Thanks for coming on. Appreciate it. Thank you very much. I'm going to have to do the little disclaimer that all lawyers do, which is nothing here as to be construed as in bias. It's just opinions and information only. I didn't mean to set you up like that. All kidding aside, we're close to the panel here for Acronis's conference. Obviously, cyber protection is their gig. Data protection is cyber protection. Makes sense. I think that category is evolving from a niche, typical enterprise niche, to a much more holistic view as data becomes critical in the security piece of it. What were you guys talking about on the panel? Well, so the first issue that you have to understand is that cyber protection is something that has now become critical for pretty much every individual on the planet, as well as governments. So something that we talked about on the panel today was how governments are actually dealing with incoming cyber threats. Because now they have to take a look at it from the perspective of, first of all, how they themselves are going to become technologically savvy enough to protect themselves and to protect their data, but also in terms of regulation and how to protect citizens. So that was what the panel discussion was about today. On the regulatory front, we've been covered on SiliconANGLE, our journalism site. The innovation balance is regulatory action, helpful or hurtful to innovation. Where is the balance? What is the education needed? What's your thoughts on this? Where are we? I mean, early stages, where's the progress? What needs to get done? What's your view of the current situation? So I'm an attorney, so my views are perhaps a bit more conservative than some of the technologists you might speak with and some of my clients as well. I think that regulation is, as a general matter, it can be a good thing. And it can be quite necessary. The issues that we see right now with regard to regulation, I think one of the hottest issues today is with respect to data laws and data privacy laws. And that's obviously something that I think everyone is familiar with. I mean, take a look at, in the United States alone, we've seen the city of Baltimore dealing with breaches. We've seen other parts of the government from the federal level all the way down to municipalities dealing with breaches and cyber attacks. We've seen data breaches from banks, Capital One, right? I believe Dunkin' Donuts suffered a breach, Equifax. And then at the same time, we've also seen individuals up in arms over companies like 23andMe and Facebook and how data is used and processed. So data seems to be a very, very hot button issue today across the board. So something that we're really thinking about now is, first of all, with respect to the regulatory climate, how to deal with it not only in the United States but on a global level. Because when we talk about technology and the internet, we're in an era of globalization. We're in an era where a lot of these things go across borders. And therefore, we have to be mindful of the regulatory regimes in other places. So I'll give you an example. You might be familiar with the GDPR. So the GDPR is in the European Union. It's been in effect now for the last year and a half. But it affects all my US clients. We still have to take a look at the GDPR because at the end of the day, my clients, my firm, might be dealing with foreign companies, foreign individuals, companies that have some sort of nexus in the European Union, et cetera. So because of that, even though the GDPR is a set of regulations that's specific to the European Union, it becomes extremely important in the context of the United States and globally. At the same time, the GDPR has certain issues that then end up conflicting oftentimes with some of the regulations that we have here in the United States. So for example, the right to be forgotten is perhaps the most famous clause or part of the GDPR. And the right to be forgotten is this concept in the GDPR that an individual can have information erased about him or her in order to protect his or her privacy. The problem is that from a technical perspective, first of all, it's an issue because it becomes very, very difficult to figure out where data is stored if you're using third party processors, et cetera. But from a regulatory perspective, the conflict comes in when you take a look at certain US laws. So take a look, for example, at banking regulations in the United States. Banks have to hold some types of data for seven years and other types of data they can never delete, right? Lawyers, I am licensed by the New York State Bar Association. Lawyers have their own rules and regulations with regard to how they store data and how they store information. HIPAA, medical records. So you see these conflicts, and there are ways to deal with them appropriately, but it becomes some food for thought. So it's complicated. It's really complicated. There's a lot of conflicts. First of all, I've talked to a storage guy who's like, data? I don't even know what strives that song. Storage has not elevated up to the level of state of the art from a tracking standpoint. So it's just, on the business logic, it's complicated. I can imagine that. So I guess my question to you is, are you finding that the jurisdictional issue is the biggest problem in terms of cross border on the business side, or is it the technical underpinnings that with GDPR is a problem? What's the, or both? What's your? I mean, it's both, right? There are a lot of issues. You're right, it's very complicated. I mean, in the United States, we don't have some sort of overarching federal law. There's no cyber protection law in the United States. There's no overarching data protection law. So even in the U.S. alone, because of federalism, we have HIPAA and we have COPPA, which protects children. And we have other types of acts, but then we also have state regulations. So in California, you have the California Privacy Act. In New York, you have certain regulations with regard to cybersecurity. And you have to deal with this patchwork. So that becomes something that adds a new layer of complexity and a new layer of issues as we take a look, even within the U.S. alone, as to how to deal with all of this. And then we start looking at the GDPR and all of this. From a technical perspective, I'm not a technologist. Coss, let me ask you a question on the entrepreneurial and business front, because I think one of the things that I'm seeing, it may or may not be an example, but I want to get your legal weigh-in on this. Sure. You know, it used to be when you started a company, you go to Delaware, very friendly, with Domicile and Delaware, do some formation there, whether you're a C Corp or whatever, that's where we tend to go, raise some money, get some preferred stock here in business. Is there a shift in where companies with Domicile, their entity, or restructure their companies around this complexity? Because there's two schools of thought. You just brute force at everything coming at you, or you restructure your corporate formation to handle some of the nuances, whether it's I have a Cayman or a Bermuda, whatever's going on in the regulatory regime, whether it's innovative or not, are people thinking like that, or what's your take on it, what's some of the data you're seeing from the field around, restructuring around the problem? So, with respect to restructuring, specifically around data laws and data protection laws, I'm not seeing too much of that, simply because of the fact that regulations like the GDPR are just so all-encompassing. With respect to companies setting up in Delaware as opposed to other jurisdictions, those are usually based on two issues, right? Two core ones, if I can condense it. One has to do with the court system and how favorable a court system is to the corporation, and the second is taxes. So, a lot of times when you see companies that are doing all of this restructuring where they're setting up in offshore zones or et cetera, it's usually because of some sort of a tax benefit. It might be because of the fact that, I don't know, for example, intellectual property. If you have a company that's then licensing IP to the United States, there's a 30% withholding tax when royalties are paid back over seats. So, a lot of times when you're looking at international structuring, you're trying to figure out a jurisdiction that might have a tax treaty with the United States that will create some sort of an opportunity to get rid of that 30% withholding. So, that's where things usually come into play with regard to taxes and IP. I haven't seen yet on the side of looking for courts that are more favorable to companies with respect to data privacy and data protection. I just haven't seen that happen yet because I think that it's too soon. How do companies defend themselves against claims that come out of these new regulations?  It just didn't, I mean, I'd get the concept, but I kind of understood the technical issues.  How are companies defending themselves? Do they just shut down? Do they hire you guys? I mean, obviously, lawyers need to be involved, but at some point, there's a line of where, I'm a U.S. company and someone consumes my media in Germany and then it says, hey, I'm a German citizen. You, American company, delete my records. How does that work? Do I have to be responsible for that? I mean, what's... So it's really case by case basis. First of all, obviously with regard to what I was talking about earlier, with respect to the fact that there are certain regulations in the U.S. that conflict with GDPR and the right to be forgotten, if you can actually assert a defense and sort of a good reason for why you have to maintain that information, that's step one. Step two is if it's, you know, some complaint that you receive to delete the person's information, right? There's an easier way to do it. Yeah, just do what they want. Just comply with what they want. If somebody wants to be off of a mailing list, take them off the mailing list. The third is putting in best practices. So I'm sure a lot of things that people see online, it's always great to go ahead and obtain legal counsel, even if you're consulting with a lawyer just for an hour or two, just to really understand your particular situation, take a look at privacy policies online. Take a look at the fact that cookies now have a pop-up whenever you go to a website. I'm sure you've noticed this, right? Yeah. So there are little things like this. Think about the fact that there are, what is known as click-rap agreements. So usually you have to consent, you have to check a box or uncheck a box with respect to, you know, reading privacy policy is being approved for having your email address and contact information somewhere. So use some common sense. So basically don't ignore the problem. Don't ignore the problem.  It'll bite you. Correct. And the thing is to be honest, for most people, for most small companies, it's not that difficult to comply. When you start talking about mid-size and large businesses, the next level and the next step, obviously beyond hiring attorneys and the like, is try to comply with standards and certifications. So for example, there's what is known as ISO standards. Your company can go through the ISO2701 certification process. I think it costs around approximately $20,000, but it's an opportunity to go ahead, go through that process, understand how compliant you are. And because you have the certification, you're then able to go to your customers and say, hey, we've been through this, we're certified. Yeah. Well I want to get caught to your thoughts as we wrap up on this segment. Around crypto and blockchain. Obviously, we're bullish on blockchain. We think this is a supply chain, the immutable blockchain can be a good force, although something that some work needs to be done on the whole energy side of it, which is we would agree, but still I'm not going to make that be a wet blanket of excitement. But cryptocurrency has been fraudulent. It's been the SEC's been cracking down in the US in the news, Libra's falling apart. Although I call that separate lead, but had nothing to do with that Libra. It was more of Facebook. But Telegram, we were talking about that. Others, people are getting handcuffed on this stuff. They're really kind of clamping down. But overseas in Asia, it's still an unregulated, seems to be rigged kind of market. Your advice to clients was to shy away, be careful. My advice to clients is as follows. First of all, blockchain cryptocurrency are not the same thing, right? Cryptocurrency is a use case coming out of blockchain technology. I think that in the United States, the best way to think about it is to understand that the term cryptocurrency from a regulatory perspective is actually a misnomer. It's not a currency, it's property. Right? It's an asset. It's digital assets. So if you think about it the same way that we think of shares in a company, it's actually much easier to become compliant because then you can understand that it's going to be subject to US securities laws just like other securities. It's going to be taxed just like securities are taxed, which means that it's going to be subject to long and short-term capital gains. And it's also going to be subject to the other regulatory restrictions that are inherent to securities both on the federal and state level. It's interesting that you mentioned security, word security, you know, if you look back at the ICO craze, internet coin offerings, crypto offerings, whatever you'll call it, the people who got whacked the most were the ones that went out as utility tokens. Not to get nerdy on this, but utility and security are two types of tokens, the ones that went out and raised money as a utility token, had no product, raised money using a utility that doesn't exist. That's essentially a security. And so no wonder why they're getting slapped. They're securities. Look, Bitcoin, different story because Bitcoin is the closest to being, I guess what we're going to consider to be truly decentralized, right? And the regulatory climate around Bitcoin is a little bit different from what I'm talking about with respect to securities laws. Although from a tax perspective it's the same. It's tax as property. It's not tax the way that foreign currency is taxed. But ultimately, yeah, you had a lot of cowboys who went out and made a lot of money and were just breaking the law. And now everyone is shocked when they see what's going on with this season to assist order from the SEC against Telegram and these other issues. But none of it is particularly surprising because at the end of the day we have regulations in place. We have a regulatory regime and most people just chose to ignore it. It's interesting how fast the SEC modernized their thinking around this. They really, from a speed standpoint, all government agencies tend to be glaciers, speed kind of movement. They were pretty fast. I mean, they kind of huddled on this for a couple months and came out with direction. They've been proactive and I got to say, it was usually skeptical of most government organizations. I don't think they're well informed. In this case, I think the SEC did a good job. So I think that the issue is as follows. Crypto is a very, very, very small portion of what the SEC deals with. So they actually paid an inordinate amount of attention to this. And I think that they did it for a couple of reasons. One is because you asked me at the beginning of this interview about regulation versus innovation. And I don't think anyone wants to stifle innovation in America. It's a very interesting technology. It's very interesting ideas, right? No one wants that to go away. No one wants people to stop experimenting and stop dreaming bigger. At the same time, the other issue that we've seen now, especially not only with the SEC but with the IRS now getting involved, is the fact that even though this is something very, very small, they're very concerned about where the technology could go in the future. The IRS is extremely concerned about erosion of the tax base. So because of that, it makes a lot of sense for them to pay attention to this very, very early on, nip this in the bud and help guide it back into the right direction. I think that's a good balance, a great point. Innovation doesn't want to be stifled at all, absolutely. What's new and exciting for you? Share some personal or business updates in your world. What's going on? What's getting you excited these days in the field? What's getting me excited these days? Well, I have to tell you that one thing that actually has gotten me excited these days is the fact that the blockchain and cryptocurrency industries have grown up substantially and now we're able to take a look at those industries in tandem with the tech industry at large because they seem to sort of be going off in a different direction and now we're taking a look at it and now you can really see sort of where the area is that things are going to get exciting. I look at my clients and I see the things that they're doing and I'm always excited for them and I'm always interested to see what new things that they'll innovate because again, I'm not a technologist so for me that's a lot of fun. And in addition to that, I think that other areas are extremely exciting as well.  I think something that's really interesting in the world of data regulation that actually has come out of the blockchain community in a way is the notion of data as a personal right, as personal property. So one of the big things is the idea that now that we've seen these massive data ratios with Facebook and 23andMe and the way that big companies are using individual's data is the idea that if data were to be personal property, it would be used very, very differently and technologists who are using blockchain technology say that blockchain technology might actually be able to make that happen because if you could have decentralized Facebook, let's say, people could own their own data and then use that data as they want to and be compensated for it. So that's really interesting. If the user's going to be the product, they might as well own their data, right? Exactly. Thanks for coming on theCUBE. Thanks for the insight, great, compelling, narrative, thanks for sharing. It's all right, thank you very much. Appreciate it. I'm John Furrier here on theCUBE, Miami Beach at the Bundablue Hotel for Acronis' Global Cyber Summit 2019. We'll be back with more coverage after this short break.