When running SCAP Workbench and trying to scan a Windows 10 machine remotely I get the following error
Failed to locate Oscar on remote machine. Please check that opens cap-scanner is installed on the remote machine.
I have Scap Workbench installed on the machine which should be the equivalent of installing opens cap-scanner on a linux machine. I also have soap compliance checker installed.
Windows machine settings below:
UAC disabled
Remote registry enabled
Visual Basic and Redistributable installed
SSH running successfully
Firewall disabled
Openscap Base msi installed, but not sure if it is running
OpenSCAP Version:
Openscap Base 1.3.
Scap Workbench 1.1.5 compiled with Qt 4.8.7, using OpenSCAP 1.3.0
Scap Compliance Checker 5.4
Operating System & Version:
Remote machine - Windows 10
Steps to Reproduce:
Using Scap workbench, load windows benchmark file
Click remediate, then scan
Sign in using SSH credentials
At that point the error is produced
Actual Results:
What the message tries to say is that when one logs in using ssh, the oscap executable is available.
Although OpenSCAP is technically capable to run on Windows, this feels like a stretch.
Description of Problem:
When running SCAP Workbench and trying to scan a Windows 10 machine remotely I get the following error
Failed to locate Oscar on remote machine. Please check that opens cap-scanner is installed on the remote machine.
I have Scap Workbench installed on the machine which should be the equivalent of installing opens cap-scanner on a linux machine. I also have soap compliance checker installed.
Windows machine settings below: UAC disabled Remote registry enabled Visual Basic and Redistributable installed SSH running successfully Firewall disabled Openscap Base msi installed, but not sure if it is running
OpenSCAP Version:
Openscap Base 1.3. Scap Workbench 1.1.5 compiled with Qt 4.8.7, using OpenSCAP 1.3.0 Scap Compliance Checker 5.4
Operating System & Version:
Remote machine - Windows 10
Steps to Reproduce:
Using Scap workbench, load windows benchmark file Click remediate, then scan Sign in using SSH credentials At that point the error is produced Actual Results:
Expected Results:
Additional Information / Debugging Steps: