LogoLogo
Knowledge BaseCommunityRelease NotesRequest Demo
  • Overview
  • Quick Start
    • Onboarding Guide
  • Data Sources & Transports
    • Supported Logs
      • 1Password Logs
      • Apache Logs
      • AppOmni Logs
      • Asana Logs
      • Atlassian Logs
      • Auditd Logs
      • Auth0 Logs
      • AWS Logs
        • AWS ALB
        • AWS Aurora
        • AWS CloudFront
        • AWS CloudTrail
        • AWS CloudWatch
        • AWS Config
        • AWS EKS
        • AWS GuardDuty
        • AWS Security Hub
        • Amazon Security Lake
        • AWS S3
        • AWS Transit Gateway
        • AWS VPC
        • AWS WAF
      • Azure Monitor Logs
      • Bitwarden Logs
      • Box Logs
      • Carbon Black Logs
      • Cisco Umbrella Logs
      • Cloudflare Logs
      • CrowdStrike Logs
        • CrowdStrike Falcon Data Replicator
        • CrowdStrike Event Streams
      • Docker Logs
      • Dropbox Logs
      • Duo Security Logs
      • Envoy Logs
      • Fastly Logs
      • Fluentd Logs
      • GCP Logs
      • GitHub Logs
      • GitLab Logs
      • Google Workspace Logs
      • Heroku Logs
      • Jamf Pro Logs
      • Juniper Logs
      • Lacework Logs
        • Lacework Alert Channel Webhook
        • Lacework Export
      • Material Security Logs
      • Microsoft 365 Logs
      • Microsoft Entra ID Audit Logs
      • Microsoft Graph Logs
      • MongoDB Atlas Logs
      • Netskope Logs
      • Nginx Logs
      • Notion Logs
      • Okta Logs
      • OneLogin Logs
      • Orca Security Logs (Beta)
      • Osquery Logs
      • OSSEC Logs
      • Proofpoint Logs
      • Push Security Logs
      • Rapid7 Logs
      • Salesforce Logs
      • SentinelOne Logs
      • Slack Logs
      • Snowflake Audit Logs (Beta)
      • Snyk Logs
      • Sophos Logs
      • Sublime Security Logs
      • Suricata Logs
      • Sysdig Logs
      • Syslog Logs
      • Tailscale Logs
      • Teleport Logs
      • Tenable Vulnerability Management Logs
      • Thinkst Canary Logs
      • Tines Logs
      • Tracebit Logs
      • Windows Event Logs
      • Wiz Logs
      • Zeek Logs
      • Zendesk Logs
      • Zoom Logs
      • Zscaler Logs
        • Zscaler ZIA
        • Zscaler ZPA
    • Custom Logs
      • Log Schema Reference
      • Transformations
      • Script Log Parser (Beta)
      • Fastmatch Log Parser
      • Regex Log Parser
      • CSV Log Parser
    • Data Transports
      • HTTP Source
      • AWS Sources
        • S3 Source
        • CloudWatch Logs Source
        • SQS Source
          • SNS Source
        • EventBridge
      • Google Cloud Sources
        • Cloud Storage (GCS) Source
        • Pub/Sub Source
      • Azure Blob Storage Source
    • Monitoring Log Sources
    • Ingestion Filters
      • Raw Event Filters
      • Normalized Event Filters (Beta)
    • Data Pipeline Tools
      • Chronosphere Onboarding Guide
      • Cribl Onboarding Guide
      • Fluent Bit Onboarding Guide
        • Fluent Bit Configuration Examples
      • Fluentd Onboarding Guide
        • General log forwarding via Fluentd
        • MacOS System Logs to S3 via Fluentd
        • Syslog to S3 via Fluentd
        • Windows Event Logs to S3 via Fluentd (Legacy)
        • GCP Audit to S3 via Fluentd
      • Observo Onboarding Guide
      • Tarsal Onboarding Guide
    • Tech Partner Log Source Integrations
  • Detections
    • Using Panther-managed Detections
      • Detection Packs
    • Rules and Scheduled Rules
      • Writing Python Detections
        • Python Rule Caching
        • Data Models
        • Global Helper Functions
      • Modifying Detections with Inline Filters (Beta)
      • Derived Detections (Beta)
        • Using Derived Detections to Avoid Merge Conflicts
      • Using the Simple Detection Builder
      • Writing Simple Detections
        • Simple Detection Match Expression Reference
        • Simple Detection Error Codes
    • Correlation Rules (Beta)
      • Correlation Rule Reference
    • PyPanther Detections (Beta)
      • Creating PyPanther Detections
      • Registering, Testing, and Uploading PyPanther Detections
      • Managing PyPanther Detections in the Panther Console
      • PyPanther Detections Style Guide
      • pypanther Library Reference
      • Using the pypanther Command Line Tool
    • Signals
    • Policies
    • Testing
      • Data Replay (Beta)
    • Framework Mapping and MITRE ATT&CK® Matrix
  • Cloud Security Scanning
    • Cloud Resource Attributes
      • AWS
        • ACM Certificate
        • CloudFormation Stack
        • CloudWatch Log Group
        • CloudTrail
        • CloudTrail Meta
        • Config Recorder
        • Config Recorder Meta
        • DynamoDB Table
        • EC2 AMI
        • EC2 Instance
        • EC2 Network ACL
        • EC2 SecurityGroup
        • EC2 Volume
        • EC2 VPC
        • ECS Cluster
        • EKS Cluster
        • ELBV2 Application Load Balancer
        • GuardDuty Detector
        • GuardDuty Detector Meta
        • IAM Group
        • IAM Policy
        • IAM Role
        • IAM Root User
        • IAM User
        • KMS Key
        • Lambda Function
        • Password Policy
        • RDS Instance
        • Redshift Cluster
        • Route 53 Domains
        • Route 53 Hosted Zone
        • S3 Bucket
        • WAF Web ACL
  • Alerts & Destinations
    • Alert Destinations
      • Amazon SNS Destination
      • Amazon SQS Destination
      • Asana Destination
      • Blink Ops Destination
      • Custom Webhook Destination
      • Discord Destination
      • GitHub Destination
      • Google Pub/Sub Destination (Beta)
      • Incident.io Destination
      • Jira Cloud Destination
      • Jira Data Center Destination (Beta)
      • Microsoft Teams Destination
      • Mindflow Destination
      • OpsGenie Destination
      • PagerDuty Destination
      • Rapid7 Destination
      • ServiceNow Destination (Custom Webhook)
      • Slack Bot Destination
      • Slack Destination (Webhook)
      • Splunk Destination (Beta)
      • Tines Destination
      • Torq Destination
    • Assigning and Managing Alerts
      • Managing Alerts in Slack
    • Alert Runbooks
      • Panther-managed Policies Runbooks
        • AWS CloudTrail Is Enabled In All Regions
        • AWS CloudTrail Sending To CloudWatch Logs
        • AWS KMS CMK Key Rotation Is Enabled
        • AWS Application Load Balancer Has Web ACL
        • AWS Access Keys Are Used Every 90 Days
        • AWS Access Keys are Rotated Every 90 Days
        • AWS ACM Certificate Is Not Expired
        • AWS Access Keys not Created During Account Creation
        • AWS CloudTrail Has Log Validation Enabled
        • AWS CloudTrail S3 Bucket Has Access Logging Enabled
        • AWS CloudTrail Logs S3 Bucket Not Publicly Accessible
        • AWS Config Is Enabled for Global Resources
        • AWS DynamoDB Table Has Autoscaling Targets Configured
        • AWS DynamoDB Table Has Autoscaling Enabled
        • AWS DynamoDB Table Has Encryption Enabled
        • AWS EC2 AMI Launched on Approved Host
        • AWS EC2 AMI Launched on Approved Instance Type
        • AWS EC2 AMI Launched With Approved Tenancy
        • AWS EC2 Instance Has Detailed Monitoring Enabled
        • AWS EC2 Instance Is EBS Optimized
        • AWS EC2 Instance Running on Approved AMI
        • AWS EC2 Instance Running on Approved Instance Type
        • AWS EC2 Instance Running in Approved VPC
        • AWS EC2 Instance Running On Approved Host
        • AWS EC2 Instance Running With Approved Tenancy
        • AWS EC2 Instance Volumes Are Encrypted
        • AWS EC2 Volume Is Encrypted
        • AWS GuardDuty is Logging to a Master Account
        • AWS GuardDuty Is Enabled
        • AWS IAM Group Has Users
        • AWS IAM Policy Blocklist Is Respected
        • AWS IAM Policy Does Not Grant Full Administrative Privileges
        • AWS IAM Policy Is Not Assigned Directly To User
        • AWS IAM Policy Role Mapping Is Respected
        • AWS IAM User Has MFA Enabled
        • AWS IAM Password Used Every 90 Days
        • AWS Password Policy Enforces Complexity Guidelines
        • AWS Password Policy Enforces Password Age Limit Of 90 Days Or Less
        • AWS Password Policy Prevents Password Reuse
        • AWS RDS Instance Is Not Publicly Accessible
        • AWS RDS Instance Snapshots Are Not Publicly Accessible
        • AWS RDS Instance Has Storage Encrypted
        • AWS RDS Instance Has Backups Enabled
        • AWS RDS Instance Has High Availability Configured
        • AWS Redshift Cluster Allows Version Upgrades
        • AWS Redshift Cluster Has Encryption Enabled
        • AWS Redshift Cluster Has Logging Enabled
        • AWS Redshift Cluster Has Correct Preferred Maintenance Window
        • AWS Redshift Cluster Has Sufficient Snapshot Retention Period
        • AWS Resource Has Minimum Number of Tags
        • AWS Resource Has Required Tags
        • AWS Root Account Has MFA Enabled
        • AWS Root Account Does Not Have Access Keys
        • AWS S3 Bucket Name Has No Periods
        • AWS S3 Bucket Not Publicly Readable
        • AWS S3 Bucket Not Publicly Writeable
        • AWS S3 Bucket Policy Does Not Use Allow With Not Principal
        • AWS S3 Bucket Policy Enforces Secure Access
        • AWS S3 Bucket Policy Restricts Allowed Actions
        • AWS S3 Bucket Policy Restricts Principal
        • AWS S3 Bucket Has Versioning Enabled
        • AWS S3 Bucket Has Encryption Enabled
        • AWS S3 Bucket Lifecycle Configuration Expires Data
        • AWS S3 Bucket Has Logging Enabled
        • AWS S3 Bucket Has MFA Delete Enabled
        • AWS S3 Bucket Has Public Access Block Enabled
        • AWS Security Group Restricts Ingress On Administrative Ports
        • AWS VPC Default Security Group Restricts All Traffic
        • AWS VPC Flow Logging Enabled
        • AWS WAF Has Correct Rule Ordering
        • AWS CloudTrail Logs Encrypted Using KMS CMK
      • Panther-managed Rules Runbooks
        • AWS CloudTrail Modified
        • AWS Config Service Modified
        • AWS Console Login Failed
        • AWS Console Login Without MFA
        • AWS EC2 Gateway Modified
        • AWS EC2 Network ACL Modified
        • AWS EC2 Route Table Modified
        • AWS EC2 SecurityGroup Modified
        • AWS EC2 VPC Modified
        • AWS IAM Policy Modified
        • AWS KMS CMK Loss
        • AWS Root Activity
        • AWS S3 Bucket Policy Modified
        • AWS Unauthorized API Call
    • Tech Partner Alert Destination Integrations
  • Investigations & Search
    • Search
      • Search Filter Operators
    • Data Explorer
      • Data Explorer SQL Search Examples
        • CloudTrail logs queries
        • GitHub Audit logs queries
        • GuardDuty logs queries
        • Nginx and ALB Access logs queries
        • Okta logs queries
        • S3 Access logs queries
        • VPC logs queries
    • Visualization and Dashboards
      • Custom Dashboards (Beta)
      • Panther-Managed Dashboards
    • Standard Fields
    • Saved and Scheduled Searches
      • Templated Searches
        • Behavioral Analytics and Anomaly Detection Template Macros (Beta)
      • Scheduled Search Examples
    • Search History
    • Data Lakes
      • Snowflake
        • Snowflake Configuration for Optimal Search Performance
      • Athena
  • PantherFlow (Beta)
    • PantherFlow Quick Reference
    • PantherFlow Statements
    • PantherFlow Operators
      • Datatable Operator
      • Extend Operator
      • Join Operator
      • Limit Operator
      • Project Operator
      • Range Operator
      • Sort Operator
      • Search Operator
      • Summarize Operator
      • Union Operator
      • Visualize Operator
      • Where Operator
    • PantherFlow Data Types
    • PantherFlow Expressions
    • PantherFlow Functions
      • Aggregation Functions
      • Date/time Functions
      • String Functions
      • Array Functions
      • Math Functions
      • Control Flow Functions
      • Regular Expression Functions
      • Snowflake Functions
      • Data Type Functions
      • Other Functions
    • PantherFlow Example Queries
      • PantherFlow Examples: Threat Hunting Scenarios
      • PantherFlow Examples: SOC Operations
      • PantherFlow Examples: Panther Audit Logs
  • Enrichment
    • Custom Lookup Tables
      • Creating a GreyNoise Lookup Table
      • Lookup Table Examples
        • Using Lookup Tables: 1Password UUIDs
      • Lookup Table Specification Reference
    • Identity Provider Profiles
      • Okta Profiles
      • Google Workspace Profiles
    • Anomali ThreatStream
    • IPinfo
    • Tor Exit Nodes
    • TrailDiscover (Beta)
  • Panther AI (Beta)
  • System Configuration
    • Role-Based Access Control
    • Identity & Access Integrations
      • Azure Active Directory SSO
      • Duo SSO
      • G Suite SSO
      • Okta SSO
        • Okta SCIM
      • OneLogin SSO
      • Generic SSO
    • Panther Audit Logs
      • Querying and Writing Detections for Panther Audit Logs
      • Panther Audit Log Actions
    • Notifications and Errors (Beta)
      • System Errors
    • Panther Deployment Types
      • SaaS
      • Cloud Connected
        • Configuring Snowflake for Cloud Connected
        • Configuring AWS for Cloud Connected
        • Pre-Deployment Tools
      • Legacy Configurations
        • Snowflake Connected (Legacy)
        • Customer-configured Snowflake Integration (Legacy)
        • Self-Hosted Deployments (Legacy)
          • Runtime Environment
  • Panther Developer Workflows
    • Panther Developer Workflows Overview
    • Using panther-analysis
      • Public Fork
      • Private Clone
      • Panther Analysis Tool
        • Install, Configure, and Authenticate with the Panther Analysis Tool
        • Panther Analysis Tool Commands
        • Managing Lookup Tables and Enrichment Providers with the Panther Analysis Tool
      • CI/CD for Panther Content
        • Deployment Workflows Using Panther Analysis Tool
          • Managing Panther Content via CircleCI
          • Managing Panther Content via GitHub Actions
        • Migrating to a CI/CD Workflow
    • Panther API
      • REST API (Beta)
        • Alerts
        • Alert Comments
        • API Tokens
        • Data Models
        • Globals
        • Log Sources
        • Queries
        • Roles
        • Rules
        • Scheduled Rules
        • Simple Rules
        • Policies
        • Users
      • GraphQL API
        • Alerts & Errors
        • Cloud Account Management
        • Data Lake Queries
        • Log Source Management
        • Metrics
        • Schemas
        • Token Rotation
        • User & Role Management
      • API Playground
    • Terraform
      • Managing AWS S3 Log Sources with Terraform
      • Managing HTTP Log Sources with Terraform
    • pantherlog Tool
    • Converting Sigma Rules
  • Resources
    • Help
      • Operations
      • Security and Privacy
        • Security Without AWS External ID
      • Glossary
      • Legal
    • Panther System Architecture
