Sponsored by CYCODE
The SolarWinds breach underscores the importance of verifying the integrity of each phase of the development to prevent code tampering. On the surface, this means establishing the expected output from each phase of development and then confirming the output is as anticipated in the next phase. For example, if code is signed at the commit, do the files still match in the build? However, there are many additional precautions that should be taken in order to reduce the likelihood of attackers or malicious insiders gaining access to critical systems, development infrastructure and code in the first place.
This webinar will discuss preventing code tampering across key phases of the SDLC including Development, the Build and Production. The webinar will cover
Attendees will learn actional steps they can take now to harden their DevOps pipelines and increase the integrity of their SDLCs to minimize the risk of their code being tampered with.
You’ve probably written a hundred abstracts in your day, but have you come up with a template that really seems to resonate? Go back through your past webinar inventory and see what events produced the most registrants. Sure – this will vary by topic but what got their attention initially was the description you wrote.
Paint a mental image of the benefits of attending your webinar. Often times this can be summarized in the title of your event. Your prospects may not even make it to the body of the message, so get your point across immediately. Capture their attention, pique their interest, and push them towards the desired action (i.e. signing up for your event). You have to make them focus and you have to do it fast. Using an active voice and bullet points is great way to do this.
Always add key takeaways. Something like this....In this session, you’ll learn about: