Requiring people to know everything is a strawman. Raising some basic awareness about risk factors in software systems such as "crypto, authentication, security are hard to get right", is not the same as expecting everyone to be able to implement constant time elliptic curve cryptography in assembly.

Understanding the boundaries of your own knowledge, where to delegate¹ to someone else or do some research to deepen your knowledge is also not the same as knowing everything.

¹ using libraries is not quite the same as delegation if you can't even assess if you're using them correctly or if they do the right thing. You still have to meet it where it is.

You don't have to know everything about everything. You just have to RTFM enough to understand what you're doing and what the ramifications are of doing it wrong. If you're not sure, ask a more senior dev for guidance.