Report operational vulnerability form
On the Report operational vulnerability form, fill in the fields.
| Field | Description |
|---|---|
| Title | Name of the vulnerability. For example, Customer data compromised due to malware. |
| Description | Brief description of the vulnerability. |
| Vulnerability type | Nature or type of the vulnerability. This field is automatically set to Vulnerability Type. |
| Sub-type | Sub-type of the vulnerability. For example, Documentation Loss. |
| Date of occurrence | Date the vulnerability occurred. For example, the vulnerability may have occurred on March 21, 2024. |
| Date of discovery | Date the vulnerability was discovered by you. For example, the vulnerability may have occurred on March 21, 2024, but it was discovered only on May 21, 2024. |
| Primary origin | |
| Impacted business unit | Business unit that is impacted by the vulnerability. |
| Impacted department | Department impacted by the vulnerability. |
| Location of occurrence | Location of the vulnerability occurrence. For example, the location is Japan. |
| Sub-location | Sub-location of the vulnerability occurrence. For example, the sub-location for the vulnerability is Tokyo. |
| Related area | |
| Source | Source of the vulnerability. For example, Manual, Importance and impact analysis, Service. |
| Source table | Table indicating the source of the vulnerability. |
| Source record | Name of the source record for the vulnerability. For example, Blackberry service This field is not displayed only when the source is Manual. |
| Add attachments | Attachments for the vulnerability. You can choose a file or drag it so that it is attached with the form. |