back to present. Okay so let me just go ahead and dive in. Of course before we do I want to thank all of our supporting partners for stepping up and giving back to the community by becoming a supporting partner. All of your funds are going towards Drupal.org and making sure our engineers are updating our tools and the infrastructure is funded. All the great things that we do on the site is because of you and I want to thank our signature partners. This is the top level that's been growing over the last year since we introduced it and we're just very thankful for everyone's support and we're also glad that we've been able to update the program so that each level gets more business value while we know that everyone is contributing back to make sure Drupal.org stays on and evolves. We know that you could be doing many things with your money and we want to make sure we provide as much business value as we can so we've been featuring a lot of great case studies off of the front page and providing other kinds of value like that and our supporter base just continues to grow with so many committed companies around the world and it's not just the Drupal shops or digital agencies but we also have many ISVs technology companies that integrate with Drupal as well as hosting companies that are working with us. They recognize that they are part of our ecosystem and generating income for their company by working with Drupal and so they want to give back as well. So we really thank you for all of your support and now let's go into some Drupal association news. On December 12th there's going to be a public board meeting followed by an executive session and it's a rather important one. It's the time of year when we get new board members. Every year in November board seats expire and so we are using this opportunity to make a few changes I just want to call out. So Tiffany Ferris, Jeff Walpole and Vesa Palmu are rolling off of the board after many years of great dedicated service to the community which we are incredibly thankful for and it's now time to replace those seats so we'll be voting on the new slate of nominees and we are also going to be making some other changes. So for example Jacob Redding will be the new treasurer as Tiffany rolls off. Mike Lamb will remain as the secretary but we are going to make a change with the chair. So Drisby Tarch has been the chair of the Drupal Association since the beginning. He wants to still stay very involved with the Drupal Association but he's decided that the chair officer position can be taken over by an independent like neutral party something that the community had asked for and he was happy to do that and so we are going to be voting on bringing in Adam Goodman into the chair position. This is a great change he has been advising the board on and off for eight years helping us evolve from a volunteer board where the board actually used to put on DrupalCon and has helped them move to a strategic board and we can now evolve even more with him as the chair. It's an interim type of chair position. He really wants to just orient the board to be used to having a nominated chair on the board versus the founder of the project and we also can continue to evolve on the strategy side too with his help. So that's going to be a really great change. To bring him on board we do need to update our bylaws. He is a paid consultant and we currently have bylaws that say no one can get paid so we are doing a change to the bylaws and a vote to the bylaws to allow us to pay him for this interim role and while we're voting on the bylaws we just looked at all of it and just wanted to update it. So there's some other changes that we're going to be voting on. Some real basic things there's a list of committees that we don't use anymore so we're just cleaning that up and some other things like us as we can only use basically telephones for our you know virtual meetings but obviously we have things like zoom now so just really simple changes like that but you'll see that in the public board meeting that we'll be voting on that as well. Some other things to note about our board is that we have 12 seats all together 10 of them are nominated and two are elected by the community so we are going to vote to look at how to get more everyone's from the community on the board but how can we get more of the community elected directors on the board get some more diversity in terms of regional representation as well as different kinds of personas and so there's two things that we're voting on that you should know about one is more operational which is basically board members that are nominated they expire and their seat expires in November but if you are community elected that cycle is different and expires in January and that's just really hard to manage so we're going to vote to extend Shamala and Ryan's Rama's seat to expire in the November of the year that their term is over rather than January and that way we can just onboard and exit everyone together but the other one is the way the bylaws are written we can actually have four community at large positions rather than two and we will look to have four community at large board members join us in November and so that is a change that we're going to discuss and make sure that's something that we can support operationally but all of these changes mean one thing that I think is important for you to know which is we're going to change when we do community elections and we've been doing that I'm kind of starting now through March somewhere in that time frame is when we normally do the community elections that we can get someone on board to come to their first in-person retreat in the Drupal con in North America but because we want this person to roll in in November then we're going to change our community elections to the summer so just note that change let your staff know and we will be promoting this communicating it out and running those elections this summer and just a few things to note about Adam Goodman I mentioned how he's moving into the chair position he's very excited to get to know the community better I mean he's worked with the community on and off as he's been advising the board he brings to the table just loads of experience he is a professor at Northwestern University in Chicago in the US and he is an advisor on leadership and advises nonprofits and companies all over the world so he's just been a really great partner and I'm excited to work with him but more importantly I'm excited for him to meet you and to understand your business's needs because the board needs to focus on that and so I'll be setting up interviews between Adam and our supporting partners so you might be getting an email from me in the next couple weeks where we can set something up because he would really like to hear what the needs and opportunities are that the Drupal Association should be focusing on and in other news kind of shifting from the board that does strategy over to the staff that does the operations we are growing as a team so our we recently hired Rachel Lawson who lives in the UK she has been the community for 11 years has deep knowledge in how our community works has played many important volunteer roles from community working group to sprint mentor she has a technical background and we have asked Rachel to be the community liaison between the Drupal Association and the community so we can have more of this bi-directional multi-directional conversation and really to foster understanding understanding of what the DA is doing understanding the needs of the community making sure that we're really as agile as possible in terms of meeting the needs of the community and then on the other hand many of you have worked with Rachel Friesen who has been our events director overseeing DrupalCon and she is leading the organization mid-January to go explore the world and take on this whole new exciting adventure so we're certainly really sad to see her go but we are excited for Brooke Candelaria to join us as the conference director she has deep knowledge and experience in tech events working with all kinds of tech events including open source ones like Linux world and she's worked in open source communities so it's great that Brooke can bring to us this whole tech event experience and marry it with Amanda Ganzer who handles our programming she has a great understanding of the Drupal community so we can really elevate DrupalCon so it is a premier tech event but without losing what is so great about our community and our culture so I'm really excited for Brooke to come and and start evolving DrupalCon she's also going to be working with me on the licensing program as some of you may know we are looking to license DrupalCon to a European entity she is going to be helping me with that process um and there's just so much more that we can do we talk about how do we do customer roundtables and how do we do events in a box that can be shared around the world so lots of lots of different ideas already coming within just a few weeks of her working here so very excited about both of these new hires speaking of DrupalCon the next one is in Nashville Tennessee April 9th to 13th and really interested in having this event be a step forward in an evolution for DrupalCon in the past it's very much been focused on the people who build a website or an application whatever you're building something amazing with Drupal and that is good it's obviously also focused on the contribution side of of the project and really accelerating the project by bringing people forward by bringing people together excuse me and that is really good because that persona the builders the the front end the back end the dev ops the project manager like all all these people that make up teams that build something amazing with Drupal plays such a critical role especially since they also you know there's a certain percentage of them that are also contributing to the software so I'm very proud of the base that we have we do want to expand the way I see it is that for a visitor to a website or a user of an app is getting a digital experience that's not just based on the builders expertise there's a whole supply chain a whole team of people made up with different personas you've got the decision maker you've got the builders of course you've got someone leading the builders and then of course once it's built and you need the people on the marketing side who are going to really bring that side alive alive with content and marketing campaigns and they're focused on being able to have agile messaging and conversions and strong SEO and we need to bring those people into the fold because as I like to say no chain is stronger than its weakest link and if we want Drupal to be adopted and have a strong foothold in any account we need to be talking to all of these touchpoints along the supply chain of creating a digital experience for a visitor we would like to bring them all under the same tent and provide really unique experiences for all of them but then also create experiences where they can interact and kind of break down the walls between the personas and so you're going to start seeing some changes at Drupal Con this year and then we'll be able to keep evolving over time this is going to be probably the first Drupal Con with so many personas served so these are the different tracks and what you're going to see are many familiar ones that are very technical from your back end development and front end development dev ops the ones we talked about but we also have some other ones you know like the the business owners that's always been served as well as project managers, site builders these are all ones that we've been talking to at every Drupal Con but we're starting to lean into a few other areas one is technical leadership we did some research and talk to directors of engineering at different end users that we really want to have them come to Drupal Con and they say well I've come once but really it's for my team and we want to make it so the technical leadership at the end user or even at the digital agency wants to come again and again and there's something for them and we ask what they would want they say well we want something that's going to like pick our heads up and help us blue sky some new ideas and thinking but also that comes in the form of case studies and talking to peers but that also comes in the form of how can I be a better manager how can I get the most out of my team there's a need for that so the technical leadership track is going to focus on that for the directors of engineers and then on the marketing side we are starting to move into that with UX and content editors content strategy content editors so here we go right here and I'm user experience sorry so we will be focusing on that with this Drupal Con in time I love to start seeing a track for marketing people to come in and really understand Drupal's value in terms of TCO and SEO and all those great acronyms so I'm just very excited about this evolution of Drupal Con because at the end of the day Drupal has many different types of people in its community and we need to serve all of them another thing I want to point out is that there are some themes that will be resonating through Drupal Con ambitious digital experience is one and the other one is headless we really have opportunities to grow in both areas and at Drupal Con Vienna the jury's note focused a lot on what is an ambitious digital experience and why headless is such a growth opportunity for us so you're going to see in all of the tracks case studies and that case studies will range from technical to business but you're also going to see a big focus on headless every track will also have some form of like javascript content and some will be very technical but in the when you look at horizons it's really about pushing boundaries with headless and what what are some amazing things that we could do or should be doing what are we doing with smart cities you know all these big topics that futurists are are covering now and Drupal can play a role in that and so lots of really big themes that will be kind of percolating through all of these tracks to look out for excuse me so I certainly encourage you to check out these tracks think about attending of course many of you are sponsoring and we greatly appreciate that support we have some new summits just so you know if you want to get in front of business leaders who are talking about it's basically peer to peer networking peer to peer learning around different industries so if you want to get a real focus I encourage you to check out the summits we have a new one called decoupled summit that's going to focus just on those kinds of headless experiences decoupled experiences so I definitely like to highlight that one because I feel that the sponsors are getting some really special value in those kinds of intimate meetings so be sure to submit your sessions share your knowledge the important date to keep in mind is January 17th that's when call for papers closes we also want to call out Drupal Europe events so we're taking the year off for Drupal con in Europe so that we can come up with a new operational model that's more sustainable and adds more value to that to that region in the meantime 20 in 2018 the community in Europe is building an event for the community it's called Drupal Europe 2018 and they're making really good progress they just told me yesterday that they look to announce the venue in the new year roughly January and so just keep an ear out for that we'll certainly be amplifying that information I'm sure many of you in Europe are eager to find out what to do and how you can support them with sponsorship which I highly encourage as well and we are working very hard on coming up with a structure for Drupal con licensing and that would be so that Drupal con can come back to Europe in 2019 they're working with this amazing committee of European event leaders and we are really close to putting something out to the community so they understand how and when to submit their proposals to be the licensee to be the event organizer for Drupal con 2019 so I just want to let you know if you're if you're interested or you know any entities out there that have expressed interest to keep their eye out for mid-December when I'll be sharing that information and I think that's it for Europe so Tim I'll hand it over to you awesome so yeah I'm going to go ahead and give an update on Drupal.org this is going to be a little bit different from some prior updates in that I'm going to be talking certainly about some of the features and things that we've been working on since our last kind of public conversation in September but I'm also going to talk about some Drupal project licensing policy issues that have recently been resolved some long-standing questions and give sort of the basic information about that and the clarifications that are in place and I'll get that in the second half of my my little conversation here and feel free to ask any questions at that point Megan go ahead next slide we'll start with the feature changes obviously as most of you know composers become kind of an integral part of Drupal 8 workflows for most organizations but if you are not kind of deeply tied into the community that may not be as visible to you or hasn't been in the past anyway and it's been a little bit hard to wrap your head around those new workflows there are a number of initiatives underway to make this easier for people who are building projects on Drupal one of them a fairly simple one is that we're now including instructions for how you install projects using composer directly on the project pages as well as linking to in-context documentation about how that works that's a small step and in addition to that we're thinking about and planning tools for site builders that might be integrated directly into Drupal's admin interface that can help people manage composer-based sites in a little bit of a more site builder friendly way so that's an initiative that we're just beginning to work on with the core maintainers if you go to the next slide we've been an announcement that you probably saw in one of our previous updates is that we've just finally cleaned up some parts of Drupal.org that had been existing with bare slash node slash random string of number URLs for such a long time and have been hard to shout across the sprint table and hard to manage and contribution and hard to bucket and analyze in our own analytics when we're looking at the activity on Drupal.org so we've just pushed out some more friendly URLs for different content types so issues now have friendly URLs and will you know if an issue is moved from project to project those aliases are automatically updated case studies have friendly URLs as do forum topics and we've created a few search shortcuts so if you do know a node id and enter it directly in the search bar you'll be taken straight there and you can even use a very short Drupal.org slash i slash issue id if you want to jump directly to an issue without using these longer search friendly URLs in addition we've been spending some time I want to call out mix logic Ryan on our team for his great work with Drupal CI obviously this is one of the big services that we provide to the project is testing and test coverage and there's a number of different things that we've been doing from providing environment testing for PHP 7.2 to just updating and troubleshooting various aspects of the system trying to make it run faster but one of the most important things is because Drupal CI is funded entirely by the kind of sponsorship that you provide we want to make sure that your dollars go farther go as far as they can in support of the project and project testing so Amazon Web Services recently instituted per second billing option for AWS so we refactored our Drupal CI dispatcher to take advantage of that per second billing option and we rewrote the plugin that we use to search across multiple availability regions to find the the cheapest instances that we can and this means a few advantages among other things it means that we can we don't have to wait to reuse unused minutes on test spots so we can provision new ones right away which actually means tests are completing faster and it also means that we're not paying for spot instance time that we're not using which means that we're saving an estimated between 20 and 30 percent a month on what our CI costs were even just a month ago so that's going to help make the sponsorship dollars that you provide go farther and allow us to do more with them in different ways next slide Megan a few things that you may have seen as well obviously we work with our partners tag1 consulting for infrastructure maintenance and support for Drupal.org so you've probably seen some messaging on our Drupal Infra Twitter handle about different maintenance windows that have occurred over the past six weeks or so as we've done various updates these have been things like general updates, machine reboots, enhancements to our monitoring systems and configuration management various things like that we've been pleased that for the most part we've been able to do these without any significant downtime or really any downtime at all in those cases we're also working on PCI compliance updates and really just reducing the scope of what we manage for PCI when it comes to accepting membership transactions or Drupalcon ticket purchases and all of those sorts of things and so that's something that you'll hear us continue to talk about as we finish that process up now to switch over to the kind of new topic for for these calls something we haven't really talked about before and that's licensing policy for the Drupal project and Drupal.org and I mean license in terms of the GPL license so there were several major questions that you may or may not know have been hanging out for honestly a couple of years that the project has been trying to resolve and some of these are very straightforward but haven't been explicitly clarified it some of them were a little a little bit more open to interpretation and have just needed some firm answers so one of the more basic straightforward questions was of course explicitly affirming can code be licensed under GPL compatible licenses included in Drupal projects and the answer to that has always been but to explicitly say it is yes you can use any GPL compatible code in a Drupal.org project it's just that when it's redistributed from Drupal.org it's distributed GPL or later and that's just a basic clause of the GPL that we're finally clarifying a little bit more clearly in our project on the next slide the next question was can Drupal projects include GPL incompatible non-code assets and this is something that's been a point of confusion for a lot of people whether it's project maintainers site builders agencies it's whether or not assets that are not derivatives of the work of the code that is GPL can be non-GPL and this is important because of course font licenses and icon copyright and licensing all that kind of stuff are just on a different spectrum from code licensing and are usually not designed to work in tandem with each other so there's an there's an explicit clause in the GPL which states that any works that aren't based on the GPL work can be packaged and distributed in aggregate with GPL code so we're just explicitly affirming that yes as long as the maintainer has the right to distribute whatever those known code assets are they may be packaged and distributed in aggregate with GPL code and this is just going to make it easier for theme developers and anybody who relies on fonts or icon sets or things like that to host their projects on Drupal. This question related to kind of the evolving understanding of what composer and dependency management means in kind of a modern PHP and Drupal world as you may know the GPL says that you can use any software you like with different licenses but if any of it is GPL and you package it or distribute it together it must be done under the GPL and therefore must be GPL compatible and that's brought up the question well if you have a third-party dependency or a library that's non-GPL and gets installed by composer when you run a composer command is that acceptable or is that distribution and after consultation with a licensed working group and Dries and looking at different legal opinions we are affirming that yes under our interpretation GPL does not restrict the use of code with other incompatibly licensed third-party libraries or dependencies just packaging or distribution so in short that means composer dependencies on libraries with other licenses are completely okay but Drupal.org can't host those in packages with the original code so that's an important clarification that we're happy to put out there. The final question is sort of more of a matter of explicitly affirming protections for agencies and freelancers and anybody who works with a client to build sites for them and this is this has been an implicitly understood assumption about the GPL in a variety of projects but the Drupal project hasn't really said it out loud so we're just going to go ahead and make sure that we do that and update that in our licensing documentation so the question is basically when an agency builds a site excuse me when an agency builds a site for a client are they distributing code per the distribution restrictions of the GPL or are they simply acting as the customer's agent to build that site for them and therefore falling under the use clause of the GPL so just to affirm our interpretation and interpretation widely across many projects agencies and freelancers and other service providers are acting as the customer's agent they are not distributing code just by building a client website they're assembling the code base acting as the client's agent so in more simple terms again service providers can go ahead and use GPL code together with maybe GPL incompatible code when they're building client site this allows you to do things like integrate with third-party APIs and use libraries and run composer to build the client website but you can't redistribute all that code with those incompatible licenses in aggregate to the public as a product or package because that's when the GPL's distribution clause would come into play so those are just the important license clarifications some of you may have been following some of these questions for a long time to some of you they may be totally new but we're really pleased to have the answers and to be updating that information and again if you have any questions feel free to use the chat or use the Q&A panel to post any questions there okay well I just see this slide that says questions but first Dan it was really great and good job with the licensing that's sometimes a hard concept to have to to share so that was really helpful and also great work to your team too thanks yeah just pretty excited about what you've done this year and then also some things that you're going to do next year it's going to really help especially making sure those people that kind of quote-unquote got left behind with some of the changes in Drupal 8 and bringing them back into the fold and supporting them I'm just really excited that we can work on that yeah I think there's a lot of great initiatives planned that we're going to require a collaboration between the Drupal Association Engineering team and core to do things like automatic updates and tools for site builders and things to make these kind of developer-centric composer workflows actually accessible to the sort of traditional site builder type roles so that those folks can continue to be first-class citizens of the community yeah absolutely great okay well I can't see the the chat or Q&A windows do we have any questions from the attendees looks like not at the moment all right well then why don't we go ahead and close this out keep your eye out for our monthly email updates that are coming from your account managers Delana or Mark and of course if you have any questions you can reach out directly to them or to Tim and I we're pretty accessible and really so grateful for your support and we're happy to give some time if you want to just hop on a call and also just follow us on at Drupal Assos because we're always putting news out there out there as well okay well thank you very much and have a great rest of your year and I wish you all the best in the new year we'll come back to you with some updates in Q1 thanks again thanks everybody


