Then the whole town will ask why this boy never sleeps, no keeper before ever kept what he keeps. There's no telling what that young fellow will do. And then, just to show them, I'll sail to Catru, and bring back an it-cuch, a preep, and a pru, a nercle, a nerd, and a seersucker too. This is the first ever instance of the word nerd in the English language in the 1950 Dr. Seuss book, If I Ran the Zoo. But as you can see, there are six other made-up words on that page alone, and none of them want on to be particularly widely used, so Dr. Seuss probably isn't responsible for popularizing the term. Especially considering this fellow here doesn't bear any obvious resemblance to our modern idea of the nerd. A better candidate for the first real instance of the word nerd comes just one year later in an issue of Newsweek, which reads, Here we see it used in a much more familiar sense, but still not quite the way most of us understand it. Other examples of the word come soon after, and a lot of them compare the word nerd to the word square. So let's talk about the word square for a second. There's a popular etymology of the word square that claims that it originally referenced the way a conductor's hands move when they conduct a regular 4-4 beat. That origin may or may not be true, but at any rate, the word square really did come from jazz culture, where at first it referred mostly to people who didn't appreciate jazz, but it wound up being expanded to mean traditional, conservative, and close-minded. It seems like in the 1950s when it was first becoming popular, the word nerd was used more or less the same way, as a way for jazz musicians and beatniks to describe the more mainstream culture and institutions that looked down on them. It didn't mean introverted or bad at socializing, or smart, or obsessed with some subject, or even necessarily unpopular. All it really meant was traditional and boring. It wasn't until around 1960 that people started using the word nerd to mean roughly what we think of today. Now, there's an argument to be made that the idea of the nerd is much older than that. The term greasy grind had been used since the 1800s to describe students who focused on academics to the exclusion of extracurricular activities or making friends. Likewise, something we could easily call nerd culture is also pretty old. But it wasn't until the early 60s that the word nerd really became associated with the modern nerd stereotype. People with poor fashion sense, poor social skills, and uncommon interests, people whose obsession with the minutia of some topic made them boring to be around. I've read reports of it being used like this as early as 1959, but it seems to me like it took until the 70s to really become mainstream. At this point, Fonzie from Happy Days was regularly using it, and the SNL skit, the nerds, also probably helped popularize it around the same time. But then, just as the word was peaking in popularity, its meaning started to shift for a second time. I found it difficult to pin down exactly when and how this happened, but I'd say that the 80s and 90s comprise a sort of transition period during which the term nerd became less and less derogatory. It still wasn't exactly cool to be a nerd, but in TV and movies from the time, nerds increasingly became the protagonists rather than just comic relief. The obvious example of this is Revenge of the Nerds. In this movie, we're still supposed to laugh at the main characters for being so nerdy, but we're also supposed to root for them and to think that their treatment is unjust. Also, quick tangent, it wasn't until this period that the term geek comes into the picture.  While nerd referred to people who were boringly conventional, geek was a synonym for freak, to the extent that circuses would literally advertise their geek pits the same way they'd advertise a freak show. So when in the 1980s people started using the phrase computer geek to describe people who were really interested in computers, it would have sounded to them basically the same as computer freak. But at that point, since the stereotypes surrounding people who were really into computers were basically the same as the nerd stereotype, it was kind of inevitable for the two words to start converging. There are still people who insist there's an important difference, but I'd argue that at this point the two are basically interchangeable. Anyway, on the other end of this transition period, the term nerd had gone through a radical shifted meaning. At least as early as the 1990s, certain social groups were describing themselves as nerds, and especially after the dot-com boom, people started wearing the term nerd as a badge of honor. It kind of looks like once the word nerd became seen as a subculture rather than just the boring mainstream, it started seeming kind of cool and rebellious. Look at the way the characters in Big Bang Theory treat the word nerd. You can't do that. Look what you've created here. It's like nerdvana. I mean, aw, like she didn't know we were nerds. They use it to just matter-of-factly describe certain types of interests, particularly having to do with science and technology and science fiction. Compare that to the way in the 1970s, the characters in Happy Days hate the prospect of being labeled nerds. Because we belong to chess club, because we belong to cam club, because we happen to be wearing matching jackets. Well, it's terrible.  Yeah, who won? He's not important. Sometime between the two, the term not only lost its sting, but became a proud self-description, broadening to anyone who's deeply enthusiastic and knowledgeable about something. Maybe I'm just weird, but I don't think in my lifetime I've ever heard someone sincerely use the word nerd as an insult. From my point of view, someone who did so would be woefully behind the times and embarrassingly unfamiliar with modern language use and culture in general. In other words, they'd be a bit of a square.


You know no matter how much you try you cannot cure someone's depression You can't undo someone's trauma You can't fix someone's grief So maybe you need to stop trying so hard this year to do that for someone and rest in the knowledge that you did your best You see them you're available to them. You love them, but you can't ultimately change these things in someone else's life. Love you guys


Kadyrov's armoured car convoy could advance towards Moscow. Expert junior sergeant, grenade launcher of the 5th separate assault brigade of the armed forces of Ukraine, one of the authors of the book, Liquidation of the Russian Empire, Yuri Sirotyuk, in an interview with RadioNV, spoke about the significance of the raids of Russian volunteers. We are observing a very interesting phenomenon, Russia's rapid loss of its own sovereignty as a result of the Russian-Ukrainian war. Internal sovereignty, first external. Russia has lost control of its own borders. Russia's western borders are uncertain. When we are now talking about the events in the Belgorod and Kursk regions over the past week, I want to remind you of other events. Back in December last year, the FSB of the Russian Federation, together with other punitive agencies, created a special group to combat manifestations of extremism, separatism and nationalism in the Kursk and Belgorod regions. That is, there indeed were anti-Russian sentiments in this territory, if special groups were created. Putin felt his regime was threatened. Accordingly, now we see the key point that Russia, which undermined and said that Ukraine has no sovereignty, is today depriving itself of sovereignty. The key point in all this was March the 17th. On March the 17th, Russia lost any legitimate power in the form of a legally elected president. Because what is that president, who is elected in the Occupy Territories, which are not recognized by the international community, where it is impossible to ensure order in the elections? When we see that the Minister of Defence of the Russian Federation, Sergei Shoigu, and the Chief of the General Staff of the Russian Federation, Valery Gerasimov, vote, and how will that Putin-Cannon fodder vote? Hundreds, thousands of his best people, as he calls them, if they go on meat assaults, it is clear that they will not have any voting. But most importantly, Putin undermines internal sovereignty because the Russians believe that they lived in a great country that no one would ever attack, no one could invade its territory, and there would always be order, peace and greatness. And today, Putin brought the war to the territory of the Russian Federation. The military expert noted that Russia is a fragile country, and in the current situation, Kadyrov could advance on Moscow tomorrow in armored cars. Russia's Belgorod region came under missile attack from the territory of Ukraine on March 17th, Russian media reported. Some 17 apartment buildings, nine houses, and three civilian infrastructure buildings were reportedly damaged in the strikes, which were said to have been launched by RM-70 vampire rocket launchers. Casualties have been reported. It should be noted that starting from March 12, the freedom of Russia legion, the Russian volunteer corps and the Siberian battalion comprised of Russians fighting against the Russian army as part of the Ukrainian army, targeted Belgorod region. Russian fighters fighting against Russia claim that the strikes will hit military facilities and the positions of Russian troops. They have demanded the regional administration to evacuate civilians. In addition to the rocket attacks on the territory of the province, ground operations are also carried out with short breaks.


