Skip to content

Example M-2.7: multiple references should have a individual tags. #12

@aaronlippold

Description

@aaronlippold
tag "ref": "1. CIS CSC v6.0 #13.1: Perform an assessment of data to identify
sensitive information. 2.
https://docs.aws.amazon.com/awscloudtrail/latest/userguide/encryptingcloudtrail-log-files-with-aws-kms.html
3. http://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html 4. CIS
CSC v6.0 #6: Maintenance, Monitoring, and Analysis of Audit Logs 5. CCE-78919-8"

something like??

ref: 'CIS CSC v6.0 #13.1: Perform an assessment of data to identify sensitive information.'
ref: 'possible text desc(opt)', url: 'https://docs.aws.amazon.com/awscloudtrail/latest/userguide/encryptingcloudtrail-log-files-with-aws-kms.html'
ref: url: 'http://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html'
ref: 'CIS CSC v6.0 #6: Maintenance, Monitoring, and Analysis of Audit Logs'
ref: 'CCE-78919-8'

This would allow us to correctly display the URI data and also perhaps note that the 2,3 is unneed data? Thoughts?

As defined here: https://www.inspec.io/docs/reference/dsl_inspec/

ref 'NSA-RH6-STIG - Section 3.5.2.1', url: 'https://www.nsa.gov/ia/_files/os/redhat/rhel5-guide-i731.pdf'
ref 'http://people.redhat.com/swells/scap-security-guide/RHEL/6/output/ssg-centos6-guide-C2S.html'

This will be easier once we have #10 done given that we can pass things to the object and it can handle some of the complexities on the back end.

Metadata

Metadata

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions