Closed mikecarenzo closed 4 months ago
Should mitigates
be changed to protects
in all mappings across all attack versions?
Should
mitigates
be changed toprotects
in all mappings across all attack versions?
Yes. This change should be reflected in all previous versions.
@emeth1 will look at the build failure on this branch; she's also going to change "mitigate" to "protect" for previous versions of the NIST mappings.
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: No coverage uploaded for pull request base (
main@dbb9553
). Click here to learn what that means.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-172_update_rev4_and_rev5_nist_mappings/
This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-172_update_rev4_and_rev5_nist_mappings/
This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-172_update_rev4_and_rev5_nist_mappings/
Fixes: #172
What Changed
Updates NIST 800-53 rev4 and rev5 mappings. The latest versions of these files:
mitigates
mapping type toprotects
.