APP -> MDF FCS requirements

The following App requirements should be handled by the following MDF requirements:

APP -> MDF
FCS_CKM.1 -> FCS_CKM.1 & FCS_CKM_EXT.3
FCS_CKM.1/2 -> FCS_CKM_EXT.3 (would require symmetric to be selected)
FCS_RBG_EXT.1 & FCS_RBG_EXT.2 -> FCS_RBG_EXT.1
FCS_STO_EXT.1 -> FCS_STG_EXT.1 & FCS_STG_EXT.2 (though maybe something to more clearly point out the chain may go further than the number of levels here)
FCS_CKM.1/ALGO -> FCS_CKM.1
FCS_CKM.1/3 -> FCS_COP.1/CONDITIONING & FCS_CKM_EXT.6
FCS_CKM.1/1 -> FCS_COP.1/ENCRYPT
FCS_COP.1/2 -> FCS_COP.1/HASH
FCS_COP.1/3 -> FCS_COP.1/SIGN
FCS_COP.1/4 -> FCS_COP.1/KEYHMAC
FCS_HTTPS_EXT.1 -> FCS_HTTPS_EXT.1

FCS_CKM.2 is not clear here, but it doesn't seem like this is likely to be selected in an FE evaluation anyway, so I don't think not having a match in the MDF is a problem.

It seems like all the crypto options should be able to be handled in an FE eval using the MDF as the base, and I don't see that there needs to be too much editing for this in the FE PPM to have this handled (beyond pointers to the proper location)

Start by locating the FE PPM content that maps APP requirements to MDF requirements. Review the crypto mappings in the issue, especially the unresolved FCS_CKM.2 case, and confirm where pointers should be added. Done means the applicable mappings are represented in the FE PPM and the treatment of FCS_CKM.2 is explicitly resolved.