detection.wiki

Detection rules › Panther

AWS VPC Healthy Log Status

Severity
informational
Log types
AWS.VPCFlow, OCSF.NetworkActivity
Tags
AWS, DataModel, Security Control
Reference
https://www.reddit.com/r/aws/comments/zt1xhg/vpc_flow_logs_when_is_logstatus_skipdata_a_concern/?rdt=41505
Source
github.com/panther-labs/panther-analysis

Checks for the log status SKIPDATA, which indicates that data was lost either to an internal server error or due to capacity constraints.

Rule body yaml

AnalysisType: rule
Filename: aws_vpc_healthy_log_status.py
RuleID: "AWS.VPC.HealthyLogStatus"
DisplayName: "AWS VPC Healthy Log Status"
Enabled: true
LogTypes:
  - AWS.VPCFlow
  - OCSF.NetworkActivity
Tags:
  - AWS
  - DataModel
  - Security Control
Severity: Info
CreateAlert: false
DedupPeriodMinutes: 1440
Description: >
  Checks for the log status `SKIPDATA`, which indicates that data was lost either to an internal server error or due to capacity constraints.
Reference: https://www.reddit.com/r/aws/comments/zt1xhg/vpc_flow_logs_when_is_logstatus_skipdata_a_concern/?rdt=41505
Runbook: >
  Determine if the cause of the issue is capacity constraints, and consider adjusting VPC Flow Log configurations accordingly.
Tests:
  - Name: Healthy Log Status
    ExpectedResult: false
    Log: { "status": "OK", "p_log_type": "AWS.VPCFlow" }
  - Name: Unhealthy Log Status
    ExpectedResult: true
    Log: { "status": "SKIPDATA", "p_log_type": "AWS.VPCFlow" }
  - Name: Healthy Log Status - OCSF
    ExpectedResult: false
    Log: { "status_code": "OK", "p_log_type": "OCSF.NetworkActivity" }
  - Name: Unhealthy Log Status - OCSF
    ExpectedResult: true
    Log: { "status_code": "SKIPDATA", "p_log_type": "OCSF.NetworkActivity" }

Detection logic

Condition

log_status eq "SKIPDATA"

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
log_statuseq
  • SKIPDATA

Output fields

Fields the rule emits when it matches. Chronicle authors list these in the outcome block; they appear on the detection and $risk_score drives alerting. Sentinel / Defender XDR rules build them up through project / summarize / extend stages. Sentinel maps these into alert fields via entityMappings and customDetails; Defender XDR custom detections surface them as alert fields directly.

Field
eventName
eventSource
awsRegion
recipientAccountId
sourceIPAddress
userAgent
userIdentity