Windows Defender is enough, if you harden it

Re:Windows Defender is enough, if you harden it by tomnipotent on Sunday March 06, 2022 @06:47PM (#30582447)

You can add folder and extension exclusions to Defender. I do this to the root of my source code folders and it helps immensely.

[ Parent | on HN ]

Re:Windows Defender is enough, if you harden it by jraph on Monday March 07, 2022 @01:37AM (#30584819)

On the other hand, isn't node_modules the folder that shouldn't be excluded from antivirus scan?

[ Parent | on HN ]

Re:Windows Defender is enough, if you harden it by sundvor on Monday March 07, 2022 @02:21AM (#30585060)

Perhaps it's one better suited for periodic scanning? At least from a performance point of view.

Perhaps one ought to have live scanning enabled when updating packages, then disabled when not.

I look forward to seeing other replies.

[ Parent | on HN ]

Re:Windows Defender is enough, if you harden it by tomnipotent on Monday March 07, 2022 @06:53PM (#30594883)

The challenge is that excluded folders/extensions apply to both real-time scanning and manual/periodic scanning.

What we really need is the ability to disable real-time scanning on one set of folders/extensions, while still including them with scheduled system-wide scans.

[ Parent | on HN ]

Re:Windows Defender is enough, if you harden it by sundvor on Wednesday March 09, 2022 @07:18PM (#30621734)

Thanks, that's a great point. It made me think we could probably do this programmatically - perhaps as part of a script to carry out the full scan? Add the folders of interest, scan, then remove when completed.

https://docs.microsoft.com/en-us/powershell/module/defender/...

Or, even just run said folders as a custom scan!

`Start-MpScan -ScanType CustomScan -ScanPath PATH\TO\FOLDER-FILES`

[ Parent | on HN ]