Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub...
by chaps on Thursday October 13, 2022 @07:17PM
(#33197732)
Heh, sometimes, sure. In a separate comment I mention a company with whiteboard passwords. What I didn't mention is that they had a glass wall that you could look into from a well-traffick'd hallway. One of the larger companies that worked at the office (not any longer) rhymes with loinbase.
Also, I no-joke heard of a company that absolutely, unironically, did the webcam thing with RSA tokens.
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub...
by gw99 on Thursday October 13, 2022 @06:56PM
(#33197551)
Just stick an Amazon t shirt on, a reflective yellow waistcoat and a box and you can walk into most SMEs without anyone blinking an eye.
I've seen it done hundreds of times...
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub...
by baxtr on Friday October 14, 2022 @04:47AM
(#33201127)
Is there a corresponding ISO control for this?
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub...
by gw99 on Friday October 14, 2022 @07:01AM
(#33201900)
There probably is but ISO certs are just paperwork filed. Reality is different.
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub...
by baxtr on Friday October 14, 2022 @09:01AM
(#33202958)
Sure. But then again you need a framework to approximate reality. ISO isn’t perfect by any means. But it’s a start.
What do you use?
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub...
by gw99 on Friday October 14, 2022 @10:24AM
(#33203909)
ISO 9001 + 27001 :(
Re:Toyota Accidently Exposed a Secret Key Publicly on GitHub...
by throwaway290 on Friday October 14, 2022 @09:43AM
(#33203392)
At least falls under 31000's framework for identifying and dealing with risk
At least, until you have a network-attached webcam pointed at your whiteboard.
But the solution to the webcam problem is to write its access credentials on your whiteboard, thus forming a circular and perfectly secure loop.