Update STIG checks to perform scope expansion

Improve the scope expansion functionality for configuration files when running STIG checks. Currently it is a 1-to-1 comparison between the ID (user or group) listed in the config file versus the access list check. It would be greatly improved by including intelligence that identifies differences between userids and group ids and is capable of considering users connected to the groups.

We think this is a good idea because:

1) The time and effort required to accurately populate and maintain the STIG configuration files is significant because careful consideration is required when selecting whether userids or group ids should be used in any given config file. Significant time savings could be realized by the user community.

2) If a userid is inappropriately connected to a group in a config file, the STIG will provide a compliant result because it considers the group and not the users connected. The accuracy of the results would be significantly improved.

3) If a userid is listed in the SYSPAUDT config file, but access to a SYS1 dataset is granted to it via a group connect; the STIG will provide a non-compliant result because it looks for the userid directly in the access list rather than considering group connections. The accuracy of the results would be significantly improved.

4) There is no ability to create organizational associations because the STIG performs a 1-to-1 check between IDs in the config file and the access list. Example: can't leverage organizational groups in config files because functional groups are what are listed on access lists and the current zSecure Audit behavior doesn't consider group connections. zOS management would be improved.

5) Competing products from other vendors include this functionality. Important customer retention would be realized.