Get the convenience of one place, one price, all in one hour during the Toyota Time Sells Event at Oxmore Toyota. Shop for your new 2017 Toyota at one place. Skip the hassle of negotiation with one low price. And one hour is all it takes to get you financed and back on the road in a new Toyota. Find the one for you with Oxmore's huge inventory of new and used Toyotas. It's the Toyota Time Sells Event with one place, one price, all in one hour at Oxmore Toyota and at OxmoreToyota.com


Welcome to the ITU studio in Geneva, where I'm pleased to be joined by Fabio Cavalliere, the rapporteur for Question 6 within ITUT Study Group 15. Question 6 is a working group that looks at characteristics of optical components, subsystems and systems for optical transport networks. Fabio, thanks for joining us. Thanks for giving me this opportunity to illustrate the Question 6 work. Now, as end users, we see on our phones 5G, we typically are on the move. Could you explain the importance of optical networks to all the services we enjoy today? They're of key importance, but perhaps not that apparent to all users? Yes, they're correct. We all use smartphones in our life, but a few people know that behind this technology there is a capillary user infrastructure that is made of optical components, fiber and system. And this is exactly what Question 6 deals with. And what happens is that with 5G, the challenges for us became higher and higher because 5G is pushing for new demands in terms of bandwidth, new demands in terms of real-time services that decrease the latency. And these, of course, add R&D challenges that are not easy to deal with, and there's also standardization challenges. And it is not easy to take these challenges because in any access segment like the 5G mobile transport, the cost must be low, but it is not easy to keep low the cost in presence of such a formidable complexity that 5G is asking to optical networks. So new topologies, new architectures, new requirements like the need for the network to self-configure. So you need just to plug and play your equipment without any expensive and long configuration. You need to be fast and accurate. And this is the challenge we are taking in Question 6. And standardization can help in this, definitely. All right. And Question 6, the particular role that you play, the value that you deliver industry, could you describe that? Yes. Optical systems, as I've said, are the motorway on which information travel. And Question 6, take care of standardizing optical equipment for transmission of optical signals. So switching the optical signal, routing optical signal from one side to the other, or to your home, in some cases, and of putting these all together with the other layer of the networks because there are, of course, different levels of processing that the optical signal must undergo. And you need to take care of the interface with these aspects that are, of course, taken by other questions. So in other words, we specify the interface of these optical components toward the optical fibers and between them. Modulators, optical switches, transmitter, at 100 gigabit per second, or even more today. And what are some of the specific areas you work on, the interfaces that your standards address, and perhaps also some of the new work you're looking to complete? Yes. A recent example is the standardization of 100 gigabit per second. Then the wavelength division multiplexing system is a complex name, but basically means that you use different wavelengths, different colors, so colored colors to transmit different signals on the same fiber. So you have a huge aggregate capacity in such a way. And each of these colors, of these wavelengths, has 100 gigabit per second transmission speed. And this is not easy because optical fiber, as any propagation medium, introduces distortion on your signal. You need to compensate for this distortion. And of course, this is the first challenge. The second challenge is that you need to compensate for these distortions in such a way that equipment that belongs to different vendors are interoperable each other. And this is where the standard, question six, as a value, was not easy. But at the end, we succeeded in releasing this recommendation. And now, looking at the future, the work is continuing. We are looking at the four-time higher capacity, 400 gigabit per second interfaces, and 800 gigabit per second interfaces. And thanks to our optical experts from all countries worldwide, I pretty confident we will succeed in that. Thank you very much. Thank you. Thank you.


