Skip to content
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.

Commit

Permalink
Fix link to 800-53 mapping r4
Browse files Browse the repository at this point in the history
added missing subdirectory causing 404 error when visiting the link to the "Mapping NIST 800-53 revision 4 to ATT&CK" document.
  • Loading branch information
stevenhardey authored Sep 11, 2021
1 parent bd291b9 commit 09a3131
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/mapping_methodology.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ To continue with the example, further review and analysis confirms the identifie

## Applying the Methodology

This methodology is designed to be tailored as it is applied to security control frameworks. We anticipate that each framework will require its own unique mapping and scoping decisions. These framework specific decisions should be documented in the ReadMe for the framework. As an example, see the [Mapping NIST 800-53 revision 4 to ATT&CK](/frameworks/nist800-53-r4#mapping-nist-800-53-revision-4-to-attck) section of the NIST 800-53 Rev. 4 mapping documentation.
This methodology is designed to be tailored as it is applied to security control frameworks. We anticipate that each framework will require its own unique mapping and scoping decisions. These framework specific decisions should be documented in the ReadMe for the framework. As an example, see the [Mapping NIST 800-53 revision 4 to ATT&CK](/frameworks/ATT%26CK-v8.2/nist800-53-r4#mapping-nist-800-53-revision-4-to-attck) section of the NIST 800-53 Rev. 4 mapping documentation.

## References

Expand Down

0 comments on commit 09a3131

Please sign in to comment.