Skip to navigation

Incidents

Incidents

Incidents triages the alerts your SIEM raises. Connect Datadog, and every Cloud SIEM signal or monitor alert you route to Pensar is investigated by an agent that decides whether it is a real attack and tells you what to do about it.

Incidents is in early access. Contact Pensar to enable it for your workspace. Workspace admins and owners connect Datadog; every member can view and act on incidents.

Investigate AWS activity

During Incidents setup or under Incidents → Settings, connect the AWS accounts and regions you want Pensar to investigate. Triage can check a security group’s current rules and look up regional CloudTrail management events within two hours of the alert, including which principal made a call and whether AWS reported an error. The role is read-only. Your team applies the recommended changes.

If you already connected AWS for recon, security group checks work with your existing role. For CloudTrail lookups, download the current template from Cloud providers and use it to update your existing CloudFormation stack, keeping its parameter values. If you manage the role yourself, add cloudtrail:LookupEvents to its permissions.

Investigate Google Cloud activity

Connect the project during Incidents setup or under Incidents → Settings. Triage can look up Admin Activity audit events by principal, method or resource and cite them in its verdict. This covers administrative changes such as IAM grants. Data Access logs require additional permissions and are outside this integration.

How it works

1

Receive

Datadog posts the alert to your workspace’s webhook. An alert that fires again is counted on the same incident rather than opening a new one, and recovery notifications are ignored.

2

Investigate

The triage agent reads the alert and checks it against what Pensar knows about your workspace: whether a Pensar pentest was running against the same asset at the time, and which open findings exist on the hosts the alert names. If you gave Pensar log access, it also searches your Datadog logs around the alert, for example to see whether a burst of failed logins ended in a successful one.

3

Decide

The incident gets a verdict, a confidence level and an assessed severity, along with the evidence behind it and the indicators involved.

4

Recommend

You get prioritized remediation with copyable AWS CLI or Datadog Pup commands, including prerequisites, verification and rollback. For benign and false positives, these steps focus on tuning the detection. Review the commands and fill in any required inputs before running them with your own credentials. Use Triage again to regenerate older prose-only recommendations.

VerdictMeaning
True positiveReal malicious or unauthorized activity
Benign positiveThe rule fired correctly on activity that is expected, such as a Pensar pentest or an admin task
False positiveThe rule fired on activity it is not meant to catch
InconclusiveThe available evidence cannot settle it; the analysis says what data would

The verdict is advice. Resolve or Dismiss an incident once you have acted on it; Triage again re-runs the agent, for example after you add log access.

Use Alerts to review verdicts and remediation. Repeated findings for the same rule and entity are grouped when their verdict, severity and status agree; the event count opens the underlying records. Findings without a reliable entity stay separate. Use Events to inspect the original Datadog webhook payload, and Settings to manage the connection. Events include all verdicts and dispositions. Repeated deliveries of the same signal share a record.

On your first visit, an introduction explains intake, investigation and remediation. Setup then walks you through Datadog and optional read-only cloud access. Cloud access significantly improves investigation quality by supplying direct evidence; choose Set up cloud access later to start with Datadog alone. After setup, you land in Alerts.

Connecting Datadog

1

Connect

Open Incidents in your workspace sidebar and follow the introduction into setup. For an existing connection, open Incidents → Settings. Choose your Datadog site, decide whether every new alert should be triaged automatically, and click Connect Datadog.

2

Copy the token

Pensar shows a webhook token once. Copy the URL, Custom headers and Payload snippets from Setup instructions before leaving the page. If you lose the token, use Rotate token and update the header in Datadog.

3

Create the webhook in Datadog

In Datadog, go to Integrations → Webhooks and add a webhook named pensar. Paste the URL, enable custom headers and paste the header snippet, and replace the payload with the Pensar payload.

4

Route alerts

Add @webhook-pensar to the notification message of each Cloud SIEM detection rule or monitor you want triaged.

If Datadog reports a failed delivery, a 400 means the payload is not the Pensar template and a 401 means the Authorization header does not match your current token.

Log access (optional)

Without keys, the agent triages from the alert alone and its confidence is lower. To let it search your logs, enter a Datadog API key and an application key with the logs_read_data scope, either when connecting or later with Add keys. Pensar checks the keys with Datadog before saving them. Log searches run on Pensar’s servers; the keys are never given to the agent.

Use Intake to pause receiving alerts and Auto-triage to triage only when someone asks. Disconnect deletes the token and keys; incidents already received stay on the page.

Notifications

Configure Slack and email rules in Settings → Notifications. Select Incident triage completed and True positive to exclude benign and false positive results. Leave Incident received unselected if you only want alerts after triage. Received and failed events are available separately. Each Slack rule can use its own channel; see Slack alert rules.