Actions85
- Alert Actions
- Asset Actions
- Case Actions
- Comment Actions
- Datastore File Actions
- Datastore Folder Actions
- Evidence Actions
- IOC Actions
- Manage Metadata Actions
- Module Actions
- Note Actions
- Note Group Actions
- Task Actions
- Timeline Actions
Alert → Add
AI-generatedOverview
This node creates a new alert in the DFIR IRIS system. It is useful for security analysts and incident responders who want to automate the process of adding alerts to their incident response platform. For example, it can be used to add alerts with detailed information such as severity, status, title, associated assets, indicators of compromise (IOCs), classification, context, and other metadata.
Use Case Examples
- Creating a new alert with a specific severity and status for a detected security incident.
- Adding assets and IOCs related to an alert to enrich the investigation context.
- Setting alert classification and resolution status to track the alert lifecycle.
Properties
| Name | Meaning |
|---|---|
| Case ID | The ID of the case to which the alert belongs. Required for linking the alert to a specific case. |
| Alert Customer Name or ID | The customer associated with the alert, selectable from a list or specified by ID. Required to identify the alert's customer. |
| Alert Severity | The severity level of the alert, such as Medium, High, or Critical. Required to indicate the alert's importance. |
| Alert Status | The current status of the alert, such as New, Assigned, or Closed. Required to track the alert's progress. |
| Alert Title | The title or summary of the alert. Required to provide a brief description of the alert. |
| Additional Fields | Optional additional data for the alert, including assets, IOCs, classification, context, description, notes, resolution status, source information, and tags. |
| Options | Optional settings for the operation, such as returning the raw response or specifying which fields to include or exclude in the output. |
Output
JSON
alert_id- Unique identifier of the created alertalert_title- Title of the alertalert_severity_id- Severity level of the alertalert_status_id- Current status of the alertalert_customer_id- Customer associated with the alertalert_classification_id- Classification of the alertalert_context- Context information related to the alertalert_creation_time- Timestamp when the alert was createdalert_description- Detailed description of the alertalert_note- Additional notes about the alertalert_resolution_status_id- Resolution status of the alertalert_source- Source from which the alert originatedalert_source_content- Raw event data from the alert source in JSON formatalert_source_event_time- Event time of the alert source in UTCalert_source_link- Link to the alert sourcealert_source_ref- Reference ID from the alert sourcealert_tags- Comma-separated list of tags associated with the alertassets- List of assets related to the alertiocs- List of indicators of compromise related to the alertcases- Cases associated with the alertclassification- Classification details of the alertcomments- Comments related to the alertcustomer- Customer details associated with the alertmodification_history- History of modifications made to the alertowner- Owner information of the alertresolution_status- Resolution status details of the alertseverity- Severity details of the alertstatus- Status details of the alert
Troubleshooting
- Ensure all required fields such as Case ID, Alert Customer ID, Alert Severity, Alert Status, and Alert Title are provided to avoid validation errors.
- If using dynamic options (e.g., customer list, asset types, IOC types), ensure the corresponding load options methods are correctly implemented and accessible.
- Check the format of JSON fields like asset enrichment, IOC enrichment, and alert source content to avoid JSON parsing errors.
- If the alert creation fails, verify API credentials and network connectivity to the DFIR IRIS system.