Powered by GitBook
On this page
  • Overview
  • How to onboard Salesforce logs to Panther
  • Prerequisites
  • Step 1: Create an API User in Salesforce
  • Step 2: Retrieve Security Token from Salesforce API
  • Step 3: Create and assign a new Permission Set in Salesforce
  • Step 4: Create a new Salesforce source in Panther
  • Supported log types
  • Salesforce.Login
  • Salesforce.LoginAs
  • Salesforce.Logout
  • Salesforce.URI

Was this helpful?

  1. Data Sources & Transports
  2. Supported Logs

Salesforce Logs

Panther supports pulling logs directly from Salesforce

PreviousRapid7 LogsNextSentinelOne Logs

Last updated 10 months ago

Was this helpful?

Overview

Support for Salesforce Sandbox environments is in open beta starting with Panther version 1.96, and is available to all customers. Please share any bug reports and feature requests with your Panther support team.

Panther has the ability to fetch logs for the following event types:

Of the Salesforce deployment types, Production, Developer, and Sandbox are supported in Panther. Staging is not supported.

How to onboard Salesforce logs to Panther

Prerequisites

  • Salesforce customers must before onboarding logs to Panther. An additional license may be required for this Salesforce add-on.

  • During , you will choose between pulling events hourly or daily. Hourly pulling requires you to make a request to your Salesforce representative, and is an added cost.

Step 1: Create an API User in Salesforce

In order to create and add permissions to the new user, the is required.

Panther requires a user account with API and Event Log File permissions in order to retrieve Event Monitoring logs.

To create a user:

    • For User License, select "Salesforce."

    • For Profile, select "Read Only."

  1. Complete the user registration process by setting a new password through the link sent to your email.

Step 2: Retrieve Security Token from Salesforce API

Salesforce API access requires username, password, and a credential called a security token.

Step 3: Create and assign a new Permission Set in Salesforce

  1. Click Edit, then check the boxes to enable the following permissions:

    • API Enabled

    • View Event Log Files

Step 4: Create a new Salesforce source in Panther

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

  2. Click Create New.

  3. Select Salesforce from the list of available log sources. Click Start Setup.

  4. On the Configure Source page, fill in the following fields:

    • Name: Enter a descriptive name for the source e.g., Salesforce Logs.

    • Log Types: Choose which log types you would like to monitor.

    • Environment: Choose Production / Developer or Sandbox.

    • Does your Salesforce instance support Daily or Hourly file intervals?: Choose hourly or daily; the interval for which you want files retrieved from Salesforce.

      • Check with your Salesforce admin to determine how your Salesforce instance is configured and which file interval is supported. Hourly event monitoring is only offered per request and purchase, and you would need to contact a Salesforce representative to enable it.

  5. Click Setup.

  6. Enter the credentials of the account that Panther will use to connect to the Salesforce API:

    • Account Username: Enter your Salesforce account username, e.g., panther-logs@mycompany.com.

    • Account Password: Enter your Salesforce account password.

  7. Click Setup. You will be directed to a success screen:

    • The Trigger an alert when no events are processed setting defaults to YES. We recommend leaving this enabled, as you will be alerted if data stops flowing from the log source after a certain period of time. The timeframe is configurable, with a default of 24 hours.