Okay, we're back in Boston covering AWS re-invent 2022. This is our second live re-invent. We've done the other ones in between as digital. My name is Dave Vellante and you're watching theCUBE. Peter McKay is here, he's the CEO of Sneak and Adi Sharabani is the Chief Technical Officer. Guys, great to see you again. Awesome being here in Boston, in Boston in July. It is. Peter, you can't be here. It's good weather, yeah. Red Sox on good, but everything else is okay. Sox are ruining our summer, you know? They're still in the playoff, a daunt. You know, all you got to do is make it in. Yes, right? And then it's a new season. Simple. Kind of like hockey, but you know, I'm worried they're going to be selling it the trading deadline. Yeah, I think they should be. I think it's not looking good. You usually have a good angle on this stuff, but well, hey, we'll see. We'll go, I got a lot of tickets, we'll go and see the Yankees, at least we'll see a winning team. Anyway, we last talked after your fundraising. Yeah. Big round at your event last night, a lot of buzz. It was a lot of fun. The largest event I saw around here. A lot of good customers there. It was a great time. So what's new? Give us the update. You guys have made some acquisitions since then. Integration, we're going to talk a little bit. Yeah, it's been a lot has happened. So the business itself has done extremely well. We've been growing at 170% year over year, 100% growth in our number of customers added. We've done six acquisitions. So now we have five products that we've added to the mix. We've tripled the size of the company. Now we're at 1,300 people in the organization. So quite a bit in a very short period of time. Well, and of course, in my intro, I said reinvent. I'm getting ahead of myself. We'll be at Reinforce in November. That's the next one. At Reinforce. We've done a lot of reinvents, by the way. There's a lot of reinvention here. So of course, you're reinventing security. So I try to think about when I go to these events, like what's the takeaway? What's the epiphany? We're really seeing the developer security momentum. And it's a challenge. They've got to worry about containers. They've got to worry about runtime. They've got to worry about platform.  Maybe describe that a little bit further. Yeah, I mean, for years, it was always after the fact, production, fixing security in runtime, and billions and billions of dollars spent in fixing after the fact, right? And so the realization early on with Sneak was you've got to fix these issues earlier and earlier. We started with open source, was the first product that waited six years ago. Then we added container security, and we added infrastructure as code. We added code security. We added, most recently, cloud security with the Fugue acquisition. So one platform, one view that a developer can look at to fix all the issues from the beginning, all the way through the software development life cycle. So we call it developer security. So allowing developers to develop fast but stay secure at the same time.  Now, a lot of M&A is, okay, we're going to buy this company, we're going to leave them alone. You guys chose to integrate them. Maybe describe what that process was like, why you chose that, how hard it was, how long it took, take us through that. Yeah, I'll give two examples, maybe. One on Sneak codes, which was an acquisition of a company that was focused on code analysis, actually not for security. And we have identified the merits of what we need in terms of that first security solution. Not an ability to take a security product and put it in the hands of the developer but rather build something that will build into the dev motion. Which means very fast, very accurate, things that you can rely on source and not just on the build code and so on. We have built that into the platform and by that our customers can gain all of their code related issues together with all of their ISC related issues, together with all of the container issues in one platform that they can prioritize accordingly. Okay, so talk more about the cloud. The few cloud, the Sneak cloud, right? So the few name goes away, I presume, right? Yes it does. So retire that and bring it in. The brand is Sneak, right? So talk about the cloud, what it does, what process it's solving. Awesome, and this goes exactly the same as we mentioned on the code. We have looked at the cloud security solutions for a while now and what we loved about the Fuq team is that they were building their product with their first approach, okay? So the notion is as followed, as you're a CISO, you have your program, you're looking, you have different types of controls and capabilities and your team is constantly looking for threats. When we are monitoring your cloud environment we can detect problems like your S3 bucket is not exposing the right permissions and is exposing the world or things like that. But from a security perspective, it might be okay to stop there. But if you're looking at an operation perspective you need to know who needs to fix, how do they need to fix it, where do they need to fix it? What will be the impact if they would fix it? So what we're actually doing is we are connecting all the dots of the platform. So on one end you know the actual resources that are running and what's the implication in the actual deployed environment. On the other end, we get correlation back to the actual code that generates that. And then I can give that context both to the security person, the context of how it affects the application. But more importantly, the context for the developer is required to fix the problem. What's the context of the cloud? And a lot of things are being exposed this way and we can talk about that. So this is really interesting because, and I love AWS to do an amazing job. One of the other things I really like about them is it seems like they're not trying to go hard and monetize their security products. They're leaving that to the ecosystem, which I like. Microsoft taking a little different approach, right? They're making a ton of money on security. But this example you're giving Adi about the S3 bucket. So we heard in the keynotes yesterday about reasoning, AI reasoning. They said, we can say, is this S3 bucket exposed to the public? They could do that with math, right? But what I'm inferring is you don't stop there. There's a lot of other stuff that has to. And sometimes it's not as simple as just as a configuration change. Sometimes the correlation between what your application is doing affects what is the resulted experience of their own user or in this case, the attacker, right? I mean like the application has access. Who has access to the application? Is this the same? Yeah, so this propagates. You have to have a solution that looks both that have a very good understanding of the application context, a very good understanding of what we refer to as the application graph, like understanding how it works, being able to analyze that and apply the same policies both at development time as well as runtime. So there's human to app. There's also machine to machine. Can you guys help with that problem as well? Or is that a sort of a futures thing? Could you, I'm not sure I understand what is. Machines talking to machines, right? I mean, there's data flowing between those machines, right? It's not just the humans interacting with the application. Is that a trend that you see? And is that something that you guys can solve? So at the end of the day, there is a lot of automation that happens both by humans for good reasons as well as by humans for bad reasons, right? And the notion is that we are really trying to focus on what matters to the developer as they're trying to improve their business around that. So both improves, making sure they know quality problems or things of this kind. But as part of that, more importantly, when we're looking at security as a quality problem, making sure that we have a flow in the development life cycle that streamline what the developer is expecting to do as they are building the solution. And if every single point, whether it's the IDE, whether it's the change management, whether it's the actual build, whether it's the deployed instance on the cloud, making sure that we identify all that and connect that back to the code. Okay, so if there's machine automation coming in that shouldn't be there, you can sort of identify that and then notify, remediate, or whatever action should be taken. Identify, identify, remediate. Yeah, we really focus on making sure that we help developers build better products. So our core focus is identify areas where the product is not built way, in a good way, and then suggest the corrective action that is required to make that happen. I think part of this is just the speed of software development today.  You're trying to get so much more productivity out of the developers that you have. Every company is trying to get more productivity out of developers. Incredible innovation, incredible pace, get those out, get as a competitive advantage. And so what we're trying to do is we make it easier for developers to go fast, innovate, but also do it securely and embed it without slowing them down. Develop fast, stay secure. So again, I love AWS, love what they're doing. We heard yesterday from CJ, I think a lot of talk about threat detection and some talk about DevOps, et cetera, but I didn't hear a lot about how to reduce the complexity for the CISO. And the reason I bring this up is, it feels like the cloud is now the first level of defense. And the CISO is becoming the next level, which is on the developer. So the developer is becoming responsible for security. The whole shift left, maybe shield right, but the shift left is becoming critical. Seems like your role, and maybe others in the ecosystem is to address my concern about simplifying the life of the CISO. Is that a reasonable way to think about it? I think it's changing the role of the CISO. How so? Really, I think it's before in the security organization, and Adi, you should chime in here, is it used to be I owned all application security, I owned the whole thing, and they couldn't keep up. Like I think it's just, every security organization is totally overwhelmed. And so they have to share the responsibility. They have to get that, fix the issues earlier and earlier because it's waiting too long, it's after the fact. And then you got to throw this over the fence and developers have to fix it. So they've got to find a new way because they're the bottleneck. They're slowing down the company from innovating and bringing these applications to market. So we're the kind of this bridge between the security teams that want to make sure that we're staying secure and the development organizations and engineering and CEOs go fast. We need you guys to go faster and faster. So we tend to be the bridge between the two. One of the things I really love happening these days is that we change the culture of the organization from a culture where the CISO is trying to push and enforce and dictate the policy which they should, but they really want to see the development teams pick up. Like the whole motion of DevOps is that we are empowering them to make the decisions that are right for the business, right? And then there is a gap because on one end, the CISO is like, you need to do this, you need to do this, you need to do that. And the dev teams don't understand how that impacts their business good enough and they don't have the tools and the ability to address those problems. So with a solution like SNCC, we really empower the developers to bake security as part of their cycle, which is what was done in many other fields, quality, other things, IT, everything moves into development already, right? So we're doing that and the entire discussion now changes into an enablement discussion. So, interesting, because you said the role of the CISO is changing, I see that in a way, like pre-sneak, the CISO with the cloud is becoming a compliance officer. Like you do this, you do this, you do this, you do this. You're- And you don't want to take responsibility to direct it to the cloud? Yeah, right, right. So you're flipping that equation, saying, hey, we're going to actually make this an accelerant to your business. So set the policy, determine compliance, but make sure that the teams, the developers are building applications in compliance with your policy, right? So make sure and don't allow them to do something if they're doing, if they're developing an application with a number of vulnerabilities, you can stop that from happening. So you can oversee it, but you don't have to be the one who owns it all the way through from beginning to end. Or get it before it's deployed, so you don't have to go back after the fact and remediate it with, you know. But think about Deploy. They're deploying apps today. I mean, they're updating by the hour, where six years ago, five years ago, two years ago was every six to nine months, right? So the pace of this innovation from developers is so fast that the old way of doing security can't keep up. Like they're built for six month release cycles. This is six hour release cycles. And so we had to, it has to change. Security can't stay the way it is. So what we've been doing for seven years for application security is exactly what we're doing for cloud security. Is moving all that earlier. All these products that we've been building over the years is really taking these afterthought security components and bringing them all earlier. You know, bringing everything. Like cloud security is done after the fact. Now we can take those issues and bring them right to the developers who created that and can fix the issues. So it's code to cloud back to code in a very automated fashion so it doesn't slow developers down. Okay, so what's the experience, we all know there's, everybody has more than one cloud. What's the experience across clouds? Can you create a consistent continuous experience? Cloud agnostic. Cloud agnostics, development environment agnostic, you know, language agnostic. So that's kind of the beauty of Steak where you have maybe other certain tools for certain clouds or certain languages or certain development environments. But you have to learn different tools, you know? And they all roll up to security in a different way. And so what we have done is consolidated all that spend for open source security, container security, infrastructure. Now cloud security, all that spend and all that fragmentation all into one platform. So it's one company that brings all those pieces together. So it's a single continuous experience. The developer experience you're saying is identical. Yes, actually one product. It's entitlement that we are getting. Yes. So you're hiding the underlying complexities of the respective clouds and those primitives. Developer doesn't have to worry about them. I call that a super cloud. Super cloud, here you go. Okay, but essentially that's what you're building. You're building on, as Ed Walsh would say, on the shoulders of giants. Exactly. You know, you don't have to worry about the hyperscale infrastructure, right? You're building a layer of value on top of that. Is that essentially a PAS layer? Can I think of it that way or is it a platform? I would say that at the end of the day, the way developers want to use a security tool is the same. So we expose our functionality to them in those ways. If you're using one Git repository or another, if you're using one cloud, we are agnostic to that. It doesn't really affect us in that matter. I want to add another thing about the experience and associate with the consolidation that Peter referred to earlier. When you have a motion that automatically assess you know, our problems that the developer is putting as part of the change management as example, you do creating pull requests. Now adding more capabilities into that motion is easy. So from enablement of the team, you can add another functionality, add cloud, add ISC, add code and so on, like that. Because you already made the decisions on how you are looking at that and how you integrated that into your developer workflows. Right, so it's already integrated for open source. Adding container and ISC is real easy. It's all, you've already done all the integrations. And so for us going to five products and eventually six, seven, eight, all based on the integrations that you already have in the same workflows that developers have become accustomed to. And that reduces a lot of work from the company perspective, right? I can ask you about another sort of trend we're seeing where you see Goldman Sachs last re-invent announced a cloud product essentially, bringing their data, their tools, their software. They're going to run it on AWS. At the Snowflake Summit, Capital One announced a service running on Snowflake, Oracle by Cerner, right? You know they're going to be doing something on OCI, Larry's going to of course make them do that. It's a spin on Andreessen's, every company's a software company. It's like every company's now becoming digital, a software company, building their own SaaS and essentially building their own clouds or maybe someday they'll be super clouds. Are you seeing industry come to sneak and say, hey, help us build products that we can monetize? There's companies, so first off, I think that kind of the first iteration is, you know, all these industries are becoming software driven like you said and more software is more software risk. And so that kind of led us down this journey of now financial services, you know, tech, you know, media and entertainment, financial services, healthcare. Now it's this long tail of low tech. Within those companies, they are offering services to the other parts of the organization. We have- So far mostly internal. Mostly internal other than the global SIs and some of the companies who do that for a living. You know, they build the apps for companies and they are offering a sneak service. So before I give you these, I update these applications, I'm going to make sure I'm running, I'm sneakifying those applications to make sure that they're secure before you get them. And so that, now a company like a Capital One coming to us saying, I want to offer this to others, I think that's a leap because, you know, companies are taking on security of someone else's and I think that's not there yet. Maybe you think it'll happen. We do have the threat Intel that we have a very strong security group that constantly monitors and analyzing the threats and we create this vulnerability database. So in open source as an example, we're at the factor standard in the field. So many of our partners are utilizing the threat Intel feed of sneak as part of their offering, okay? If you go to Docker as an example, you can scan with sneak intelligence immediately out of the gate over there, right? And Tenable, Rapid 7, Trend Micro, they all use the vulnerability database as well. So a lot of financial institutions use it because they did have seven, 10 people doing security research on their own and now they can say, well, I don't have to have those seven, I've got the industry standard for vulnerability database from sneak. And they don't have to throw out their existing tool sets where they have skills. Yes, exactly. All right, Peter, bring us homes, give us the bumper sticker, summarize, reinforce and what we can expect going forward. Yeah, I know. I mean, we're going to continue the pace. We don't see anything slowing us down in terms of just a number of customers that are shifting laughed. Everybody's talking about, hey, I need to embed this earlier and earlier. And I think what they're finding is this need to reinnovate, like get innovation back into their business. And a lot of it had to slow down because we can't let developers develop an app without it going through security and that takes time, it slows you down and allows you not to slow the pace of innovation. And so for us, it's, it helped developers go fast, innovate incredibly quickly, aggressively, creatively, but do it in a secure way. And I think that balance, making sure that they're doing what they're doing, they're increasing developer productivity, increasing the amount of innovation that developers are trying to do, but you've got to do it securely. And that's where we compliment really what every CEO is pushing companies. I need more productivity. I need more aggressive creativity, innovation, but you better be secure at the same time. And that's what we bring together for our customers. And you better do that without slowing us down. Don't slow us down. That's the trade-off that you said it made. Guys, thanks so much for coming to theCUBE. Thanks, David. It's always great to see you again. Thanks, David. I appreciate it. All right, keep it right there. The coverage of Reinforced 2022 from Boston. We'll be right back right after this short break.


