The Accidental Cybersecurity Leader

G๐˜ถ๐˜ช๐˜ฅ๐˜ฆ๐˜ฅ ๐˜ฃ๐˜บ ๐˜ข ๐˜ค๐˜ฐ๐˜ฎ๐˜ฑ๐˜ข๐˜ด๐˜ด, ๐˜ฏ๐˜ฐ๐˜ต ๐˜ข ๐˜ฎ๐˜ข๐˜ฑ. I never set out to become a cybersecurity leader โ€” my career began in development and evolved through application leadership and low-code platforms. But when offered the chance to lead our cyber roadmap, I leaned in โ€” not as a specialist, but as someone who understood how systems, people, and business goals connect. Years spent bridging gaps in delivery, support, and governance gave me the mindset to navigate complexity and risk. Cybersecurity leadership, Iโ€™ve learned, is less about controls and more about culture, clarity, and alignment. Sometimes, the best paths arenโ€™t mapped โ€” theyโ€™re guided by a compass.

Dawn Thiart

7/27/20251 min read

I didnโ€™t plan to work in cybersecurity.

My early career started as a developer โ€” head down, solving problems, building systems. Over time, I shifted into senior developer roles mostly working within the ๐—ฃ๐—ผ๐˜„๐—ฒ๐—ฟ ๐—ฃ๐—น๐—ฎ๐˜๐—ณ๐—ผ๐—ฟ๐—บ, and then later into leadership roles. I charted a path in ๐—ฎ๐—ฝ๐—ฝ๐—น๐—ถ๐—ฐ๐—ฎ๐˜๐—ถ๐—ผ๐—ป ๐—ฑ๐—ฒ๐˜€๐—ถ๐—ด๐—ป, ๐—ฏ๐˜‚๐—ถ๐—น๐—ฑ, ๐˜€๐˜‚๐—ฝ๐—ฝ๐—ผ๐—ฟ๐˜, ๐˜๐—ฟ๐—ฎ๐—ป๐˜€๐—ถ๐˜๐—ถ๐—ผ๐—ป๐—ถ๐—ป๐—ด ๐—ฎ๐—ฝ๐—ฝ๐—น๐—ถ๐—ฐ๐—ฎ๐˜๐—ถ๐—ผ๐—ป๐˜€ ๐—ณ๐—ฟ๐—ผ๐—บ ๐—ฝ๐—ฟ๐—ผ๐—ท๐—ฒ๐—ฐ๐˜๐˜€ ๐˜๐—ผ ๐˜€๐˜‚๐—ฝ๐—ฝ๐—ผ๐—ฟ๐˜ ๐˜๐—ฒ๐—ฎ๐—บ๐˜€. That was the ๐˜ฎ๐˜ข๐˜ฑ (IT applications) I had in my hands โ€” and I was following it.

I thought Iโ€™d stay in that lane.

But roles evolve โ€” especially when youโ€™re open to stepping into unfamiliar spaces. So when I was asked to lead our ๐—ฐ๐˜†๐—ฏ๐—ฒ๐—ฟ๐˜€๐—ฒ๐—ฐ๐˜‚๐—ฟ๐—ถ๐˜๐˜† ๐—ฟ๐—ผ๐—ฎ๐—ฑ๐—บ๐—ฎ๐—ฝ, I said yes โ€” not because I had deep expertise in cyber, but because my world in IT applications had already prepared me. I understood how systems were designed, how they were supported, and how they connected to business processes and people. That end-to-end view โ€” from architecture to adoption โ€” gave me the clarity and context to drive cybersecurity forward, even in unfamiliar territory.

That was the moment the ๐˜ค๐˜ฐ๐˜ฎ๐˜ฑ๐˜ข๐˜ด๐˜ด ๐˜ต๐˜ฐ๐˜ฐ๐˜ฌ ๐˜ฐ๐˜ท๐˜ฆ๐˜ณ.

I didnโ€™t come up through traditional cybersecurity channels. But years spent in ๐—ฎ๐—ฝ๐—ฝ๐—น๐—ถ๐—ฐ๐—ฎ๐˜๐—ถ๐—ผ๐—ป ๐—ฑ๐—ฒ๐—น๐—ถ๐˜ƒ๐—ฒ๐—ฟ๐˜†, ๐—น๐—ถ๐—ณ๐—ฒ๐—ฐ๐˜†๐—ฐ๐—น๐—ฒ ๐˜๐—ฟ๐—ฎ๐—ป๐˜€๐—ถ๐˜๐—ถ๐—ผ๐—ป๐˜€, ๐—น๐—ฒ๐—ฎ๐—ฑ๐—ฒ๐—ฟ๐˜€๐—ต๐—ถ๐—ฝ gave me something else: ๐˜ต๐˜ฉ๐˜ฆ ๐˜ฎ๐˜ช๐˜ฏ๐˜ฅ๐˜ด๐˜ฆ๐˜ต ๐˜ต๐˜ฐ ๐˜ต๐˜ฉ๐˜ช๐˜ฏ๐˜ฌ ๐˜ฃ๐˜ณ๐˜ฐ๐˜ข๐˜ฅ๐˜ญ๐˜บ, ๐˜ค๐˜ฐ๐˜ฏ๐˜ฏ๐˜ฆ๐˜ค๐˜ต ๐˜ณ๐˜ช๐˜ด๐˜ฌ๐˜ด ๐˜ต๐˜ฐ ๐˜ณ๐˜ฆ๐˜ข๐˜ญ๐˜ช๐˜ต๐˜ช๐˜ฆ๐˜ด, ๐˜ข๐˜ฏ๐˜ฅ ๐˜ข๐˜ด๐˜ฌ ๐˜ต๐˜ฉ๐˜ฆ ๐˜ณ๐˜ช๐˜จ๐˜ฉ๐˜ต ๐˜ฒ๐˜ถ๐˜ฆ๐˜ด๐˜ต๐˜ช๐˜ฐ๐˜ฏ๐˜ด.

Cybersecurity, Iโ€™ve learned, is more than just firewalls and frameworks โ€” itโ€™s about people, processes, and priorities. Itโ€™s about embedding security into the way an organisation thinks and operates. It requires translating technical risks into business language, influencing behaviours, and making decisions that balance protection with progress. And thatโ€™s exactly where my journey in IT applications gave me the edge.

๐—Ÿ๐—ฒ๐—ฎ๐—ฑ๐—ฒ๐—ฟ๐˜€๐—ต๐—ถ๐—ฝ ๐—ฑ๐—ผ๐—ฒ๐˜€๐—ปโ€™๐˜ ๐—ฎ๐—น๐˜„๐—ฎ๐˜†๐˜€ ๐—ฏ๐—ฒ๐—ด๐—ถ๐—ป ๐˜„๐—ถ๐˜๐—ต ๐—ฎ ๐˜๐—ถ๐˜๐—น๐—ฒ โ€” ๐˜€๐—ผ๐—บ๐—ฒ๐˜๐—ถ๐—บ๐—ฒ๐˜€ ๐—ถ๐˜ ๐˜€๐˜๐—ฎ๐—ฟ๐˜๐˜€ ๐˜„๐—ถ๐˜๐—ต ๐—ฎ ๐—ด๐—ฎ๐—ฝ. A gap no one owns, but one you understand well enough to step into. Thatโ€™s how it happened for me.

If youโ€™ve found yourself stepping outside your original skillset โ€” into cybersecurity, into leadership, into strategy, into uncertainty โ€” youโ€™re not lost.

You might just be an ๐—ฎ๐—ฐ๐—ฐ๐—ถ๐—ฑ๐—ฒ๐—ป๐˜๐—ฎ๐—น ๐—ฐ๐˜†๐—ฏ๐—ฒ๐—ฟ ๐—น๐—ฒ๐—ฎ๐—ฑ.

And thatโ€™s not a detour. Thatโ€™s the path.