[Enter feedback here]
running the _DG_Readiness_Tool_v3.7.2.ps1 -Ready_

tells everything is running.
lsalso.exe is running too.

but credetial dumping from LSASS.exe is still possible:

found out on running _.DG_Readiness_Tool_v3.7.2.ps1 -Capable_
that there is SSM Mitigation an HSTI absent:

⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Hello @mario-sit - Thank you for your feedback on the document. Can you please confirm what changes is required on the document side? Is this the code somewhere or anything else.
Thanks.
Imran.
This ticket appears to be about whether the security improvement is available and enabled, or not available and disabled, when running the DG Readiness Tool.
See for example closed issue ticket #5787 (Blue Screen Enabling DG/CG with DG Readiness Tool) and How do I enable HSTI, NX and SMM on Windows 10 Enterprise? (https://answers.microsoft.com/en-us/windows/forum/all/how-do-i-enable-hsti-nx-and-smm-on-windows-10/333c0fe1-6dd5-4ae2-b9f8-dce615de21c9?auth=1)
Hi @joinimran!
i think it is wrong in the description and the result of the ps1 script that there is mentioned, that device guard is working on all SKU's. it is only working on the Enterprise Edition. it does not take affect for example on win10 pro. it gives people a wrong confidence when running the script, and it tells that Credential Guard is running. even if it is not supported on other SKU's then the enterprise edition.
thank you, Mario
i think it is wrong in the description and the result of the ps1 script that there is mentioned, that device guard is working on all SKU's. it is only working on the Enterprise Edition. it does not take affect for example on win10 pro. it gives people a wrong confidence when running the script, and it tells that Credential Guard is running. even if it is not supported on other SKU's then the enterprise edition.
But Windows (Pro) itself provide this feature in group policy editor (gpedit.msc) under:
Computer Configuration -> Administrative templates -> System -> Device Guard -> Turn on Virtualization Based Security
And there isn't such an info too.
Regarding a document update and note to the effect of stating that the tool may only be effective on Windows 10 Enterprise:
PR #8869 is ready for review, comments, and suggestions.