I'm Grady Edwards with Beau Gorszewski. Welcome to DISCAST, a podcast from the Ori County School's digital integration team. We believe that educational technology can be used to transform teaching and learning in the classroom. We strive to spotlight the good work our teachers are doing across our county and hope our discussions will inspire possibilities for your classroom. Your journey into the world of edtech starts right now. Say test a couple times. Get your voices working. Testing, testing. Testing, testing. I am Cass. Kangaroo. I'm Samantha. I'm Grady. I'm DJ. I'm Abby. I'm Gabby. I'm Karim. I'm... Come to the DISCAST. Welcome to the DISCAST. We'd like to thank you for tuning in to today's episode. If you're new to the DISCAST, we are edtech specialists looking to promote the fantastic work taking place all across Ori County Schools. Be sure to check out all of our previous episodes and, as always, don't forget to subscribe, like, and spread the word. If you're a returning listener, welcome back. We have a very special kids take over episode today. But before we get to that, let's recognize our tech innovators of the month. Thanks, Bo. Let's start as we always do by congratulating our tech innovators of the month for April. We know we're a little behind, but we want to make sure to give a huge shout out to Nicole Peters of St. James Intermediate, Kim Weissong of North Myrtle Beach Middle, and Jennifer Meyers of Ori County Education Center. Great job, April Tech Innovators. I'd also like to take a moment to thank Ms. Candace Lane for her assistance with our podcast, Audio. It was really great to have someone with her musical background and expertise to train us up, if you will, with some of our audio settings. Thanks, Grady. I tell you what, we have a great episode lined up for you today and another great interview with two fantastic elementary teachers from Riverside Elementary School. But before we get to that, let's talk about how some of the Discs were inspired by students. Students, you say? Like which ones, Bo? Well, you know, Grady, if you followed Dear Discs on social media, I got to see some videos and student samples of podcasting from Anna King's and Whitney Cook's classes. These students were doing book reports and interviewing a partner to learn more about the book. That's great. I haven't heard about such great collaboration since I talked to my folks at Loris Middle in our Discast episode five. Well, anyways, these students were amazing. I love inflection, their voices, and I can tell a decent amount of planning and thought was put into the projects. Maybe these students were inspired by our episode two podcast where Jenny Leckie informed our listeners on how to get podcasting started in their classes. Well, luckily our very own Megan Quillen informed us about these projects and she was able to sit down with Ms. King and Ms. Cook to find out a little bit more about their projects and podcasting. I also would like to give a shout out to our fellow Discs, Holly Jackson, who was a huge help with teaching the students some garage band tips while you and Megan did your interviews. Nice. Now let's take a listen and hear what these students and teachers have to say. Hey, I'm really excited to be here today at Riverside Elementary and I'm sitting here today with a couple awesome teachers and they're going to introduce themselves really quick. I'm Anna King and I teach second grade. And I'm Whitney Cook and I teach first grade. And today we're here to talk a little bit about how podcasting is starting here in elementary school and we're just really, really excited to hear that students are able to take their devices and to create something that allows them to put their voice out there. So when you first started getting started with this podcasting in the very beginning, what were some of the thoughts or your initial thoughts or ideas as to how you were going to get this started with your students? I'm assuming that this is somewhat of a new idea for elementary school. So give us just a little bit of an idea of what your initial thoughts were and kind of how you worked through those to prepare for podcasting for the first time. So at first I listened to Jenny Lecky's podcast with the Discast about podcasting and she has older kids but I was trying to think to myself, how can I bring this into a first grade classroom? And at first I was like, okay, there's going to be a long process of this.  So I kind of just first started thinking what did I need to teach them about podcasting and how was I going to implement it into our curriculum and meet our standards. So we kind of first just started out with reading a story and then responding in a podcast form and it kind of led to bigger podcasting projects that we've done in our classroom. Yeah and I agree. I listened to Lecky's podcast Discast with you guys and I was inspired that she mentioned bringing it down to that level. She said to use split grid or padlet and so I had thought about using that as well just like Miss Cook had mentioned just responding to something like that. And I agree I thought it was going to be a big long process but I was proven wrong a quick introduction and giving them some background and they were often running. That's awesome to hear and a lot of times we hear that with students. You know teachers take this time to prepare and they're sometimes shocked at how fast and how quickly students are able to pick up and run with it. So it sounds like that's the case here with the podcasting in first and second grade. That's awesome. So beyond using podcasting in your classroom for students to work on the curriculum or whatever standard it is that you're focusing on that day what are some other areas that you feel like podcasting has helped to prepare your students with or some other other skills that it's helping your students with. I think it's helped with teamwork just being able to collaborate or collaborate yeah together and they had to work as a team it just could it wasn't in the beginning we did our podcast and it was just their podcast where they were just speaking and then we introduced them to having two people on their podcast and so they had to kind of feed off of each other and know what to say next and we actually ended up using scripts for our really big podcast that they did and I think they turned out pretty good. I love that and I love that you took it in steps like you allowed them to kind of do something non-academic first by themselves and then took it to a partner and then a much larger project including a script and I know some of your students earlier when we were talking with them we're talking about how the script was one of their favorite parts and so I think that that allowed going that that route that process really allowed the students to appreciate every step of the way instead of expecting them to do it all at one time so that's awesome yeah we um I I agree with miss cook the collaboration was a big piece also the communication being able to communicate and speak they learned a lot of different skills on their iPads and practice that as well awesome so if you know after this this discast there might be some other elementary schools and students who want to get started with podcasting in their classrooms and if you had if you were able to give them any advice what would be your words of advice or wisdom or any tips for success that you give other teachers that are looking to do some podcasting in elementary school I think um just go for it I mean don't be hesitant don't be nervous it was a learning process for my students and I together so just take it as that and I think that your kids will be relieved to know that you're learning with them so don't overthink it and just do it I would listen to that podcast or that discast that Jenny like he was on I think that really inspired me and I know when miss cook started it that's what made me start so I think you know hopefully listening to this can inspire you to know that somebody's already done it so I can do it too yeah I say just go for it too um you know listening to Jenny like he's podcast and then bring bring podcast into your room so if you go on iTunes they're even for the younger primary level there are tons of podcasts out there that you can just show to your students and they can kind of get the idea of what a podcast is but you'll be really surprised that if you just let them go at it the first time it's like they're already in the zone for it they introduce themselves and they show you to subscribe and like at the end and you don't even prompt them for those kinds of things but they just do it and it was amazing to watch how they it just clicked for them um so take those podcasts in your room just show them and just go for it and don't be afraid to fail because we all learn through failure yep I love that we listen to a joke of the day in our class that we found on Apple podcast and they love listening to that so they get to hear podcasts every day and be able to listen to that intro and all the different pieces of a podcast and so that's really excited them to hear it very cool that's a great idea to give them exposure to those and we'll for our listeners we'll make sure we put some of these links to these podcasts so that you have them available and you all both you both touched on an awesome thing so one thing that I'm always inspired on inspired by in education is teachers learning and taking from other teachers right and so I've heard a couple times you all reference our Teacher of the Year Miss Jenny Leckie who did a previous discast which was awesome so for our listeners if you haven't heard that one definitely go back and check that one out but I also heard it was episode two oh episode two yeah episode two thank you for that um I also heard that um Anna you said that you really kind of jumped on board with this after Whitney was using it in your classroom and talk a little bit about how here at Riverside you all are sharing what you're doing in your classrooms because I've heard some other teachers in the building asking what y'all are doing as well well we have something called the pineapple chart and so we were able to share some of our podcasting and script writing and the process and some of the videos and what they've completed and so we post that on the pineapple chart and then other teachers can check it out and listen or they can stop by the room and see it in action so we hope that that happens because it's always nice to see it done and then also sharing it on social media obviously that's where we heard the discast and listened to Jenny Lucky so on twitter and whatnot really cool and it also provides like that authentic audience for your students too when people come in to watch them as well very cool um so changing direction just a little bit one one thing that us as teachers right we're always tasked with the test and making sure we're always content driven um and so when we're being held accountable for our standards what is a way that we can justify or how is there a way for us to justify using podcasting in our classrooms so how are you all able to use something like podcasting but still make sure that you're covering your standards and all the things that we're held accountable for I mean I don't really think there's any justifying I mean it's we're teaching the standards we're teaching you know digital content standards we're teaching story elements we're teaching communication standards inquiry standards I mean we could go on and on and sure miss cook has lists of them lists of them as well so I mean we're just jamming so much in by using podcast or any type of app and technology I just think you know they can always write with pencil and paper but verbally voicing their ideas and their thoughts whenever we reference a certain skill like main idea I mean you're hitting all of those skills whenever you're making a podcast just making them think about a topic the skills are just already embedded so like Anna said there's no justifying it's just happening without even knowing it that's amazing it's just it's such a joy to hear that you're able to find such an easy connection between the two um and I love it because you're right I think there is something to be said about student voice and when we were interviewing the students they that was one of the things they were most proud of as well is how it it gave them that that student voice so that's awesome I think teachers they are hesitant to do a lot of technology and even podcasting something so new and unsure about it but it's so it's really I think it's actually been fairly easy to put in ELA standards or writing or you know writing standards communication standards they all flow very easily with podcasting I think it worked out great so excellent that's so good to hear so um just in general just for our people who might be getting into podcasting for the first time I know you all just started off very basic what just give us an idea of the equipment that you and your students did use so what devices what was kind of the workflow for when students were actually ready to record did they all stay in one room just that just the kind of the logistics of how you all ran that first podcasting in your room so in our classroom we first used padlet because it was just a read and respond type project that we did and so after reading the story I kind of sent them back to their seats and I made them jot down their notes about what they wanted their response to be so they'd have something in front of them so it wasn't just on the fly but then I kind of just I just spread them out around the room but all we had were their iPads and they just recorded straight to padlet and um it was it was great it was simple later on we added the recorder app just where they could record their voices so we could upload it to different places like to our seesaw or I wanted to post them on twitter that just made it easier making it in the recorder app so just an iPad ourselves that's all we had and that was the same with us we used our iPads and recorder HQ I think it was we used and like Whitney said we uploaded them to seesaw but you know we don't have the fancy microphones we didn't have a quiet area we just kind of scattered ourselves in the hallway went in the bathroom in the classroom and cracked the door and just found quiet places to be and really didn't have anything fancy so and it works and I know we are going to try to take it to the next level so using garageband to create an intro with music would be the next step so nice and that actually that's great because that actually leads me into the next question is um so I love first of all that you didn't overthink the process of preparing for this like you didn't wait until you had all the tools to be able to do it you just jumped right in with what you had and students got used to it so now that you have gotten your first one or two podcasts under your belts are you your next steps with podcasting um what what do you kind of see do you do you all feel like uh eventually your students will be able to put their stuff out there to a different platform for maybe a different audience or what are your next thoughts or steps with podcasting in your classrooms well the school year's ending so we and my class we are trying to make a second grade like mrs king's podcast we actually have kind of voted on a classroom podcast name I think we're going to be kap cap king's awesome podcasters so check us out if when it gets out there but um we're going to try to um focus our first few episodes we're going to focus on getting the second or first grade first graders ready to come up to us by teaching them expectations and the cool things that are in second grade about different things that they can be excited about when coming up so I think that's what we're going to do um like I said we're going to try to work with garage band and get an intro and kind of just take it to the next step in that way um great idea yeah that was the music piece at the beginning the intro and the ending my kids have wanted to add music so that was going to be our next step but they also want to know like how they can get their podcast on iTunes like the other because there are kids down there that have podcast and they're like well how do we get ours on there because they want to take them home and just be able to listen to them so that's our where we're headed I think like they for them to hear that they can put it on apple podcasts or youtube can we see it on youtube mrs king I think that they're really excited about that so like miss cook Whitney said just to be able to have other people at home and family members and friends here what they've worked so hard on absolutely well we are really excited to see both of your classrooms in your podcasts come to life and we will be your first subscribers for sure awesome so keep us posted on all of that and is there anything else that you wanted to share or anything else that that you wanted to kind of leave our listeners with about podcasting you all definitely covered a lot of stuff today and we appreciate you really taking that time to reflect on on how it was successful in your classroom are there anything else that you wanted to share before we kind of close out oh like I already said just go for it yeah the kids love it there's no hesitation it was a great experience and we're excited to just keep on moving along with it yep you're going to be excited what your kids can do that's right yeah well thank you ladies and thank you so much for our listeners and again if you're looking for the disc cast episode number two with Jenny Leckie make sure you go back and listen to that one and we'll also put in a few other links that were mentioned here by miss my miss cook and miss king so thank you very much and we're excited mega was even able to sit down with some first and second graders from Riverside Elementary to talk about podcasting in their classroom let's listen in so you're fairly new to podcasting can you tell me so far what has been your favorite part about being able to podcast in your second grade classroom my favorite part about podcasting would probably be being to be able to do it with a partner because i like to do stuff with my partner a lot if you could choose one thing to do your next podcast on in your classroom with miss king what would be your next podcast what would be what would be the topic or what would you want to podcast about my class and what what about your class that they're the best thing in the whole entire world i love that i love that you all have been playing around with podcasting in your second grade class with miss king and i want to know so far what has been your favorite part about podcasting in class with your teacher working on um definitely working on my speaking voice cool and elaborate on that a little bit what do you mean by that working on your speaking voice expression like the good and good amount of expression expression and like the voice fluctuation as well yeah equivalency definitely very cool love it how do you think podcasting can help students in classrooms with their with their peers and with their teachers so thinking thinking about all the personalities you know that you have in a classroom you have some people who are really shy you have some people who are really energetic and want to talk all the time right so how do you think using podcasting can help in a in the classroom um maybe you can help in the classroom like maybe it can help like to be more serious because you know you don't want to be like you don't want to be all like boom and a podcast you know yeah time to be serious but i'll be putting all your thoughts somewhere yeah but the right right amount just the right amount funny and serious i like that the right amount of funny and serious a good balance okay it could help people with their um voice okay what do you think um i think it helped people like learn new things like if you were an older kid and you made a podcast you could ask your teacher if you want to interview it to other um smaller kids than you so they could learn new things i love that idea so so your audience could be younger students to hear some of the things that maybe they haven't learned yet that's a great idea you think podcasting can help classrooms like a second grade classroom or a fifth grade classroom what are some things you do while you're podcasting that you think can help almost every classroom if they if they tried to the podcast in their room get a good speaking voice speaking voice and what do you mean by a good speaking voice like loud and clear not why is being loud and clear and having a good speaking voice important so people can understand what you're saying and hear correctly what you're saying i agree with ty because like if you didn't have a good speaking voice many people wouldn't know what you're like trying to say wow what an interview thank you Riverside students and mrs cook and king for their time today be sure to continue to follow their adventures on twitter with at anna underscore king 001 and at wn cook make sure to check out our dear diss on social media like instagram twitter and our facebook page to see some of the highlights from our other schools in ory county also be sure to check out the vodcast version of our episode of youtube the first person to leave a comment get some hcspdl swag oh man some hcspdl swag don't want to miss out on that well unfortunately it looks like right of time remember all of the resources discussed in today's discasts can be found in the description of the youtube video you will find reference tools audio files and a transcript of this episode let's head back to our riverside podcasters to close us out my name is oi my name is my name is camera my name is my name is carter to continue to follow our story please subscribe to the discast thank you for joining us today and always remember in the words of george kuros technology will never replace great teachers but technology in the hands of great teachers can be transformational see you next time thank you for watching this tutorial be sure to subscribe like comment and follow us by clicking on the links below in the description


