# Adding an Incident

Clicking on the `Add Incident` button brings up the `Add Incident` form. Fill in the required fields marked with a `*` and click `Add` to log a new incident.

<figure><img src="/files/yuaIa12vel755OtmThhU" alt=""><figcaption><p>Add Incident form</p></figcaption></figure>

**Incident Name**

The name given for an individual incident to help distinguish it from other incidents.

**Description**

The description section offers a detailed and complete summary of the incident, and should provide the reader with a clear understanding of what occurred.

**Rating**

The rating assigned to this incident in terms of its impact and implications.

**Asset Affected**

The specific asset(s) which are affected by this incident.

**Date Reported**

The specific date on which the incident was reported.

**Status**

In the context of an Information Security Management System (ISMS), the status of incident can be described as either open or closed

* **Open -** An open incident is a incident that has been identified, assessed, and acknowledged, but has not been mitigated or treated. It remains a potential threat to the organisation and requires further action to reduce its likelihood or impact.
* **Closed -** A closed incident, on the other hand, is an incident that has been adequately mitigated or treated. The organisation has taken appropriate measures to address the incident, and it no longer poses a significant threat to the information assets.

**Date Closed**

The specific date on which the incident was mitigated.

**Category**

When reporting an incident in an Information Security Management System (ISMS), incidents can be categorised into several categories, including:

* Breach: Unauthorised access to sensitive data or systems.&#x20;
* Denial of Service: Overwhelming a system or network with traffic or requests to make it unavailable.&#x20;
* Physical damage: Physical destruction or damage to IT infrastructure or devices.&#x20;
* Theft: Stealing or unauthorised access to physical or digital assets.&#x20;
* Vulnerability: Weaknesses or flaws in a system or application that can be exploited by attackers.&#x20;
* Misconfiguration: Errors or oversights in system settings or configurations.&#x20;
* Exploitation: Taking advantage of a vulnerability or weakness in a system or application.&#x20;
* Unauthorised Access Attacks: Gaining access to a system or application without proper authorisation.&#x20;
* Privilege Escalation Attacks: Exploiting a vulnerability to gain higher levels of access than authorised.&#x20;
* Insider Threat Attacks: Malicious actions taken by an authorised individual within an organisation.&#x20;
* Phishing Attacks: Deceptive techniques to trick individuals into revealing sensitive information or performing actions.&#x20;
* Man-in-the-Middle (MitM) Attacks: Intercepting communication between two parties to steal or modify information.&#x20;
* Password Attacks: Attempting to crack or steal passwords to gain access to systems or applications.

**Identified By**

The name of the individual who reported the incident.

**Last Reviewed**

The date on which this incident was last reviewed.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://manual.harpe.io/start/manual/incidents/adding-an-incident.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.