search

ComplianceAsCode / content

Security automation content in SCAP, Bash, Ansible, and other formats
https://complianceascode.readthedocs.io/en/latest/
Other
2.22k stars 698 forks source link

Common Criteria references and information should be cross-linked and explained #2461

Closed trevor-vaughan closed 5 years ago

trevor-vaughan commented 7 years ago

Description of problem:

This stems from the STIG requirement for screen for virtual terminal locking per this mailing list discussion. Basically, if there is a reason that one technology is chosen over another, then there should be an actionable cross-reference between the two policies.

Additionally, any additional configuration information from the other standard (in this case the Common Criteria Protection Profile) should be inherited by the referencing standard for a complete configuration solution.

redhatrises commented 5 years ago

Closing. Screen is no longer being used going forward. Also, we know have references to the OSPP profiles starting with OSPP 4.2