Supported log types

Salesforce.Login

Login events contain details about your org’s user login history.

schema: Salesforce.Login
referenceURL: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_eventlogfile_login.htm
description: 'Login events contain details about your org’s user login history.'
parser:
    csv:
        delimiter: ','
        hasHeader: true
        columns:
            - EVENT_TYPE
            - TIMESTAMP
            - REQUEST_ID
            - ORGANIZATION_ID
            - USER_ID
            - RUN_TIME
            - CPU_TIME
            - URI
            - SESSION_KEY
            - LOGIN_KEY
            - USER_TYPE
            - REQUEST_STATUS
            - DB_TOTAL_TIME
            - BROWSER_TYPE
            - API_TYPE
            - API_VERSION
            - USER_NAME
            - TLS_PROTOCOL
            - CIPHER_SUITE
            - AUTHENTICATION_METHOD_REFERENCE
            - TIMESTAMP_DERIVED
            - USER_ID_DERIVED
            - CLIENT_IP
            - URI_ID_DERIVED
            - LOGIN_STATUS
            - SOURCE_IP
fields:
    - name: EVENT_TYPE
      type: string
      required: true
      validate:
        allow: ['Login']
      description: The type of event. The value is always Login.
    - name: TIMESTAMP
      required: false
      type: timestamp
      timeFormat: '%Y%m%d%H%M%S.%f'
      description: 'The access time of Salesforce services in GMT. For example: 20130715233322.670.'
    - name: REQUEST_ID
      required: false
      type: string
      indicators:
        - trace_id
      description: >-
        The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST_ID. For example: 3nWgxWbDKWWDIk0FKfF5DV.
    - name: ORGANIZATION_ID
      required: true
      type: string
      description: 'The 15-character ID of the organization. For example: 00D000000000123.'
    - name: USER_ID
      required: false
      type: string
      description: >-
        The 15-character ID of the user who’s using Salesforce services through the UI or the API. For example: 00530000009M943
    - name: RUN_TIME
      required: false
      type: bigint
      description: The amount of time that the request took in milliseconds.
    - name: CPU_TIME
      required: false
      type: bigint
      description: >-
        The CPU time in milliseconds used to complete the request. This field indicates the amount of activity taking place in the app server layer.
    - name: URI
      required: false
      type: string
      description: 'The URI of the page that’s receiving the request. For example: /home/home.jsp.'
    - name: SESSION_KEY
      required: false
      type: string
      description: >-
        The user’s unique session ID. You can use this value to identify all user events within a session. When a user logs out and logs in again, a new session is started. For Login Event Type, this field is usually null because the event is captured before a session is created. Example d7DEq/ANa7nNZZVD
    - name: LOGIN_KEY
      required: false
      type: string
      description: >-
        The string that ties together all events in a given user’s login session. It starts with a login event and ends with either a logout event or the user session expiring. For example: GeJCsym5eyvtEK2I.
    - name: REQUEST_STATUS
      required: false
      type: string
      description: >-
        The status of the request for a page view or user interface action. Possible values are:
          S—Success. Salesforce handled the request successfully. If an Apex controller throws an exception, this status is also returned.
          F—Failure. Typically 4xx or 5xx HTTP codes, such as no permission to view page, page took too long to render, page is read-only.
          U—Undefined
          A—Authorization Error
          R—Redirect. Typically a 3xx HTTP code, possibly initiated by an Apex controller in a Visualforce page.
          N—Not Found. 404 error.
    - name: DB_TOTAL_TIME
      required: false
      type: bigint
      description: >-
        The time in nanoseconds for a database round trip. Includes time spent in the JDBC driver, network to the database, and DB_CPU_TIME. Compare this field to CPU_TIME to determine whether performance issues are occurring in the database layer or in your own code.
    - name: BROWSER_TYPE
      required: false
      type: string
      description: >-
        The identifier string returned by the browser used at login. Example values are:
            Go-http-client/1.1
            Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv%3A50.0) Gecko/20100101 Firefox/50.0
            Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36
    - name: API_TYPE
      required: false
      type: string
      description: >-
        The type of API request. Possible values are:
            D—Apex Class
            E—SOAP Enterprise
            I—SOAP Cross Instance
            M—SOAP Metadata
            O—Old SOAP
            P—SOAP Partner
            S—SOAP Apex
            T—SOAP Tooling
            X—XmlRPC
            f—Feed
            l—Live Agent
            p—SOAP ClientSync
    - name: API_VERSION
      required: false
      type: string
      description: 'The version of the API that’s being used. For example: 36.0.'
    - name: USER_NAME
      required: false
      type: string
      description: The username that’s used for login.
      indicators:
        - username
    - name: TLS_PROTOCOL
      required: false
      type: string
      description: 'The TLS protocol used for the login. There are 3 possible values: 1.0, 1.1, 1.2'
    - name: CIPHER_SUITE
      required: false
      type: string
      description: >-
        The TLS cipher suite used for the login. Values are OpenSSL-style cipher suite names, with hyphen delimiters. For more information, see OpenSSL Cryptography and SSL/TLS Toolkit.
    - name: TIMESTAMP_DERIVED
      required: true
      type: timestamp
      timeFormat: rfc3339
      isEventTime: true
      description: >-
        The access time of Salesforce services in ISO8601-compatible format (YYYY-MM-DDTHH:MM:SS.sssZ). For example: 2015-07-27T11:32:59.555Z. Timezone is GMT.
    - name: USER_ID_DERIVED
      required: false
      type: string
      description: >-
        The 18-character case insensitive ID of the user who’s using Salesforce services through the UI or the API. For example: 00590000000I1SNIA0.
    - name: CLIENT_IP
      required: false
      type: string
      indicators:
        - ip
      description: >-
        The IP address of the client that’s using Salesforce services. A Salesforce internal IP (such as a login from Salesforce Workbench or AppExchange) is shown as "Salesforce.com IP". For example: 10.0.0.1.
    - name: URI_ID_DERIVED
      required: false
      type: string
      description: The 18-character case insensitive ID of the URI of the page that’s receiving the request.
    - name: LOGIN_STATUS
      required: false
      type: string
      description: >-
        The status of the login attempt. For successful logins, the value is LOGIN_NO_ERROR. All other values indicate errors or authentication issues. For details, see https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_eventlogfile_login_status.htm
    - name: SOURCE_IP
      required: false
      type: string
      indicators:
        - ip
      description: The source IP of the login request.
    - name: AUTHENTICATION_METHOD_REFERENCE
      type: string
      description: >-
        The authentication method used by a third-party identification provider for an OpenID Connect single sign-on protocol. This field is available in API version 51.0 and later.
    - name: USER_TYPE
      type: string
      description: >-
        The category of user license. Possible values are:
            CsnOnly — Users whose access to the application is limited to Chatter. This user type includes Chatter Free and Chatter moderator users.
            CspLitePortal — CSP Lite Portal license. Users whose access is limited because they’re organization customers and access the application through a customer portal or an Experience Cloud site.
            CustomerSuccess — Customer Success license. Users whose access is limited because they’re organization customers and access the application through a customer portal.
            Guest — Users whose access is limited so that your customers can view and interact with your site without logging in.
            PowerCustomerSuccess — Power Customer Success license. Users whose access is limited because they’re organization customers and access the application through a customer portal. Users with this license type can view and edit data they directly own or data owned by or shared with users below them in the customer portal role hierarchy.
            PowerPartner — Power Partner license. Users whose access is limited because they’re partners and typically access the application through a partner portal or site.
            SelfService — Users whose access is limited because they’re organization customers and access the application through a self-service portal.
            Standard — Standard user license. This user type also includes Salesforce Platform and Salesforce Platform One user licenses, and admins for this org.

