- Prerequisites for Configuring Exabeam Threat Detection, Investigation & Response (TDIR) Use Case Categories
- Configure Compromised Insiders Use Cases
- Configure External Threats Use Cases
- Configure Malicious Insiders Use Cases
Configure the Compromised Credentials Use Case
Configure Exabeam Security Operations Platform to protect your environment against the Compromised Credentials use case. Ensure that you collect the right data, set up investigation tools, enable response mechanisms, and import relevant Data Lake reports.
To protect against a use case, you might follow an end-to-end workflow that looks like:
Collect – Ensure that you bring in the correct logs for the use case and that all fields populate.
Detect – Use out-of-the-box rules and models to identify suspicious activity.
Investigate – Ask important questions about the data from log sources, rules, and models.
Respond – Isolate, neutralize, eliminate, and mitigate any threats you find.
Report – Gather all the evidence in a report so you can share your investigation with others or use for compliance purposes.
Let's configure everything you need to successfully follow each stage of this workflow.
Collect
Collect the data needed to investigate the Compromised Credentials use case and ensure all context tables are populated correctly.
Ensure that you contacted Exabeam Customer Success and they helped you onboard and validate the log sources needed to implement the Compromised Credentials use case.
Ensure that you have specific out-of-the-box context tables:
web_malicious_categories
is_publicemail_domain
workstations
sourcecode_file_extensions
user_is_executive
user_is_privileged
is_ip_threat
user_employee_type
user_is_executive
is_dynamicdns_domain
is_ranked_domain
reputation_domains
Create custom context tables for domain controllers and critical systems.
Ensure that users and assets have the correct labels based on the context tables. For example, if a user is in the user_is_privileged context table, navigate to the user's profile to verify they have the privileged label.
Detect
Ensure you have all mechanisms in place, like rules, models, watchlists, and Threat Hunter searches, to successfully identify suspicious activity.
Rules and models
Validate out-of-the-box rules and models to ensure you accurately detect anomalous activity.
Import the latest content packages on the Exabeam Community. These content packages contain the latest rules and models, which aren't available to install in Content Updates settings. You must download them from the Exabeam Community, then import them.
Ensure that related rules and models are triggering correctly.
Threat Hunter searches
To quickly search for events that indicate someone's credentials have been compromised create and save the suggested Threat Hunter search queries.
Threat Hunter search | Search criteria |
|---|---|
Service accounts with interactive logons |
|
User's first VPN connection |
|
User, peer group, or organization's first activity from a geolocation |
|
New user agent's first activity |
|
Executive users who logged in from a new geolocation |
|
First time a process launched in the organization |
|
First access to a domain generated from a Domain Generation Algorithm (DGA) |
|
VPN connections from multiple WAN IPs in the last 30 days |
|
Failed logins to an asset that a user has not previously accessed |
|
Abnormal number of denied web activity events for a user |
|
Configure Settings to Search for Data Lake Logs in Advanced Analytics
If you have an on-premises deployment, ensure that you configure certain Advanced Analytics settings so you can search for Data Lake logs from a Smart Timelines™ event.
If you have a cloud-delivered product offering, ensure that you configure Data Lake as a log source.
Investigate
Ensure you have the tools you need, like tasks and incident types, to investigate the evidence you collect from log sources, rules, and models.
Case Manager Incident Type
In Case Manager, ensure that you have the out-of-the-box Compromised Credentials incident type, or create one if it isn't available out-of-the-box in your Exabeam product offering. Ensure the incident type has all corresponding incident fields.
Case Manager Tasks and Phases
In Case Manager, define a clear response plan to ensure everyone across your organization responds to a Compromised Credentials incident consistently. Under each phase, prescribe the relevant tasks for investigating, containing, and remediating a Compromised Credentials incident.
The out-of-the-box Compromised Credentials incident type comes with suggested phases and tasks. If you don't have the out-of-the-box Compromised Credentials incident type, create the following suggested phases and tasks for your custom Compromised Credentials incident type.
Phase: Detection & Analysis
Task name – Review normal activity for the user
Task instruction:
Validate if the user recently changed roles or is involved in a new project.
Validate if the user is on vacation or part of a separation event.
Task name – Identify the anomalous activity
Task instruction:
Determine if the user accessed resources from unexpected locations. Look for anomalous geolocation activity.
Determine if the user accessed resources they don't normally access.
Determine if the user generated activity at times that are not normal for them (User agent/browser/etc.)
Determine if the user accessed applications or functions within applications they don't normally access or use.
Determine how many systems were accessed.
Determine whether the user's peers emulate any similar activity.
Determine if there was any additional anomalous activity, like if the account accessed new applications, triggered security alerts, or exfiltrated data.
Task name – Validate logs were sent to the SIEM
Task instruction – Validate that logs for the impacted users or systems were sent to the SIEM or system of record.
Task name – Assess impacted systems
Task instruction – Determine if the potentially impacted systems are critical business or infrastructure systems.
Task name – Proactively monitor impacted users and systems
Task instruction – Add the systems and users to a watchlist to proactively monitor them.
Phase: Containment
Task name – Tell the SOC Manager about the incident
Task instruction:
If needed, inform your SOC Manager of the incident and include the incident's expected start and end date.
Determine whether additional team members or teams, like HR, Legal, or Physical Security, must get involved.
Task name – Determine adequate response measures to contain the threat
Task instruction:
If appropriate, disable the user account.
Quarantine affected systems.
Force multi-factor authentication (MFA) re-authentication or step-up authentication to the affected user accounts.
Phase: Eradication
Task name – Take measures to preserve logs for impacted systems and users
Task instruction:
Retrieve and preserve all Data Lake logs associated with the user from the expected start to the present.
Upload the Data Lake logs to the incident.
To determine if there's possible nefarious intent, obtain a forensic image of the system or isolate the physical machine from the network.
Task name – Reset all affected credentials
Task instruction – Reset all affected credentials in all systems.
Task name – Re-issue authentication tokens for affected users
Task name – Identify root cause
Task instruction:
Determine whether a social engineering or phishing email was involved.
If a social engineering or phishing email was involved, determine how the team can increase user awareness for and better monitor similar occurrences.
Task name – Determine if there was a technical exploit
Task instruction – If there was a technical exploit, ensure you put a patch or workaround in place.
Task name – Remediate
Task instruction – Manually remove remnants like files, Microsoft registry keys, and autostart services, or re-image the impacted systems using the latest enterprise image and updated software patches.
Phase: Recovery
Task name – Restore functional state of affected assets
Task instructions:
After you re-image or clean the impacted systems, return the machines to users if it's safe to do so.
Ensure you restore the affected applications or network operations.
Task name – Notify affected users
Task instruction – Notify affected users that they were involved in a security incident and their credentials were reset.
Task name – Implement relevant global security measures
Task instruction – Implement any additional security measures to prevent a similar incident from happening.
Phase: Post-Incident Activity
Task name – Update documentation
Task instruction:
Ensure the incident contains documentation of all relevant events and actions taken.
Identify methods to improve the team’s response to future incidents.
Task name – Hold post-mortem meeting
Task instruction:
Meet with your team. Review the incident and lessons learned.
Document and track administrative and technical gaps identified during the incident.
Case Manager Incident Email Communication
To collaborate on an incident with people across your organization, ensure that you configure incident email communication.
Respond
Enable response mechanisms you need to isolate, neutralize, eliminate, and mitigate any threats you find.
In Incident Responder, create triggers for all turnkey playbooks.
Report
To share your investigation with others or for compliance purposes, ensure you have the relevant out-of-the-box Data Lake reports:
Exabeam - File Alert Activity
Exabeam - Insecure Authentication Attempts
Exabeam - IPS and IDS Alert Activity
Exabeam - Object Access Summary
Exabeam - Office 365 Summary
Exabeam - Security Alert Summary - Impacted Hosts
Exabeam - Security Alert Summary - Origin Hosts
Exabeam - Security Alert Summary - Users
Exabeam - Successful Application Logon Activity
Exabeam - Successful Database Logon Activity
Exabeam - User Account Lockout Activity
Exabeam - Vendor Authentication Activity