Windows Hardening

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

CredulousDane

Well-known member
Sep 26, 2020
62
6
Windows is vulnerable to the same three things that most OSes are:
1. an attacker who can put hands on the hardware
2. a user who is ignorant of good security/safety practices
3. an attacker using the network

So my recommendations are:
1. don't let strangers near your hardware
2. get educated on good security and safer computing
3. use a good router/firewall device and keep it up to date

If you do these things, I don't think anyone would consider you not making a best effort. There are always going to be zero days and other things that you can't prepare for.... so the absolute best advice is to make sure you follow a good backup strategy for the data you care most about.
 
I think I'm doing alright with those recommendations, I'm just always curious to learning more and hardening is new to me. But is your recommendation then that hardening is more for the hardcore and not so much the mainstream? ;)
 
Microsoft has some white papers for hardening.

Standard rules apply; go through every component and every service and understand what it exists for. Disable or remove everything you can. Limit the accounts and rename administrator (plus change the password and put the only copy of that password in a safe). Think about limiting your daemons into their own accounts without system-wide access, especially to the filesystem.

I assume this is Internet-facing; I'd only allow the necessary ports/protocols to it, isolate it from other devices in at least a VLAN and patch early.
 
  • Like
Reactions: CredulousDane
Microsoft has some white papers for hardening.

Standard rules apply; go through every component and every service and understand what it exists for. Disable or remove everything you can. Limit the accounts and rename administrator (plus change the password and put the only copy of that password in a safe). Think about limiting your daemons into their own accounts without system-wide access, especially to the filesystem.

I assume this is Internet-facing; I'd only allow the necessary ports/protocols to it, isolate it from other devices in at least a VLAN and patch early.

I'll go throught it carefully and will start with the Simple solution for now :)
 
is your recommendation then that hardening is more for the hardcore
I wouldn't quite go that far, there are simple things you can do, but even the simple things come with the tradeoffs of making your PC less friendly. Let's say you disable file sharing between PCs (as one measure you could take to slow down the spread of a crypto-malware, for example.) Some time later you want to do something unrelated, and it fails, and now you're in this icky situation of not understanding why shit's broke. (Say printing breaks (yes I know it's already broke right now, LOL) and you really need to print something... are you going to guess that turning sharing back on is the fix? Maybe, but not right away.)
 
  • Like
Reactions: CredulousDane
Yeah, I see. It could be those changes that are forgotten and some day I need what has been disabled not consciously knowing what's wrong ;)

Will look into hardening but probably not change a lot.

Thanks for your feedback :)
 
I just recently started using a similar program from the same developer called "Configure Defender". Nothing has blown up as of yet but I am rather puzzled as to why he has 3 programs that "seem" to do the same thing?
 
After RTFM of all three, I see that Configure Defender can be run along side (compliment) Simple Windows Hardening or Hard Configurator.
 
Simple Windows Hardening now comes with a tool which seems good if you have MS Office installed AND Microsoft decides to enable VBA again.

1653081203691.png