The Risks of Component Security & How to Deal with Them

Watch Now

To watch this webinar you’ll need an Infosecurity Magazine account. Log in or sign up below.

Log In

Sign Up

Get up-to-the-minute news and opinions, plus access to a wide assortment of Information Security resources that will keep you current and informed.

This will be used to identify you if you take part in our online comments.

Your password should:

  • be at least eight characters long
  • be no more than 25 characters long
  • contain at least one uppercase, lowercase and special character
  • contain at least one digit
  • only contain alphanumeric characters or ~!@#$%^&*()_-+=?.

For more information explaining how we use your information please see our privacy policy.

By registering you agree with our terms and conditions.

Research shows that only 52% of organizations that use third party applications update them when a new security vulnerability becomes public.

Third-party code is now relied upon more than ever by companies seeking to leverage features and functionality that already exists, but these organizations must inventory and manage these components in order to ensure visibility into potential security exposure, reducing the risk of breaches, failing to meet compliance requirements and new, stricter regulations.

In this webinar we will explore how organizations can best take on open source risk and elaborate on findings from a recently published Vanson Bourne study with input from 400 applications.

Key takeaways:

  • How IT organizations are approaching DevOps and security’s role within this new paradigm
  • Detailed insights into the level of usage of open source components 
  • The latest trends and practices around application inventory management

Speakers

Callum  Budd

Callum Budd Project Manager, Vanson Bourne

    Mark Curphey

    Founder and CEO, SourceClear

      James Jardine

      CEO, Jardine Software Inc

      Brought to You by

      Should you register for this event your information will be shared with the sponsor indicated above. Please see Infosecurity Magazine’s privacy policy for additional information.