Did your software team scramble when the Log4j vulnerability became public? Was it easy for your team to identify the different versions used in all your software projects? Are you ready for when the next big open source vulnerability hits?
Software bills of materials (SBOMs) are effective at helping you identify all the software components that are embedded in your applications. This is not only useful when a security incident arises but is becoming a necessary requirement to ensure software transparency.
Just as food labels provide consumers with a list of ingredients in the food they consume, an SBOM provides software consumers with a list of components included in the software they procure. In addition, an SBOM can also help to gauge the quality of those software components.
In this Techstrong Learning Experience, learn how SBOM generation can easily become a part of your continuous integration/continuous delivery (CI/CD) pipeline and how developers can leverage SBOMs to produce higher-quality software products.
Key Takeaways:
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: