Timeline for Software Security Testing in a DevSecOps Pipeline
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 9, 2018 at 21:29 | comment | added | Tensibai | I fully agree it worth it :) It just sounds too summarized in your answer to fully answer the question in my personal opinion. | |
| Jan 9, 2018 at 18:49 | comment | added | Moritz | I agree that doing it properly has many facets and has to reflect the team’s values. That being said, there is so much support/many frameworks and the payoff so significant that spending time/money on it is well worth it. | |
| Jan 9, 2018 at 18:46 | history | edited | Moritz | CC BY-SA 3.0 |
added 971 characters in body
|
| Jan 3, 2018 at 14:52 | comment | added | Tensibai | Complement after thinking about it: the overall idea is OK, the main problem is ensuring the test coverage is really covering all the app, and that's far from straightforward to be summarized as 'Integrate properly with a CI server' | |
| Jan 3, 2018 at 13:25 | comment | added | Tensibai | And how do you ensure there's enough unit tests for the whole application and none of the form are vulnerable to code/sql/javascript injection ? (That's everything this question is about) | |
| Dec 31, 2017 at 9:59 | history | answered | Moritz | CC BY-SA 3.0 |