-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Operational Best Practices for FFIEC. Closes #418 #420
Add Operational Best Practices for FFIEC. Closes #418 #420
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vkumbha Please see review comments, thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The controls listed under benchmarks need to be sorted. I have provided comments in a few benchmarks, please verify this across all the other benchmarks.
ffiec/d_1/d_1_rm.sp
Outdated
} | ||
|
||
benchmark "ffiec_d_1_rm_rm_b_1" { | ||
title = "D1.RM.Rm.B.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should use the titles as per the official documentation. We could change them once - awsdocs/aws-config-developer-guide#21 is resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will keep an eye on the AWS issue and see if there is a logical explanation for the deviation in the Control ID. However, for the time being, going with the Control Id what I think is right based on the FFIEC document available at https://www.ffiec.gov/cyberassessmenttool.htm.
Please make changes wherever required 👍 |
This reverts commit b99333a.
Checklist