Salesforce.LoginAs

Login As events contain details about what a Salesforce admin did while logged in as another user.

schema: Salesforce.LoginAs
referenceURL: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_eventlogfile_loginas.htm
description: 'Login As events contain details about what a Salesforce admin did while logged in as another user.'
parser:
    csv:
        delimiter: ','
        hasHeader: true
        columns:
            - EVENT_TYPE
            - TIMESTAMP
            - REQUEST_ID
            - ORGANIZATION_ID
            - USER_ID
            - RUN_TIME
            - CPU_TIME
            - URI
            - SESSION_KEY
            - LOGIN_KEY
            - DELEGATED_USER_NAME
            - DELEGATED_USER_ID
            - TIMESTAMP_DERIVED
            - USER_ID_DERIVED
            - CLIENT_IP
            - URI_ID_DERIVED
            - DELEGATED_USER_ID_DERIVED
fields:
    - name: EVENT_TYPE
      required: true
      type: string
      validate:
        allow: ['LoginAs']
      description: The type of event. The value is always LoginAs.
    - name: TIMESTAMP
      required: false
      type: timestamp
      timeFormat: '%Y%m%d%H%M%S.%f'
      description: 'The access time of Salesforce services in GMT. For example: 20130715233322.670.'
    - name: REQUEST_ID
      required: false
      type: string
      description: >-
        The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST_ID. For example: 3nWgxWbDKWWDIk0FKfF5DV.
      indicators:
        - trace_id
    - name: ORGANIZATION_ID
      required: true
      type: string
      description: 'The 15-character ID of the organization. For example: 00D000000000123.'
    - name: USER_ID
      required: true
      type: string
      description: >-
        The 15-character ID of the user who’s using Salesforce services through the UI or the API. For example: 00530000009M943
    - name: RUN_TIME
      required: false
      type: bigint
      description: The amount of time that the request took in milliseconds.
    - name: CPU_TIME
      required: false
      type: bigint
      description: >-
        The CPU time in milliseconds used to complete the request. This field indicates the amount of activity taking place in the app server layer.
    - name: URI
      required: false
      type: string
      description: 'The URI of the page that’s receiving the request. For example: /home/home.jsp.'
    - name: SESSION_KEY
      required: false
      type: string
      description: >-
        The user’s unique session ID. You can use this value to identify all user events within a session. When a user logs out and logs in again, a new session is started. For example: d7DEq/ANa7nNZZVD.
    - name: LOGIN_KEY
      required: false
      type: string
      description: >-
        The string that ties together all events in a given user’s login session. It starts with a login event and ends with either a logout event or the user session expiring. For example: GeJCsym5eyvtEK2I.
    - name: DELEGATED_USER_NAME
      required: false
      type: string
      description: >-
        The username of the user who’s using Salesforce services through the UI or API. In this case, the user who’s doing the impersonation.
      indicators:
        - username
    - name: DELEGATED_USER_ID
      required: true
      type: string
      description: >-
        The 15-character ID of the user who’s using Salesforce services through the UI or API. In this case, the user who’s doing the impersonation.
    - name: TIMESTAMP_DERIVED
      required: true
      type: timestamp
      timeFormat: rfc3339
      isEventTime: true
      description: >-
        The access time of Salesforce services in ISO8601-compatible format (YYYY-MM-DDTHH:MM:SS.sssZ). For example: 2015-07-27T11:32:59.555Z. Timezone is GMT.
    - name: USER_ID_DERIVED
      required: false
      type: string
      description: >-
        The 18-character case insensitive ID of the user who’s using Salesforce services through the UI or the API. For example: 00590000000I1SNIA0.
    - name: CLIENT_IP
      required: false
      type: string
      indicators:
        - ip
      description: >-
        The IP address of the client that’s using Salesforce services. A Salesforce internal IP (such as a login from Salesforce Workbench or AppExchange) is shown as "Salesforce.com IP". For example: 10.0.0.1.
    - name: URI_ID_DERIVED
      required: false
      type: string
      description: The 18-character case insensitive ID of the URI of the page that’s receiving the request.
    - name: DELEGATED_USER_ID_DERIVED
      required: false
      type: string
      description: >-
        The 18-character case-insensitive ID of the user who’s using Salesforce services through the UI or API. In this case, the user who’s doing the impersonation.

