Good afternoon,
Before I start getting too far down the road with creating the rule for this, I
had some basic process questions about the contents of references and
identifiers in the rule.yml. Basically, I don't know where to obtain about 60%
of the documents referenced in other similar rules.
Inside, for example,
linux_os/guide/system/auditing/auditd_configure_rules/audit_kernel_module_loading/audit_rules_kernel_module_loading_init/rule.yml
there are references to cui, cis, hipaa, and so on...
- Do I need to establish those as part of the rule writing, and if so, is there
a handy place to obtain that information?
- if the answer is no, should I leave stubs entries for the other guidance
documents ( eg "hipaa: " ) and just focus on populating the DISA information
- How do I find out if a CCE has been assigned for the rule and add it to
identifiers
- I'm unfamiliar with the offerings outside the EL(5-8) products, how do I (or
do I) determine product applicability for prodtype
I'd like to do as much right as I can out the gate, so thanks in advance for
any and all advice,
Mark Salowitz, CTR
Principal Architect, PaaS Engineering
Ace Info Solutions, a Dovel company
ITIL® V3 Foundation Certified
CompTIA Security+ CE
USCG Operations Systems Center
email: <mailto:[email protected]>
phone: (304) 433-3200
_______________________________________________
scap-security-guide mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/[email protected]
