Skip to content

Instantly share code, notes, and snippets.

@rkreddyp
Created September 8, 2023 08:25
Show Gist options
  • Save rkreddyp/49d59a43048c9a7290e4af920763d120 to your computer and use it in GitHub Desktop.
Save rkreddyp/49d59a43048c9a7290e4af920763d120 to your computer and use it in GitHub Desktop.

Incident Report Template

<incident_report_template>

        ## Incident Overview and Summary

        ## Incident Description

        This notification is to inform you about a recent security incident that occurred within our organization. We take the security and privacy of your data seriously, and we want to provide you with a detailed overview of the incident.

        ## Incident Timeline

        - **Start Date :** [Insert Start Date, when did the incident start]
        - **Incident Step1 :** [Incident step 1 Date, incident steps and dates ]
        - **Incident Step2 :** [Incident step 2 Date, incident steps and dates ]
        - **Incident StepN :** [Incident step N Date, incident steps and dates ]            
        - **Resolution Date and Time:** [Insert Resolution Date ]

        ## Incident Details

        ### Incident Cause

        The incident was caused by [briefly describe the cause, e.g., a malware infection, a phishing attack, an unauthorized access attempt, etc.].

        ### What Happened

        During the incident, the following events occurred:
        - [Describe the sequence of events leading up to and during the incident in chronological order, including any unauthorized access, data breaches, or malicious activities.]

        ### Impact Assessment

        The incident had the following impacts:

        #### Data Breach

        - [List any data that may have been exposed or compromised.]
        - [Indicate the number of affected records, if applicable.]

        #### System Disruption

        - [Describe any disruptions or outages to our systems, services, or applications.]
        - [Include details on the duration and extent of the disruption.]

        #### Financial Impact

        - [Detail any financial losses incurred as a result of the incident, if applicable.]

        #### Reputational Impact

        - [Explain any potential impact on the organization's reputation.]

        ## Action Items Taken

        In response to the incident, we took the following actions:

        ### Immediate Mitigation

        - [Detail the immediate steps taken to mitigate the incident, such as isolating affected systems, disabling compromised accounts, etc.]

        ### Investigation

        - [Explain the steps taken to investigate the incident, including forensic analysis, identifying the root cause, and determining the extent of the breach.]

        ### Communication

        - [Outline the communication plan, including who has been informed (internal and external stakeholders) and how they were informed.]

        ### Remediation

        - [Describe the steps taken to remediate the issue, including patching vulnerabilities, improving security controls, and implementing additional security measures.]
        
        ### Incident Monday Morning Quarterbacking
        what should have been done to prevent this incident from happening?

        ### Preventative Measures

        - [Explain the steps taken to prevent similar incidents in the future, such as security awareness training, policy updates, or infrastructure enhancements.]

        # Notes and References
        ## Notes
        This report is based on the new data provided from the specified URL.
        ## Reference_URL_Table
            Below is the reference URL table:

            | URL                                            | Summary                                                        |
            | ---------------------------------------------- | -------------------------------------------------------------- |
            | [incidentdetails](https://www.incident.com/details)    | Information on the benefits of wind energy                |

 </incient_report_template>
 """
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment