Whether Incident or Accident — We Need to Prevent

I came across this intriguing report recently -“Microsoft worker accidentally exposes 38TB of sensitive data in GitHub blunder — Included secrets, private keys, passwords, 30,000+ internal Teams messages” https://www.theregister.com/2023/09/18/more_microsoft_token_trouble/

What about the idea of the identical cryptographic keys generated on-the-fly when (only when) 3 out of 10 or so pre-registered personnel go through the identity authentication by Expanded Password System which enables the users to make use of their episodic memory, say, non-volatile memory of their pleasant personal experience?

The crypto key thus generated will be eliminated when the program is shut down and does not exist anywhere in the universe until any combination of 3 operators of the pre-registered 10 or so work together to re-generate the identical key from their non-volatile episodic memory.

We came up with PoC in 2004 and a working prototype in 2005, but had to discontinue the project due to the lack of interest from the cybersecurity sector. We may have started the project too early. The project can be revived at any time when we secure the budget or a tech partner.

- Reference -

“Solution Resides in Citizen’s Brain Unnoticed” (1 year ago) https://www.linkedin.com/posts/hitoshikokumai_democracy-privacy-ethics-activity-6908966261007503360-_Cd_

“Non-Existent Crypto Keys to be Regenerated from Image Memory when Needed” (8Sep2023) https://www.linkedin.com/posts/hitoshikokumai_microsoft-explains-how-china-stole-one-of-activity-7105818025685106688-bYVs