Why is configure_crypto_policy checking for existence of /etc/crypto-policies/back-ends/nss.config?

#### Description of problem:

The `configure_crypto_policy` rule checks for the [existence](https://github.com/ComplianceAsCode/content/blob/cbfa007df7f249a2823f11c0a701d030d8502995/linux_os/guide/system/software/integrity/crypto/configure_crypto_policy/oval/shared.xml#L89) of the `/etc/crypto-policies/back-ends/nss.config` file, without reading its content nor verifying if it's a symlink.

#### SCAP Security Guide Version:

[v0.1.77](https://github.com/ComplianceAsCode/content/releases/tag/v0.1.77)

#### Operating System Version:

Red Hat Enterprise Linux 9

#### Question

What is the rationale behind the check of the existence of the `/etc/crypto-policies/back-ends/nss.config` file?

I've not been able to find the answer in the CIS Red Hat Enterprise Linux Benchmark documentation.

Thanks.