Salesforce.Logout

Logout events contain details of user logouts.

schema: Salesforce.Logout
referenceURL: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_eventlogfile_logout.htm
description: Logout events contain details of user logouts.
parser:
    csv:
        delimiter: ','
        hasHeader: true
        columns:
            - EVENT_TYPE
            - TIMESTAMP
            - REQUEST_ID
            - ORGANIZATION_ID
            - USER_ID
            - USER_TYPE
            - SESSION_TYPE
            - SESSION_LEVEL
            - BROWSER_TYPE
            - PLATFORM_TYPE
            - RESOLUTION_TYPE
            - APP_TYPE
            - CLIENT_VERSION
            - API_TYPE
            - API_VERSION
            - USER_INITIATED_LOGOUT
            - SESSION_KEY
            - LOGIN_KEY
            - TIMESTAMP_DERIVED
            - USER_ID_DERIVED
            - CLIENT_IP
fields:
    - name: EVENT_TYPE
      required: true
      type: string
      validate:
        allow: ['Logout']
      description: The type of event. The value is always Logout.
    - name: TIMESTAMP
      required: false
      type: timestamp
      timeFormat: '%Y%m%d%H%M%S.%f'
      description: 'The access time of Salesforce services in GMT. For example: 20130715233322.670.'
    - name: REQUEST_ID
      required: false
      type: string
      indicators:
        - trace_id
      description: >-
        The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST_ID. For example: 3nWgxWbDKWWDIk0FKfF5DV.
    - name: ORGANIZATION_ID
      required: true
      type: string
      description: 'The 15-character ID of the organization. For example: 00D000000000123.'
    - name: USER_ID
      required: true
      type: string
      description: >-
        The 15-character ID of the user who’s using Salesforce services through the UI or the API. For example: 00530000009M943
    - name: USER_TYPE
      required: false
      type: string
      description: >-
        The category of user license of the user that logged out. Possible Values:
          A: Automated Process
          b: High Volume Portal
          C: Customer Portal User
          D: External Who
          F: Self-Service
          G: Guest
          L: Package License Manager
          N: Salesforce to Salesforce
          n: CSN Only
          O: Power Custom
          o: Custom
          P: Partner
          p: Customer Portal Manager
          S: Standard
          X: Salesforce Administrator
    - name: SESSION_TYPE
      required: false
      type: string
      description: >-
        The session type that was used when logging out. Possible Values:

          A: API
          I: APIOnlyUser
          N: ChatterNetworks
          Z: ChatterNetworksAPIOnly
          C: Content
          P: OauthApprovalUI
          O: Oauth2
          T: SiteStudio
          R: SitePreview
          S: SubstituteUser
          B: TempContentExchange
          G: TempOauthAccessTokenFrontdoor
          Y: TempVisualforceExchange
          F: TempUIFrontdoor
          U: UI
          E: UserSite
          V: Visualforce
          W: WDC_API
    - name: SESSION_LEVEL
      required: false
      type: string
      description: >-
        The security level of the session that was used when logging out. Possible Values: 1: Standard Session, 2: High-Assurance Session
    - name: BROWSER_TYPE
      required: false
      type: string
      description: >-
        The identifier string returned by the browser used at login. Example values are:
            Go-http-client/1.1
            Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv%3A50.0) Gecko/20100101 Firefox/50.0
            Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36
    - name: PLATFORM_TYPE
      required: false
      type: bigint
      description: >-
        The code for the client platform. If a timeout caused the logout, this field is null. Example Values:
          1000: Windows
          2003: Macintosh/Apple OSX
          5005: Android
          5006: iPhone
          5007: iPad
    - name: RESOLUTION_TYPE
      required: false
      type: float
      description: The screen resolution of the client. If a timeout caused the logout, this field is null.
    - name: APP_TYPE
      required: false
      type: string
      description: >-
        The application type that was in use upon logging out. Example Values:
          1007: SFDC Application
          1014: Chat
          2501: CTI
          2514: OAuth
          3475: SFDC Partner Portal
    - name: CLIENT_VERSION
      required: false
      type: float
      description: The version of the client that was in use upon logging out.
    - name: API_TYPE
      required: false
      type: string
      description: >-
        The type of API request. Possible values are:
            D—Apex Class
            E—SOAP Enterprise
            I—SOAP Cross Instance
            M—SOAP Metadata
            O—Old SOAP
            P—SOAP Partner
            S—SOAP Apex
            T—SOAP Tooling
            X—XmlRPC
            f—Feed
            l—Live Agent
            p—SOAP ClientSync
    - name: API_VERSION
      required: false
      type: string
      description: 'The version of the API that’s being used. For example: 36.0.'
    - name: USER_INITIATED_LOGOUT
      required: false
      type: boolean
      description: >-
        The value is 1 if the user intentionally logged out of the organization by clicking the Logout button. If the user’s session timed out due to inactivity or another implicit logout action, the value is 0.
    - name: SESSION_KEY
      required: false
      type: string
      description: >-
        The user’s unique session ID. You can use this value to identify all user events within a session. When a user logs out and logs in again, a new session is started. For example: d7DEq/ANa7nNZZVD.
    - name: LOGIN_KEY
      required: false
      type: string
      description: >-
        The string that ties together all events in a given user’s login session. It starts with a login event and ends with either a logout event or the user session expiring. For example: GeJCsym5eyvtEK2I.
    - name: TIMESTAMP_DERIVED
      required: true
      type: timestamp
      isEventTime: true
      timeFormat: rfc3339
      description: >-
        The access time of Salesforce services in ISO8601-compatible format (YYYY-MM-DDTHH:MM:SS.sssZ). For example: 2015-07-27T11:32:59.555Z. Timezone is GMT.
    - name: USER_ID_DERIVED
      required: false
      type: string
      description: >-
        The 18-character case insensitive ID of the user who’s using Salesforce services through the UI or the API. For example: 00590000000I1SNIA0.
    - name: CLIENT_IP
      required: false
      type: string
      indicators:
        - ip
      description: >-
        The IP address of the client that’s using Salesforce services. A Salesforce internal IP (such as a login from Salesforce Workbench or AppExchange) is shown as "Salesforce.com IP". For example: 10.0.0.1.