What is going on guys, welcome back to the channel and I do appreciate you being here. Today I bring you another Destiny 2 video and today I want to talk about the Twilight Oath, the Dreaming City Sniper Rifle and if it's possible to get this beast from the Menagerie as a curated version. But before we go any further guys, if you do enjoy the video and would like to show your support you can by hitting that like button. If you are new around here and enjoy daily Destiny 2 videos be sure to subscribe. So the Twilight Oath has become a must have sniper for many people out there. Before the Menagerie it was known to only drop upon the Dreaming City as an extremely rare drop. I know it dropped from the Shattered Throne, I believe it dropped from a Tier 3 or Tier 4 Blind Well and a few of the possible places but it is an extremely rare drop and I've only ever seen about 2 drop in my entire time playing Destiny which is craziness. So what's actually special about this curated Twilight Oath? Well the fact it has snapshot sites and box breathing with a Masterwork 10 handling is what seems to draw many people towards this weapon plus people just like to collect these curated weapons just for the collection. And the fact sniping now has become much more popular within PvP due to many people within the community looking to obtain a crucible pinnacle weapon, the revoker you're going to see many many more people sniping and getting the best sniper to help them with this quest is something people are looking to do. So the curated Twilight Oath does it drop from the Menagerie? Well after doing extensive research people it seems as though it actually does. Many people on Twitter are speaking about it, I read it post I saw many people claim they had it dropped from the Menagerie and a few people have actually spoken to myself claim they've had the curated version drop from the Menagerie, proving it with pictures and much more. So what can you do to obviously up your chances of obtaining the curated version from the Menagerie? Well if it does drop here like many are claiming there might be a few things that will work. Firstly I've seen people claim that it will only drop as one of the powerful rewards you get from the Menagerie each week unless you have power and efficiency to unlock I believe it's only one per week. Now this isn't factual it could still drop not being a powerful reward but I did see someone claim unread it that this was the case but they did not prove it but just bear that in mind. So to get the Twilight Oath from the Menagerie within slot one of your chalice you want to use a Rune of Jubilation as you see it guarantees a sniper rifle. In Rune Slut 2 you can either use Rune of Jubilation, Rune of the Beast or Rune of Joy. All of these as far as I know drop the Twilight Oath. Now if you have Rune Slut 3 opened the Rune you want to use here is either Rune of Joy, Rune of Jubilation or Rune of the Beast making the chalice a triple purple Rune combo. Purple Runes in the third Rune Slut give the weapon Masterwork Handling which is to say Masterwork the Twilight Oath curated version has. So to be honest guys even if you don't get the curated version chances are you will indeed land yourself some decent road snipers doing this for sure. But yeah guys this in my opinion is the best way of you up in your chances of getting a curated version from that Menagerie chest. If you do get this to drop or you can confirm you've already had this to drop from the Menagerie please leave a comment down below. Because before this before the Menagerie it was only known to drop on a Dreaming City. Now I've seen many many people claiming that they've had it drop from the Menagerie hence why I've made this video hoping I can help you out in opening your chances of getting the weapon to drop. So yes if you had it drop do confirm down below in that comment section. But on that note guys I am out. Massive shout out to Shucks over on Twitter for supplying me the footage of the Twilight Oath curated version you can see on the screen now. This looking morpher got this to drop yesterday on the Dreaming City. So massive shout out to him his twitter can be found linked within the video description. So yeah on that note I am out. So I hope you guys enjoyed the video if you did leave me a like who did this happen and hopefully I will see you on that next one.


Tip for teaching grammar to EFL students abroad, find it in the text you're reading. Even if you are not doing a grammar lesson, you can still look for and point out the use of interesting, and correct or incorrect grammar in a text you read in class, such as a semi-colon in Dickens for example. You can even go a step further, and collect good examples of grammar from texts if they fit your grammar topics, and write them down on a specific area of the whiteboard or somewhere else in the classroom. You might even have your students create a correct grammar notebook, and collect the examples there for reference. Thanks so much for watching. We are ITTT, the leading provider for TEFL and TESOL training courses. If you like this video, please subscribe by clicking that button down here, and click on any of the videos here on the left, for more interesting teaching tips for getting certified to teach English abroad and online.