💼 RS.AN-2: The impact of the incident is understood
- ID:
/frameworks/nist-csf-v1.1/rs-an/02
Description​
Empty...
Similar​
- Sections
/frameworks/iso-iec-27001-2013/16/01/04/frameworks/iso-iec-27001-2013/16/01/06/frameworks/nist-sp-800-53-r4/cp/02/frameworks/nist-sp-800-53-r4/ir/04
- Internal
- ID:
dec-c-befeaaa6
- ID:
Similar Sections (Take Policies From)​
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|---|---|---|---|---|
| 💼 ISO/IEC 27001:2013 → 💼 A.16.1.4 Assessment of and decision on information security events | no data | ||||
| 💼 ISO/IEC 27001:2013 → 💼 A.16.1.6 Learning from information security incidents | no data | ||||
| 💼 NIST SP 800-53 Revision 4 → 💼 CP-2 CONTINGENCY PLAN | 8 | no data | |||
| 💼 NIST SP 800-53 Revision 4 → 💼 IR-4 INCIDENT HANDLING | 10 | no data |
Similar Sections (Give Policies To)​
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|---|---|---|---|---|
| 💼 NIST CSF v2.0 → 💼 RS.MA-02: Incident reports are triaged and validated | 25 | no data | |||
| 💼 NIST CSF v2.0 → 💼 RS.MA-03: Incidents are categorized and prioritized | 1 | no data | |||
| 💼 NIST CSF v2.0 → 💼 RS.MA-04: Incidents are escalated or elevated as needed | 1 | no data |
Sub Sections​
| Section | Sub Sections | Internal Rules | Policies | Flags | Compliance |
|---|