Salesforce.URI

URI events contain details about user interaction with the web browser UI.

schema: Salesforce.URI
referenceURL: https://developer.salesforce.com/docs/atlas.en-us.api.meta/api/sforce_api_objects_eventlogfile_uri.htm
description: 'URI events contain details about user interaction with the web browser UI.'
parser:
    csv:
        delimiter: ','
        hasHeader: true
        columns:
            - EVENT_TYPE
            - TIMESTAMP
            - REQUEST_ID
            - ORGANIZATION_ID
            - USER_ID
            - RUN_TIME
            - CPU_TIME
            - URI
            - SESSION_KEY
            - LOGIN_KEY
            - REQUEST_STATUS
            - DB_TOTAL_TIME
            - DB_BLOCKS
            - DB_CPU_TIME
            - REFERRER_URI
            - TIMESTAMP_DERIVED
            - USER_ID_DERIVED
            - CLIENT_IP
            - URI_ID_DERIVED
            - USER_TYPE
fields:
    - name: EVENT_TYPE
      required: true
      type: string
      validate:
        allow: ['URI']
      description: The type of event. The value is always URI.
    - name: TIMESTAMP
      required: false
      type: timestamp
      timeFormat: '%Y%m%d%H%M%S.%f'
      description: 'The access time of Salesforce services in GMT. For example: 20130715233322.670.'
    - name: REQUEST_ID
      required: false
      type: string
      indicators:
        - trace_id
      description: >-
        The unique ID of a single transaction. A transaction can contain one or more events. Each event in a given transaction has the same REQUEST_ID. For example: 3nWgxWbDKWWDIk0FKfF5DV.
    - name: ORGANIZATION_ID
      required: true
      type: string
      description: 'The 15-character ID of the organization. For example: 00D000000000123.'
    - name: USER_ID
      required: false
      type: string
      description: >-
        The 15-character ID of the user who’s using Salesforce services through the UI or the API. For example: 00530000009M943
    - name: RUN_TIME
      required: false
      type: bigint
      description: 'The amount of time that the request took in milliseconds.'
    - name: CPU_TIME
      required: false
      type: bigint
      description: >-
        The CPU time in milliseconds used to complete the request. This field indicates the amount of activity taking place in the app server layer.
    - name: URI
      required: true
      type: string
      description: >-
        The URI of the page that’s receiving the request. For more granular URI information for Lightning Experience and the Salesforce app, see the Lightning Error, Lightning Interaction, Lightning Page View, and Lightning Performance event types. Examples: /aura (Lightning Experience), /lightning (Lightning Experience and the Salesforce app), /home/home.jsp (Salesforce Classic)
    - name: SESSION_KEY
      required: false
      type: string
      description: >-
        The user’s unique session ID. You can use this value to identify all user events within a session. When a user logs out and logs in again, a new session is started. For Login Event Type, this field is usually null because the event is captured before a session is created. Example d7DEq/ANa7nNZZVD
    - name: LOGIN_KEY
      required: false
      type: string
      description: >-
        The string that ties together all events in a given user’s login session. It starts with a login event and ends with either a logout event or the user session expiring. For example: GeJCsym5eyvtEK2I.
    - name: REQUEST_STATUS
      required: false
      type: string
      description: >-
        The status of the request for a page view or user interface action. Possible values are:
          S—Success. Salesforce handled the request successfully. If an Apex controller throws an exception, this status is also returned.
          F—Failure. Typically 4xx or 5xx HTTP codes, such as no permission to view page, page took too long to render, page is read-only.
          U—Undefined
          A—Authorization Error
          R—Redirect. Typically a 3xx HTTP code, possibly initiated by an Apex controller in a Visualforce page.
          N—Not Found. 404 error.
    - name: DB_TOTAL_TIME
      required: false
      type: bigint
      description: >-
        The time in nanoseconds for a database round trip. Includes time spent in the JDBC driver, network to the database, and DB_CPU_TIME. Compare this field to CPU_TIME to determine whether performance issues are occurring in the database layer or in your own code.
    - name: DB_BLOCKS
      required: false
      type: bigint
      description: >-
        Indicates how much activity is occurring in the database. A high value for this field suggests that adding indexes or filters on your queries would benefit performance.
    - name: DB_CPU_TIME
      required: false
      type: bigint
      description: >-
        The CPU time in milliseconds to complete the request. Indicates the amount of activity taking place in the database layer during the request.
    - name: REFERRER_URI
      required: false
      type: string
      description: The referring URI of the page that’s receiving the request.
    - name: TIMESTAMP_DERIVED
      required: true
      type: timestamp
      timeFormat: rfc3339
      isEventTime: true
      description: >-
        The access time of Salesforce services in ISO8601-compatible format (YYYY-MM-DDTHH:MM:SS.sssZ). For example: 2015-07-27T11:32:59.555Z. Timezone is GMT.
    - name: USER_ID_DERIVED
      required: false
      type: string
      description: >-
        The 18-character case insensitive ID of the user who’s using Salesforce services through the UI or the API. For example: 00590000000I1SNIA0.
    - name: CLIENT_IP
      required: false
      type: string
      indicators:
        - ip
      description: >-
        The IP address of the client that’s using Salesforce services. A Salesforce internal IP (such as a login from Salesforce Workbench or AppExchange) is shown as "Salesforce.com IP". For example: 10.0.0.1.
    - name: URI_ID_DERIVED
      required: false
      type: string
      description: The 18-character case insensitive ID of the URI of the page that’s receiving the request.
    - name: USER_TYPE
      type: string
      description: >-
        The category of user license. Possible values are:
            CsnOnly — Users whose access to the application is limited to Chatter. This user type includes Chatter Free and Chatter moderator users.
            CspLitePortal — CSP Lite Portal license. Users whose access is limited because they’re organization customers and access the application through a customer portal or an Experience Cloud site.
            CustomerSuccess — Customer Success license. Users whose access is limited because they’re organization customers and access the application through a customer portal.
            Guest — Users whose access is limited so that your customers can view and interact with your site without logging in.
            PowerCustomerSuccess — Power Customer Success license. Users whose access is limited because they’re organization customers and access the application through a customer portal. Users with this license type can view and edit data they directly own or data owned by or shared with users below them in the customer portal role hierarchy.
            PowerPartner — Power Partner license. Users whose access is limited because they’re partners and typically access the application through a partner portal or site.
            SelfService — Users whose access is limited because they’re organization customers and access the application through a self-service portal.
            Standard — Standard user license. This user type also includes Salesforce Platform and Salesforce Platform One user licenses, and admins for this org.

