Boris Arapovic
Yeah, correct. So I think there are many ways on how we as QAs can contribute. I think, first of all, it actually starts in having some static application security testing place that actually helps also the developers and when we develop code, for example, just to also detect already some security issues which might be having hardcoded password as a prime example. Trust me, it still happens. It's not that this is something like, no, this won't happen on application. This for sure can happen, but I think as a first step we QAs can help to set those things up. Maybe even consult involve a cybersecurity engineer in properly to set this up properly. As I said, for example, checking the source code, but it also might be checking the packages that you have and you know about Node.js, you typically have the NPM and when you just type NPM install, it will print out some security vulnerabilities that you will have from packages. And I would say we as QA, also should drive this together with the developer and make the developer a surveyor fit. And also kind of I wouldn't say fight for that, but make also time that we can also fix such issues because those are typical low hanging fruit when it comes to SAS. As a next step, typically when because you mentioned agile and sprints and so on. I think what we can do is, as you said, already create some test cases where we also cover some of the edge cases. Let's say for example, we implement the log in feature. When I think about the login feature, my first thought would be what about the recapture? Do we need like how do we protect it? This is like, I don't need a speed to be necessarily a cybersecurity expert to bring such perspective. And I think we as QA often have to perspective the technical, but also on the other hand, the business perspective. And this is like also think about on I as a user, how I can be protected in a way from it's really quite often really obvious security issues. And I would say that's of course the test cases, the SAS that I mentioned. And I would say also where we can bring a lot of value is in designing session based exploratory test sessions together with two teams. We have those, for example, personas that I can do. And imagine now you create the persona where you have the hacker, how hacker calls, where you can see this is the objective of the hacker, this is the approach of the hacker, this what the hacker want to do. And then you organize such a session where you have like, let's say all the typical personas, but you have also like the hacker persona. And you then just let, for example, the developer pick the persona and really think about they are now the hacker, what could they do? You could do that for example, during the release level, but you could also do that on a feature level. But I just mentioned log in for example. How could such a hacker may be bypass the authentication mechanism? Or what could a hacker do? And yeah, as I mentioned for exploratory testing, we have one path is the persona and the other path what we also as ..... could do is create charts where we could say, for example, we could create in case of the login as a hacker, I want to bypass the security restriction by providing some SQL injections or we could make it brought up by some injections. And they are like different things, but you can use there to apply it and you can be really creative and that other from experience, that's typically what the developer likes the most to test. It's not having the checklist, but it's really like having this creativity that they can play out and that really helps also to boost it. And additional point, what I want to add there is of course, we as QAs test. That's also like when we test a feature, we can bring in this perspective of course. But I think also at the moment when we have like very critical releases, very critical features that we want to release, let's say, for example, we add a new payment method within the checkout. There, we might then consider a security expert to actually pen test it once we maybe done some basic checks. And I think that's really something that that's a lot of value also from the whole team perspective in addition to that, because sometimes you really need an expert. You can't test all like maybe the tricky combinations, but the low hanging fruits, I'm pretty sure confident a Scrum team can cover a lot of those things.