System Errors

Overview

Panther's System Errors alert you when a part of the Panther platform is not functioning as expected. This includes the following:

• Log Source Health Notifications

  • Log sources turning unhealthy as a result of a failed health check

  • Logs dropping off entirely from a log source

• Alert limit notifications

• Alert Delivery Failure

  • Alerts failing to deliver to the Alert Destination

• Log Classification Errors

  • Logs failing to classify

• S3 GetObject Errors

  • Panther failing to fetch S3 objects

• Cloud Security Scanning Failure

  • Panther failing to scan a cloud resource because of an "access denied" error

• Query errors in Scheduled Searches not connected to a Scheduled Rule

  • Query errors in Scheduled Searches connected to a Scheduled Rule are surfaced as rule errors

• Timed out Scheduled Searches

These types of alerts are classified as System Errors in Panther. System Errors will always have a CRITICAL severity level—and be sent to alert destinations configured to receive System Errors, even if they are not configured to receive alerts with a CRITICAL severity. They are automatically generated, with the exception of log drop-off alarms which you can configure manually per log source. System Error alerts are visible in your Panther Console within Alerts & Errors > System Errors.

System Errors are also a type of in-app notification in your Panther Console. Learn more about notifications on Notifications and Errors.

How to configure System Error alarms

To ensure that you receive alerts for all types of System Errors:

• Configure an alert destination that is receiving the System Error alert type.

• Configure Log Drop-off alarms for log sources that will trigger an alert when data is no longer being received.

  • Note that you do not need to enable alerts for Log Classification errors, Alert Delivery failure, S3 GetObject errors, and Cloud Security Scanning failure.

Configuring an Alert Destination for System Errors

By default, Panther will send System Errors alerts to the Alerts page in your Panther Console. It is also strongly recommended to configure one of your alert destinations to receive them.

To ensure these alerts are sent to a custom Alert Destination, follow the steps below:

1. Log in to your Panther Console.

2. On the left sidebar navigation, click Configure > Alert Destinations

3. Choose an existing Alert Destination or add a new Alert Destination.

4. On the configuration page for the Alert Destination, add System Errors to the Alert Types section:

Configuring log drop-off alarms for log sources

Panther allows you to set up event threshold alarms for individual log sources, which will trigger an alert if data is not received over a specific time interval.

For example, if you configure the threshold to 15 minutes, then you will receive an alert if no events are processed in 15 minutes.

This can be useful for log sources that have been incorrectly linked to Panther or are experiencing issues outside of Panther.

You can add an alarm to a new or an existing log source:

Add alarm to new log source

Add alarm to existing source

Setting up an alarm for a new log source

1. In the left-hand navigation bar of your Panther Console, click Configure > Log Sources.

2. In the upper-right corner, click Create New.

3. Complete each step of the onboarding workflow.

   • See Data Sources and Transports for specific setup instructions by source.

4. On the success page at the end of the onboarding workflow, the Trigger an alert when no events are processed defaults to YES. Leave this enabled.

   • Enter your desired time period by filling in the Number and Period fields next to How long should Panther wait before it sends you an alert that no events have been processed?.

Setting up an alarm for an existing log source

1. In the left-hand navigation bar of your Panther Console, click Configure > Log Sources.

2. Select the log source to configure an alarm for.

3. On the log source's details page, in the Overview tab, click the pencil icon to the right of the value in the Drop-off Alarm field.

4. In the pop-up window, toggle the Trigger an alert when no events are processed setting to ON.

5. Next to How long should Panther wait before it sends you an alert that no events have been processed? set a Number and Period.

6. Click Apply Changes.

Types of System Errors

Log Source Health alerts

Panther performs health checks on log sources to ensure that Panther is correctly linked to the source, has the right credentials, and is receiving data from the source consistently.

Log drop-off alerts

Panther allows you to set up event threshold alarms for individual log sources, which will trigger an alert if data is not received over a specific time interval. For instructions on enabling these alerts, see the section above: Configuring log drop-off alarms for log sources.

It is not possible to set up a log drop-off alarm for Panther audit logs, when enabled as a log source.

Log Classification alerts

