[nhf]

I would encourage your daughter to cast a wide net. Being technical does not always mean being an engineer or a scientist (computer or otherwise), and being an engineer/scientist doesn't always mean being technical.

Some of today's most interesting and exciting "technical" challenges have their roots in many disciplines. Cybersecurity can be tackled from a full range of perspectives, from the highly technical (e.g. cryptography) to traditionally non-technical disciplines like law, public policy, and design. The kind of deep thought our world needs on things like AI and ML needs people who are just as informed about the social sciences, psychology, philosophy, and economics as they are about computer science. Our ongoing debates about issues like content moderation or digital privacy need folks who understand how to think about people, including those who are at risk and vulnerable, and then translate that knowledge into the language of engineers.

And even though we've made progress on this front, our governments, courts, and legislatures are still running on a deficit of knowledge about tech, which is a whole different ballgame. (I'd encourage reading Bruce Schneier's site on public interest technology if you're interested: https://public-interest-tech.com/)

All this is to say: if your daughter wants to go the hardcore tech route and loves solving CS or software engineering challenges, more power to her! But I also hope that she doesn't feel limited or boxed in by the traditional definitions of the discipline.