Safeguarding open source
Gespeichert in:
| Veröffentlicht in: | SC Magazine vol. 27, no. 2 (Feb 2016), p. 17. |
|---|---|
| 1. Verfasser: | |
| Veröffentlicht: |
SC Media
|
| Schlagworte: | |
| Online-Zugang: | Citation/Abstract Full Text Full Text - PDF |
| Tags: |
Keine Tags, Fügen Sie das erste Tag hinzu!
|
MARC
| LEADER | 00000nab a2200000uu 4500 | ||
|---|---|---|---|
| 001 | 1777248847 | ||
| 003 | UK-CbPIL | ||
| 022 | |a 1547-6693 | ||
| 022 | |a 1051-2500 | ||
| 022 | |a 1095-0893 | ||
| 022 | |a 1066-7822 | ||
| 035 | |a 1777248847 | ||
| 045 | 2 | |b d20160201 |b d20160229 | |
| 084 | |a 102809 |2 nlm | ||
| 100 | 1 | |a Weinberg, Bill | |
| 245 | 1 | |a Safeguarding open source | |
| 260 | |b SC Media |c Feb 2016 | ||
| 513 | |a Commentary | ||
| 520 | 3 | |a How do you overcome this challenge? The key is ensuring use of the most current versions of open source project code and applying the most recent patches - a process I call "open source hygiene." This assures your open source software code base comprises the most resilient code available. Visibility into where open source code "lives" within your stack makes this level of control possible. | |
| 651 | 4 | |a United States--US | |
| 653 | |a Open source software | ||
| 653 | |a Network security | ||
| 653 | |a Automation | ||
| 653 | |a Product development | ||
| 653 | |a Hygiene | ||
| 653 | |a Copyright | ||
| 653 | |a Property | ||
| 653 | |a Visibility | ||
| 773 | 0 | |t SC Magazine |g vol. 27, no. 2 (Feb 2016), p. 17. | |
| 786 | 0 | |d ProQuest |t Science Database | |
| 856 | 4 | 1 | |3 Citation/Abstract |u https://www.proquest.com/docview/1777248847/abstract/embedded/H09TXR3UUZB2ISDL?source=fedsrch |
| 856 | 4 | 0 | |3 Full Text |u https://www.proquest.com/docview/1777248847/fulltext/embedded/H09TXR3UUZB2ISDL?source=fedsrch |
| 856 | 4 | 0 | |3 Full Text - PDF |u https://www.proquest.com/docview/1777248847/fulltextPDF/embedded/H09TXR3UUZB2ISDL?source=fedsrch |