Updated AWS Foundation Security Best Practices and PCI DSS v3.2.1 to correct control mappings #7017
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated AWS Foundation Security Best Practices and PCI DSS v3.2.1 to correct control mappings
Context
This pull request addresses the need for accurate and updated control mappings between AWS Foundation Security Best Practices and PCI DSS v3.2.1. Ensuring these mappings are correct is crucial for maintaining compliance and security posture.
Description
This PR updates the AWS Foundation Security Best Practices and PCI DSS v3.2.1 to refine the control mappings. The previous mappings were not entirely accurate, leading to potential misinterpretations of compliance status. This change ensures that the mappings reflect the latest best practices and standards.
Dependencies: None.
Checklist
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.