Panther generates a Log Classification alert when incoming logs fail to parse correctly according to the schema(s) attached to their log source. When this happens:

• Logs that failed to classify are sent to the data lake and are searchable in a table called classification_failures in the panther_monitor database.

• An alert is generated immediately after the first log fails to classify. The alert will display all log lines that are failing to classify.

An alert's details page in the Panther Console highlights the log lines that fail to parse correctly, to help you determine which lines in the log type's respective schemas need to be corrected or added.

The alert includes a link to the respective log source's Log Source Ops page where you can view the rate at which events are failing to classify within the Health tab.

Remediating Classification Failures

When one of your log sources receives a Classification Failure, you can remediate it by taking the following steps:

1. If the log source has more than one schema attached, identify which schema failed.

   • You can find this information either on the Health tab of the log source's detail page, or directly from Data Explorer, in a table called classification_failures in the panther_monitor database.

2. Understand why the schema failed to parse the event(s). Common causes for Classification Failures include:

   • A field with required:true didn't exist on some of the incoming data

   • A field has type:string but the actual data received is an object

   • A timestamp field has the wrong format definition

   • The event was of a LogType that was not configured in the source

   • Event was malformed in some other way

3. Update the schema as needed.

4. Resolve the Classification Failure alert by clicking Mark as Resolved.

   
5. On the Reprocess events? pop-up modal that appears, handle the events that failed to classify clicking either:

   • (Beta) Reprocess Events: events that failed classification will be processed again.

     Reclassification of events that failed to initially classify is in open beta starting with Panther version 1.114, and is available to all customers. Please share any bug reports and feature requests with your Panther support team.

     Event reclassification is only possible for events that failed classification within the last 15 days.

     If the Classification Failure alert you are resolving contains both events received within the last 15 days and events older than 15 days, only the former will be reprocessed—the latter will be ignored.

     

     • If reprocessing completes successfully, you will receive a System Notification:

     • If classification fails again, you will receive a new Classification Failure alert.

   • Skip Reprocessing: events that failed classification will not be ingested into Panther.

S3 GetObject Error Notifications

S3 GetObject error alerts generate when Panther fails to fetch S3 objects. When this happens, the following actions take place by default:

• Panther stores the S3 objects in the data lake which can be queried through the Data Explorer in a table titled panther_monitor.data_audit.

• An alert is generated if Panther fails to fetch any S3 object in the last 24 hours. The alert displays the specific S3 objects that are failing.

Alert Delivery Failure

Alert Delivery Failure alerts are generated when Panther fails to deliver an alert to a destination.

If the initial attempt to deliver an alert fails, Panther automatically attempts to re-deliver it. After breaching a certain threshold of alert delivery failures, a system health alert is generated and sent to any alert destinations configured to receive System Error alerts.

Cloud Security Scanning Failure

Cloud Security Scanning Failure alerts are generated when Panther fails to scan a cloud resource because of an "access denied" error.

This occurs when permissions are not configured properly to allow scanning to occur. This is most commonly caused by one of the following scenarios:

• Our scanning role (PantherAuditRole) is not configured with sufficient permissions.

  • This is an extremely rare case as the permissions of this role rarely change. This can be resolved by updating the PantherAuditRole to the latest version.

• An AWS organizations Service Control Policy (SCP) is preventing our scanning role from carrying out scans.

  • Commonly this occurs with SCP's with restrictions for certain regions or services. This can be resolved by either modifying the SCP to add an exception for our scanning role, or by modifying the Cloud Security integration to exclude certain regions or resource types.

• An AWS resource base policy is preventing our scanning role from carrying out scans.

  • In AWS, permissions are bidirectional. The PantherAuditRole may be granted permission to access a resource, but the resource itself may not grant permission to be accessed by our role. This can be resolved by either modifying the resource based policy to add an exception for our scanning role, or by modifying the Cloud Security integration to exclude certain resources or resource types.

The alert will indicate which resource scanning failed on, and the AWS error that caused the scanning to fail:

You can use this information to pinpoint the exact permissions issue. In the example above, we can see no resource-based policy allows the kms:ListResourcetags action. This indicates to us that the issue is related to a resource-based policy.