nano SIEM
User Guide

Alerts & Incident Response

Supported in:Self-hosted

Triage nano alerts from detection rules: alert states, acknowledging and closing with a disposition, bulk actions, filters, metrics and troubleshooting.

Review alerts to triage detection matches, record investigation actions, and close each signal with a disposition. nano creates alerts when a rule in Alerting mode matches events; use the workflow below to track ownership and response.

Permissions

To view alerts, you need alerts:view. Acknowledging alerts requires alerts:acknowledge; closing them requires alerts:close.

Overview

The alert system turns detection rule matches into incidents with:

  • Automated Detection - Rules monitor logs and generate alerts
  • Deduplication - Suppresses duplicate events to reduce alert fatigue
  • Workflow Management - New → Acknowledged → Closed lifecycle
  • Risk Scoring - Prioritizes alerts by threat severity and context
  • Audit Trail - Timeline of investigation and response actions

Alert lifecycle

1. alert generation

Alerts are created when a detection rule in Alerting mode matches events. Rules in Live mode record findings but raise no alerts (see Detection Rules):

Detection Rule → Event Match → Alert Created → Analyst Notification

Key Properties:

  • Severity: Critical, High, Medium, Low, Info (inherited from detection rule)
  • Status: new → acknowledged → closed
  • Matched Events: The specific log events that triggered the alert
  • Detection Latency: Time between event occurrence and alert generation
  • Alert Mode: Rules with alert_mode: per_event produce one alert per source event, with matched_events always containing exactly one element. This is used for vendor pass-through detections (e.g., CrowdStrike, SentinelOne) where each vendor detection maps 1:1 to a nano alert. The default grouped mode bundles all matches from a single execution into one alert.

2. alert states

New (new)

  • Freshly generated alerts requiring initial review
  • Highest priority for SOC analysts
  • Automatically assigned based on severity and routing rules

Acknowledged (acknowledged)

  • Analyst has reviewed and is actively investigating
  • Prevents duplicate work by other team members
  • Requires disposition before closure

Closed (closed)

  • Investigation complete with final disposition
  • Includes resolution notes and lessons learned
  • Archived for reporting and trend analysis

Alert management

Viewing alerts

Navigate to Alerts in the main menu to see:

Alert Dashboard

  • Real-time alert counts by status and severity
  • 7-day activity trends and patterns
  • Severity distribution charts
  • Critical alert indicators

Alert List

  • Sortable table with key alert information
  • Filtering by status, severity, and rule name
  • Bulk operations for efficient triage
  • Quick actions for common workflows

Alert details

Click any alert to view full details:

Overview Section

  • Alert metadata (severity, status, timestamps)
  • Detection rule information and query
  • Risk score and threat indicators
  • Investigation timeline

Matched Events Tab

  • Complete event data that triggered the alert
  • Detection latency indicators for each event
  • Expandable event details with all fields
  • Pagination for large event sets

Detection Rule Tab

  • Full rule definition and query syntax
  • MITRE ATT&CK technique mappings
  • Rule metadata (author, schedule, references)
  • Narrative description of the threat

Timeline Tab

  • Chronological investigation history
  • Status changes and analyst actions
  • Audit trail for compliance reporting

Detection latency

nano tracks how quickly alerts are generated after events occur:

Latency Levels:

  • 🟢 Fast (≤5 minutes) - Optimal real-time detection
  • 🟡 Moderate (≤15 minutes) - Acceptable for most use cases
  • 🔴 Slow (>15 minutes) - May indicate performance issues

Factors Affecting Latency:

  • Log ingestion delays
  • Detection rule complexity
  • System resource availability
  • Data processing pipeline health

Alert operations

Acknowledging alerts

Purpose: Claim ownership and begin investigation

Process:

  1. Review alert details and matched events
  2. Click Acknowledge button
  3. Alert status changes to "Acknowledged"
  4. Your username is recorded as the analyst

Best Practices:

  • Acknowledge alerts promptly to prevent duplicate work
  • Use bulk acknowledge for related alerts
  • Add investigation notes as you progress

Closing alerts

Purpose: Complete investigation with final disposition

Required Information:

  • Disposition: Classification of the alert outcome
  • Notes: Investigation summary and actions taken

Disposition Types:

True positive (true_positive)

  • Confirmed security incident requiring response
  • Threat was real and actionable
  • May trigger incident response procedures

False positive (false_positive)

  • Alert triggered incorrectly on benign activity
  • Detection rule needs tuning or refinement
  • Common during initial rule deployment

Benign (benign)

  • Alert correctly identified the activity
  • Activity is authorized or expected
  • No security response required

Bulk operations

Efficiently manage multiple alerts simultaneously:

Bulk Acknowledge

  • Select multiple new alerts
  • Acknowledge all at once
  • Useful for related alerts from the same incident

Bulk Close

  • Close multiple acknowledged alerts
  • Apply same disposition to similar alerts
  • Streamline routine alert processing

Selection Methods:

  • Individual checkboxes for specific alerts
  • "Select All" for current page
  • Filter-based selection for targeted operations

Status filters

All Status - View alerts in any state New - New alerts requiring attention Acknowledged - Alerts under investigation Closed - Completed investigations

Severity filters

All Severity - View alerts of any severity Critical - Immediate response required High - Urgent investigation needed Medium - Standard priority review Low - Routine monitoring alerts

