This TechNet blog states that:
Cryptographic Operators: FIPS 140-2 defines a “Crypto Officer” role, which is represented by the Cryptographic Operators group in Windows, first introduced in Windows Vista SP1.
When the "
System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing
" security setting is configured in local or group policy objects, only members of the Cryptographic Operators group or the Administrators group can configure Cryptography Next Generation (CNG) settings by default. Specifically, Cryptographic Operators can edit the cryptographic settings in the IPsec policy of Windows Firewall with Advanced Security (WFAS).
I have performed the following:
- Enabled the "
System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing
" security setting in Local Security Policy. It can be found under theSecurity Settings -> Local Policies -> Security Options
key. - Created a new standard user.
- Added the user to the
Cryptographic Operators
group.
I noted that this user cannot even access Windows Firewall with Advanced Security (WFAS), without first being a member of Network Configuration Operators
. Then, I noted that any member of such group can access WFAS, and create new rules under the Connection Security Rules
, including IPsec rules. In other words, the user need not be a member of the Cryptographic Operators
group.
I then tried another thing: I opened MMC, and added the "IP Security Policy" snap-in. Oddly, the user (which is a member of the Cryptographic Operators
group) does not have access to these settings:
Could you please help me figure out the task which members of the Cryptographic Operators
group (but not standard users) can perform?