CIPP icon

CIPP

Interact with CIPP API

Actions129

Overview

This node operation sets the status of a security alert within a specified tenant environment. It is useful for managing and updating the lifecycle of security alerts by marking them as 'In Progress' or 'Resolved'. Practical applications include automating alert status updates in security monitoring workflows or integrating with incident response systems to reflect the current state of alerts.

Use Case Examples

  1. Automatically mark alerts as 'In Progress' when investigation starts.
  2. Set alerts to 'Resolved' after remediation actions are completed.

Properties

Name Meaning
Tenant Filter The tenant ID or domain name to specify the environment where the alert exists.
GUID The unique identifier of the alert to update its status.
Status The status to set for the alert, either 'In Progress' or 'Resolved'.
Vendor The vendor of the alert, identifying the source or system that generated the alert.
Provider The provider of the alert, specifying the service or platform responsible for the alert.
Request Options Additional settings for the request such as batching, SSL certificate validation, proxy configuration, and timeout settings.

Output

JSON

  • status - The updated status of the alert after the operation.
  • guid - The GUID of the alert that was updated.
  • vendor - The vendor associated with the alert.
  • provider - The provider associated with the alert.

Dependencies

  • An API key credential for authenticating with the CIPP API service.

Troubleshooting

  • Ensure the tenant ID or domain name is correct and accessible.
  • Verify the GUID corresponds to an existing alert in the specified tenant.
  • Check that the vendor and provider values match those expected by the API.
  • If SSL errors occur, consider enabling the option to ignore SSL issues, but be aware of security risks.
  • If requests time out, increase the timeout setting or check network connectivity.

Links

Discussion