Windows 11 x64 security hardening guide • Hacker News Board

Re: Windows 11 x64 security hardening guide

#51

Post by BrandoElFollito » Sun, Aug 14, 2022, 9:08 PM UTC

pid-1 wrote: post #6

> create another Admin account and transform your current one to limited/ restricted/ standard user account to reduce the attack surface enormously. Don't use Admin account for your tasks! It's crazy how Windows doesn't have a sane way for users to became administrators temporarily. LAPS is a weird hack and Azure PIM doesn't work for local admin.

> enormously

[citation needed]

https://xkcd.com/1200/

What is the valuable thing for an attacker?

User data, credentials? Available as a user

Computer capacities for mining? Available as a user

Installing persistence? Available as a user

Installing remote management? Available as a user

Re: Windows 11 x64 security hardening guide

#52

Post by nick9847 » Mon, Aug 15, 2022, 9:19 AM UTC

Talk about unnecessary complication. This is extreme paranoia in this day and age.

Re: Windows 11 x64 security hardening guide

#53

Post by AshamedCaptain » Mon, Aug 15, 2022, 1:34 PM UTC

TingPing wrote: post #47

encryptluks2 wrote: post #36

Earlier quoted context omitted.

A quick Google search will show how easy it is to enable the Local Group Policy Editor on Windows Home.

Sure it's easy to crack windows too. They still put too much behind Pro like disk encryption, something that should be default.

Note that (boot) disk encryption is available on Home (and enabled by default), it's just external disk encryption which is only available on Pro.

Re: Windows 11 x64 security hardening guide

#54

Post by PcChip » Tue, Aug 16, 2022, 2:57 AM UTC

josephcsible wrote: post #46

PcChip wrote: post #45

Earlier quoted context omitted.

Why would that be a joke?

Because a zero-day doesn't actually stop being a zero-day just because it's existed for more than 24 hours.

by definition it does... after 24 hours, that gives other people time to be the guinea pigs to run the program first, so that Defender will recognize it by the time you run it

Re: Windows 11 x64 security hardening guide

#55

Post by josephcsible » Tue, Aug 16, 2022, 1:02 PM UTC

PcChip wrote: post #54

josephcsible wrote: post #46

Earlier quoted context omitted.

Because a zero-day doesn't actually stop being a zero-day just because it's existed for more than 24 hours.

by definition it does... after 24 hours, that gives other people time to be the guinea pigs to run the program first, so that Defender will recognize it by the time you run it

> by definition it does

https://www.trendmicro.com/vinfo/us/security/definition/zero... says that the definition of a zero-day vulnerability is "a vulnerability in a system or device that has been disclosed but is not yet patched." There's no magic patching fairy that comes after 24 hours, so it's still a zero-day after that for as long as it takes someone to patch it.