QA Kitchen #01 - Testers vs CISO: Battle Royale

Imagine this: In a simple setup, every tester has access to the system and databases without much hassle. But once things get more complex, especially in hybrid environments, access starts becoming a real pain. You’ve got VPNs, firewalls, policies where databases are locked down, and then you add the need for credentials—whether it’s for a database or Kafka, whatever.

Now, picture a bigger company. Testers come and go, and each time, you have to go through the whole process again—setting them up with access, managing credentials, and navigating security policies. Worse, you could run into a situation where a tester gets access, but a policy change revokes it from someone else. It's a headache!

So how do we solve this in a way that works across the board and doesn’t break every time a new tester shows up or a policy shifts?

Registration required see event link: https://events.teams.microsoft.com/event/5575dbde-f8c1-4783-bf52-86f4229528ac@fcb1a5fb-a322-461e-95d9-e47db41c605c

QA Kitchen in general

The concept of QA Kitchen is to share problems and solutions across borders, to get out of own bubble. Each session has a pre-selected theme (case study) with a kitchen master that presents the issue and also one of possible solutions.

QA Kitchen is brought to you by PumpITup, a small company specialising in Application Delivery Transformation especially around QA issues. This initiative aims to have a broader platform to learn new things a bit more interactive than just webinars and more time efficient than regular meetups or conferences.

General agenda

15min - Case study intro by the kitchen master
10min - Discussion in smaller groups in break-up rooms
15min - Summary of proposed solutions to the whole audience
20min - Presentation by the kitchen master of their solution