Post Quantum Readiness Guideline

Administration made a mission statement to go Post Quantum safe by 2029 to ensure security of the organization and users of the products produced by the company. Therefore, an initiative has been started by CTO to progress on the areas affected by possible PQC attacks and prevent future possible ones as well.

Important

Please for the love of god, don't copy-pasta the instruction or anything to LLM (AI generally speaking) to get further help, trust me it won't end good.

About

This repository strives to make a concise guideline for the company executives based on researches done on Post Quantum Cryptography by Open Source team. Guidelines are categorized based on responsibilities and areas to execute specific changes to.

Pick guide for ...

If the reader is (replace your title) refer to the file ...:

• Q&A: Q&A.md [Ready!]
• SecOps: SecOps.md [Almost Ready!]
• DevOps: DevOps.md [In Progress...]
• Sysadmin: Sysadmin.md [WIP!!!]
• Backend Developer: Backend.md [WIP!!!]
• IoT & Embedded developer: [WIP!!!]

Contacts

If you have questions to ask, please feel free to DM me on Uchar/Matrix at @orzklv:uchar.uz.

Useful Links

All useful links used in researches will be listed at Useful.md and updated over the time as the research progresses more on this field with the help of our professionals. Contributions are welcomed! Also, this file serves us as a way to citate things.

License

The contents are licensed under the CC-BY-4.0 License - see the LICENSE file for details.