A vulnerable third-party component can introduce risk even when an application’s own code has not changed. Development and security teams examine historical examples, use public resources to identify disclosed issues, and consider inventory and update practices for managing dependencies.

Participants of this module will…

• Hear about historical examples of risks identified in 3rd party components
• Learn about resources on the web that can be used to identify emerging and newly identified vulnerabilities
• Discuss strategies to catalog and update components used in applications properly