Let's get rolling here. All right, so we're going to talk about continuous security with Docker. And our company has been using Docker for several years now. So this is kind of a culmination of stories and experiences that I've had through the lens of trying to get our company to take Docker to production and bring security to that realm for us as well. So starting off here, I want to see for an audience poll, how many people here use an automated build system for Docker? A lot awesome. I've asked this before, and there's been one hand in the room raised, and I'm like, ooh, that was a couple years ago, right? So how many people have Docker containers in production? Like, you have a customer-facing system run on Docker, and it is out in production. All right, cool. Still a good number of people in here. That's good. And next, how many people have implemented some sort of automated security measure for Docker? Like, you're scanning your APIs, or you're looking at the layers to see if they're vulnerable. Still a couple hands. A few less hands. But yes, I see one in the back there as well, perfect. And then this next one, I can really tell the people who have gotten really deep with the Docker engine and worked with it and such. How many people have found a breaking API change and a patch release of Docker? Yes. You're banging your head against the wall, and they're like, it's not supposed to break. Yeah, it was a couple years ago I was at DockerCon, and one of the engineers for Uber was giving a talk about pushing Docker to have more performant GoLang code. And right before the talk started, maybe a couple hours before he upgraded his Docker engine with a patch release, and suddenly his demo just didn't work at all, like fell flat on the floor. He looks in the front row, and he's like, what happened, Docker? What did you guys do? And then he just, like, read in the face smiling. It's really funny you use Docker a lot. Eventually you're going to run into something like that, right? So Docker at Workiva, you start out with a lot of smaller deployments at Workiva. We were starting on version 0.7 of Docker, right? So we are building the Docker files on our laptops, pushing it to a registry, things like that. So it's pretty small. You might grab an internal tool for your company and say, hey, let's test out this cool new tech by dockerizing this internal tool that builds code, or pushes code up for us, like, all right, that's how we started, right? So you get a couple of containerized tools that way. And our first bump with security there is when we were taking one of our systems and dockerizing it. We talked to a security auditing firm, like a really nice small boutique shop, really super good at web app penetration testing. We come in and said, all right, we have this really small internal web app we use to track some statistics. Why don't you guys just do a test of it, see what you find, let us know. And it was part of the onboarding meeting for that. It's a completely dockerized application. And they'd never heard that. They're like, dockerized what? They hadn't heard a docker. But it didn't really matter. They still popped our top, grabbed some data out of our database, right, showed us what was going wrong. So they're like, ah, god, right? And one of the engineers on our team was like, but they didn't get root on the server. You bought two box was fine. Like, well, it doesn't matter, right? They still grabbed all your data out of the database. Who cares if they grabbed root or not, right? So the first little bump showing you that just because you have a little bit of obscurity inside Docker, you're not necessarily free from any vulnerabilities or security problems you might have, right? So then it gets a little bit bigger. Docker started getting more mature as a platform. There were more companies offering tools and methodologies for that. And so we started taking an even more serious look at, like, can we get some of our more production applications in this platform? Are there tools to help automation to push this out, clustering it, getting it running? And so you start getting several containers for a system, right? You start taking a look at microservice architectures, rapid deployment, redundant failovers, things like that, right?  Our dock deployments are getting super complex. Moving forward, everything in production for our application is going to be dockerized. We're going to have hundreds of thousands of containers, multiple data centers, failovers in different regions, things like that, right?  It's kind of what happened to us. Rikiva exploded. If you know me, I love Iron Man. I always got to try to fit a gif of this in. But it wasn't a good way, right? So we were completely bought all into the container story, started having our entire applications, like I said, built on this. And when you're going that direction, you kind of got to ask yourself, how do companies, Rikiva or not, deal with security threats inside this, right? You can almost think of docker as an abstraction layer. How do you deal with security inside your container when your entire platform is now built inside here? You're shipping it differently. You're building it slightly differently. What really changes? So let's dive into this. Why is security a little bit different inside docker?  But for some of the folks a little bit newer in the room to docker, I don't want to just skim over this part. You have a complete shift in the application architecture. So previously, how you have is that you have VMs you're installing for every one of your applications, right?   And then when you move to putting your application inside a docker, right, you're sharing kernel space, your application libraries a lot of times can be shipping with your docker containers.  And it looks a little bit more like this, right? You might have your host OS being CoralS or Debian, Ubuntu, Windows, things like that. And you just have hundreds of applications sitting on the same server now. They're completely shipping with their entire set of problems they need to run. So that's kind of how the game changed overnight in terms of what you need to focus on in terms of security now. So what I want to run through today is kind of the maturity of Docker security that we went through as a company, where we started out at and where we are at today and some of the tools we've used to get there in methodologies. So starting out here, running containers in production or looking at the viability of running containers in production, if you're a financial services company like us or any type of regulated industry, you might have to solve some of these security challenges before you can get to that step of being in production. So you might have to look at, you might not be able to start at just pushing production, figuring some of this out next. But getting containers running in production or in a development environment, right? Getting that situation figured out for your company. And next, creating this automated, immutable infrastructure. So that's like one of the most beautiful things about Docker, right? You can ship your container anywhere and it's identical across the cloud, across your data centers, et cetera. It's great. It's a good tool you can use to leverage. It can be really bad if you ship bad code. It's going to be identical everywhere and vulnerable everywhere. We can also use that as a tool to know exactly what's running. We'll talk more about that here in a minute. And then passive data collection. We found, actually, with Docker it's a lot easier for us to figure out what libraries and tools and code are running inside our containers way quicker and more efficiently than we did deploying applications, the more classical way with tools like using JustChef or JustSalt Stack and putting it on a raw Ubuntu host, for example. And we're going to talk about active scanning. You have your containers out in production now. You have some automated way of building and pushing it out there. Now we need to do this continuous scanning to see what's going on inside our environments. And we'll discuss a couple of methodologies for that. And then the automated rebuild and redeploy. And I kind of see that as the pinnacle of what you can get at to Docker security. You see what's going wrong in your platform. You identified that with a bunch of automated tools. You get a rebuild and you redeploy and push out either bug-free or vulnerability-free code. So starting out with immutable infrastructure. So when we started using Docker, we just built on our laptops, like Steve's like, all right, I'm ready to push my code. I'm just going to pull master from GitHub, do a Docker build, and Docker pushed to our registry. And that is unsafe for a number of reasons. But one of the biggest ones is he might add anything. He wants that doc container thinking it might make the application work, thinking he's just going to fix a bug really quick on the way out the door. There's just a lot of processes that can go wrong the more manual things are. So the first step that a lot of you that are using Docker are like, I use a build system, right? Awesome. That's the biggest key first step that you'd be surprised that I've seen a lot of people that are still building locally or building on their laptop, especially when they're just getting new and into the space and introduced to using a Dockerized platform. So there's a ton of options out there, everything, from Jenkins to CircleCI and even Docker Hub, you can push your containers up there and you can push your code and Docker files up to GitHub and Docker Hub will build them for you automatically, right? That's awesome. But a key thing to be aware of is once you build an image, once vulnerable, always vulnerable. So in an immutable infrastructure where your code should not change, once that container is built, it is there that way forever. Like when we started running Docker, I'll admit we occasionally were like, let's just jump into that container, do an app get update and upgrade. We're good to go. We're only wanting one container for this application. It's all set, right? So that's not really a good route to go, right? Because something might go wrong and it's not caught in your unit test. It's not caught in smoke testing as easily, right? So we don't do that anymore. If it's not built by CI, it's not running for us. But that also means if you build a bad version of your code or you have a CVE, like hard bleed, you build it in that container, it's always there, right? So it gives you an idea that your containers have a shelf life. When we, everyone containers in the past, you get a microservice architecture, you know, that idea that your code does one small thing very well. So when you succeed at that and does it very well, there's not a lot of updates to that microservice, right? So that container might sit there for six, eight months because you didn't have to make any changes to it. Well, in that time, God knows how many system libraries are now vulnerable and have CVEs published. So we'll have that thing sitting out there for a while and we realize like that's not great. You know, you can't really, you gotta really be aware of how long these are sitting out there and make sure you're continuously rebuilding and redeploying these, even if you don't have an automated vulnerability scanner, you know, every couple of weeks, just make a new container, deploy it out there, patch all the bugs that might be in system libraries for yourself. So for example, for us, once we're doing this, you know, how does your company respond to G-Lib C? You know, for us, what really happened was security came to us and asked like, hey guys, G-Lib C is a thing, shell shock's out there, what, you know, heart bleed, et cetera, what's impacted? And at this particular point in time when our company says to you, you're like, I don't know, it's some of it maybe, we'll see. And so if you've had, you know, the DevOps culture type of thing in your company, you've probably seen this mean before, right? Either you or security has had this, I know Jeff Smith has had this in Toxies had before, but you know, sometimes you're like, we're just pushing stuff out really quick and forgetting about it and, you know, creating all these security problems. Well, in this case, it was actually exact ops that way around. Security's like, you don't know what's running out there?   And so we're sitting in the conference room for like 72 hours or so, right? You know, like taking shifts, rebuilding, redeploying everything.  So, you know, you have your postmortem, your sprint review, you try to figure out what did we do wrong here? Why did we take so much time to fix this? What could we do better? And like Bill Weiss was talking about in his talk yesterday, anytime you have security incidents like this, and you have to dedicate engineers for two, three, four days to solve the problem, like you just lost four days worth of development work that you could have been pushing out features to your platform, you know, more automated tooling for deploying or fixing bugs, et cetera. So out of this situation, we came to the idea that, you know, let's do some passive data collection on these Docker builds. Next time security comes knocking on our door and says, we got a vulnerability in our platform, what's affected, we can be able to answer that more easily for them. So, in our situation, we can even avoid this idea of initially scanning prod, right? You don't have to, you know, set up Nessus or other tools and just try to point them at a host and scan everything and hope it picks up a problem in your API or they come out with a, you know, feature plugin due Docker. It's like, well, great first step is just know what's inside your container. So we wrote a plugin for a build system that literally spit out the list of app packages and Python packages that are sitting inside your container. It sounds pretty simple, but it's super powerful. So after you just do like, if you can see on the screen here, this is just an output from an actual build system. It's literally doing a DPKG dash dash list, spitting out a giant list of app to packages, storing them off in a SQL database. And then same with the Python package order, you know, pip list, pip freeze, grab list the Python libraries and versions you're using, throw it in a database. So security comes to us and is like, what version of XYZ library are you running? Like just hit our API endpoint, you know? Check it there. So you have this entire record of packages for every container and we map that back to a tag. You know, so what we did in our instance is we let the build process go all the way through and finish and build this container, right? So as soon as container is finished being built, you just write this small service that does a Docker run on that container, runs those two commands, stores the output and puts it in this database and then you can, you know, use anything from a Flask app to, you know, API gateway and Lambda to be able to query this database and you just tie your list of packages to a list of Docker images and tags. So you can tie these two together. So on top of that, to be even more powerful is we have an API endpoint in our production system so they can look at what containers are running in prod, right? So we're running in the Amazon cloud, we're using ECS to run our containers so they can go out there and look what version and tag of an application is running in production, cross-reference that against a list of packages in the database and say like, all right, this one needs to change, this one does not. Instead of three days in this war room and a cake from the head of your security team, you have like Steve like hit a couple buttons where you build a few containers and you're good to go, right? You didn't like lose an entire sprint to a security bug. So like literally those two commands being put into a database like saved a world of time for us. All right, so the next part of this is I wanna talk about semi-active scanning and we have kind of a couple different flavors of this. You know, we have your traditional style of active scanning using things like Nessus or Rational App Scan or a lot of those tools in the market. But then also with Docker, and we have this idea of it's a completely immutable infrastructure. Does it make sense to scan every identical copy of something? Maybe, maybe not, well, we'll give it a shot and find out. So this is actually really important for us especially as a financial services company when you're operating the regulated space. A lot of these are required by compliance standards, right? So you wanna go for your PCI audits, you gotta do PCI DSS scans on a regular basis, save the results, be able to supply those records to auditors, et cetera. For us right now, we just recently announced that our company is gonna be going for FedRAM compliance rights so being able to sell our products in the federal marketplace. So what's interesting about that is the same kind of thing. You have an entire Dockrise platform, still have to do a lot of these automated scans in production and a couple of our security members went out there and started trying to talk to auditors and vendors for FedRAM compliance saying, hey, we're looking to do this thing as a company. We're going, building roadmap and working on this right. What tips can you offer us? What tools do you have? What things can you give us to make this process easier? Because they're reading the controls in this particular audit and saying, we need to scan all the platforms that our applications are running in. And so they pretty much posed the question, we're not running SSH inside our Dock containers. Nobody's running SSH inside there. These security tools can't log in and do an authenticated scan. And I think that was the term that was used in this particular controls, like the authenticated scan, right? So in the past when we were running on just like a raw Ubuntu host, USSHN scans the box, everything's good. Ship that report off and now it's like, well, USSHN scan the box, but our app's not running there technically, right? It's all package-in-sized Dock containers that's not getting scanned by that. So it's not the same exact thing. So I think it was like five or six auditors we talked to and five of them were like, weird, you should just put Nessus on the Ubuntu box and scan that, it's like close enough, right? And then our security team, being who they are, they're really passionate about what they do and they're not gonna settle for that answer, right? Right, that they're saying, well, it's technically gonna check a box, but in the spirit of this control, we're not doing what we're supposed to do, we're not actually providing security and value to our application if you're just saying Ubuntu is secure, right? So trying to get an idea of how they can look and peek inside what's actually in your container to pass these audit standards, I'm gonna come up with this idea of semi-active scanning and I'm gonna jump into the minute of some of the, in a minute here, jump into some of the tools we've used for this. But first, another one of the reasons that I, when I worked at jobs, you know, doing pen testing in the past or web application vulnerability assessments, things like that, if you try to like scan or run vulnerability audits against production continuously, people in operations get pretty nervous a lot of times, right? So active scanning can be really bad. So I stole this picture from another presenter that was at DockerCon several years ago. He was using it in the context of debugging containers, but I thought it worked perfectly for, you know, assessing the security containers in production as well. So this was the container ship that MOLComfort, it was sailing through the ocean out of nowhere, it's hull just snapped in half and relatively calm seas. And then next it just set on fire. The crew jumped out, got on life rafts, went to another boat and then the thing just sank like 13,000 feet. Like, well, everybody made it out. We're not really gonna spend a lot of time figuring out what happened, that just fire just happened. It's okay, cool. So that's happened to me before when I'm like assessing web applications. Like the first thing I do is like, you know, you open up Burp Suite, you might open up Durabuster, you just start fuzzing this application, trying to like traverse directory trees, see what's all is there in the application.  I think I knocked over this company's production, right? Like, dear God. So when you're looking at Docker, you're like, well, I don't have to like scan and knock over production potentially, right? Like when you're, the operations team, the security team, you don't always have the luxury of making sure these are the most robust, non-fragile applications, right? So for us, we used by semi-active scanning, we were able to take a Docker image, push it to the registry, use the Docker feature of the content trusted registry and their notary tool and you get that cryptographic signature of what is pushed up by your Docker client that pushes that registry. So your build system finishes an image, can cryptographically sign it and push it up to your registry and then when you have a security system pulling down to scan this image, you can say, what's running in production? Let me hit an API endpoint. It's gonna give me the name of a Docker container with a tag. I can see what the signature of that container is, compare it to something that I just pulled from the registry and make sure that signature is identical and we'll just scan that way and then we can say, yeah, see, I can cryptographically prove this is the same thing running production that I just pulled from the registry and scanned on a box that's, you know, on the security team owns, right? So for us right now, we're using a tool called Clare, made by CoreOS. So this actually provides you an endpoint where you can just give them a container name and a tag. They'll pull it down. They'll do all the scanning for you. They are backed against the MITRE CVE database, right? So that gives you an opportunity to just have all the CVEs that are published out there immediately available to be checked against. So this is a great tool to use and I've actually had people that I've talked about this before say, well, if you have this active scanner that's looking through all your dock containers that are in production, why are you guys still like pulling all this metadata about your containers, right? Like if Clare can just say this has a CVE or it doesn't, why are you still storing the name of every package built in every container, right? Like that's a very fair and valid question. In reality, sometimes when these vulnerabilities hit, you know, you see a hacker news post or proof of concept code dropping and say, hey, I just like rocked the open SSL library and here's my proof of concept code of how you do it. And people are like, you know, scrambling around trying to find patches for it or trying to like make the patch for it, right and release that. And sometimes there can be a little bit of leg time between when proof of concept codes dropped when the patch becomes available to you put in your environment. And in those situations, you know, it gives everybody a lot more comforting feeling when you can say where and how you're affected before any patches are available. So before, you know, CVE is officially published and recognized by a scanning tool and scan your environment. You know, you might be able to see a news post or something about one of the researchers of that bug saying these are the versions of the libraries that are affected. You can still look in your environment and say, all right, this is super critical.   Nobody outside the company can get to it anyway. We're just gonna keep running it. It's cool. We'll wait for the patch to become available in a couple of days and we'll go about our business, right? So in our environment, you know, it gives the ability to go either route.  So other than this tool, there's a lot of vulnerability scanners out there. When we first started using this, this is one of the, Claire was one of the most mature and robust tools, but now like, you know, you do a quick survey and there's just a ton out there. You know, these are just four of the ones that I played around with and tested myself. You know, I was relatively happy with every one of them. Like, yeah, that does a good job. It'll pull down your container, look through the image layers for everyone, tell you what CVEs match up in there, if any, and you know, generate a nice, pretty report for you. So other than that, like a quick Google search for Dockervano vulnerability scanners, like a hundred more than there were last year. It's really cool. You know, it really shows you a lot of people are taking this security of containerization a lot more seriously, which in turn makes it a lot more easily doable in large enterprise environments and getting your containers to production. Like the first day when they asked like, who here works for a 10,000 plus person company and a ton of people raise their hands? Like this is great for those type of companies, right? Cause sometimes they have, you know, they're really a lot more mature than a startup. They have a lot more requirements and concerns on security than a younger company would. So this is gonna help them out a lot as well. So looking at this and the development life cycle, and I'm literally just taking this straight from our handbook of how we started looking at pushing our containers and how we do now.  And you do your Docker build through your binary or your code into a container and then ship it out and deploy it to production, right? And so when you're adding your security measures in there for our environment today, it looks more like this where we've added a couple more steps in there where we have right after the Docker build that image audit. And then after the image audit at the very end, you have that semi-active scanning where we're taking a look at all the containers running production and scanning a copy of them as well. So that's why, you know, that's how like actually throwing that in your, you know, standard operating procedures of the SDLC is really gonna help paint the picture for how important security is in your environment as well. So these are kind of some of the concepts that, you know, we just went through here talking about this today. You know, I found that a lot of times after I go to a meetup group or something like that and talk about this, a lot of the smaller conferences and places like DevOps days, there's a lot of great conversation that comes on this topic afterwards, you know, grab a drink and a beer. A lot of people have had some really good ideas and I've actually, some of these scanning tools actually figured out about at other conferences and meetups and started testing them out at our company as well. So after going over this, the question kind of is like, what's the way forward, right? We talked about a couple of different tools we can use here.  They're just gonna throw these buzzwords at you where cloud encrypted docker with a seem scanning DLP, right?  A couple, I was a month or two ago, one of the people on our security team got a phone call. You know, one of the fun cold calls from a vendor that everybody loves to get saying that, hey, we got this great storage solution for containers and disk and disk space in general. And the best part about it is we write our own encryption that's better than AES in-house so you know what's good, right? And he thought he was gonna be like a little cheeky and he's like, so you guys work with like Bruce Schneier? That's great. And the sales guy was like, Bruce who? Like, I don't know this like God of cryptography now.  They're just throwing buzzwords out there. So there's a lot of signal to noise ratio out there.   But in reality, there are some really good vendors out there and they're gonna solve one piece of that puzzle, right? We talked about it a couple of them today. Nessus is awesome. It's been a vulnerability scanner that's been around forever. Claire is pretty great. You know, a lot of CI tools in creating that beautiful infrastructure are really good pieces of that puzzle. But they're one piece, right? When you start talking about security, you realize that, you know, the security and layers type of idea, right? You know, one piece of the puzzle to a holistic security idea. So in terms of your Docker environment, I like to think of these products as kind of like their own little islands, right? Each thing is an island providing a certain feature set for you. You know, you have your Docker build. You have your scan. You have your metadata. You know, you have your logging system. You have your monitoring system. And like as DevOps engineers and site reliability engineers, it's kind of our job to figure out what tools are actually gonna add to this holistic picture of security for us. And like we're tasked with like building the bridges between these islands, right? Take your build system. Take your security scanner. Figure out how to get the data you need from production and feed it through the pipeline so you can get the kind of information that allows your security team to have, you know, a good incident response to any situations that pop up, right? So that is all I have in terms of Docker security. So I'll open it up for questions now. And I got my slides there at the bottom on my website if you wanna go and look through some of that later. Otherwise, I'll be out in the lobby hanging out here as well and feel free to come up and talk to me afterwards as well. You mentioned Claire to help see inside of a Docker container that was running in production. Obviously you're not accessing the production instance you have, you know, another copy down. Is Claire a tool to see into a container that we normally don't have that visibility in production? Like, did you install an SSH client? I just, I've not heard of it before and I'm curious how it's implemented. Sure, so the way we use that tool at our company is, you know, our security team wrote a small tool that will grab the list of containers running in production, right? And then it can pass that container name to the actual Claire system. So Claire has an API endpoint.  So it's just a go-lang tool that can inspect Docker image layers. So it's not actually, it doesn't need to actually do like a Docker run and all that to spin it up. It looks at the file system layers for it. All right, I got two questions here and then we'll have to call it at the time. We haven't moved to containers yet but we have issues with automating some of our, just automating the audit points. Like, I don't know what it is for other companies but they want screenshots sometimes. Versus like we could run a batch audit and pull the data. They don't trust that data. Like, does that an issue with you or have you guys ever experienced that or is that just one after me? Sure, I'll talk to that the best I can because I am not an otter and I'm not on our audit team. Being kind of more in the site reliability and operations side of it, right now I'm the person that gets the call that says, can you pull this screenshot for us, right? But they do need screenshots for a lot of this and to my knowledge, a lot of times, we are still doing a lot of the classic audit steps, showing them the screenshots of the updates happening and the version of XYZ application running, et cetera. So yeah, to my knowledge, I don't think a lot of that type of audit requirements has really changed for us. A lot of these are just tools that really help us respond quickly to incidents. It doesn't really shift the audit responsibility for us at all. A lot of the ideas you presented here in your slides seem to be at least somewhat oriented around the idea of Docker images that are built on top of a full base OS. How do you feel about other approaches like using a more minimal OS like Alpine or even a scratch image and static compilation in compared to using the full OS base? Sure. So last time I looked, actually, the CIS standard for building Docker images was based on Alpine. So we, for our base image, actually use like Deb Bootstrap and start from scratch and put like this super minimal Linux image in there, whether it's like Ubuntu or Debian, et cetera. And that works best for our environment right now, but what we actually wanna move towards is exactly that, just throw an Alpine base in there, throw your Golang binary in there, ship it, because the smaller it is, the less there is to audit. So if you don't have a ton of libraries in there, everything's compiled into your binary, like that's awesome. So like that, like I was saying, I'm kind of giving this talk through the lens of my experience. So that's definitely the direction we are heading and wanna be in. And this is kind of where we are at right now. Great, well thanks again. Let's hear it one more time for Matthew.


