- Elastic Security: other versions:
- Elastic Security overview
- What’s new
- Get started with Elastic Security
- Elastic Security UI
- Anomaly Detection with Machine Learning
- Detections and Alerts (beta)
- Creating detection rules
- Managing detection rules
- Monitoring and troubleshooting rule executions
- Rule exceptions and value lists
- About building-block rules
- Managing detection alerts
- Tuning prebuilt detection rules
- Prebuilt rule changes per release
- Prebuilt rule reference
- AWS Access Secret in Secrets Manager
- AWS CloudTrail Log Created
- AWS CloudTrail Log Deleted
- AWS CloudTrail Log Suspended
- AWS CloudTrail Log Updated
- AWS CloudWatch Alarm Deletion
- AWS CloudWatch Log Group Deletion
- AWS CloudWatch Log Stream Deletion
- AWS Config Service Tampering
- AWS Configuration Recorder Stopped
- AWS EC2 Encryption Disabled
- AWS EC2 Flow Log Deletion
- AWS EC2 Network Access Control List Creation
- AWS EC2 Network Access Control List Deletion
- AWS EC2 Snapshot Activity
- AWS Execution via System Manager
- AWS GuardDuty Detector Deletion
- AWS IAM Assume Role Policy Update
- AWS IAM Brute Force of Assume Role Policy
- AWS IAM Deactivation of MFA Device
- AWS IAM Group Creation
- AWS IAM Group Deletion
- AWS IAM Password Recovery Requested
- AWS IAM User Addition to Group
- AWS Management Console Root Login
- AWS RDS Cluster Creation
- AWS RDS Cluster Deletion
- AWS RDS Instance/Cluster Stoppage
- AWS Root Login Without MFA
- AWS S3 Bucket Configuration Deletion
- AWS WAF Access Control List Deletion
- AWS WAF Rule or Rule Group Deletion
- Adding Hidden File Attribute via Attrib
- Administrator Privileges Assigned to Okta Group
- Adobe Hijack Persistence
- Adversary Behavior - Detected - Elastic Endpoint Security
- Anomalous Process For a Linux Population
- Anomalous Process For a Windows Population
- Anomalous Windows Process Creation
- Attempt to Create Okta API Token
- Attempt to Deactivate MFA for Okta User Account
- Attempt to Deactivate Okta MFA Rule
- Attempt to Deactivate Okta Policy
- Attempt to Delete Okta Policy
- Attempt to Disable IPTables or Firewall
- Attempt to Disable Syslog Service
- Attempt to Modify Okta MFA Rule
- Attempt to Modify Okta Network Zone
- Attempt to Modify Okta Policy
- Attempt to Reset MFA Factors for Okta User Account
- Attempt to Revoke Okta API Token
- Attempted Bypass of Okta MFA
- Base16 or Base32 Encoding/Decoding Activity
- Base64 Encoding/Decoding Activity
- Bypass UAC via Event Viewer
- Clearing Windows Event Logs
- Command Prompt Network Connection
- Connection to External Network via Telnet
- Connection to Internal Network via Telnet
- Creation of Hidden Files and Directories
- Credential Dumping - Detected - Elastic Endpoint Security
- Credential Dumping - Prevented - Elastic Endpoint Security
- Credential Manipulation - Detected - Elastic Endpoint Security
- Credential Manipulation - Prevented - Elastic Endpoint Security
- DNS Activity to the Internet
- DNS Tunneling
- Delete Volume USN Journal with Fsutil
- Deleting Backup Catalogs with Wbadmin
- Deletion of Bash Command Line History
- Direct Outbound SMB Connection
- Disable Windows Firewall Rules via Netsh
- Elastic Endpoint Security
- Encoding or Decoding Files via CertUtil
- Enumeration of Kernel Modules
- Execution via Regsvcs/Regasm
- Exploit - Detected - Elastic Endpoint Security
- Exploit - Prevented - Elastic Endpoint Security
- External Alerts
- FTP (File Transfer Protocol) Activity to the Internet
- File Deletion via Shred
- File Permission Modification in Writable Directory
- Hex Encoding/Decoding Activity
- Hping Process Activity
- IPSEC NAT Traversal Port Activity
- IRC (Internet Relay Chat) Protocol Activity to the Internet
- Interactive Terminal Spawned via Perl
- Interactive Terminal Spawned via Python
- Kernel Module Removal
- Local Scheduled Task Commands
- Local Service Commands
- Malware - Detected - Elastic Endpoint Security
- Malware - Prevented - Elastic Endpoint Security
- Microsoft Build Engine Loading Windows Credential Libraries
- Microsoft Build Engine Started an Unusual Process
- Microsoft Build Engine Started by a Script Process
- Microsoft Build Engine Started by a System Process
- Microsoft Build Engine Started by an Office Application
- Microsoft Build Engine Using an Alternate Name
- Mknod Process Activity
- Modification of Boot Configuration
- Modification or Removal of an Okta Application Sign-On Policy
- MsBuild Making Network Connections
- Net command via SYSTEM account
- Netcat Network Activity
- Network Connection via Certutil
- Network Connection via Compiled HTML File
- Network Connection via MsXsl
- Network Connection via Mshta
- Network Connection via Regsvr
- Network Connection via Signed Binary
- Network Sniffing via Tcpdump
- Nmap Process Activity
- Nping Process Activity
- Okta Brute Force or Password Spraying Attack
- PPTP (Point to Point Tunneling Protocol) Activity
- Permission Theft - Detected - Elastic Endpoint Security
- Permission Theft - Prevented - Elastic Endpoint Security
- Persistence via Kernel Module Modification
- Possible Okta DoS Attack
- Potential Application Shimming via Sdbinst
- Potential DNS Tunneling via Iodine
- Potential Disabling of SELinux
- Potential Evasion via Filter Manager
- Potential Modification of Accessibility Binaries
- Potential Shell via Web Server
- PowerShell spawning Cmd
- Process Activity via Compiled HTML File
- Process Discovery via Tasklist
- Process Injection - Detected - Elastic Endpoint Security
- Process Injection - Prevented - Elastic Endpoint Security
- Process Injection by the Microsoft Build Engine
- Proxy Port Activity to the Internet
- PsExec Network Connection
- RDP (Remote Desktop Protocol) from the Internet
- RDP (Remote Desktop Protocol) to the Internet
- RPC (Remote Procedure Call) from the Internet
- RPC (Remote Procedure Call) to the Internet
- Ransomware - Detected - Elastic Endpoint Security
- Ransomware - Prevented - Elastic Endpoint Security
- Rare AWS Error Code
- SMB (Windows File Sharing) Activity to the Internet
- SMTP on Port 26/TCP
- SMTP to the Internet
- SQL Traffic to the Internet
- SSH (Secure Shell) from the Internet
- SSH (Secure Shell) to the Internet
- Setgid Bit Set via chmod
- Setuid Bit Set via chmod
- Socat Process Activity
- Spike in AWS Error Messages
- Strace Process Activity
- Sudoers File Modification
- Suspicious Activity Reported by Okta User
- Suspicious MS Office Child Process
- Suspicious MS Outlook Child Process
- Suspicious PDF Reader Child Process
- Suspicious Powershell Script
- Svchost spawning Cmd
- System Shells via Services
- TCP Port 8000 Activity to the Internet
- Telnet Port Activity
- Threat Detected by Okta ThreatInsight
- Tor Activity to the Internet
- Trusted Developer Application Usage
- Unusual AWS Command for a User
- Unusual City For an AWS Command
- Unusual Country For an AWS Command
- Unusual DNS Activity
- Unusual Linux Network Activity
- Unusual Linux Network Port Activity
- Unusual Linux Network Service
- Unusual Linux Username
- Unusual Linux Web Activity
- Unusual Login Activity
- Unusual Network Connection via RunDLL32
- Unusual Network Destination Domain Name
- Unusual Parent-Child Relationship
- Unusual Process Execution - Temp
- Unusual Process For a Linux Host
- Unusual Process For a Windows Host
- Unusual Process Network Connection
- Unusual Web Request
- Unusual Web User Agent
- Unusual Windows Network Activity
- Unusual Windows Path Activity
- Unusual Windows Remote User
- Unusual Windows Service
- Unusual Windows User Privilege Elevation Activity
- Unusual Windows Username
- User Account Creation
- User Discovery via Whoami
- VNC (Virtual Network Computing) from the Internet
- VNC (Virtual Network Computing) to the Internet
- Virtual Machine Fingerprinting
- Volume Shadow Copy Deletion via VssAdmin
- Volume Shadow Copy Deletion via WMIC
- Web Application Suspicious Activity: No User Agent
- Web Application Suspicious Activity: POST Request Declined
- Web Application Suspicious Activity: Unauthorized Method
- Web Application Suspicious Activity: sqlmap User Agent
- Whoami Process Activity
- Windows CryptoAPI Spoofing Vulnerability (CVE-2020-0601 - CurveBall)
- Windows Script Executing PowerShell
- Investigate events
- Cases (beta)
- Elastic Security APIs
- Detections API
- Exceptions API
- Lists API
- Timeline API
- Cases API
- Create case
- Add comment
- Update case
- Update comment
- Find cases
- Get case
- Get all case comments
- Get comment
- Get all case activity
- Get tags
- Get reporters
- Get status
- Delete comment
- Delete all comments
- Delete case
- Set default Elastic Security UI connector
- Update case configurations
- Get current connector
- Find connectors
- Add external details to case
- Actions API (for pushing cases to external systems)
- Elastic Security fields and object schemas
- Enable process analyzer after upgrade
- Release Notes
The SIEM app is now a part of the Elastic Security solution.
Click
here to view SIEM documentation for previous releases.
Configuring external connections
editConfiguring external connections
editYou can push Elastic Security cases to these third-party systems:
- ServiceNow
- Jira (including Jira Service Desk)
- IBM Resilient
To push cases, you need to create a connector, which stores the information required to interface with an external system.
After you have created a connector, you can set Elastic Security cases to automatically close when they are sent to external systems.
To create connectors and send cases to external systems, you need the appropriate license.
Create a new connector
edit-
Go to Security → Cases → Edit external connection.
-
From the
Incident management systemlist, selectAdd new connector. -
Select one of these:
- ServiceNow: To send cases to ServiceNow
- Jira: To send cases to Jira or Jira Service Desk
- IBM Resilient: To send cases to IBM Resilient
-
Fill in the following:
- Connector name: A name for the connector.
- URL: The URL of the external system to which you want to send cases.
- Organization ID (IBM Resilient connectors only): Your organization’s IBM Resilient ID number.
- Username (ServiceNow connectors only): The username of the ServiceNow account used to access the ServiceNow instance.
- Password (ServiceNow connectors only): The password of the ServiceNow account used to access the ServiceNow instance.
- Project key (Jira connectors only): The key of the Jira project to which you are sending cases.
- Email or Username (Jira connectors only): The Jira account’s username or email address.
- API token or Password (Jira connectors only): The API token or password used to authenticate Jira updates.
- API key ID (IBM Resilient connectors only): The API key used to authenticate IBM Resilient updates.
- API key secret (IBM Resilient connectors only): The API key secret used to authenticate IBM Resilient updates.
- Save the connector.
To represent an Elastic Security case in an external system, Elastic Security case fields are mapped as follows:
-
For ServiceNow incidents:
-
Title: Mapped to the ServiceNowShort descriptionfield. When an update to a Security case title is sent to ServiceNow, the existing ServiceNowShort descriptionfield is overwritten. -
Description: Mapped to the ServiceNowDescriptionfield. When an update to a Security case description is sent to ServiceNow, the existing ServiceNowDescriptionfield is overwritten. -
Comments: Mapped to the ServiceNowCommentsfield. When a comment is updated in a Security case, a new comment is added to the ServiceNow incident.
-
-
For Jira issues:
-
Title: Mapped to the JiraSummaryfield. When an update to a Security case title is sent to Jira, the existing JiraSummaryfield is overwritten. -
Description: Mapped to the JiraDescriptionfield. When an update to a Security case description is sent to Jira, the existing JiraDescriptionfield is overwritten. -
Comments: Mapped to the JiraCommentsfield. When a comment is updated in a Security case, a new comment is added to the Jira incident.
-
-
For IBM Resilient issues:
-
Title: Mapped to the IBM ResilientNamefield. When an update to a Security case title is sent to IBM Resilient, the existing IBM ResilientNamefield is overwritten. -
Description: Mapped to the IBM ResilientDescriptionfield. When an update to a Security case description is sent to IBM Resilient, the existing IBM ResilientDescriptionfield is overwritten. -
Comments: Mapped to the IBM ResilientCommentsfield. When a comment is updated in a Security case, a new comment is added to the IBM Resilient incident.
-
Close sent cases automatically
editTo close cases when they are sent to an external system, select Automatically close Security cases when pushing new incident to external system.
Change and update connectors
editYou can create additional connectors, update existing connectors, and change the connector used to send cases to external systems.
You can also configure which connector is used for each case individually (see Open a new case).
-
To change the default connector used to send cases to external systems:
- Go to Security → Cases → Edit external connection.
-
Select the required connector from the
Incident management systemlist.
-
To update an existing connector:
-
Click
Update <connector name>. - Update the connector fields as required.
-
Click
Was this helpful?
Thank you for your feedback.