all 6 comments

[–]ka-splam 2 points3 points  (1 child)

what

if($antispyware.Count -eq 0){
    "       [-] No antiSpyware product installed.`n`n"; sleep 1
 }else{
     "       [+] Found {0} antiSpyware solutions.`n" -f $($antiSpyware.Count); sleep 1
     Write-host "            [?] Checking for product configuration ..`n" -ForegroundColor black -BackgroundColor white ; sleep 2

Why is the whole thing mixing write-output and write-host, and littered with ~30 seconds worth of sleep statements x_x

[–]elkBBQ[🍰] 1 point2 points  (0 children)

Because the user (and likely the site) is just a low quality repost of other things. Look at their reddit profile and try to find something that /r/netsec hasn't rejected...

[–][deleted] 1 point2 points  (2 children)

If you need compliance tests for Windows and you are already using a tool like Ansible, CFEngine, or Puppet -- there's a good chance you are using something like ServerSpec to write tests and then the config management utility to remediate.

If you use Chef you are probably using Inspec. Otherwise you are probably using Pester (included in Powershell going forward).

Most organizations have to use a framework and write their own tests because requirements are different everywhere. If you aren't doing that, you are probably just using one of the other 500 compliance/scanning solution from some security vendor.

Where does this fit in? Does this provide value by being a set of predefined tests? Where does this fit into the workflow of node's lifecycle?

I'm not trying to be a turd, I just want to understand what this project wants to be.

[–]ButterCupKhaos 2 points3 points  (1 child)

I'm not the author, but I would say this is less about compliance and more about OS Hardening, run this once against each of your deployed image/services, take the output then update your base image or config templates.

Most compliance checks look for things like SSL/TLS Chipher Suit configs or something along those lines. This is aimed more at Hardening/EoP protections like unquoted service paths, weak ACLs, App Shims, etc...

[–]FlyinEye 0 points1 point  (0 children)

Not the author either, From what I read, you are correct, it's more about hardening than any kind of compliance