We recommend creating a new, dedicated user with the minimum permissions required by Panther. Salesforce requires each user to have a , but the same email address can be included for multiple users. Thus, you can create a Panther-only account without having to manage an additional email address in your organization.

Follow the instructions in the to add a new user.

To request a security token for a new Salesforce user account, follow the instructions . The new security token is sent to the email address in your Salesforce personal settings.

To assign permissions to the new user, you must create a new .

Follow the instructions in Salesforce's to add a new permission set that grants Panther access to the Event Monitoring data via the SOAP/REST API.

On your new Permisson Set's page, click System Permissions:

Assign the Permission Set to the designated user by following the instructions in Salesforce's documentation: .

Security Token: Enter the the that you obtained earlier in this documentation.

You can optionally enable one or more .

Reference:

Reference:

Reference:

Reference:

unique username
Salesforce documentation
in this Salesforce documentation
Permission Set
Create Permission Sets documentation
Assign Permission Sets to a Single User
Detection Packs
Salesforce Documentation on Login Event Types.
Salesforce Documentation on Login As Event Types.
Salesforce Documentation on Logout Event Types.
Salesforce Documentation on URI Event Types.
Salesforce Event Monitoring
Login
LoginAs
Logout
URI
enable Event Monitoring
'Manage Users' permission
setup of your Salesforce source in Panther
Security Token
The success screen reads, "Everything looks good! Panther will now automatically pull & process logs from your account"
The "Trigger an alert when no events are processed" toggle is set to YES. The "How long should Panther wait before it sends you an alert that no events have been processed" setting is set to 1 Day