Rwy'n gallu gwirionedd i chi'n gynnau'r ddaeth yn Yra, o'r cymdeithasol digital. Mae'n ffordd, Fforka Bousha, mae'n Cymraeg Llywodraeth Pwyllachol, ac mae'n dweud o'r gwerthfawr newydd cyd-dweithio, ond y grwp bod ymlaen, mae'n ddweud o hyd i gynnwys i gyd-dweithiau hynny o'r llwyth. Ac mae'n cael y brif wedi bod ni'n ddweud oherwydd, ac mae'n ddweud oherwydd o'r llwystau dechrau sy'n rhan o'r cyllidau, mewn aethau arian. We are about 12,000 people, we think, globally in around 70 countries around the world and we do everything from structural engineering and civil engineering for bridges, which I'll show you later, to behavioural psychology and change management in how airports transform themselves as an asset in complex operations. We've done quite a lot of research in this space of digital bit environment. In 2010 we issued our first smart cities report and since then we published about a dozen reports for government industry and our own as we are completely independent and self-funded. We have no debt, we don't borrow money, we don't have links to any product company, so we sometimes also invest in our own research to take genuinely independent views. And a few findings of that were quite interesting about our industry. We did a report around utilities broadly for UK government and identified a 40 billion digital export market in waterways, transport and energy. The cost of congestion in London and other cities is around 730 million and there clearly is a link how more transparent and open data could make a contribution to that. We tried this year something around utility data and reducing DIC disruptions in London and we failed with that but we'll try again this year. One of our property clients is a corporate real estate organisation that provides real estate for 100,000 people where every single member of staff moves around every six months. So you have 100,000 people moving office every six months and the data management they use to organise all these moves and changes is an advanced version of Excel which we don't think is necessarily the future. The tech sector, nothing against Excel by the way. The tech sector by the way was the only sector in London during the recession that didn't reduce headcount and every city and government we work for right now is trying to develop a digital economy in their own city or country to be part of that job and economic growth and investment discussion. We're trying quite hard right now to convince the two mayoral candidates in London to provide a digital manifesto which would be in line with what some of the Scandinavian North American cities have done recently to also address the political and the humane issues that cities face around digitisation. Because we think this is not just about startups and beanbags and slides which are often associated with it, we think this is transformational in our industry. We looked at what we mean by digital. Is it just IP? Is it just Ethernet? Is it just open data? And unfortunately what we found is a picture like that which basically means it is everywhere. The entire technology stack in the built environment is going through a change. A camera with edge analytics capabilities can now count people and publish that data in JSON or via an API to anybody who wants to know how many people are in that frame. A large real estate portfolio usually has around 15,000 cameras on it who are currently only used for or primarily used for security. And this happens to every single asset that is currently going into the built environment. So it's social, mobile, cloud, IoT, analytics. I call it the new digital skin is everywhere. It will connect the cloud. It will reach your mobile. It will require novel data science approaches to great value. And I think Tim Berners-Lee, who I probably called wrong here with him in the room is at risk, last year made it quite succinct and said you don't exist if you're not on the internet. And I think right now that's what the built environment is doing. It's starting to think about being on the internet. And Gavin was right, too. In the talk he gave recently, I think it was at Bloomberg's. I'm not sure. We talked about data infrastructure and I agree with that, too. Data or perhaps digital is an infrastructure and you could almost compare to rail. Rail is not just tracks and trains and stations. It is the backbone of many countries and around which they want to develop their economy. This morning that's why I'm very formally dressed. I was actually hoping this year I would come in my ODI T-shirt, but then was invited to breakfast with the Deputy Mayor of London and my chairman explained to me that the T-shirt wasn't a dress code. So we discussed there the role of digital and again it was seen as an economic infrastructure. It was seen as part of participatory democracies, it was part of job creation and it was part of efficiency gains, material efficiency gains across all industries in the city. So what are we doing about this? What do we see as an opportunity for us and others in that? This is, this should be, that was Kevin, sorry. This is the, I always thought the fourth crossing was actually the fourth crossing. It shows you make moves as a German who lived here for 20 years. The fourth is actually the river apparently and the crossings there are only three which makes us a rather complicated story. But each of those will have about a thousand sensors on the bridge. We are now looking at using ideally an open API from a Met Office on weather data. We're working with Vodafone as our preferred mobile data vendor for transport analytics to have occupancy data. We clearly have camera data around occupancy on the bridge. And we're looking right now on how we can create a platform that will allow us to create insight about the performance of these big expensive assets. To get more value out of them. So let's say we extend the one that was built in 1880 on the right and we extend the life by another 50 years. That is worth tens of not hundreds of millions of pounds. Now the next bridge I quite like because it was recently before it was finished up there on a leadership training course. I'm not sure what they tried to teach us other than that we are insane to go up there. It was on a little steel lift that goes up on the outside. And these are by the way the cranes they used to offload the mega container ships. This is stone cutters in Hong Kong one of the biggest bridges in the world. So there's nothing really stopping us to take that data, to take that one. Take Golden Gate Bridge the one into Wales and maybe another 10 and create a platform that will allow us to create insight around all the biggest bridges in the world. Which I think would be an unbelievably valuable asset to have in the built environment itself. And when we then look back to our original research I mentioned and we looked at asset monitoring in the built environment we then identified actually the same platform could do wind farms, offshore rigs or oil platforms. There's a whole raft of infrastructures that we could do. We then compared it with our UKTI research and we found, oh gosh, transport, utility, cities, property, sports major events and another complex assets are all trying to do that. And that got us quite excited. So all the sectors we work in are starting to develop digital narratives or digital agendas in their own right and collectively that will mean the built environment soon we believe will be as big in digital terms as currently finance, consumer, retail, marketing. Our clients supporting that. This is a list of the clients we currently work with around their digital agendas and they are also all changing. They are changing from what we call the bottom-up approach where they did project by project to a digital agenda that will combine strategy with activists led change. They are not trying to cut out the entrepreneur and the innovator who is sitting in the department self-teaching themselves on Python or all sorts of other interesting stuff. It is actually now combining the power of organisations with the individual activism that these companies have. They look at the use of open, shared and closed data. They want to explore what data science has to offer and they want to re-engineer the fabric of the built environment to include this new digital skin and in theory everything could be measured if that is of value or helpful. In Arup right now we are setting out a number of activities. We are launching something that we call INSIGHT which brings together our data strategy, analytics, visualisation, city modelling, 3D modelling and development of online tools. We are looking at the data infrastructure discussion the way Gavin and ODI defined it both as an open asset where we can with others or as a platform that we want to develop with our ecosystem partners to also create two-sided platform business models on this. We obviously do that to help our clients generate insight that is true and actionable but we are also doing that to prepare our own firms. We believe our 11,000, 12,000 engineers, behavioural psychologists will all have to learn to a degree what digital means or what skills they need to have to fit into a digital future. We are very keen to develop our ecosystem of partners further. The Open Data Institute is already one of our most strategic partners in there. We are keen on the Alan Turing Institute and talking to them right now. I think that is a great initiative. Mastodon C, Open Sensors are two of the startups. ISOFSTONE in China we just signed an MOU with and there will be more that will add to our ecosystem framework. We want to work with Open Innovation. I will come back to it later why. We like to launch, for example, and raise the funding to create a city 3D model that will be open sourced. We already have a lot of data from five or six major UK cities which we like to flip open into an open innovation environment which I think would create quite an interesting platform for developers and companies in each cities to develop their own solutions in that environment. We are discussing and we are hoping to launch a campaign around climate action data. We are in Paris this month or next month for COP where we present another climate action report but the data is locked up in reports right now and we are campaigning right now internally and with some of our partners to create an open innovation environment for climate action data. My personal view is that what we do as Arab is around 11,000 projects at any point in time and that on our own we would struggle to scale fast enough and stay on top of the next disruption. I think Uzman will speak to all of you about what he is doing right now with the new travel makers who is just going to come in left field with a big idea that if it's true will mean our 11,000 projects have to again respond to a new technology trend. We need to develop a porous organisation that can create value with our partners and we need to shape a better world. Thank you.