Renamed to vulnerablecomponents
This commit is contained in:
@ -0,0 +1,17 @@
|
||||
= Vulnerable Components
|
||||
|
||||
== Concept
|
||||
|
||||
The way we build software has changed. The open source community is maturing and the availability of open source software has become prolific without regard to determining the provenance of the libraries used in our applications. Ref: https://www.sonatype.com/hubfs/SSC/Software_Supply_Chain_Inforgraphic.pdf?t=1485298506170[Software Supply Chain]
|
||||
|
||||
This lesson will walk through the difficulties with managing dependent libraries, the risk of not managing those dependencies, and the difficulty in determining if you are at risk.
|
||||
|
||||
image::images/OpenSourceGrowing.png[caption="Figure: ", title="Software Supply Chain", alt="SSC", width="500", height="300", style="lesson-image" link="https://www.sonatype.com/hubfs/SSC/Software_Supply_Chain_Inforgraphic.pdf?t=1485298506170[Software Supply Chain"]
|
||||
|
||||
|
||||
== Goals
|
||||
|
||||
* Gain awareness that the open source consumed is as important as your own custom code.
|
||||
* Gain awareness of the management, or lack of management, in our open source component consumption.
|
||||
* Understand the importance of a Bill of Materials in determining open source component risk
|
||||
|
Reference in New Issue
Block a user