kubehunter-icn-20200513.txt
notes-icn-20200513.txt
vuls-icn-20200513.txt
[ICN-357] Investigate kubehunter failures Created: 12/May/20 Updated: 24/Jul/20 Resolved: 13/May/20 |
|
| Status: | Done |
| Project: | Integrated Cloud Native NFV |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Medium |
| Reporter: | Igor Duarte Cardoso | Assignee: | Igor Duarte Cardoso |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
kubehunter-icn-20200513.txt
notes-icn-20200513.txt
vuls-icn-20200513.txt
|
| Epic Link: | ICN Bluval compliance |
| Sprint: | ICN Sprint 17, ICN Sprint 18 |
| Story Points: | 3 |
| Description |
|
Investigate kubehunter failures and decide what the next steps are. Perhaps they are fixable within the time outline below, perhaps the issues have to be raised to the security committee. The investigation will encompass that. |
| Comments |
| Comment by Igor Duarte Cardoso [ 13/May/20 ] |
|
Some work was also done on investigating Vuls vulnerabilities. Together with the remaining kubehunter failures (inside pod scanning), an email was send to the security sub-committee requesting feedback. Attaching vuls and kubehunter notes and failures. Closing story. |