Alert Management
Alerts are the primary interface for security operations in Tamandua Sentinel. This guide covers alert viewing, filtering, investigation workflows, and alert management best practices.
Accessing Alerts
Navigate to Alerts in the left navigation panel to access the alert management interface.
[Screenshot: Alerts page with list view, filters, and action toolbar]
Alert List and Filtering
Alert List View
The alert list displays security alerts with the following default columns:
| Column | Description |
|---|---|
| Severity | Alert severity level (Critical, High, Medium, Low) |
| Title | Alert name and brief description |
| Status | Current workflow status |
| Agent | Affected endpoint |
| Category | Alert classification |
| MITRE | Associated ATT&CK technique |
| Created | Alert creation timestamp |
| Assignee | Assigned analyst |
Customizing Columns
Add or remove columns:
- Click the Columns button in the toolbar
- Select desired columns
- Drag to reorder
- Click Apply
[Screenshot: Column customization panel with available fields]
Additional available columns:
- Detection Source (YARA, Sigma, ML, Behavioral)
- Process Name
- Process Path
- User
- IP Address
- File Hash
- Rule Name
- Resolution
- Time to Acknowledge
- Time to Resolve
Filtering Alerts
Quick Filters
Use the filter bar for rapid filtering:
| Filter | Options |
|---|---|
| Severity | Critical, High, Medium, Low |
| Status | Open, Acknowledged, Investigating, Resolved, Suppressed |
| Time Range | Last hour, 24h, 7d, 30d, Custom |
| Agent | Specific endpoint or group |
| Category | Malware, Suspicious, Policy, etc. |
| Assignee | Unassigned, Me, specific user |
[Screenshot: Quick filter bar with severity and status filters applied]
Advanced Filters
Click Advanced for complex queries:
severity = "critical" AND
status = "open" AND
created > "2024-01-14" AND
(category = "malware" OR category = "ransomware") AND
agent.group = "Production Servers"
Saved Filters
Save frequently used filters:
- Configure desired filters
- Click Save Filter
- Enter a name
- Optionally set as default view
- Access saved filters from the dropdown
Filter Presets
Built-in presets for common views:
| Preset | Description |
|---|---|
| Critical Open | Critical severity, open status |
| My Alerts | Assigned to current user |
| Unassigned | No assignee, open status |
| Today's Alerts | Created in last 24 hours |
| Needs Attention | Open > 4 hours, unassigned |
Sorting
Click column headers to sort:
- First click: Ascending
- Second click: Descending
- Third click: Clear sort
Default sort: Severity (descending), then Created (newest first)
Search
Full-text search across:
- Alert title
- Process name and path
- File name and path
- Command line
- Hash values
- IP addresses
- Hostnames
Alert Details View
Click any alert to open the detail panel.
[Screenshot: Alert detail panel showing all sections expanded]
Alert Header
Key information at a glance:
+----------------------------------------------------------+
| [CRITICAL] Ransomware Activity Detected |
+----------------------------------------------------------+
| Agent: WORKSTATION-042 | User: john.doe |
| Status: Investigating | Assignee: analyst@corp.com |
| Created: 2024-01-15 14:32:45 UTC |
+----------------------------------------------------------+
Overview Section
| Field | Description |
|---|---|
| Alert ID | Unique identifier |
| Detection Source | YARA, Sigma, ML, Behavioral |
| Rule Name | Triggering rule identifier |
| Confidence | Detection confidence score (0-100) |
| MITRE Technique | ATT&CK technique ID and name |
| Category | Alert classification |
Process Details
When the alert relates to process activity:
| Field | Description |
|---|---|
| Process Name | Executable name |
| Process Path | Full path to executable |
| Command Line | Full command line arguments |
| PID | Process identifier |
| Parent Process | Parent process details |
| User | Process owner |
| Integrity Level | Windows integrity level |
| Signed | Code signature status |
| Signer | Certificate signer name |
[Screenshot: Process details section with parent process tree]
File Details
When the alert relates to file activity:
| Field | Description |
|---|---|
| File Path | Full path to file |
| File Name | File name |
| File Size | Size in bytes |
| SHA256 | File hash |
| MD5 | File hash (legacy) |
| Created | File creation time |
| Modified | File modification time |
| Entropy | File entropy score |
Network Details
When the alert relates to network activity:
| Field | Description |
|---|---|
| Local IP | Source IP address |
| Local Port | Source port |
| Remote IP | Destination IP address |
| Remote Port | Destination port |
| Protocol | TCP, UDP, etc. |
| Direction | Inbound, Outbound |
| Bytes | Data transferred |
Related Events
Timeline of events surrounding the alert:
[14:32:45] Process: powershell.exe started (PID: 1234)
[14:32:46] File: C:\Users\...\malware.ps1 read
[14:32:47] Network: Connection to 192.168.1.100:443 <-- Alert
[14:32:48] Registry: HKCU\...\Run modified
[14:32:50] Process: cmd.exe started (child of powershell)
Click any event to view full details.
Response Actions
Available actions directly from the alert:
| Action | Description |
|---|---|
| Kill Process | Terminate the associated process |
| Quarantine File | Move file to quarantine |
| Isolate Host | Enable network isolation |
| Create Investigation | Start formal investigation |
| Run Live Response | Open live response session |
[Screenshot: Response actions dropdown with available options]
Severity Levels
Severity Definitions
| Level | Indicator | Description | SLA |
|---|---|---|---|
| Critical | Red | Confirmed threat requiring immediate response | < 15 min |
| High | Orange | Likely threat requiring prompt investigation | < 1 hour |
| Medium | Yellow | Suspicious activity requiring review | < 4 hours |
| Low | Green | Informational or low-confidence detection | < 24 hours |
Severity Determination
Severity is calculated based on:
| Factor | Weight |
|---|---|
| Rule Severity | 40% - Base severity defined in detection rule |
| Confidence | 30% - ML model or rule confidence score |
| Asset Criticality | 20% - Target endpoint importance |
| Threat Context | 10% - Threat intelligence correlation |
Severity Adjustment
Analysts can adjust severity when context warrants:
- Click Change Severity in alert actions
- Select new severity
- Enter justification (required)
- Click Save
Adjustments are logged in the audit trail.
Alert Workflow
Status Definitions
| Status | Description |
|---|---|
| Open | New alert, not yet reviewed |
| Acknowledged | Alert seen, pending investigation |
| Investigating | Active investigation in progress |
| Resolved | Investigation complete, threat addressed |
| Suppressed | Alert matched suppression rule |
Standard Workflow
Open
|
v
Acknowledged (Analyst reviews alert)
|
v
Investigating (Active investigation)
|
+-------+-------+
| |
v v
Resolved Escalated
(Closed) (Create Investigation)
Acknowledge Alert
Mark alert as reviewed:
- Select alert(s)
- Click Acknowledge
- Optionally add note
- Click Confirm
Or use keyboard shortcut: A
Assign Alert
Assign to analyst:
- Click Assign in alert actions
- Select analyst from dropdown
- Optionally add assignment note
- Click Assign
Self-assign: Click Assign to Me
[Screenshot: Assignment dropdown with team members]
Start Investigation
Begin formal investigation:
- Click Investigate
- Investigation status is set
- Alert is auto-assigned if unassigned
Resolve Alert
Close the alert:
- Click Resolve
- Select resolution:
- True Positive: Confirmed threat, action taken
- True Positive - Benign: Real activity, authorized
- False Positive: Detection error
- Not Applicable: Alert not relevant
- Enter resolution notes
- Click Resolve
[Screenshot: Resolution dialog with options and notes field]
Resolution Notes
Document investigation findings:
- What was detected
- Actions taken
- Root cause (if determined)
- Recommendations
Resolution notes support Markdown formatting.
Bulk Alert Operations
Selecting Alerts
- Individual: Click checkbox next to alert
- Page: Click header checkbox
- All Matching: Click "Select all X alerts" link
- Shift-Click: Select range
Available Bulk Operations
| Operation | Description |
|---|---|
| Acknowledge | Mark multiple alerts as acknowledged |
| Assign | Assign multiple alerts to analyst |
| Change Status | Update status in bulk |
| Change Severity | Adjust severity in bulk |
| Resolve | Close multiple alerts |
| Add to Investigation | Link to existing investigation |
| Create Suppression | Create rule from selected alerts |
| Export | Export selected alerts |
Executing Bulk Operations
- Select alerts using checkboxes
- Click action in bulk toolbar
- Configure operation parameters
- Review confirmation:
- Number of affected alerts
- Operation details
- Click Confirm
[Screenshot: Bulk operation confirmation with alert count]
Bulk Acknowledge
- Select alerts
- Click Acknowledge
- Optionally add note (applies to all)
- Confirm
Bulk Resolve
- Select alerts
- Click Resolve
- Select resolution type
- Enter resolution notes
- Confirm
Alert Suppression Rules
Suppression rules automatically suppress alerts matching specific criteria, reducing noise from known-good activity.
Viewing Suppression Rules
Navigate to Alerts > Suppression Rules tab.
[Screenshot: Suppression rules list with status indicators]
| Column | Description |
|---|---|
| Name | Rule name |
| Criteria | Match conditions |
| Created By | Rule author |
| Suppressed | Count of suppressed alerts |
| Expires | Expiration date (if set) |
| Status | Enabled/Disabled |
Creating Suppression Rules
From Alert
- Open alert details
- Click Suppress Similar
- Review pre-filled criteria
- Modify as needed
- Enter rule name and description
- Set expiration (optional)
- Click Create
[Screenshot: Create suppression rule dialog from alert]
From Scratch
- Click Create Rule
- Define match criteria:
- Rule name/ID
- Process path
- File path
- Command line pattern
- Agent group
- User
- Enter rule name and description
- Set expiration
- Click Create
Suppression Criteria
Available match fields:
| Field | Operators |
|---|---|
| Rule Name | equals, contains, regex |
| Process Path | equals, contains, regex, startswith, endswith |
| Process Name | equals, contains, regex |
| Command Line | contains, regex |
| File Path | equals, contains, regex |
| File Hash | equals |
| User | equals |
| Agent | equals (specific agent) |
| Agent Group | equals (agent group) |
Suppression Best Practices
- Be Specific: Use narrow criteria to avoid over-suppression
- Set Expiration: Review suppression rules periodically
- Document Reason: Include why activity is benign
- Monitor Usage: Track suppression counts
- Audit Regularly: Review suppressed alerts for changes
Editing Suppression Rules
- Click rule name
- Modify criteria or settings
- Click Save
Disabling vs. Deleting
- Disable: Temporarily stop suppression, preserve rule
- Delete: Permanently remove rule
Disabled rules can be re-enabled; deleted rules must be recreated.
Suppression Reports
View suppression effectiveness:
- Navigate to Reports > Suppression
- Select time range
- View:
- Alerts suppressed per rule
- Suppression trends
- Top suppression rules
Alert Notifications
Notification Channels
Configure how alerts are delivered:
| Channel | Use Case |
|---|---|
| Console | In-app notifications |
| Individual or digest alerts | |
| Slack | Team channel notifications |
| PagerDuty | On-call escalation |
| Webhook | Custom integrations |
| SIEM | Forward to security platform |
Notification Rules
Create rules for alert routing:
- Navigate to Settings > Notifications
- Click Create Rule
- Define conditions:
- Severity >= High
- Agent group = Production
- Category = Ransomware
- Select notification channels
- Configure recipients
- Click Save
[Screenshot: Notification rule builder with conditions and channels]
Escalation Policies
Configure automatic escalation:
| Level | Condition | Action |
|---|---|---|
| 1 | Alert created | Notify assigned analyst |
| 2 | Unacknowledged > 15 min | Notify team lead |
| 3 | Unacknowledged > 30 min | Page on-call |
| 4 | Unresolved > 4 hours | Notify SOC manager |
Alert Analytics
Alert Trends
View alert patterns over time:
- Volume by severity
- Volume by category
- Detection source distribution
- Agent distribution
- Resolution trends
[Screenshot: Alert analytics dashboard with trend charts]
SLA Metrics
Track response time performance:
| Metric | Target | Actual |
|---|---|---|
| Mean Time to Acknowledge (MTTA) | < 5 min | 3.2 min |
| Mean Time to Investigate | < 30 min | 22 min |
| Mean Time to Resolve (MTTR) | < 4 hours | 2.5 hours |
| Critical Alert MTTA | < 2 min | 1.8 min |
False Positive Rate
Monitor detection accuracy:
+------------------------------------------+
| FALSE POSITIVE RATE (30 days) |
+------------------------------------------+
| Overall: 12% |
| YARA Rules: 8% |
| Sigma Rules: 10% |
| ML Detections: 15% |
| Behavioral: 18% |
+------------------------------------------+
High false positive rates indicate rule tuning needed.
Export and Integration
Export Alerts
- Apply filters
- Click Export
- Select format:
- CSV: Spreadsheet analysis
- JSON: API/programmatic use
- PDF: Formal reporting
- Select fields
- Click Export
SIEM Integration
Forward alerts to SIEM:
- Navigate to Settings > Integrations
- Configure SIEM connector:
- Splunk
- Elastic
- Microsoft Sentinel
- QRadar
- Chronicle
- Map alert fields
- Test connection
- Enable forwarding
API Access
Query alerts programmatically:
# List alerts
curl -X GET "https://api.tamandua.io/v1/alerts?severity=critical&status=open" \
-H "Authorization: Bearer YOUR_API_KEY"
# Get alert details
curl -X GET "https://api.tamandua.io/v1/alerts/{alert_id}" \
-H "Authorization: Bearer YOUR_API_KEY"
# Update alert status
curl -X PATCH "https://api.tamandua.io/v1/alerts/{alert_id}" \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{"status": "investigating"}'
Next Steps
- Investigations - Conduct threat investigations
- Live Response - Execute remote commands
- Agent Management - Manage endpoints
- Dashboard Guide - Monitor alerts at scale