News for hackers. Stuff that matters.
Re:Ten Simple IT Security Rules for Early-Stage Startups by guappa on Monday January 22, 2024 @09:02AM (#39089627)
Your coworkers can just film you while you type the password to unlock the screen. And of course if the machine is running the decryption key for the disk is located in the RAM.

If you can't trust your coworkers in the same office, you should absolutely have private rooms that get locked, and shut down your machine completely every time you leave it.

Re:Ten Simple IT Security Rules for Early-Stage Startups by daniel_iversen on Monday January 22, 2024 @09:24AM (#39089816)
It's not about trusting coworkers, it's about creating the right security habits so you don't leave your computer unlocked in situations where it is easily compromised. And it's about closing of the easiest attack vectors (open laptops, reused or simple passwords etc) not about nation-state level hacking possibilities :)
Re:Ten Simple IT Security Rules for Early-Stage Startups by lazide on Monday January 22, 2024 @10:22AM (#39090381)
Trusting co-workers has nothing to do with it. Any random person walking by could do it - cleaning staff, maintenance folks, a guest or visitor, someone ‘surfing’ in behind someone, etc.

And it gives some incentive to everyone to watch each others backs and keep each other honest. Which is how actual trust gets built IMO.

Knowing someone will catch and make sure you know you screwed up on something important before it became a bigger problem, rather than ignoring it and letting it fester.

Higher stakes areas, but most military combat MOS, LEO, skydiving, and climbing groups do similar things - always check that everyone around you has their act together (and give them shit if they miss something) so that there isn’t something serious that gets missed and gets someone or the group killed.

Or in this case, something serious gets missed and the company gets ‘killed’.

Think of it as tough love. And if they can dish it out, they’d better be able to take it or that is a whole nother level of ribbing that’s coming.

Re:Ten Simple IT Security Rules for Early-Stage Startups by guappa on Tuesday January 23, 2024 @01:27AM (#39100215)
> Trusting co-workers has nothing to do with it. Any random person walking by could do it - cleaning staff, maintenance folks, a guest or visitor, someone ‘surfing’ in behind someone, etc.

Precisely. So if you want to be safe, shut down completely the machine. Then all of the people you listed can't access it.

Re:Ten Simple IT Security Rules for Early-Stage Startups by lazide on Tuesday January 23, 2024 @09:48AM (#39103998)
And then wait minutes for things to start up, even if things reopen to their prior state perfectly. As compared to seconds to lock/unlock.

Suspend adds major security issues above and beyond either of these scenarios.

The majority of scenarios, none of those folks are able to do much to a locked machine without powering it off, which resets it to the state you were referencing.

They could install a hardware keylogger of course, and none of these protections would help.

It’s all tradeoffs. SCIF’s are better still after all, and a nightmare productivity wise.

Re:Ten Simple IT Security Rules for Early-Stage Startups by guappa on Tuesday January 23, 2024 @01:33PM (#39107542)
> And then wait minutes for things to start up, even if things reopen to their prior state perfectly. As compared to seconds to lock/unlock.

The price of security is always wasted time.

> The majority of scenarios, none of those folks are able to do much to a locked machine without powering it off

But they are able to unlock it if they saw you unlock it yesterday.

If you have an encrypted hard drive and the key is in a usb you carry with you, they can't do anything.

Re:Ten Simple IT Security Rules for Early-Stage Startups by lazide on Tuesday January 23, 2024 @02:00PM (#39107971)
What is your point exactly?