Update latest docs (#7016)

Author: tradebot-elastic

docs/detections/prebuilt-rules/downloadable-packages/8-19-3/prebuilt-rule-8-19-3-crowdstrike-external-alerts.asciidoc

@@ -0,0 +1,116 @@
+[[prebuilt-rule-8-19-3-crowdstrike-external-alerts]]
+=== CrowdStrike External Alerts
+
+Generates a detection alert for each CrowdStrike alert written to the configured indices. Enabling this rule allows you to immediately begin investigating CrowdStrike alerts in the app.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-crowdstrike.alert-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 1m
+
+*Searches indices from*: now-2m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 1000
+
+*References*: 
+
+* https://docs.elastic.co/en/integrations/crowdstrike
+
+*Tags*: 
+
+* Data Source: CrowdStrike
+* Use Case: Threat Detection
+* Resources: Investigation Guide
+* Promotion: External Alerts
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating CrowdStrike External Alerts*
+
+
+CrowdStrike Falcon is a cloud-native endpoint protection platform that delivers real-time threat detection and response capabilities. The rule captures security alerts generated by Falcon and enables analysts to investigate threats rapidly based on behavioral indicators and threat intelligence.
+
+
+*Possible investigation steps*
+
+
+- Review the associated process, file path, and command line to determine whether the activity is legitimate or suspicious.
+- Investigate the user account and host involved in the alert to validate whether the activity was authorized.
+- Cross-reference the alert with CrowdStrike Falcon console for additional context, including process tree, behavioral tags, and threat intelligence matches.
+- Check for any related alerts from the same host, user, or file hash to identify whether this is part of a larger attack chain.
+- Consult the Crowdstrike investigation guide and resources tagged in the alert for specific guidance on handling similar threats.
+
+
+*False positive analysis*
+
+
+- Alerts involving known and trusted software tools (e.g., remote administration tools) may be false positives. Confirm intent before excluding.
+- Security assessments or penetration testing activities might mimic real threats. Validate the activity with responsible teams.
+- Scheduled jobs, IT scripts, or automation tools may trigger alerts if they behave similarly to malicious code.
+- Review alerts based on detection confidence levels and behavioral scoring to filter out low-confidence or known-benign triggers.
+
+
+*Response and remediation*
+
+
+- Isolate affected endpoints to prevent lateral movement if malicious behavior is confirmed.
+- Quarantine any identified malicious files and block related hashes or domains.
+- Investigate how the threat entered the environment and close any exploited vulnerabilities.
+- Reset credentials for compromised user accounts or escalate to incident response.
+- Review CrowdStrike Falcon policies and detections to fine-tune future alerting and response coverage.
+- Document the findings and update detection logic or exceptions accordingly.
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+*CrowdStrike Alert Integration*
+
+This rule is designed to capture alert events generated by the CrowdStrike integration and promote them as Elastic detection alerts.
+
+To capture CrowdStrike alerts, install and configure the CrowdStrike integration to ingest alert events into the `logs-crowdstrike.alert-*` index pattern.
+
+If this rule is enabled alongside the External Alerts promotion rule (UUID: eb079c62-4481-4d6e-9643-3ca499df7aaa), you may receive duplicate alerts for the same CrowdStrike events. Consider adding a rule exception for the External Alert rule to exclude data_stream.dataset:crowdstrike.alert to avoid receiving duplicate alerts.
+
+
+*Additional notes*
+
+
+For information on troubleshooting the maximum alerts warning please refer to this https://www.elastic.co/guide/en/security/current/alerts-ui-monitor.html#troubleshoot-max-alerts[guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind: alert and data_stream.dataset: crowdstrike.alert
+
+----------------------------------

docs/detections/prebuilt-rules/downloadable-packages/8-19-3/prebuilt-rule-8-19-3-elastic-security-external-alerts.asciidoc

@@ -0,0 +1,118 @@
+[[prebuilt-rule-8-19-3-elastic-security-external-alerts]]
+=== Elastic Security External Alerts
+
+Generates a detection alert for each Elastic Security alert written to the configured indices. Enabling this rule allows you to immediately begin investigating Elastic Security alerts in the app.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-elastic_security.alert-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 1m
+
+*Searches indices from*: now-2m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 1000
+
+*References*: 
+
+* https://docs.elastic.co/en/integrations/elastic_security
+
+*Tags*: 
+
+* Data Source: Elastic Security
+* Use Case: Threat Detection
+* Resources: Investigation Guide
+* Promotion: External Alerts
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+
+*Triage and analysis*
+
+
+
+*Investigating Elastic Security External Alerts*
+
+
+The Elastic Security integration facilitates transferring security alert data from another Elasticsearch instance to your own, enabling threats to be investigated in a centralized manner.
+
+
+*Possible investigation steps*
+
+
+- Correlate the alert with recent activity on the affected endpoint to identify any unusual or suspicious behavior patterns.
+- Check for any additional alerts or logs related to the same endpoint or user to determine if this is part of a broader attack or isolated incident.
+- Investigate the source and destination IP addresses involved in the alert to assess if they are known to be malicious or associated with previous threats.
+- Analyze any files or processes flagged in the alert to determine if they are legitimate or potentially malicious, using threat intelligence sources if necessary.
+- Consult the Elastic Security investigation guide and resources tagged in the alert for specific guidance on handling similar threats.
+
+
+*False positive analysis*
+
+
+- Alerts triggered by routine software updates or patches can be false positives. Review the context of the alert to determine if it aligns with scheduled maintenance activities.
+- Legitimate administrative tools or scripts may trigger alerts. Identify and whitelist these tools if they are verified as non-threatening.
+- Frequent alerts from known safe applications or processes can be excluded by creating exceptions for these specific behaviors in the Elastic Security configuration.
+- Network scanning or monitoring tools used by IT teams might be flagged. Ensure these tools are documented and excluded from triggering alerts if they are part of regular operations.
+- User behavior that is consistent with their role but triggers alerts should be reviewed. If deemed non-malicious, adjust the rule to exclude these specific user actions.
+
+
+*Response and remediation*
+
+
+- Isolate the affected endpoint immediately to prevent lateral movement and further compromise within the network.
+- Analyze the specific alert details to identify the nature of the threat and any associated indicators of compromise (IOCs).
+- Remove or quarantine any malicious files or processes identified by the Elastic Security alert to neutralize the threat.
+- Apply relevant security patches or updates to address any exploited vulnerabilities on the affected endpoint.
+- Conduct a thorough scan of the network to identify any additional endpoints that may have been compromised or are exhibiting similar behavior.
+- Document the incident and escalate to the appropriate security team or management if the threat is part of a larger attack campaign or if additional resources are needed for remediation.
+- Review and update endpoint protection policies and configurations to enhance detection and prevention capabilities against similar threats in the future.
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+*Elastic Security Alert Integration*
+
+This rule is designed to capture alert events generated by the Elastic Security integration and promote them as Elastic detection alerts.
+
+To capture Elastic Security alerts, install and configure the Elastic Security integration to ingest alert events into the `logs-elastic_security.alert-*` index pattern.
+
+If this rule is enabled alongside the External Alerts promotion rule (UUID: eb079c62-4481-4d6e-9643-3ca499df7aaa), you may receive duplicate alerts for the same Elastic Security events. Consider adding a rule exception for the External Alert rule to exclude data_stream.dataset:elastic_security.alert to avoid receiving duplicate alerts.
+
+
+*Additional notes*
+
+
+For information on troubleshooting the maximum alerts warning please refer to this https://www.elastic.co/guide/en/security/current/alerts-ui-monitor.html#troubleshoot-max-alerts[guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind: alert and data_stream.dataset: elastic_security.alert
+
+----------------------------------

docs/detections/prebuilt-rules/downloadable-packages/8-19-3/prebuilt-rule-8-19-3-google-secops-external-alerts.asciidoc

@@ -0,0 +1,116 @@
+[[prebuilt-rule-8-19-3-google-secops-external-alerts]]
+=== Google SecOps External Alerts
+
+Generates a detection alert for each Google SecOps alert written to the configured indices. Enabling this rule allows you to immediately begin investigating Google SecOps alerts in the app.
+
+*Rule type*: query
+
+*Rule indices*: 
+
+* logs-google_secops.alert-*
+
+*Severity*: medium
+
+*Risk score*: 47
+
+*Runs every*: 1m
+
+*Searches indices from*: now-2m ({ref}/common-options.html#date-math[Date Math format], see also <<rule-schedule, `Additional look-back time`>>)
+
+*Maximum alerts per execution*: 1000
+
+*References*: 
+
+* https://docs.elastic.co/en/integrations/google_secops
+
+*Tags*: 
+
+* Data Source: Google SecOps
+* Use Case: Threat Detection
+* Resources: Investigation Guide
+* Promotion: External Alerts
+
+*Version*: 1
+
+*Rule authors*: 
+
+* Elastic
+
+*Rule license*: Elastic License v2
+
+
+==== Investigation guide
+
+
+Triage and analysis
+
+
+*Investigating Google SecOps External Alerts*
+
+
+Google SecOps provides a robust framework for monitoring and managing security operations within cloud environments. The rule leverages specific event identifiers to flag suspicious alerts, enabling analysts to swiftly investigate potential threats and mitigate risks.
+
+
+*Possible investigation steps*
+
+
+- Examine the timeline of events leading up to and following the alert to identify any unusual patterns or activities that may indicate malicious behavior.
+- Cross-reference the alert with other security logs and alerts to determine if it is part of a broader attack pattern or isolated incident.
+- Investigate the source and destination IP addresses involved in the alert to assess their legitimacy and check for any known malicious activity associated with them.
+- Analyze user activity associated with the alert to identify any unauthorized access or privilege escalation attempts.
+- Consult the Google SecOps investigation guide and resources tagged in the alert for specific guidance on handling similar threats.
+
+
+*False positive analysis*
+
+
+- Alerts triggered by routine administrative actions can be false positives. Review the context of the alert to determine if it aligns with known maintenance activities.
+- Automated scripts or tools that interact with Google SecOps may generate alerts. Identify these scripts and consider creating exceptions for their expected behavior.
+- Frequent alerts from specific IP addresses or user accounts that are known to be secure can be excluded by adding them to an allowlist.
+- Alerts resulting from testing or development environments should be reviewed and, if deemed non-threatening, excluded from triggering further alerts.
+- Regularly update and review exception lists to ensure they reflect current non-threatening behaviors and do not inadvertently exclude genuine threats.
+
+
+*Response and remediation*
+
+
+- Immediately isolate affected systems or accounts identified in the Google SecOps alert to prevent further unauthorized access or data exfiltration.
+- Conduct a thorough review of the alert details to identify any compromised credentials or access tokens and reset them promptly.
+- Implement network segmentation or access control measures to limit the spread of potential threats within the environment.
+- Review and update firewall rules and security group settings to block any suspicious IP addresses or domains associated with the alert.
+- Escalate the incident to the security operations center (SOC) or incident response team for further analysis and to determine if additional resources are needed.
+- Document the incident, including all actions taken, and update incident response plans to incorporate lessons learned from this event.
+- Enhance monitoring and detection capabilities by tuning existing alerts and deploying additional rules to detect similar activities in the future.
+
+
+==== Setup
+
+
+
+*Setup*
+
+
+
+*Google SecOps Alert Integration*
+
+This rule is designed to capture alert events generated by the Google SecOps integration and promote them as Elastic detection alerts.
+
+To capture Google SecOps alerts, install and configure the Google SecOps integration to ingest alert events into the `logs-google_secops.alert-*` index pattern.
+
+If this rule is enabled alongside the External Alerts promotion rule (UUID: eb079c62-4481-4d6e-9643-3ca499df7aaa), you may receive duplicate alerts for the same SecOps events. Consider adding a rule exception for the External Alert rule to exclude data_stream.dataset:google_secops.alert to avoid receiving duplicate alerts.
+
+
+*Additional notes*
+
+
+For information on troubleshooting the maximum alerts warning please refer to this https://www.elastic.co/guide/en/security/current/alerts-ui-monitor.html#troubleshoot-max-alerts[guide].
+
+
+==== Rule query
+
+
+[source, js]
+----------------------------------
+event.kind: alert and data_stream.dataset: google_secops.alert
+
+----------------------------------