Search capabilities

Text Search

  • Search alert rule names
  • Filter by severity or status keywords
  • Case-insensitive substring matching on the rule name

Advanced Filtering

  • Combine multiple filter criteria
  • Time range selection
  • Rule-specific alert views

Alert metrics & analytics

Key performance indicators

Mean Time to Acknowledge (MTTA)

  • Average time from alert creation to acknowledgment
  • Measures SOC responsiveness
  • Target: <15 minutes for critical alerts

Mean Time to Resolution (MTTR)

  • Average time from alert creation to closure
  • Measures investigation efficiency
  • Varies by severity and complexity

Alert Volume Trends

  • Daily/weekly alert generation patterns
  • Seasonal variations and anomalies
  • Capacity planning indicators

Alert quality metrics

False Positive Rate

  • Percentage of alerts marked as false positives
  • Indicates detection rule accuracy
  • Target: <10% for mature rules

True Positive Rate

  • Percentage of alerts confirmed as real threats
  • Measures detection effectiveness
  • Higher rates indicate better rule quality

Integration with detection rules

Rule-based alert generation

Alerts inherit properties from their detection rules:

  • Severity Level - Determines alert priority
  • MITRE ATT&CK Mapping - Provides threat context
  • Narrative Description - Explains the threat scenario
  • Reference Links - Additional threat intelligence

Alert feedback loop

Alert dispositions improve detection rules:

  • False Positives → Rule tuning opportunities
  • True Positives → Validation of rule effectiveness
  • Benign → Baseline refinement needs

Detection rule metrics

View rule performance from alert outcomes:

  • Alert generation frequency
  • False positive rates per rule
  • Investigation time by rule type
  • Analyst feedback and recommendations

Notebook integration

Automatic investigation capture

When notebooks are active, alert investigations are automatically documented:

  • Alert View Capture - Records when alerts are opened
  • Action Logging - Tracks acknowledgments and closures
  • Query Suggestions - AI-generated investigation queries
  • Evidence Collection - Preserves investigation artifacts

Linked investigations

Alerts can reference notebook investigations:

  • Bidirectional Links - Connect alerts to detailed analysis
  • Investigation History - Track related research and findings
  • Collaboration - Share investigation notes with team members

Best practices

Alert triage

  1. Prioritize by Severity

    • Critical alerts require immediate attention
    • Use severity-based escalation procedures
    • Balance urgency with investigation quality
  2. Context Gathering

    • Review matched events thoroughly
    • Check for related alerts or patterns
    • Consult threat intelligence sources
  3. Efficient Workflows

    • Use bulk operations for similar alerts
    • Develop standard investigation procedures
    • Document common false positive patterns

Investigation process

  1. Initial Assessment (5-10 minutes)

    • Review alert details and matched events
    • Determine if immediate escalation is needed
    • Acknowledge alert to claim ownership
  2. Detailed Analysis (15-60 minutes)

    • Examine all matched events and context
    • Search for related activity or indicators
    • Consult external threat intelligence
  3. Response Actions (varies)

    • Implement containment measures if needed
    • Coordinate with incident response team
    • Document findings and recommendations
  4. Alert Closure (5 minutes)

    • Select appropriate disposition
    • Add comprehensive investigation notes
    • Update detection rules if needed

Alert hygiene

Regular Review

  • Monitor alert volume and trends
  • Identify rules generating excessive false positives
  • Adjust detection thresholds based on feedback

Documentation Standards

  • Use consistent disposition criteria
  • Include actionable investigation notes
  • Reference external tickets or systems

Performance Monitoring

  • Track MTTA and MTTR metrics
  • Monitor detection latency indicators
  • Review analyst workload distribution

Troubleshoot

Need help with these checks? Contact support with the affected deployment, request ID and time with timezone.

Too many false positives

  • Review detection rule logic and thresholds
  • Analyze environmental factors and baselines
  • Consider rule tuning or suppression lists

The alert queue is too noisy

  • Implement intelligent alert grouping
  • Adjust severity levels for routine events
  • Use prevalence-based filtering

Alerts arrive late

  • Check log ingestion pipeline health
  • Monitor system resource utilization
  • Optimize detection rule queries

Expected alerts are missing

  • Verify detection rule schedules
  • Check log source connectivity
  • Review rule query syntax and filters

Performance optimization

Query Efficiency

  • Filter on specific OCSF fields (class_uid, metadata.log_source, entity paths) before aggregating
  • Limit time ranges for complex queries
  • Implement proper field filtering

System Resources

  • Monitor CPU and memory usage
  • Scale detection infrastructure as needed
  • Optimize database performance

Alert Processing

  • Batch similar alerts when possible
  • Implement intelligent deduplication
  • Use asynchronous processing for large volumes

Compliance & reporting

Audit requirements

nano maintains complete audit trails for:

  • Alert generation and modification
  • Analyst actions and timestamps
  • Investigation notes and dispositions
  • System configuration changes

Reporting capabilities

Executive Dashboards

  • High-level security metrics
  • Trend analysis and comparisons
  • Risk posture indicators

Operational Reports

  • Alert volume and response times
  • Analyst performance metrics
  • Detection rule effectiveness

Compliance Reports

  • Incident response documentation
  • Audit trail exports
  • Regulatory requirement mapping

What's next

On this page