FIPS enabling REG_DWORD Registry Key will need to be set to value 1

[TSI-Prognosis]

Hello,

FIPS enabling query for Registry key settings:

Acording to guide we also need to have Microsoft  API encrypted.

We checked servers where is this in state ENABLED.

(HKLM\System\CurrentControlSet\Control\Lsa\FIPSAlgorithmPolicy\Enabled)

This thing is the part where is recomended to "set  REG_DWORD Registry Key will need to be set to value 1"

This seems to be an action that could change and disable other sethings on server not only for Prognosis purposes.

As this is change in registry key settings, I assume it will affect all passwords and more windows parts what could be harmful for other funcionalities of our servers.

Is this step "to set REG_DWORD Registry Key to value 1 needed or can this be omitted  to fulfil Prognosis FIPS encryption recommendations?

Thank you

Martin

[SCOTT_BALDWIN · Accepted solution]

Hello @TSI-Prognosis,

Prognosis to Prognosis communication is encrypted by default. When FIPS is enabled in Prognosis, then additional security actions are also enabled.

I believe this setting REG_DWORD is required for Microsoft communication to be considered FIPS compliant. Prognosis should work with or without changing this setting.

Thank you,
Scott Baldwin

[TSI-Prognosis]

Thank You Scott! This makes sense. I appreciate your reply.

Kind Regards,

Martin Babco